Seen this in Mavericks also, but 9.21 binary…
not sure if it's really a problem or not ? (Seems like recurring checkins are happening via the logs)

Yes, I noticed it too. However, the jamf binary is still functioning. Just like you, I don't like to see a process "Not Responding".

We are seeing this and reported it. This is what we got back from Kubley.

Thank you for reaching out about this. This issue is actually a defect in Mavericks currently, as we have even seen our Parallels VM’s report this same way. This issue was opened as DTS 600706615 which ended up in Apple confirming that it is their issue. It is now living as bug #15424012 at Apple. The status of the agent should be harmless, but it might be a good idea to wait for 10.9.1 of Mavericks, as I am sure that will be more stable.

Regards,

Dan Kubley

We're seeing the same thing on Mavericks and JSS 9.2.0. We've reported it, but haven't heard anything back. I'll pass along the info @charlesludwick to the others on my team, until we heard something contrary.

I am upgrading the JSS tomorrow to 8.7.3 as a stopgap Mavericks move.
I would wager that this is more likely to be a 10.9.2 fix as what I've read about 10.9.1 is focused in other directions and is rather small. But it wouldn't hurt to file with Apple as more reports tend to get more attention.

Yes, I'm seeing the same thing on my test Mavericks machines and JSS 8.7.3, specifically on machines that upgraded to Mavericks. I'm still testing to see if it appears on newly imaged machines.

FWIW, I thought we were good to go but after a few minutes, the Binary is now in "Not Responding" status after going to 8.7.3 and a certain "other" software update on the client side.
So, at this point it's not fixed in a very current Mavericks Mac and JSS 8.7.3.

Same issue, 10.9 machine with 8.73 JSS

I've seen this with one of our Macs yesterday running Mavericks and 9.21

+1 same issue on 9.21

Looks like it is a know Apple issue with Mavericks. Take a peek at the response from @charlesludwick

same issue here. Seeing it sometimes in our environment. +1 on 9.21 and Mavericks.

I can confirm this is not fixed in 10.9.1, still having the same issues. Maybe 10.9.2.....

Yep, same here...ugh...

@donmontalvo are you seeing machines actually not checking in or running policies? It seems as most of our 10.9 machines work normally, but I am in the middle of confirming it. Just curious to see what others are actually experiencing because of this.

Those policies that are 10.9.x compliant seem to work, but we've only done limited tests so far.
We have some that are older and need to be fixed, but that's not the JSS' fault.
FWIW, although the process is "not responding" it never seems to peg CPU or cause any grief that we've seen. So far.

JSS 9.22
OS 10.9.1
Still see jamfAgent (Not Responding)

Client still checks in fine and all policies run fine. I only have a few clients on 10.9.1 some have this and some don't. I haven't seen any problems related to this.

Enrolling using the Recon app cleared the "Not Responding" message on my client.

@bog I wonder if it stays that way after a reboot?

@donmontalvo after restart jamfAgent is running fine. No "Not Responding".

+1 - I'm also seeing this on 10.9.1 with Casper 8.7.3.

Seeing this on All machines running Mavericks. We also recently upgraded to Casper 9.2.2. Mavericks issue?

Seeing this too on:
OS 10.9.1
JSS: 9.21

However, we are running into an issue where computers are not running login policies, and I'm wondering if it's because of the agent "not responding." Anyone else having policy trouble in 10.9.1?

thoughton, I'm seeing this as well on:

OS 10.9.1
JSS: 9.22

No sign that policies aren't executing yet. I chose to use a script/launch agent that grabs the jamfAgent process and kills it periodically until Apple/JAMF fixes things.

+1 10.9 10.9.1 on jss 9.2.1 saw it on jss 9.22 and as well as today on Jss9.23