recon hangs with /Applications/MAMP folder

glpi-ios
Contributor III

Hello,

I noticed that the inventory was not done on computers with MAMP installed.
When I do a "jamf recon -verbose", the inventory hangs completely and I think that it is the /Applications/MAMP/ folder that is causing the problem and not the MAMP.app application.

Have you seen this issue before and do you know how to work around this behavior?

Thank you for your help

1 ACCEPTED SOLUTION

Levi_
Contributor II

If you look in Activity Monitor under CPU do you have stacks of softwareupdate processes? If you do, kill them and see if your recon in verbose mode completes. 

View solution in original post

4 REPLIES 4

Levi_
Contributor II

If you look in Activity Monitor under CPU do you have stacks of softwareupdate processes? If you do, kill them and see if your recon in verbose mode completes. 

glpi-ios
Contributor III

Thanks very much  @Levi_ 
It works. You are our savior :)

Levi_
Contributor II

Glad I could help. I was plagued with this issue myself, eventually had a horde of Macs with no inventory for 8+ days. I thought at first it was my extension attributes causing the issue but it wasn't. Currently, there is a known issue - 
PI109755 - When a computer software update hangs and Collect available software updates is selected in the Computer Inventory Collection settings, the computer also hangs.

If you don't have a smart group looking out for machines not reporting inventory over X days I recommend you create one and take a look to make sure you don't have the same problem I did. Support recommended disabling the Available Software Updates from inventory collections. If you have the issue, disable inventory collections from collecting the Available Software Updates in Computer Management > Inventory Collection in the Admin Settings. 

Secondly, create a policy to run recon with a trigger to kill running SoftwareUpdate processes if they exist against the smart group of machines not reporting inventory over X days. Over time, these Macs will hang on a policy check and you won't be able to push MDM commands to them so if you have a restart reminder to the impacted Macs, do that too. You can do this with a script or the built-in file & processes to kill softwareupdate processes and Maintenance to collect inventory to run recon. I went with the script approach and had success myself. Unless you force the users to restart their machines this can take a couple days even a week before you start to see improvement.

For now I am not collecting available software updates and I have disabled the Software Update Policy just in case. There are likely other Admins here that have had this problem and might have more and better info for you/us :). 

glpi-ios
Contributor III

Thank you for all these explanations.

I find it a pity to no longer have to collect available software updates because it is always interesting to know the status of updates on company computers.

I think for now we will leave that but implement the rule as you advise me.

Thank you very much for taking the time to give me all this information.