Tranquil IT Forum

Published: **February 9, 2024 - 12:34 PM**

Hello everyone,

Having recently migrated to the 2.5 branch, I have two machines that have decided to rebel. I should mention that they've always been more or less like that, with the host package update either not launching at all, or I have to do it manually from the command prompt on the PC using `wapt-get update /upgrade`... And even then, it's not exactly a success.

The difference compared to version 2.4 is that I now have errors in the server logs for both of these machines:

Code: Select all

Feb 09 12:20:44 xxxx waptserver[7412]: 2024-02-09 12:20:44,799 [waptauth       ] WARNING Failed auth for None from 192.168.x.1 path /add_host
Feb 09 12:20:46 xxxx waptserver[7412]: 2024-02-09 12:20:46,308 [waptauth       ] WARNING Failed auth for None from 192.168.x.2 path /add_host

I have already tried uninstalling the agent on the PCs, deleting the installation remnants in %programfiles(x86)%, restarting the PCs, restarting the server, reinstalling the agents directly from version 2.5 downloaded from my portal... But nothing works, these two PCs consistently have problems.

These are PCs running Windows 7 with all updates still available. One is a physical PC, the other is a VirtualBox VM (accessible from the rest of the network and not configured with NAT).

---- Additional test from both PCs ----

Code: Select all

C:\Program Files (x86)\wapt>wapt-get update-status
Using config file: C:\Program Files (x86)\wapt\wapt-get.ini
2024-02-09 12:36:56,131 WARNING Host on the server is not known or not known under this FQDN name (known as pc1.MON.DOM). Trying to register the computer...
...

I tested DNS resolution from the server to pc1 (same test on the other pc).

---- Test from the wapt server ---

Code: Select all

nslookup pc1 --> renvoie bien l'ip
nslookup ip de pc --> renvoie bien le nom dns pc1.mon.dom
nsloolup pc1.mon.dom --> renvoie bien l'ip de pc1

I think I've tried just about everything for these two Gauls

I have other PCs with similar specs and I don't have any problems. Do you have any other ideas?

Configuration:
-- Server: Debian 11.8, updated yesterday
-- PC: Windows 7 64-bit, up to date, firewall disabled.

Thanks in advance.
Philippe.

Published: **February 26, 2024 - 10:04 AM**

Hi Philippe,

what's the authentication method for the workstations?

What happens if you force a manual registration?

Denis

Published: **February 27, 2024 - 11:27**

Hello Denis,

What is the authentication method for the workstations?

Between the agent and the Wapt server?
When I generated the agent installation package, I used the following parameters:

: wapt.png (44.15 KB) Viewed 6395 times

This morning I tried to delete the machine from the wapt console and in the server logs I have this message:

Code: Select all

Feb 27 11:14:56 serveur waptserver[557]: 2024-02-27 11:14:56,126 [waptws         ] WARNING SocketIO connection refused for uuid 4c4c4544-0031-5910-8031-c4c04f35354a, sid -rKFnq7zhI-icCq4AG2F: Unknown host 4c4c4544-0031-5910-8031-c4c04f35354a, instance
Feb 27 11:14:57 serveur waptserver[557]: 2024-02-27 11:14:57,097 [waptserver     ] CRITICAL update_host failed EWaptMissingCertificate('You try to update status of an unknown host 4c4c4544-0031-5910-8031-c4c04f35354a (pc1). Please register first.')
Feb 27 11:14:57 serveur waptserver[557]: 2024-02-27 11:14:57,280 [waptserver     ] CRITICAL update_host failed EWaptMissingCertificate('You try to update status of an unknown host 4c4c4544-0031-5910-8031-c4c04f35354a (pc1). Please register first.')
Feb 27 11:14:58 serveur waptserver[557]: 2024-02-27 11:14:58,530 [waptauth       ] WARNING Failed auth for None from 192.168.x.x path /add_host
Feb 27 11:14:58 serveur waptserver[557]: 2024-02-27 11:14:58,532 [waptserver     ] WARNING Unauthenticated registration for pc1
Feb 27 11:14:58 serveur waptserver[557]: 2024-02-27 11:14:58,623 [waptauth       ] WARNING Failed auth for None from 192.168.x.x path /add_host
Feb 27 11:14:58 serveur waptserver[557]: 2024-02-27 11:14:58,627 [waptserver     ] WARNING Unauthenticated registration for pc1
Feb 27 11:14:58 serveur waptserver[557]: 2024-02-27 11:14:58,860 [waptdb         ] CRITICAL Error updating data for 4c4c4544-0031-5910-8031-c4c04f35354a : IntegrityError: duplicate key value violates unique constraint "hosts_pkey"
Feb 27 11:14:58 serveur waptserver[557]: DETAIL:  Key (uuid)=(4c4c4544-0031-5910-8031-c4c04f35354a) already exists.
Feb 27 11:14:58 serveur waptserver[557]: 2024-02-27 11:14:58,932 [waptserver     ] CRITICAL add_host failed IntegrityError('duplicate key value violates unique constraint "hosts_pkey"\nDETAIL:  Key (uuid)=(4c4c4544-0031-5910-8031-c4c04f35354a) already exists.\n')

And on the console side, the machine hasn't been deleted. It appears the machine is listed multiple times in the database on the server.

What happens if you force a manual register?

Given the duplicate key error message, I'll avoid adding it manually for now

Tranquil IT Forum

WARNING: Auth failed for None

WARNING: Auth failed for None

Re: WARNING Failed auth for None

Re: WARNING Failed auth for None