Logging Jamf Connect Login
You can view logs from Jamf Connect Login with the Console application or using the log command in Terminal. When capturing logs, you can filter on all logs from the Security Agent process, which runs all of the Jamf Connect Login mechanisms. Alternatively, you can filter the com.jamf.connect.login subsystem. The most recent login on the computer is stored in the following location: /private/tmp/jamf_login.log
To debug the log in process, use secure shell (SSH) to access the computer and execute following command:
log stream --predicate 'subsystem == "com.jamf.connect.login"' --debug
Note: Remote Login must be enabled on the computer to use SSH.
To stop logging, press control-C.
You can also execute the log show command to view logs after the user login process completes:
log show --predicate 'subsystem == "com.jamf.connect"' --debug
For more information see the Collecting Logs in Jamf Connect Login Knowledge Base article.
Logging Jamf Connect Sync or Verify
You can troubleshoot Jamf Connect Sync or Verify by running it in verbose mode and capturing the logs. Verbose mode is used by running the app from the command line with the -v flag. You can run multiple copies of Jamf Connect at the same time by running an additional copy of the software instead of unloading a launch agent. The following command runs Jamf Connect Sync or Verify in verbose mode:
Jamf Connect Sync
/Applications/Jamf\ Connect\ Sync.app/Contents/MacOS/Jamf\ Connect\ Sync -v
Jamf Connect Verify
/Applications/Jamf\ Connect\ Verify.app/Contents/MacOS/Jamf\ Connect\ Verify -v
You can also add the -prefs flag to have all of the current preferences displayed in the command line output. Preferences set with a configuration profile are specified as “Forced”.