Created on
10-01-2018
08:05 AM
Edited on
01-21-2025
01:22 AM
By
Anthony_E
Description
This article describes how to collect Persistent Agent debug logging in macOS for troubleshooting purposes.
Scope
FortiNAC, Persistent Agent Version 3.0.x - 3.4.x
Solution
la -l
sudo launchctl unload /Library/LaunchDaemons/com.bradfordnetworks.agent.plist
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"
sudo launchctl load /Library/LaunchDaemons/com.bradfordnetworks.agent.plist
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:
Related articles:
Technical Tip: Troubleshooting the Persistent Agent
Troubleshooting Tip: Windows Persistent Agent logs
The Fortinet Security Fabric brings together the concepts of convergence and consolidation to provide comprehensive cybersecurity protection for all users, devices, and applications and across all network edges.
Copyright 2025 Fortinet, Inc. All Rights Reserved.