Skip to main content

Understanding Jamf Auto Update's Log Messages

  • Updated

Overview

The below messages will either be returned by Jamf Auto Update’s extension attribute, within a Jamf Auto Update policies log within Jamf Pro as well as the Jamf Auto Update’s log file, which can be found at the below location:

/var/log/JamfAutoUpdate.log

See below for Jamf Auto Update’s more pertinent log messages :

Level Message Reason
ERROR Script result: sh:/Library/Application Support/JAMF/tmp/Jamf Auto Update.py: /usr/local/munki/munki-python: bad interpreter: No such file or directory

If running Jamf Auto Update 1.5, please see this article.

Jamf Auto Update was not installed at the time an Jamf Auto Update policy was run on the device.


Verify that Jamf Auto Update is installed and then run the policy again, if the issue persists raise a new support incident by visiting: https://support.datajar.co.uk/hc/en-us/requests/new.
ERROR Failed to process the returned JWT, run terminated.  The returned JWT was malformed.
Run Jamf Auto Update on the device again, and if the issue persists raise a new support incident by visiting: https://support.datajar.co.uk/hc/en-us/requests/new.
ERROR Terminating run due to encountering error: <error message>  Run Jamf Auto Update on the device again, and if the issue persists raise a new support incident by visiting: https://support.datajar.co.uk/hc/en-us/requests/new
INFO <x> installed, <x> uninstalled, <x> installs pending, <x> uninstalls pending Summary of the prior Jamf Auto Update run.
Where <x> will either be 0 or the number of items installed/uninstalled or pending install/uninstall.
INFO Nothing pending, run terminated. No items were found pending install/uninstall within Jamf Auto Update’s manifest.
As such, the run is terminated.
INFO New branding supplied, rebranding... The branding defined by the “branding_image” key appears to be different to prior, and as such Jamf Auto Update will apply the branding.
For more information on rebranding Jamf Auto Update, please click here.
INFO Low data mode enabled and we are set to be network aware, run terminated. The run was terminated as the primary network interface is set to be in Low Data Mode, and Jamf Auto Update’s “network_aware” key is set to: true.
For more information on customising Jamf Auto Update, please click here.
INFO Device is tethered or connected to a personal hotspot and we are set to be network aware, run terminated. The run was terminated as the primary network interface is either a hotspot or the device is on a tethered connection, and Jamf Auto Update’s “network_aware” key is set to: true.
For more information on customising Jamf Auto Update, please click here.
INFO Offline, run terminated.  The device had no network connection when Jamf Auto Update ran. So the run was terminated.
WARNING Removed <item_name> due to it raising the warning: <warning_message>

The item named: <item_name>, was automatically removed from Jamf Auto Update’s manifest due to: <warning_message>.
This can be due a few reasons, such as:
 

  • The item being removed from Jamf Auto Update.
  • The item name being incorrectly capitalised or spelt.
  • The device does not meet one or more requirements for the item to be processed.


If you need any assistance with items being automatically removed from the Jamf Auto Update manifest, please raise a new support incident by visiting: https://support.datajar.co.uk/hc/en-us/requests/new

 

Need further support?

Automate. Simplify. Succeed. If you still require assistance with us or have any further questions, please raise a ticket with our support team.

Alternatively, please see our frequently updated knowledge base articles for reference.

Related articles