Overview ✨
Liongard Agent logs are typically stored in the Liongard Agent installation directory on the endpoint. These logs are one of the first places to check when troubleshooting connectivity issues, job failures, update problems, installation errors, or unexpected agent behavior.
This article covers where to find Liongard Agent logs on Windows, Linux, and macOS, along with how to use Windows Event Viewer to find service-related events.
Windows Agent 💻
Log Location
Current versions of the Liongard Windows Agent use a single consolidated log file:
C:\Program Files (x86)\LiongardInc\LiongardAgent\logs\agent.log
The agent.log file contains all primary agent activity, including:
Heartbeat and connectivity events
Inspector and job execution activity
Agent startup and shutdown events
Error and warning messages
General runtime and troubleshooting information
This should be the first log reviewed when troubleshooting agent-related issues.
How to Access the Logs
1️⃣ Using PowerShell
Open PowerShell as Administrator and use the following commands:
View the latest agent activity:
Get-Content "C:\Program Files (x86)\LiongardInc\LiongardAgent\logs\agent.log" -Tail 50
Monitor the log in real time:
Get-Content "C:\Program Files (x86)\LiongardInc\LiongardAgent\logs\agent.log" -Wait -Tail 100
Search the log for errors:
Select-String -Path "C:\Program Files (x86)\LiongardInc\LiongardAgent\logs\agent.log" -Pattern "error" -CaseSensitive:$false
2️⃣ Using File Explorer
Press Win + E to open File Explorer.
Browse to:
C:\Program Files (x86)\LiongardInc\LiongardAgent\logs
Open agent.log using Notepad or your preferred text editor.
3️⃣ Windows Event Viewer
If the agent installation does not complete successfully and the log files are not present, review Windows Event Viewer.
Press Win + R.
Type
eventvwr.mscand press Enter.Review the following locations:
Application and Service Logs > LiongardAgentLogs
Look for:
Liongard Agent events
Errors and warnings
Service failures
MSIInstaller events related to installation failures
Quick Troubleshooting Checklist
1. Review agent.log for heartbeat activity, warnings, and errors
2. Verify the Liongard Agent service is running
Get-Service roaragent, LiongardAgentSVC
3. Restart the service if necessary and monitor the log in real time
Get-Content "C:\Program Files (x86)\LiongardInc\LiongardAgent\logs\agent.log" -Wait -Tail 100
4. Check Windows Event Viewer for Liongard Agent or MSIInstaller events
Linux Agent 🐧
Primary log locations
For Linux agents, the main logs are typically located in:
/opt/liongard/logs/
Common log files include:
Log File | Purpose |
| Confirms whether the agent is successfully communicating with the Liongard platform. Check this first when investigating connectivity issues. |
| Contains agent errors, failures, and exceptions encountered during operation. |
| Provides detailed troubleshooting information, inspector execution details, and verbose logging useful for advanced diagnostics. |
| Contains information related to agent updates, update failures, and upgrade activity. |
PM2 Logs
Many Linux deployments run the Liongard Agent through PM2. To identify the exact PM2 log locations, run:
pm2 show roar-agent
Common PM2 log files include:
Log File | Purpose |
| Standard application output generated by the agent process. |
| Process startup failures, runtime errors, and unexpected exceptions. |
Typical locations:
/home/$USER/.pm2/logs/roar-agent-out.log
/home/$USER/.pm2/logs/roar-agent-error.log
System Service Logs
For service-level troubleshooting, review the system journal:
journalctl -u liongard-agent.service
These logs can help identify:
Service startup failures
Unexpected service restarts
Permission issues
Resource constraints
Operating system level errors affecting the agent
How to Access the Logs
1️⃣ Via Terminal (SSH or Local Console)
Connect to the Linux host:
ssh username@<host-ip>
Navigate to the Liongard log directory:
cd /opt/liongard/logs
View available log files:
ls -la
View a specific log:
cat heartbeat.log
cat error.log
cat debug.log
cat updater.log
View the most recent entries:
tail -n 100 heartbeat.log
tail -n 100 error.log
Monitor logs in real time:
tail -f heartbeat.log
tail -f debug.log
2️⃣ Accessing PM2 Logs
To determine the exact PM2 log locations:
pm2 show roar-agent
View PM2 logs:
pm2 logs roar-agent
Or open the files directly:
cat /home/$USER/.pm2/logs/roar-agent-out.log
cat /home/$USER/.pm2/logs/roar-agent-error.log
3️⃣ Accessing Service Logs
Review service-level events:
journalctl -u liongard-agent.service
Recent entries only:
journalctl -u liongard-agent.service --since "1 hour ago"
4️⃣ Useful Log Searches
Search for errors:
grep -i error /opt/liongard/logs/*.log
Search for warnings:
grep -i warning /opt/liongard/logs/*.log
What to Check First
When troubleshooting a Linux Agent:
Review heartbeat.log to verify communication with Liongard.
Check error.log for any obvious failures.
Review debug.log for inspector execution issues.
Check updater.log if the issue appears after an upgrade.
Review PM2 and system service logs if the agent is failing to start or stopping unexpectedly.
macOS Agent🍎
Primary Log Locations
The primary Liongard Agent logs on macOS are located in:
/Library/Liongard/logs/
Common log files include:
Log File | Purpose |
| Confirms communication between the Mac Agent and the Liongard platform. |
| Contains errors encountered by the agent during operation. |
| Detailed troubleshooting and diagnostic information, including inspector execution details. |
| Records agent update activity and update-related failures. |
Additional files may also be useful during troubleshooting:
Log File | Purpose |
| General agent activity, status information, and runtime events. |
| Logging subsystem errors. This file should normally be empty. |
| Installation log used when troubleshooting installation failures. |
| macOS crash and diagnostic reports generated when the agent crashes or becomes unresponsive. |
Crash and Diagnostic Reports
If the agent is unexpectedly stopping, crashing, or becoming unresponsive, review:
/Library/Logs/DiagnosticReports/
Look for:
Liongard-related crash reports
Segmentation faults
Resource exhaustion events
Application termination messages
Installation Troubleshooting
If the issue occurs during installation, review:
cat /tmp/liongard-agent-installer.log
This log often contains details about:
Package installation failures
Permission issues
Invalid configuration values
Dependency-related problems
How to Access the Logs
1️⃣ Via Terminal
Open Terminal from:
Applications → Utilities → Terminal
Navigate to the Liongard log directory:
cd /Library/Liongard/logs
View available log files:
ls -la
View a specific log:
cat heartbeat.log
cat error.log
cat debug.log
cat updater.log
View recent log entries:
tail -n 100 heartbeat.log
tail -n 100 error.log
Monitor a log in real time:
tail -f agent.log
Check the logger error file:
cat loggerError.log
2️⃣ Via Finder (GUI)
Open Finder.
Press Cmd + Shift + G.
Enter:
/Library/Liongard/logs
Click Go.
Open the desired log file using TextEdit or another text editor.
3️⃣ Accessing Crash Reports
Open Finder.
Press Cmd + Shift + G and browse to:
/Library/Logs/DiagnosticReports/
Or use Terminal:
ls /Library/Logs/DiagnosticReports/
Open a report:
cat /Library/Logs/DiagnosticReports/<filename>
4️⃣ Accessing Installation Logs
If the issue occurs during installation:
cat /tmp/liongard-agent-installer.log
Useful Log Searches
Search for errors:
grep -i error *.log
Search for heartbeat activity:
grep -i heartbeat *.log
What to Check First
When troubleshooting a macOS Agent:
Review heartbeat.log to confirm communication with Liongard.
Check error.log for reported failures.
Review debug.log for detailed diagnostics.
Check updater.log if the issue began after an update.
Review loggerError.log for logging-related problems.
Check DiagnosticReports if the agent appears to be crashing.
Review the installer log if the problem occurs during installation.
Summary 🦁
Liongard Agent logs are usually found in the agent installation directory. For Windows, also check Windows Event Viewer for service, application, and installer-related events. For Linux and macOS, the main agent logs are stored locally on the machine and can be reviewed directly from the terminal or file system.
When troubleshooting, start with the heartbeat log, then review error and debug logs, and finally check service-level or system-level events if the issue is not obvious.