Tranquil IT Forum

Can this version be used in production on a new server?

Hello,
We use Wapt 1.5.1.8 in production at our clients' (Debian server)

Hubert.

On some machines where I uninstalled the old agent and reinstalled the new one, the "Check Updates" or "Apply upgrades" button is grayed out, and I don't understand why.

Any ideas?
Thanks.

guigeek wrote: ↑Dec 5, 2017 - 5:06 PM On some computers where I uninstalled the old agent and reinstalled the new one, the "Check Updates" or "Apply upgrades" button is grayed out and I don't understand why.

Any ideas?
Thanks,

In fact, all the installed clients appear as "unreachable"...

I have a feeling it's the WebSocket that's not working... in the WaptService logs on the client I have this:
Error in socket io connection ConnectionError (unexpected status code (401 Unauthorized)).

The permissions on the server in /var/www/wapt are correct.
I'm a bit stumped

Here I am again, spamming.
Apparently, a file is missing:
/var/www/wapt-host/45EC4D56-BA0D-3CFF-6F8C-8C1E31C46A3A.wapt" failed (2: No such file or directory).

How can I recreate it?

Hello,

The message "(unexpected status code (401 Unauthorized))" means that the WebSocket connection is not authorized because either the computer is not registered on the server or the public key stored in the server's database does not match the computer's private key.

Indeed, in version 1.5, the computer creates a private/public key pair (using its FQDN as the object) and sends the X.509 certificate with the public key to the server during the initial registration (when installing the waptagent.exe client).

This key pair is then used to authenticate inventories sent by the client and to authenticate WebSocket connections.

If the key pair is generated after the waptservice has started, the computer will appear disconnected until the waptservice restarts.

If the computer is incorrectly registered or not registered at all, you can try "wapt-get register -ldebug" on the client with administrator privileges and restart the service ("net stop"). "waptservice" "net start waptservice"

If the key doesn't match, you can try removing the client from the inventory (this will remove the certificate/public key of the client in question from the database) and re-registering the client.

If it still doesn't work, it's a bug...

----

Regarding the second point, the message
"/var/www/wapt-host/45EC4D56-BA0D-3CFF-6F8C-8C1E31C46A3A.wapt" failed (2: No such file or directory)"
is normal as long as you haven't created a configuration for the machine in the console.

The machine tries to retrieve its target configuration with each update.

In wapt 1.3, machine packages were named with the machine's FQDN.

In wapt 1.5, machine packages are named by default with the machine's UUID.

A script allows you to recreate machine packages in bulk if necessary. (/opt/wapt/waptserver/scripts/migrate-hosts.py )

Thanks,
I ran `wapt-get register` in debug mode and everything went smoothly. It says "success." But on the server side, I still don't have the UUID.wapt...

For the CentOS Wapt 1.5 repository, the packages are available here: https://wapt.tranquil.it/centos7/wapt-1.5/
They require PostgreSQL 9.4 and Nginx

: https://www.wapt.fr/fr/doc-1.5/Installa ... _wapt.html

guigeek wrote: ↑Dec 6, 2017 - 10:20 AM Thank you,
I ran `wapt-get register` in debug mode and everything went smoothly. It says "success." But on the server side, I still don't have the UUID.wapt...

Apparently, following a server update, the problem seems to be resolved...