Kace Clients not reporting in, not connect by AMP
I have a few clients that will not check in to the server. I have tried all of the tools to reset the conf file, etc. I still get nowhere with these machines. We are using server version: 5.3.53053 and agent version: 5.3.53177. One of my clents shows up in inventory but not connect via AMP as having the 5.1 agent, even though it has the 5.3 installed. The others are not ininventory at all. When I try to do a runkbot 4 0, I get the following errors
I have tried installing the agent locally on the machines which does not work. I have removed and reinstalled the agent. I can't think of anything else to try. Kace support has not been very helpful with this issue.
0 Comments
[ + ] Show comments
Answers (3)
Answer Summary:
Please log in to answer
Posted by:
dugullett
11 years ago
Is your %allusersprofile%dell\kace\amp.conf populated with the correct info?
How are you installing the agent? Manually or with switches?
Also check amp.log. See if it's stating something like "retrying again in 10 seconds" over and over.
Comments:
-
The amp.conf file has all the correct info, and I have tried installing the agent both with switches and manually.
This is the error in my amp.log:
[KACE Agent version 5.3.53177 Jan 16 2012]
[Fri Aug 03 11:01:00 2012] Config: debug: false
[Fri Aug 03 11:01:00 2012] Config: config: amp.conf
[Fri Aug 03 11:01:00 2012] Config: log: amp.log
[Fri Aug 03 11:01:00 2012] Config: host: kbox
[Fri Aug 03 11:01:00 2012] Config: lasthost:
[Fri Aug 03 11:01:00 2012] Config: serverversion:
[Fri Aug 03 11:01:00 2012] Config: appliance:
[Fri Aug 03 11:01:00 2012] Config: ampport: 52230
[Fri Aug 03 11:01:00 2012] Config: ampurl: http://kbox:52230
[Fri Aug 03 11:01:00 2012] Config: webport: 443
[Fri Aug 03 11:01:00 2012] Config: weburl:
[Fri Aug 03 11:01:00 2012] Config: hideapps:
[Fri Aug 03 11:01:00 2012] Config: rto: 20
[Fri Aug 03 11:01:00 2012] Config: wto: 20
[Fri Aug 03 11:01:00 2012] Config: crto: 10
[Fri Aug 03 11:01:00 2012] Config: krash: false
[Fri Aug 03 11:01:00 2012] Config: pl: pluginDesktopAlerts,pluginPatching,pluginRunProcess,pluginWeb
[Fri Aug 03 11:01:00 2012] Machine ID: 9C34D698-1920-4A20-93F5-261C01E49B02
[Fri Aug 03 11:01:00 2012] Creating Pipe Server...
[Fri Aug 03 11:01:00 2012] Creating Agent Listener...
[Fri Aug 03 11:01:00 2012] Creating scheduler...
[Fri Aug 03 11:01:00 2012] Creating connection...
[Fri Aug 03 11:01:01 2012] Failed to connect: (7) Failed to connect to 10.0.24.2: Connection refused
[Fri Aug 03 11:01:01 2012] Agent info: ver=5.3.53177&os=windows&arch=x86&host=rppr32&ip=10.0.72.112&mac=00-14-C2-08-C5-A5
[Fri Aug 03 11:01:01 2012] Connection established (http://kbox:52230)...
[Fri Aug 03 11:01:09 2012] Header: msgid (14859); msgType (0)
[Fri Aug 03 11:01:09 2012] Payload: pluginId: RunProcess (6); payloadLen (15)
[Fri Aug 03 11:01:09 2012] Failed to connect: (7) Failed to connect to 10.0.24.2: Connection refused
[Fri Aug 03 11:11:14 2012] Header: msgid (15102); msgType (0)
[Fri Aug 03 11:11:14 2012] Payload: pluginId: RunProcess (6); payloadLen (15)
[Fri Aug 03 11:11:14 2012] Failed to connect: (7) Failed to connect to 10.0.24.2: Connection refused
[Fri Aug 03 11:31:24 2012] Header: msgid (15203); msgType (0)
[Fri Aug 03 11:31:24 2012] Payload: pluginId: RunProcess (6); payloadLen (15)
[Fri Aug 03 11:31:24 2012] Failed to connect: (7) Failed to connect to 10.0.24.2: Connection refused
[Fri Aug 03 12:01:29 2012] Header: msgid (15266); msgType (0)
[Fri Aug 03 12:01:29 2012] Payload: pluginId: RunProcess (6); payloadLen (15)
[Fri Aug 03 12:01:29 2012] Failed to connect: (7) Failed to connect to 10.0.24.2: Connection refused
[Fri Aug 03 12:41:31 2012] Header: msgid (15649); msgType (0)
[Fri Aug 03 12:41:31 2012] Payload: pluginId: RunProcess (6); payloadLen (15)
[Fri Aug 03 12:41:31 2012] Failed to connect: (7) Failed to connect to 10.0.24.2: Connection refused
[Fri Aug 03 13:31:36 2012] Header: msgid (16105); msgType (0)
[Fri Aug 03 13:31:36 2012] Payload: pluginId: RunProcess (6); payloadLen (15)
[Fri Aug 03 13:31:36 2012] Failed to connect: (7) Failed to connect to 10.0.24.2: Connection refused - tayana 11 years ago-
I'm assuming you can ping 10.0.24.2? Is this the IP address of your Kbox? If not it could be a DNS issue.
Are you using a proxy, or could there be a firewall rule blocking this (port 52230)?
Did you edit this line out, or is the name of your kbox?
[Fri Aug 03 11:01:00 2012] Config: ampurl: http://kbox:52230
Are you using SSL?
You can also attempt a telnet session. If this is working it will not return an error.
telnet 10.0.24.2 55230 - dugullett 11 years ago
-
I can ping the server without an issue. I can access the admin console from the computer. We do not use a proxy or have a firewall rule that is blocking this. We do not use SSL.
I am unable to bring up a telnet session on this computer. It doesn't give me an error just sits for a few moments and then goes back to the command prompt. - tayana 11 years ago-
If it just sits there that's actually a good thing. I would return an error if it cannot connect.
Looking at my amp.log under host I have the FQDN of my kbox. Not just kbox.
[Fri Aug 03 11:01:00 2012] Config: host: kbox
the same under
[Fri Aug 03 11:01:00 2012] Config: ampurl: http://kbox:52230
Is the name of your kbox "kbox"?
What is your full command line when installing the msi. Are you modifying the msi name to match your Kbox? - dugullett 11 years ago
-
If it helps here's a copy of my amp.conf file (slightly modified to remove my kbox name). Does yours look close to this?
host=mykbox.domain.org
log=amp.log
lasthost=mykbox.domain.org
serverversion=5.3.53053
appliance=k1000
ampport=52230
ampurl=http://mykbox.domain.org:52230
webport=443
weburl=https://mykbox.domain.org
rto=20
wto=20
crto=10
pl=pluginDesktopAlerts,pluginPatching,pluginRunProcess,pluginWeb
companyname=my company
splashtext=dell kace systems management appliance is verifying your pc configuration and managing software updates. please wait... - dugullett 11 years ago
Posted by:
AbhayR
11 years ago
Looks like amp.conf file is corrupted. Can you please delete the amp.conf file , uninstall agent and then again install the agent back.
Posted by:
SMal.tmcc
11 years ago
When you remove the agent, manually delete the keys hklm\software\kace and then try a reinstall
