Repository navigation
Troubleshooting
Confirm jamJAR is installed and check its version:
/usr/local/munki/jamJAR --version
No output or a "command not found" error means the binary is missing or not executable. Verify it exists at /usr/local/munki/jamJAR with permissions root:wheel 755.
jamJAR logs to a fixed path:
/var/log/jamJAR.log
Log entry format:
YYYY-MM-DD HH:MM:SS +0000 ~ LEVEL: message
Example:
2026-01-01 10:00:00 +0000 ~ INFO: 1 installed, 0 uninstalled, 0 installs pending, 0 uninstalls pending
The log rotates at 10 MB. No archive is kept — save a copy before rotation if you need to retain it.
To gather all relevant logs into a single directory for sharing or escalation, run:
sudo /usr/local/munki/jamJAR --collect-logs
This copies the following to /Users/Shared/jamJAR Logs/:
| File | Contents |
|---|---|
/var/log/jamJAR.log |
jamJAR log |
/var/log/jamf.log |
Jamf Pro agent log |
/var/log/install.log |
macOS installer log |
/Library/Managed Installs/Logs/ManagedSoftwareUpdate.log |
Munki log |
Logging verbosity can be increased by passing a value to $9 of the policy script to enable verbose_mode
If the policy log shows an error from jamJAR.sh:
| Error message | Cause | Fix |
|---|---|---|
ERROR: This script must be run as root |
Policy not running as root | Ensure the Jamf policy runs as root |
ERROR: /usr/local/munki/jamJAR not found |
Binary missing | Re-deploy the jamJAR package |
ERROR: Nothing assigned to $4 - $7 |
No parameters set in the policy | Set at least one of $4–$7 in the policy script parameters |
ERROR: Failed to retrieve version from /usr/local/munki/jamJAR |
Binary not executable or corrupt | Check permissions; re-deploy if needed |
To reset all jamJAR and Munki preferences, manifests, and logs to defaults:
sudo /usr/local/munki/jamJAR --reset
Warning: This removes the LocalOnlyManifest and clears all pending installs and uninstalls. Use only when troubleshooting a broken state.