Skip to main content

We are testing Mavericks 10/9 (13A603), JSS 8.73. Occasionally we see the jamfAgent process freeze, is anyone else seeing this?



external image link



I did a search through the forum, came up dry. I set tag for this thread to jamf binary but this is for jamfAgent process.



After a reboot the jamfAgent process was back to normal. Checked again about an hour later, shows not responding again.



TIA
Don

Hi @syunetsy



This is a known issue with the 8.x series and any JSS series earlier than 9.4.



In all cases, the solution will be to upgrade to at least 9.6.



In addition, the 8.x series of the JSS does not have 10.10 (or iOS 😎 compatibility, so we can’t guarantee you won’t see unexpected behavior when having 10.10 clients enrolled into an 8.x series JSS.
The solution in that case is also to upgrade to 9.6x.



If you have any additional questions or concerns, please feel free to reach out to your Technical Account Manager by giving them a call, sending an e-mail in to support@jamfsoftware.com, or by using the My Support section of JAMF Nation.



Thanks!
Amanda Wulff
JAMF Software Support


Thanks amanda.wulff We're in the process of migrating everyone to our new 9.64 JSS instance. :)


Currently investigating, but in our 9.93 quickadd package appears to miss putting the SUID and world execution bits on /usr/local/jamf/bin/jamfAgent



Results in a borked Self Service.app



Also randomly misses putting on execution bit on /usr/local/jamf/bin/jamf



issuing /usr/local/jamf/bin/jamf manage fixes the issue. Of course - you might have to add the execution bit manually first.



Results in a really borked casper deployment.



Haven't tested with Recon, but its as stable as it ever was (snicker that's sarcasm BTW).