- Jamf Nation Community
- Products
- Jamf Pro
- Re: Troubleshooting Computers checking in but not ...
Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Mute
- Printer Friendly Page
Troubleshooting Computers checking in but not running policies
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Posted on 11-16-2021 12:32 PM
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 9
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Posted on 11-16-2021 01:36 PM
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.
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Posted on 11-17-2021 06:05 AM
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).
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Posted on 11-19-2021 09:04 AM
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.
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Posted on 02-15-2022 07:33 AM
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
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Posted on 02-18-2022 08:58 AM
^^^ my question, too-- BUMP
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Posted on 07-13-2022 06:05 AM
From terminal you can
chmod 777 NAMEOFDIRECTORY
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Posted on 02-18-2022 09:06 AM
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
Reply
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Posted on 05-09-2023 12:36 PM
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!
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Posted on 05-10-2023 09:46 AM
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.
