[SOLVED] Problem since update 2.6.0.16881

Questions about WAPT Server / Requests and help related to the WAPT server
Forum Rules
Community Forum Rules
* English support on www.reddit.com/r/wapt
* French community support is available on this forum
* Please prefix the topic title with [RESOLVED] if it is resolved.
* Please do not edit a topic that is tagged [RESOLVED]. Open a new topic referencing the old one.
* Specify the installed WAPT version, full version, and build number (2.2.1.11957 / 2.2.2.12337 / etc.) as well as the Enterprise/Discovery edition.
* Versions 1.8.2 and earlier are no longer supported. The only questions accepted regarding version 1.8.2 are related to upgrading to a supported version (2.1, 2.2, etc.).
* Specify the server OS (Linux/Windows) and version (Debian Buster/Bullseye - CentOS 7 - Windows Server 2012/2016/2019).
* Specify the OS of the administration/package creation machine and the machine with the problematic agent, if applicable (Windows 7/10/11/Debian 11/etc.).
* Avoid asking multiple questions when opening a topic, otherwise it may be ignored. If there are multiple topics, open separate topics, preferably one after the other and not all at the same time (i.e., do not spam the forum).
* Include code snippets, screenshots, and other images directly in the post. Links to Pastebin, Bitly, and other third-party sites will be systematically removed.
* As with any community forum, support is provided voluntarily by members. If you require commercial support, you can contact Tranquil IT's sales department at 02.40.97.57.55
Locked
TomTom
Messages: 79
Registration: May 25, 2018 - 3:43 p.m.

February 4, 2025 - 9:06 AM

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
Attachments
2025-02-04_08h58_33.png
2025-02-04_08h58_33.png (9.22 KB) Viewed 4892 times
2025-02-04_08h57_54.png
2025-02-04_08h57_54.png (111.26 KB) Viewed 4892 times
2025-02-04_08h57_33.png
2025-02-04_08h57_33.png (114.04 KB) Viewed 4892 times
Last modified by TomTom on 04 Feb 2025 - 11:32, edited 1 time.
WAPT version: 2.6.0.17392 (Enterprise Edition)
Server OS: Debian 12 "Bookworm"
Administration/package creation machine OS: Windows 11 24h2
User avatar
htouvet
WAPT Expert
Messages: 436
Registration: March 16, 2015 - 10:48
Contact :

February 4, 2025 - 9:18 AM

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?
Tranquil IT
TomTom
Messages: 79
Registration: May 25, 2018 - 3:43 p.m.

February 4, 2025 - 9:20 AM

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.
Last modified by TomTom on 04 Feb 2025 - 11:54, edited 1 time.
WAPT version: 2.6.0.17392 (Enterprise Edition)
Server OS: Debian 12 "Bookworm"
Administration/package creation machine OS: Windows 11 24h2
TomTom
Messages: 79
Registration: May 25, 2018 - 3:43 p.m.

February 4, 2025 - 10:29

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.
WAPT version: 2.6.0.17392 (Enterprise Edition)
Server OS: Debian 12 "Bookworm"
Administration/package creation machine OS: Windows 11 24h2
Locked