[RESOLVED] Updated from 2.4 to 2.5 and disconnected workstations

[GT36]

Good morning,


- Installed WAPT version: 2.5.4.15337 / Discovery
- Server operating system (Linux / Windows): Debian GNU/Linux 12 (bookworm)
- Operating system of the administration/package creation machine: Windows 10 Pro

I upgraded to the latest version of 2.5 from version 2.4.
I followed this procedure: https://www.wapt.fr/fr/doc/wapt-server- ... 2-x-to-2-5

Everything went well on the server side.
I then downloaded the new console version 2.5 and installed it on my admin machine. No problems there either.

Next, the agent needs to be updated --> so I generated a new agent as explained in the procedure and then I modified my GPO task.

The agent seems to be settling in well in 2.5.

wapt.png (6.73 KB) Viewed 6039 times

After all that, the problem is that all the posts appear in "ok" status but as "disconnected" reachable.

So I looked at the WAPT service logs, and I see the following (I've modified some values, here in uppercase):

Code: Select all

2024-02-15 14:06:40,379 [wapttasks SocketIOClient 17868] INFO Socketio connection params have changed. Socketio needs reconnect
2024-02-15 14:06:40,380 [wapttasks SocketIOClient 17868] INFO Creating socketio client: https://WAPT.MONDOMAINE.local:443 client auth cert: ('C:\\Program Files (x86)\\wapt\\private\\NOM_DU_CERTIFICAT.crt', 'C:\\Program Files (x86)\\wapt\\private\\NOM_DU_CERTIFICAT.pem') proxies: None verify_cert: C:\Program Files (x86)\wapt\ssl\server\CERT_DOMAINE.crt
2024-02-15 14:06:40,380 [wapttasks SocketIOClient 17868] INFO Connecting Socketio to https://WAPT.MONDOMAINE.local:443
2024-02-15 14:06:41,428 [waptws SocketIOClient 17868] WARNING Exception ConnectionError('One or more namespaces failed to connect'), waiting 60s before retrying

Can you help me?
Otherwise, I'll have to revert to the snapshot, but the problem is that the GPO deployed agent version 2.5 to the workstations. We would then need to be able to revert the agent to version 2.4...

Thank you for your help.

[dcardon]

Hello Théo,

The message indicates that the websocket component is unable to connect. Did you correctly run the postconf file (postconf makes changes to nginx)?

Does the package download function work properly on a workstation?

Code: Select all

wapt-get update
wapt-get install xyz-monpaquet

Why does the command `wapt-get register` return an error?

Code: Select all

wapt-get register

We had some issues with certificates earlier this week, but this version has fixed everything, so there's no reason to go back.

Sincerely,

Denis

[GT36]

Thank you for the quick response.

The postconf was successfully launched just after the server updates and just before the installation of the admin console and before the creation of the new agent.
I answered "no" for the "nginx" modifications.

The package download part works well (see the two screenshots).

wapt-get update.png (18.66 KB) Viewed 6024 times

wapt-get install.png (14.55 KB) Viewed 6024 times

I forgot to mention that Kerberos authentication is enabled for machine registration.
For wapt-register:

The recording doesn't seem to be working (see screenshot).

wapt-get register.png (27.97 KB) Viewed 6024 times

Thank you.

[dcardon]

Thank you for the quick reply.

The postconf was indeed launched right after the server updates and just before the admin console installation and before the new agent was created.
I answered "no" for the "nginx" modifications.

Ah, that's where the problem lies. The nginx configuration needs to be modified to take into account the evolution of certificate-based authentication.

If you have customized your nginx.conf, the best thing to do is to make a copy (postconf normally makes one itself), answer yes to the question, then check the differences, and transfer your changes into it.

In practice, it is not necessary to update the nginx conf every time, but it is preferable to answer yes, unless you know that it is not necessary to do so.

Sincerely,

Denis

[GT36]

But normally, if I'm not mistaken, I already had certificate-based authentication on version 2.4 (verify_cert).
I'll try restarting the postconf and see what happens.

[GT36]

I restarted the post-configuration process, accepting the modification to the "nginx" configuration.
I compared the versions and reapplied the necessary changes (I had indeed customized the nginx configuration).

Thank you very much for your help and for identifying the problem so quickly.

The issue is resolved.

[dcardon]

Hi Théo,

thanks for the feedback, I'm marking the topic as RESOLVED.

Denis