Description
Collect Persistent Agent debug logging in macOS for troubleshooting purposes.
Scope
FortiNAC.
Solution
Enable Logging
Agent Version 3.0.x - 3.4.x
Perform the below commands from a terminal window on the end station:
1. Confirm owner of com.bradfordnetworks.agent.plist. In order to make any changes to the plist file, the owner must be the logged in user:
la -l
2. Stop the PA Service:
sudo launchctl unload /Library/LaunchDaemons/com.bradfordnetworks.agent.plist
3. Enable the logging properties:
sudo defaults write /Library/LaunchDaemons/com.bradfordnetworks.agent.plist StandardOutPath -string "/var/log/bndaemon.log"
sudo defaults write /Library/LaunchDaemons/com.bradfordnetworks.agent.plist StandardErrorPath -string "/var/log/bndaemon.error.log"
4. Start the PA Service:
sudo launchctl load /Library/LaunchDaemons/com.bradfordnetworks.agent.plist
Agent Version 3.5 and Higher
Logging is enabled by default.
Collect Logs and Submit to Support
One of the following sets of log files are created (dependent upon agent version):
Agent 3.x and 4.x:
/var/log/bndaemon_stdout.txt
/var/log/bndaemon_stderr.txt
/var/log/bndaemon.error.log
/var/log/bndaemon.log
Agent 5.x:
/var/log/bndaemon.error.log
/var/log/syslog
Attach the log files to the ticket. Upon submission, add a case comment with the following information:
- Details regarding the symptoms experienced, including any error messages.
- Steps were taken that resulted in the symptom.
Related articles
Technical Note: Troubleshooting the Persistent Agent
Troubleshooting Tip: Windows Persistent Agent logs
