Unimus writes log files to the following directories:
Linux: /var/log/unimus Windows: C:\ProgramData\Unimus\log |
Depending on the deployment type, you will find either the unimus.log file (for the Unimus Server) or the unimus-core.log file (for Remote Core deployments) in these directories.
In cases where Unimus fails to start correctly, or when there's an issue with the connection between the Server and a Core, checking the log file should be the first step in troubleshooting.
The Unimus log file contains detailed information about the following:
System events – Unimus Server and Core startup events, communication between the Unimus Server and Core, log level changes (e.g., enabling/disabling debug mode)
Database operations – Connections to the database, schema updates
Unimus system setting changes – Notification settings, schedules, user management, device credential updates, etc.
Tag and zone management – Creation, modification, and deletion of tags and zones
Job events – Device discovery, configuration backups, mass config pushes, network scans, configuration searches
Device CLI accesses
Connections to NMS systems (NMS Sync)
Incoming API requests
For advanced troubleshooting, you can enable Debug Logging and/or Device Output Logging.
Navigate to the Zones menu.
Click the expander arrow on the right side of the Zone you want to debug.
3. Click the Debug Mode button, then enable:
Debug Logging
Device Output Logging