Good afternoon-

I have about 20 Linux servers in my environment, all of which are running the KACE agent. In the web GUI, the agent icon shows as connected, but something is causing these machines to stop sending their inventory to my K1000 (the "Last Sync" column will show hours or days).

Is there something that I can check, either on the server or in my GUI, to see why this happening?

Thank you!

0 Comments   [ + ] Show Comments

Comments

Please log in to comment

Answers

0

What happens if you force a check in?

  • RHEL/Suse:  su root -c "/opt/dell/kace/bin runkbot 2 0"
  • Ubuntu: sudo /opt/dell/kace/bin runkbot 2 0

Is the KACE agent running?  Run this in terminal:  ps aux | grep AMPAgent

It should return two lines if it's running, one will say "daemon".

If you are still having problems, enable debug and open a support ticket: http://www.kace.com/support/resources/kb/article/how-to-enable-debug-logs-on-the-kace-k1000-client-kbox-client-deployment

Answered 06/12/2013 by: jknox
Red Belt

  • If I force a check in through the GUI, I get the "Agent has been asked for updated inventory information. To refresh this page press [here]." message. After a few seconds, that message disappears, but the "Last Sync" column is still hours or days and the "Last Inventory" value is still 7 days, 1 hour, 56 minutes, 49 seconds ago on 06/05/2013 at 12:27:54.

    When I run the (Ubuntu) command above, I get a "command not found" error, but I noticed that I can't cd into the /bin directory. This might be something specific to my server though.

    When I run the ps command, I actually have three instances of ./AMPAgent --daemon.
  • I should add that it's not that these servers never sync because they have, but then something happens that causes them to stop for an extended period of time.
  • I was able to force the inventory, but was getting a message that it couldn't update while in disconnected mode. I killed all of the agent processes, restarted the agent using sudo /etc/init.d/AMPctl restart, then forced the inventory and that seemed to work. I'll keep an eye on this and see if they stop reporting in and open a ticket if necessary.

    Thank you!
    • Hi @brupnick - are you still seeing this issue? I'm seeing this with our Ubuntu desktop machines.
Please log in to comment
Answer this question or Comment on this question for clarity