Patch discovery failing
Hi
I've followed all the troubleshooting tips from this post
http://www.itninja.com/question/what-to-do-when-detect-failures-in-patching
However over half my agents are failing to complete patch detection, according to Kace appliance.
The detection seems to continue for ages (hours/forever?) on the failing machines - so assume this may be a timeout on the appliance just giving up on the slow clients?
Looking at my laptop (one of the "broken" machines) shows that a detect which started at 10:30 is still running at 1400. So something is clearly wrong here.
kpatch.out files are flicking in and out with kpatch.out.lastdetect file showing
puid={B1DA7B15-B82C-4437-8F5A-3FAC0AEFE602}
detect_result=1
error=0
plpFilename=790C97CC-E622-4756-8621-E45095C9FB25.plp
For example so I assume this is ok..?
I've tried reinstalling the agent to no avail. Any ideas?
Thanks.
0 Comments
[ + ] Show comments
Answers (3)
Please log in to answer
Posted by:
Darkplace
7 years ago
Further to this...all agent actions (force checkin/run now/patch reporting etc...) seem to takes ages since upgrading to v7. Anyone else notice this...I'm rebooting the KACE appliance just in case the appliance is to blame...
Posted by:
brucegoose03
7 years ago
What does your Security > Patching page show for you subscription?
is it showing expired? i noticed that mine was doing that today, and i don't think it's just me.
Comments:
-
Thanks for the reply...my catalog updated last night as per my schedule.
Nothing i can see in the Security->Patch Management shows anything has expired.
I tried changing the detect schedule last night just in case this would kick things in - I extended the timeout to 5 hours...nothing seemed to help. - Darkplace 7 years ago -
Just looked for common factors - nothing I can see...affects clients and servers alike, have servers working and broken on the same VLAN...grrrr! WIndows 7-10, Server 2008,RS,2012,2012R2
Also nothing useful in the logs on the endpoint...although this is probably my lack of log reading skill ;) - Darkplace 7 years ago-
If your patch detect is taking longer than an hour and you're not on 7.0, then you probably are hitting the timeout. But, you said you extended the timeout ot 5 hours, so it sounds like you're on 7.0 since that's now an option.
Post your latest kpatch.log from a machjine that failed and maybe we can figure out what it's doing.
If not, it might be best to check with support. - brucegoose03 7 years ago-
I don't see any kpatch.log file - I've enabled loggin by add debug=true to the amp.conf (i also set this using the script - but I manually checked as was not getting a file) and restarted the konea service - Darkplace 7 years ago
-
Old habits, i meant KAgent.log in C:\ProgramData\Dell\kace\user - brucegoose03 7 years ago
Posted by:
Darkplace
7 years ago
Ah thought so ;)
Strangely the machines which were not working since last Thursday are now reporting back. They are taking a very long time to complete...started at 1530 and finishes at 1945...maybe that was the issue?
Anyways thanks for the assist.