KACE Agents suddenly stop checking in until server reboot
Good morning,
Currently seeing an issue every now and then where we'll notice that the KACE agents stop checking into the KACE server (goes well past the 2 hour check-in rate) and the only way to fix it is to do a reboot of the KACE server. Upon reboot, check-ins start working again.
Anyone else run into this?
Running 6.0.101864
Thanks!
1 Comment
[ + ] Show comment
Answers (2)
Answer Summary:
Please log in to answer
Posted by:
chucksteel
9 years ago
I will very rarely see the AMPAgent service crash. Have you checked to see if the service is running before restarting? It is listed as Dell KACE Agent in services.
Comments:
-
I am running the KACE Server as a virtual appliance - which is running as Linux - so not sure how to restart just that service? If you are referring to service on the workstations crashing - I would be surprised they all crash at the same time. - bpatton 9 years ago
-
Sorry, I misread your question and thought it was a few clients not checking in. If no clients are checking in then I would recommend contacting technical support. The appliance logs might indicate what the problem is but chances are it will be something that technical support needs to resolve. - chucksteel 9 years ago
kverify - Version 0.5
kverify start Mon Dec 8 14:16:10 CET 2014
Verifying a K1000 Series
[1] ok ... Running for K1000 Serial #:############# - Mon Dec 8 14:16:10 CET 2014
[2] FAILED ... service - z.cron_server.sh running - Mon Dec 8 14:16:10 CET 2014
[3] FAILED ... service - z.kbagentless.sh running - Mon Dec 8 14:16:10 CET 2014
[4] FAILED ... service - z.kbagentless_cron.sh running - Mon Dec 8 14:16:10 CET 2014
[5] FAILED ... service - z.kbinventory.sh running - Mon Dec 8 14:16:10 CET 2014
[6] FAILED ... service - z.kbinventory_cron.sh running - Mon Dec 8 14:16:10 CET 2014
[7] FAILED ... service - z.kbprovisioner.sh running - Mon Dec 8 14:16:10 CET 2014
[8] FAILED ... service - z.kbprovisioner_cron.sh running - Mon Dec 8 14:16:10 CET 2014
[9] FAILED ... service - z.kbpusher.sh running - Mon Dec 8 14:16:10 CET 2014
[10] FAILED ... service - z.kbscanner.sh running - Mon Dec 8 14:16:10 CET 2014
[11] FAILED ... service - z.kbscanner_cron.sh running - Mon Dec 8 14:16:10 CET 2014
[12] ok ... service - z.kbserver.sh running - Mon Dec 8 14:16:10 CET 2014
[13] FAILED ... service - z.kbsoftwareinventory.sh running - Mon Dec 8 14:16:10 CET 2014
[14] FAILED ... service - z.kbsoftwareinventory_cron.sh running - Mon Dec 8 14:16:10 CET 2014
[15] FAILED ... service - z.kbwaker.sh running - Mon Dec 8 14:16:10 CET 2014
[16] FAILED ... service - z.khelpdeskmailnotifier.sh running - Mon Dec 8 14:16:10 CET 2014
[17] FAILED ... service - z.kmsgprocess.sh running - Mon Dec 8 14:16:10 CET 2014
[18] ok ... service - z.kmsgr.sh running - Mon Dec 8 14:16:10 CET 2014
[19] ok ... service - z.konductor.sh running - Mon Dec 8 14:16:10 CET 2014
[20] ok ... service - z.smarty_server.sh running - Mon Dec 8 14:16:10 CET 2014
[21] ok ... service - z.sudo_server.sh running - Mon Dec 8 14:16:10 CET 2014
[22] FAILED ... service - z.verify_app_key.sh running - Mon Dec 8 14:16:10 CET 2014
[23] ok ... mysql - K1000 version (6.2.109330) - Mon Dec 8 14:16:10 CET 2014
kverify end Mon Dec 8 14:16:10 CET 2014
***************************************************************************
kverify FAIL:
***************************************************************************
Does anyone have a solution for this problem? - Gerhart 9 years ago