Jamf Connect Logs
You can collect logs from Jamf Connect using Terminal or Console to help you troubleshoot issues with Jamf Connect in your environment.
Login Window Logs and Debugging
You can collect logs from the Jamf Connect login window 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 loginwindow mechanisms.
Alternatively, you can filter with the com.jamf.connect.login
subsystem. The most recent logs on the computer are stored in the following location: /private/tmp/jamf_login.log
To debug the login process, use secure shell (SSH) to access the computer and execute any of the following common commands:
Command | Output |
---|---|
| Outputs all historical logs to a file. |
| Output recent logs to a file. This example collects logs from the last 30 minutes. |
| Streams current logs in Terminal |
Remote Login must be enabled on the computer to use SSH.
To stop logging, press Control-C.
Menu Bar App Logs and Debugging
You can run the menu bar app in verbose mode and collect logs to help troubleshoot issues.
For increased log levels, you can download and install the debug logging configuration profile from the Jamf Connect DMG. While installed, Jamf Connect logs include more detailed error messages.
You can use any of the following common commands to collect logs from the Jamf Connect menu bar app.
Command |
Output |
---|---|
|
Outputs all historical logs to a file. |
|
Output recent logs to a file. This example collects logs from the last 30 minutes. |
|
Streams current logs in Terminal |
Logs in Console Application
You can use the Console app to view Jamf Connect logs. To view all logs related to Jamf Connect, enter the process Jamf Connect in the search field.
To view logs by subsystem, enter one of the following subsystems in the search field:
com.jamf.connect
com.jamf.connect.login
