Collecting crash dumps AGENTS WINDOWS Minidumps Collect .dmp files from C:\ProgramData\Resilio\Connect Agent Full memory dump 1. Stop Resilio Connect Agent service and exit UI agent. 2. Create .reg file and apply its settings: Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\Windows Error Reporting\LocalDumps\Resilio Connect Agent.exe] "DumpFolder"="C:\\Dumps" "DumpType"=dword:00000002 "DumpCount"=dword:00000002 3. Create C:\Dumps (the directory mentioned in .reg file above) 4. Start the service and wait for it to crash 5. Collect dumps from C:\Dumps and new minidumps in C:\Programdata\Resilio\Connect Agent Alternatively, you can set the environment variable RESILIO_SYNC_BIG_DUMP to 1. Note that you should add it to both the User and System sections to cover the case when the agent is started by a user or the Local System. If not specified by DumpFolder in Registry, a full dump will be put in the agent's storage folder. LINUX Minidumps Collect dmp files from agent's storage folder Core dump 1. In Terminal run command ulimit -c unlimited. 2. From this Terminal window start the Agent the way you usually do. 3. When the Agent crashes, there should be a crash dump placed beside rslagent binary. It will be a file with digits in its name. NOTE: if you launch the Agent at startup via a startup script, dump will be placed in another directory, depending on your script, being most likely file system root. If you can’t find coredump at the base (current) directory, refer to http://sigquit.wordpress.com/2009/03/13/the-core-pattern/. OS X Minidumps Collect dmp files from /Users/<user_name>/Library/Application Support/Resilio Connect Agent”. OS X crash reports are located at /Users/<user_name>/Library/Logs/DiagnosticReports/ -- they would be files whose names start with "Resilio Connect...". Related articles Manually collect debug logs from Resilio Connect Possible errors for SMTP connection Agents package installation on Linux Aborting a job run on an error Profiling Resilio agent