Support Forum
The Forums are a place to find answers on a range of Fortinet products from peers and product experts.
PE1
New Contributor II

FortiNac Persistant agent - log files Mac do they exist?

Hi there, log files Mac do they exist? I have problems losing connection with Wifi. Is FortNac creating log files 

10 REPLIES 10
adambomb1219
SuperUser
SuperUser

So you are having posture issues once connecting?  Or you can't even join the WiFi?  What do the FortiNAC logs say?  Does it receive the posture status of the endpoint at all?  Is this just one client or multiple?  What version of FortiNAC?

AEK
SuperUser
SuperUser

It is not certain that it is caused by FortiNAC. You may also check the logs on the WiFi controller.

On FNAC you can access to logs via menu Logs > Events & Alarms.

AEK
AEK
PE1
New Contributor II

The problem is that Mac's are losing their connection with Wifi. Push an Profile with Jamf all settings ,so it works, and random Macbooks  lose the connection some times (the SSID is not visible anymore) solution is to remove the profile and push the profile again and Wifi is working again (SSID is visible)

Persistant agent is version 10.7.2.13

PE1
New Contributor II

so I was hoping that the Persistant agent had its own log file to see what is happening. (and not the Wifi.log from Mac it self (no info)

AEK

AEK
ebilcari
Staff
Staff

You can refer to this article that shows where you can find the agent logs in the end host for every OS.

- Emirjon
If you have found a solution, please like and accept it to make it easily accessible for others.
PE1
New Contributor II

Thanks for your article @ebilcari but with version 10 Fortinac dont write into 

On MacOS hosts (Agent version 10.x):

 

/var/log/bndaemon.error.log

/var/log/syslog

Or do i need to activate it first in what @AEK mention first ?

ebilcari

No need to activate them as I know. I did a quick internal check and it seems that there was a recent change, the logs now are moved to 'bndaemon.log'.

- Emirjon
If you have found a solution, please like and accept it to make it easily accessible for others.
PE1
New Contributor II

sudo launchctl unload /Library/LaunchDaemons/com.bradfordnetworks.agent.plist

 

  1. 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"

  1. Start the PA Service:

 

sudo launchctl load /Library/LaunchDaemons/com.bradfordnetworks.agent.plist

works for me now

 

Announcements
Check out our Community Chatter Blog! Click here to get involved
Labels
Top Kudoed Authors