LOST AGENT CONNECTION AFTER UPGRADING TO 13.1.73
Dear All,
I have upgraded my KACE SMA to v13.1.73, after that I have noticed that agents are not able communication and connection is lost or rejected by server. also I have updated agent from provisioning by uploading agent bundle but I don't see any result and no single agent is updated, appreciate you response and answers.
-
Ditto, I have an appointment scheduled this afternoon for a KACE engineer to take a look. I would refrain from upgrading, I let everyone on the Reddit thread know too. - Yadnus 1 year ago
-
Ditto, I have an appointment scheduled this afternoon for a KACE engineer to take a look. I would refrain from upgrading, I let everyone on the Reddit thread know too. - Yadnus 1 year ago
-
Has anyone received resolution on this? All of my agents have been down for over a month. I've upgraded to the newest 13.2 version sma and agent with no resolution, included from my quest ticket. They said it must be on my side. - jfangman 9 months ago
Answers (7)
I already logged a case with support, until they respond wanted to check here . Also the error message we get in konea log is as below,
2023-04-17.13:15:55+0300|ERROR|serverconn.go:397:connect | Could not send connect msg|{"err":"Post \"https://xyz.:443/connect?ip=0.0.0.0%3A61018&kuid=c8e615d4-9a9a-4f7b-9d65-1c727ddb17de&os=windows&ver=12.0.38\": context deadline exceeded (Client.Timeout exceeded while awaiting headers)"}
2023-04-17.13:15:55+0300|ERROR|serverconn.go:291:func1 | Failed to connect |{"url":"https://xyz:443"}
2023-04-17.13:15:55+0300|INFO |serverconn.go:181:Run | Reconnecting |{"retry":"160s"}
I'm facing the same issue, on my both KACE SMA appliance... case opened but no answer so far.
Have the same problem, but only with macOS agents. Support had me remove and re-upload the "agent logo alert", but I still have the issue.
here are my logs about the checksum not matching.
[2023-04-13.08:53:49][runkbot:DownloadUsingCurl ] DownloadFile: Downloaded /Library/Application Support/Quest/KACE/data/kbots_cache//packages/kbots/2/KUpdater.macos.64 from http://127.0.0.1:49518/packages/kbots/2/KUpdater.macos.64.46c704f2d2b9d9b219eac284146f06e3 Download speed: 9240869.000000 bytes/second
[2023-04-13.08:53:49][runkbot:KCopyFile ] copy of http://127.0.0.1:49518/packages/kbots/2/KUpdater.macos.64.46c704f2d2b9d9b219eac284146f06e3 to /Library/Application Support/Quest/KACE/data/kbots_cache//packages/kbots/2/KUpdater.macos.64 succeeds
[2023-04-13.08:53:49][runkbot:DownloadDependency ] Downloaded dependency chksum of /Library/Application Support/Quest/KACE/data/kbots_cache//packages/kbots/2/KUpdater.macos.64 [35fb37a8bfef8d905f0eddb632623a78] doesn't match expected chksum [46c704f2d2b9d9b219eac284146f06e3]
kbot[2:0] @ 2023-04-13T08:53:49 (status) KBotScriptRunner::Execute - Downloading dependencies failed.
kbot[2:0] @ 2023-04-13T08:53:49 (status) runkbot - Main: Failed to execute script
I'm having the same issue with our K1000 box, recently updated to v13.0.383. Newly added systems never appear in the Devices area and they're not in Quarantine, either. Looks like I'm opening a support ticket on this.
In my case (macOS agents), it has not been solved. After upgrading to 13.1.73, support told me to wait for the new re-released, and the ticket was closed.
This week 13.1.74 was released, applied, and the same problem still happens. We are on the third day of our ticket open with a tether, but no solution yet.
My recommendation; have a plan B (or C) in case you run into problems like some of us. Two weeks unable to manage 25% of our endpoints.
Good Luck!
Comments:
-
well with 13.1.74 the issue should have been solved (do you use a replication share which still have the old files?) - Nico_K 1 year ago