I have just discovered that the windows kbox agent we are using has a memory leak. I am currently running agent version 5.0.24256

The agent uses approximately 80 handles on startup, but when ran for extended periods of time (days or weeks) the count climbs to the tens of thousands. This is affecting our servers and our desktops based on a spot check of ~10 machines.

Does anyone know if the 5.0.25648 agent version fixes this issue?

Right now, the only solution is to restart al the agents... Not an easy task with over 1000 systems attached.

Regards,
Rob
0 Comments   [ + ] Show Comments

Comments

Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

Answers

1
I'd try upgrading to the latest agent version. Submit a ticket to KACE if that doesn't resolve the issue.
Answered 11/24/2009 by: airwolf
Tenth Degree Black Belt

Please log in to comment
1
airwolf -

Yeah, I opened a ticket with KACE as well. When i created that post i was trying to get a solution asap, so i was trying all the possible avenues. Unfortunately the memory leak exists in all the 5.0.x releases thus far and KACE has no fix for the problem yet. I'm told it will be fixed in the next release, which wont be till March-ish of 2010. Disappointing to say the least.

For now, I have a job scheduled to bounce the service once a week.
Answered 11/30/2009 by: bf_rob
Senior Yellow Belt

Please log in to comment
1
What method are you using to create the scheduled jobs? Are you using KBOX scripting? I'm sure there are plenty of ways to automate the rollout of the job if you don't want to create them all manually.
Answered 11/30/2009 by: airwolf
Tenth Degree Black Belt

Please log in to comment
1
Sorry airwolf, havent been on the boards in a while to see you replied. Yeah, I just used a scheduled script run within the KBOX to bounce the service and its been working fine for the past month or so.
Answered 01/13/2010 by: bf_rob
Senior Yellow Belt

Please log in to comment
1
This bug was resolved in the latest client bundle release, Windows client build 26616. If any of you are running 26616 or later, and still see the file handlers increasing uncontrolled, please let us know in support!
Answered 01/15/2010 by: vaelin
Yellow Belt

Please log in to comment
1
Excellent, just noticed it was available before I jumped on the forums this morning. Time to test it out and see if the issue is resolved.
Answered 01/26/2010 by: bf_rob
Senior Yellow Belt

Please log in to comment
Answer this question or Comment on this question for clarity