fleet/articles/fleet-troubleshooting-for-it-admins.md

Fleet troubleshooting for IT admins

It would be great if computers always performed flawlessly, but sometimes errors occur. When things go wrong, digging into logs is one of the first steps to resolving an issue.

Finding fleetd logs

Fleetd will send stdout/stderr logs to the following directories:

• macOS: /var/log/orbit/orbit.std{out|err}.log.
• Windows: C:\Windows\system32\config\systemprofile\AppData\Local\FleetDM\Orbit\Logs\orbit-osquery.log (the log file is rotated).
• Linux: Orbit and osqueryd stdout/stderr output is sent to syslog (/var/log/syslog on Debian systems, /var/log/messages on CentOS, and journalctl -u orbit on Fedora).

If the logger_path agent configuration is set to filesystem, fleetd will send osquery's "result" and "status" logs to the following directories:

• macOS: /opt/orbit/osquery_log
• Windows: C:\Program Files\Orbit\osquery_log
• Linux: /opt/orbit/osquery_log

The Fleet Desktop log files can be found in the following directories depending on the platform:

• macOS: $HOME/Library/Logs/Fleet
• Windows: %LocalAppData%/Fleet
• Linux: $XDG_STATE_HOME/Fleet or $HOME/.local/state/Fleet

The log file name is fleet-desktop.log.

Enabling debug mode for fleetd

Debug mode can be helpful by providing more information in the logs.

When generating an installer package with fleetctl package, add the --debug argument to enable debug mode for the agent installer.

If you've already installed Fleet on the device, you can run a script on macOS or Windows devices to turn on debug mode. After you're done, run the script again to disable debug mode on the device.

Checking MDM commands

If you suspect something went wrong with an MDM command for a device (such as locking, wiping, installing an app, etc.), you can use the UI or API to view the MDM command results.

For the UI, open the host details page and under Activity toggle the switch for Show MDM commands.

Hover over the command you'd like to view, and select the "i" button.

For the API, use the List MDM commands endpoint to find the command_uuid for the command. Use this UUID with the Get MDM command results endpoint. The result of this looks like a random string of characters, but this is because it's base64 encoded. A quick way to decode this is on a Mac is to copy the long string, then decode it in the Terminal:

pbpaste | base64 -d

MDM troubleshooting

Fleet's MDM software engineering team has created a resource they use for MDM support escalations. The MDM troubleshooting checklist lives as a plain-text document in the public Fleet GitHub repository so that anyone can keep it up-to-date as needed.

Server-side logs

Use fleetctl to see server logs.

fleetctl debug errors