Skip to main content
Question

Troubleshooting Computers checking in but not running policies


Forum|alt.badge.img+19

Any suggestions for troubleshooting computers that are checking in on a regular basis but not running policies (or collecting inventory?) 

I have looked at the jamf.log and I see a boat load of network change triggers, but no policy triggers. It appears the LD is not loaded either. 

Anyone else have this issue and any suggestion on how to fix? Right now, about 3% of my fleet is having this issue.

9 replies

Forum|alt.badge.img+4
  • Contributor
  • 14 replies
  • November 16, 2021

Did these computers become unmanaged? In my experience computers not running policies are down to not being managed so there are no credentials for them to run the policies with.


Forum|alt.badge.img+4
  • New Contributor
  • 7 replies
  • November 17, 2021

What happens when you run sudo jamf manage or sudo jamf policy in a terminal?  We have a problem with some of our computers as well.  We receive an error when we run one or both of those commands (I don't have a computer that is doing it in front of me to get the actual error).


Forum|alt.badge.img+4

Seeing this issue as well. Working with Jamf Support we found the issue could be caused by a hanging policy... check for anything in /Library/Application Support/JAMF/tmp

If that tmp folder isn't empty, open one of the log files up to identify the policy that's holding things up. Then try deleting the entire tmp folder and see if policies begin to run like normal. My org is dealing with the same but have not identified the culprit policy just yet.


Forum|alt.badge.img+5
  • Contributor
  • 30 replies
  • February 15, 2022
hunter_gardner wrote:

Seeing this issue as well. Working with Jamf Support we found the issue could be caused by a hanging policy... check for anything in /Library/Application Support/JAMF/tmp

If that tmp folder isn't empty, open one of the log files up to identify the policy that's holding things up. Then try deleting the entire tmp folder and see if policies begin to run like normal. My org is dealing with the same but have not identified the culprit policy just yet.


How are you checking in the tmp folder since it is locked down? I know it is a stupid question but still new to this and a few of my Mac's have this issue


Forum|alt.badge.img+8
  • Contributor
  • 40 replies
  • February 18, 2022
ckulesza wrote:

How are you checking in the tmp folder since it is locked down? I know it is a stupid question but still new to this and a few of my Mac's have this issue


^^^ my question, too-- BUMP


Forum|alt.badge.img+4
ckulesza wrote:

How are you checking in the tmp folder since it is locked down? I know it is a stupid question but still new to this and a few of my Mac's have this issue


You can view the contents by first dragging the tmp folder to your desktop to create a copy. Once created you can then open the folder and view the contents. @ckulesza @tony_schaps 


Forum|alt.badge.img+4
  • Contributor
  • 11 replies
  • July 13, 2022
tony_schaps wrote:

^^^ my question, too-- BUMP


From terminal you can

chmod 777 NAMEOFDIRECTORY


Forum|alt.badge.img+7
  • Contributor
  • 26 replies
  • May 9, 2023

This thread is almost 2 years old and the most recent reply was over 1 year ago... but I'm running into the same issues:

Machines will check-in but not update inventory nor run policies.

/Library/Application Support/JAMF/tmp was empty

running sudo jamf policy -verbose came back with "An unknown error occured

 

Sorry to bump this, but if anybody had any resolutions I'd be happy to hear them!


Forum|alt.badge.img+4
  • Contributor
  • 14 replies
  • May 10, 2023
Nate1 wrote:

This thread is almost 2 years old and the most recent reply was over 1 year ago... but I'm running into the same issues:

Machines will check-in but not update inventory nor run policies.

/Library/Application Support/JAMF/tmp was empty

running sudo jamf policy -verbose came back with "An unknown error occured

 

Sorry to bump this, but if anybody had any resolutions I'd be happy to hear them!


I had an issue with some M1 and M2 MacBooks that were not updating inventory. Turned out to be a Sentry log collection issue. I would recommend trying to disable that and see if you can update inventory afterwards.

https://learn.jamf.com/en-US/bundle/technical-articles/page/Sentry_Crash_Logging_and_Usage_Analytics_Integrations.html


Reply


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings