During troubleshooting, technical support may ask for the Log files for Barracuda RMM. Here are the locations of the Log files, as well as a description of their use.
You can also utilize the Support Diagnostics feature from the Configuration > System Settings > Support Diagnostics page to collect OM application and setup logs with just a few clicks and then download a single zip from the SC.
However, if the OM is in a bad state, the collection from Service Center might fail. However, the tool can still be invaluable when running manually as it will combine most of the application and setup logs for Onsite Manager, Device Manager, and Service Center. It does not yet collect the logs for Mwus.
Barracuda RMM Installation log files
The installation log files for all Barracuda RMM products are located in the following folder, regardless of the systems architecture:
C:\Program Files\Level Platforms\LPISetupLogs
Barracuda RMM Onsite Manager and Device manager log files
|Barracuda RMM 12 SP4 and beyond|
|Barracuda RMM before 12 SP4 or upgrading from earlier versions|
|Contains log output from the MWExpertSystem service. This covers service startup, shutdown, monitoring, and other service activity.|
|Contains activity about MWUS (Integrated patch management), such as patch metadata synchronization and device check-in activity.|
|Contains OMNetworkService activity about remote access connection activity.|
|These logs track access and error activity for the lighttpd.exe used for hosting the local patch cache on Onsite Managers.|
|These logs contain activity about service modules with the Service Module name in place of the *. IE: com.avg.hyperv.txt|
Barracuda RMM Service Center log files
The log files for Service Center are located in the following folder assuming the default installation path is used:
C:\Program Files (x86)\Level Platforms\Service Center\Logs.
|Contains information about the SCMonitor service and other system-wide operations of a particular service center environment. Essentially anything not specific to a VAR will be included in the SCMonitor.txt log. This log also contains information about the startup and shutdown of the Service Center Monitor (SCMonitor) service.|
|Contains information regarding changes or activities within a specific VAR in a service center environment, whether hosted or on-premise. Any activities occurring within a SCData_varname database will be logged in the DefaultVarLog.txt or VarLog associated with a particular VAR. This log also contains information about VAR initialization.|
|Contains information related to communications with the SCMessaging site in IIS. Remote Access connection activity will be held in SCMessaging to name an example.|
|Contains information and messages related to the Service Center web page. User Interface errors for example, will likely appear in the SCWeb.txt log|
|Contains activity about Patch Metadata synchronization and failures.|
|Contains activity related to individual service module plugins that may be loaded in a service center VAR. The log file name will include the Service Module name in place of the *. IE: DefaultVar_com.avg.hypervLog.txt|
To run the MWDiagnosticCollector on an Onsite Manager or Device Manager
If you require the logs to be sent to Support, please visit this article.