Posted on 07-07-2022 01:13 AM
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
Posted on 07-07-2022 03:42 AM
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
Posted on 07-07-2022 05:35 AM
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
Posted on 07-07-2022 08:51 AM
Looks as if the softwareupated got stuck and needs to be kicked with "sudo /bin/launchctl kickstart -k system/com.apple.softwareupdated".
07-12-2022 04:22 AM - edited 07-12-2022 04:24 AM
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
Posted on 12-20-2022 09:02 AM
No need for sudo though?
Posted on 01-11-2023 06:17 AM
No sudo needed when run from the MDM, but needed when run by user from command-line.
Posted on 01-11-2023 09:55 AM
Exactly, that's what I was saying. the OP has sudo in their policy, and I was asking why.