/build/static/layout/Breadcrumb_cap_w.png

Server Errors: [Tue May 07 07:45:14 2013] [error] [client xxx.xxx.xxx.xxx] File does not exist: /kbox/kboxwww/dell

Why might I get this error? It repeats in the Server Errors log with different IP's that are valid for our desktops.

Server Errors: [Tue May 07 07:45:14 2013] [error] [client xxx.xxx.xxx.xxx] File does not exist: /kbox/kboxwww/dell

We're set to patch desktops in about 1 hour with an announcement having already been sent to our staff to notify of this month patch. It's a pain to reschedule at this point. I'd just research this on my own otherwise, but I'm trying to find a quick solution so I can deploy patches.

When I tried to patch my own desktops early this morning, there appears to be no response (no action in Task Mgr) on my clients. Tested only on W7 at the moment.

I upgraded the K1K to 5.4 SP1 a couple weeks ago and had some trouble doing so but all has been fine since then. I patch 100 servers seperately from desktops and did so successfully after the 5.4 SP1 install. So servers were patched without error just after the 5.4SP1 update, now 2 weeks later, my test desktops are not patching at all. I tried removing and reinstalling the agent which was already at 5.4.10622...no change.

 

FROM A CLIENT's amp.log:


[KACE Agent version 5.4.10622 Feb  8 2013]
[Mon May 06 14:19:04 2013] Config: debug:          false
[Mon May 06 14:19:04 2013] Config: config:         amp.conf
[Mon May 06 14:19:04 2013] Config: log:            amp.log
[Mon May 06 14:19:04 2013] Config: host:           SERVER.inner.domain.com
[Mon May 06 14:19:04 2013] Config: lasthost:       SERVER.inner.domain.com
[Mon May 06 14:19:04 2013] Config: serverversion:  5.4.76848
[Mon May 06 14:19:04 2013] Config: appliance:      k1000
[Mon May 06 14:19:04 2013] Config: ampport:        52230
[Mon May 06 14:19:04 2013] Config: ampurl:         http://SERVER.inner.domain.com:52230
[Mon May 06 14:19:04 2013] Config: webport:        80
[Mon May 06 14:19:04 2013] Config: weburl:         http://SERVER.inner.domain.com
[Mon May 06 14:19:04 2013] Config: hideapps:      
[Mon May 06 14:19:04 2013] Config: rto:            20
[Mon May 06 14:19:04 2013] Config: wto:            20
[Mon May 06 14:19:04 2013] Config: cto:            10
[Mon May 06 14:19:04 2013] Config: crto:           30
[Mon May 06 14:19:04 2013] Config: krash:          false
[Mon May 06 14:19:04 2013] Config: pl:             pluginDesktopAlerts,pluginPatching,pluginRunProcess,pluginWeb
[Mon May 06 14:19:04 2013] Machine ID: D0806804-5B1B-4CBB-A636-E45388265697
[Mon May 06 14:19:04 2013] Creating Pipe Server...
[Mon May 06 14:19:04 2013] Creating Agent Listener...
[Mon May 06 14:19:04 2013] Creating scheduler...
[Mon May 06 14:19:04 2013] Creating connection...
[Mon May 06 14:19:04 2013] Failed to connect: (6) Could not resolve host: SERVER.inner.domain.com; No data record of requested type
[Mon May 06 14:19:04 2013] Failed to connect: (6) Could not resolve host: SERVER.inner.domain.com; No data record of requested type
[Mon May 06 14:19:04 2013] Failed to connect: (6) Could not resolve host: SERVER.inner.domain.com; No data record of requested type
[Mon May 06 14:19:04 2013] [SetConnectedMarker] couldn't remove C:\ProgramData\Dell\KACE\AMP_CONNECTED, unlink(No such file or directory)
[Mon May 06 14:19:04 2013] Adding server retry for D0806804-5B1B-4CBB-A636-E45388265697 into queue. Sleeping for 30 seconds
[Mon May 06 18:00:07 2013] Client socket failed read [curl] (56): Failure when receiving data from the peer
[Mon May 06 18:00:07 2013] Client socket failed read [err]  (9): Bad file descriptor
[Mon May 06 18:00:07 2013] Adding server retry for D0806804-5B1B-4CBB-A636-E45388265697 into queue. Sleeping for 30 seconds
[Mon May 06 18:00:48 2013] Header: msgid (4038901); msgType (0)
[Mon May 06 18:00:48 2013] Payload: pluginId: RunProcess (6); payloadLen (24)
[Mon May 06 18:00:49 2013] SSL is not detected
[Tue May 07 07:00:07 2013] Client socket failed read [curl] (56): Failure when receiving data from the peer
[Tue May 07 07:00:07 2013] Client socket failed read [err]  (9): Bad file descriptor
[Tue May 07 07:00:08 2013] Adding server retry for D0806804-5B1B-4CBB-A636-E45388265697 into queue. Sleeping for 30 seconds
[Tue May 07 07:00:42 2013] Header: msgid (4233136); msgType (0)
[Tue May 07 07:00:42 2013] Payload: pluginId: RunProcess (6); payloadLen (37)
[Tue May 07 07:00:43 2013] SSL is not detected
[Tue May 07 07:00:44 2013] Header: msgid (4233149); msgType (0)
[Tue May 07 07:00:44 2013] Payload: pluginId: RunProcess (6); payloadLen (24)
[Tue May 07 07:33:01 2013] BOOTUP
[Tue May 07 08:18:23 2013] Client socket failed read (0 bytes read)
[Tue May 07 08:18:23 2013] Adding server retry for D0806804-5B1B-4CBB-A636-E45388265697 into queue. Sleeping for 30 seconds
[Tue May 07 08:19:03 2013] Failed to connect: (28) connect() timed out!
[Tue May 07 08:19:13 2013] Failed to connect: (28) connect() timed out!
[Tue May 07 08:19:23 2013] Failed to connect: (28) connect() timed out!
[Tue May 07 08:19:44 2013] [SetConnectedMarker] couldn't remove C:\ProgramData\Dell\KACE\AMP_CONNECTED, unlink(No such file or directory)
[Tue May 07 08:19:44 2013] Adding server retry for D0806804-5B1B-4CBB-A636-E45388265697 into queue. Sleeping for 30 seconds
[Tue May 07 08:20:18 2013] Failed to connect: (7) couldn't connect to host
[Tue May 07 08:20:24 2013] SSL is not detected
[Tue May 07 08:20:34 2013] Failed to connect: (28) connect() timed out!
[Tue May 07 08:20:43 2013] [SetConnectedMarker] couldn't remove C:\ProgramData\Dell\KACE\AMP_CONNECTED, unlink(No such file or directory)
[Tue May 07 08:20:43 2013] Adding server retry for D0806804-5B1B-4CBB-A636-E45388265697 into queue. Sleeping for 30 seconds
[Tue May 07 08:21:23 2013] Failed to connect: (28) connect() timed out!
[Tue May 07 08:21:33 2013] Failed to connect: (28) connect() timed out!
[Tue May 07 08:21:43 2013] Failed to connect: (28) connect() timed out!
[Tue May 07 08:21:59 2013] [SetConnectedMarker] couldn't remove C:\ProgramData\Dell\KACE\AMP_CONNECTED, unlink(No such file or directory)
[Tue May 07 08:21:59 2013] Adding server retry for D0806804-5B1B-4CBB-A636-E45388265697 into queue. Sleeping for 30 seconds

 


0 Comments   [ + ] Show comments

Answers (2)

Posted by: c_brock 11 years ago
Third Degree Brown Belt
0

Any firewall or DNS changes?  How about Group Policy?  Servers are known to be overly secure.

Posted by: murbot 11 years ago
10th Degree Black Belt
0

Thanks for the reply. I meant to update this issue. We have a restricted GPO set on the Servers OU that we don't change. I checked DNS as well. All good there.

I called Kace support and explained the problem, also noting that I had been unable to set the clock on the Kace server (something I didn't catch when I wrote my question above). Or rather it didn't pull the correct time from the time server. Other machines use the same time server without issue.

I'm in the EST and our K1000 was set to point to it as well as a known good time server. For a still unknown reason, our K1000 was 3 hours behind as if it was on PST.

If it matters to anyone reading this out of the U.S. I'm on the east coast of the states (EST) and our K1000 was using the time from the west coast (PST). Our K1000 is a VM and the ESX server it's on has the correct time as well.

After manually setting the correct time on the K1000, patching began to run normally. I still need to fix the issue with the time zones. We want to use a time server and not manually confgure the time on the K1000, but at the moment, the servers is working fine otherwise.

If anyone has seen a K1000 VM with an offsite time and found a fix, please let me know.

Don't be a Stranger!

Sign up today to participate, stay informed, earn points and establish a reputation for yourself!

Sign up! or login

Share

 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ