Error Occurred While Running Policy "Update Inventory" on Computer "xxx"

BookMac
Contributor

Hi folks,

for a few weeks now we've been getting messages that the inventory has failed. The log looks like this:

An error occurred while running the policy "Update Inventory" on the computer "xxx".

Actions from policy log:

	Executing Policy Update Inventory
	Running Recon...
	Retrieving inventory preferences from https://xxx.jamfcloud.com/...
	Locating accounts...
	Locating package receipts...
	Searching path: /System/Applications
	Locating software updates...
	Locating plugins...
	Locating printers...
	Searching path: /Applications
	Locating hardware information (macOS 12.2.1)...
	Software update timed out after 300 seconds.

The complete policy log is available in the JSS at:
https://xxx.jamfcloud.com/policies.html?id=1&o=l


Computer Info: 
ID:		xxx
IP Address:	xxx
Serial Number:	xxx

 Can someone tell me what's going wrong? The inventory there for too long and then he breaks it off?

Regards

7 REPLIES 7

jsherwood
Contributor

We've also been seeing this behaviour for the last couple of weeks - I was wondering if it was something related to our infrastructure but clearly it's a wider issue

JustDeWon
Contributor III

You may want to check the policy itself.... Looks like you have softwareupdates running with the inventory update, and it's timing out on the software update

mschroder
Valued Contributor

Looks as if the softwareupated got stuck and needs to be kicked with  "sudo /bin/launchctl kickstart -k system/com.apple.softwareupdated".

BookMac
Contributor

It looks like the solution is the one posted by @gachowski  at https://community.jamf.com/t5/jamf-pro/recon-error-software-update-timed-out-after-300-seconds/m-p/2...

I adjusted the update inventory policy and added sudo launchctl kickstart -k system/com.apple.softwareupdated under Files and Processes

No need for sudo though?

No sudo needed when run from the MDM, but needed when run by user from command-line.

 

Exactly, that's what I was saying. the OP has sudo in their policy, and I was asking why.