Page 1 of 1

[SOLVED] Problem since update 2.6.0.16881

Published: February 4, 2025 - 9:06 AM
by TomTom
Hello everyone,

Since this morning I have noticed abnormal CPU activity on my Linux machines (ubuntu/debian).
I just noticed that they installed the latest WAPT 2.6.0.16881 update overnight, which seems to be affecting the agent's operation.
I've attached screenshots of the usage before and after stopping the Waptservice; the difference is striking. Also included is a screenshot of the status in the console.

When I try a wapt-get upgrade on the machines, here's the output:

Code: Select all

Using config file: /opt/wapt/wapt-get.ini
Nothing to upgrade
2025-02-04 08:58:46,341 WARNING Host on the server is not known or not known under this computer name (known as None). Trying to register the computer...
2025-02-04 08:58:49,342 WARNING Host on the server is not known or not known under this computer name (known as None). Trying to register the computer...
2025-02-04 08:58:51,664 WARNING Host on the server is not known or not known under this computer name (known as None). Trying to register the computer...
2025-02-04 08:58:54,749 WARNING Host on the server is not known or not known under this computer name (known as None). Trying to register the computer...
2025-02-04 08:58:57,502 WARNING Host on the server is not known or not known under this computer name (known as None). Trying to register the computer...
2025-02-04 08:59:01,060 WARNING Host on the server is not known or not known under this computer name (known as None). Trying to register the computer...
2025-02-04 08:59:03,257 WARNING Host on the server is not known or not known under this computer name (known as None). Trying to register the computer...
2025-02-04 08:59:05,931 WARNING Host on the server is not known or not known under this computer name (known as None). Trying to register the computer...
2025-02-04 08:59:08,402 WARNING Host on the server is not known or not known under this computer name (known as None). Trying to register the computer...
2025-02-04 08:59:11,145 WARNING Host on the server is not known or not known under this computer name (known as None). Trying to register the computer...
2025-02-04 08:59:13,385 WARNING Host on the server is not known or not known under this computer name (known as None). Trying to register the computer...
2025-02-04 08:59:15,909 WARNING Host on the server is not known or not known under this computer name (known as None). Trying to register the computer...
Thank you for your help, my server is starting to overload :roll:

Thomas

Re: Problem since update 2.6.0.16881

Published: February 4, 2025 - 9:18 AM
by htouvet
If the server hasn't been updated to the same version, that could be the source of the problem.
We had an issue with a client whose machines in Active Directory had a different name than their hostname.
So now we're matching (to determine if a machine has been cloned, for example, or deleted and needs to be re-registered) based on the hostname only.
Unfortunately, the server with the previous version doesn't return this computer_name, and therefore the machine re-registers (correctly) in a loop.

Have you updated the server?

Re: Problem since update 2.6.0.16881

Published: February 4, 2025 - 9:20 AM
by TomTom
No, not yet, I didn't want to cause any more problems. I'll take a snapshot and try the update to see if, as you say, the problem might be coming from there.
I'll get back to you as soon as I have more information.

Thanks for the quick reply, Hubert.

Re: Problem since update 2.6.0.16881

Published: February 4, 2025 - 10:29 AM
by TomTom
Indeed, the problem stemmed from the client/server version difference.

We can now close this issue; everything is back to normal.

Thanks again, Hubert, for the explanation.