Tranquil IT Forum

Good morning,

Distributor ID: Debian
Description: Debian GNU/Linux 10 (buster)
Release: 10
Codename: buster
Postgres 11.2

This ticket follows the ticket viewtopic.php?t=3766

Version 2.5.4 resolved the error encountered during the execution of the post-configuration script. The server has successfully migrated to version 2.5.4.15337
WAPT Server version: 2.5.4.15337
WAPT Agent version: 2.2.3.12463
WAPT Setup version: 2.5.4.15337
WAPT Deploy version: 2.5.4.15337
Database status: OK

I am now encountering a problem with the console that I downloaded from the server and installed after uninstalling version 2.2.3:
1) WAPTConsole indicates the Discovery version even though we have an Enterprise license
2) The inventory is empty, as is the private deposit box

I have attached the service logs Could you please help me understand where the problem might be coming from? Thank you.

Sincerely,

Hello Mohamed,

it seems the client is unable to connect to the server (at least the Socket.IO part).

Did you restart the postconf after the upgrade?

Regards,

Denis

Hello Denis,

what do you mean by postconf?
I also upgraded to 2.5.4.15342 (waiting for some stability) and my console is empty (no connected machines).

Regards,

Hello David,

version etc. (see forum rules). Is the inventory empty or are the workstations disconnected? If the console is empty, it's a different bug; please open a new topic. If you are using WAPTServer on Windows (which isn't mentioned), there's no postconf script to run because it's launched by the Windows installer.

Regards,

Denis

Sorry, sorry: wapt under Windows (version 2.5.4.15342)

console in which all workstations are disconnected (see attached image). However, it seems the agent upgrade task is being deployed, so I'll wait for the workstations to restart.

Sorry, I only noticed it afterward. It seems I left the "verify certificate" box checked...

I'll update tomorrow morning depending on how the network is doing. Otherwise, I'll revert.

Regards

Hello David,

OK for the server under Windows. The postconf is a script that is run at the end of the installation/update for the WAPT server under Linux.

The log in the screenshot in question was for your latest update, version 2.4.0. Could you please try running the upgrade from the command line on a machine?
Were your agents configured for HTTP or HTTPS? If HTTPS, was it with or without certificate verification?

Sincerely,

Denis

dcardon wrote: ↑Feb 15, 2024 - 3:56 PM Hello Mohamed,

it seems the client is unable to connect to the server (at least the Socket.IO part).

Did you restart the postconf after the upgrade?

Regards,

Denis

Hello Denis,

I apologize for the late reply.
Yes, I successfully ran postconfig, which executes without errors. Therefore, this problem is resolved compared to version 2.5.
However, in the certificate information displayed at the end, the FQDNs shown do not match the FQDNs in the server URL. The names are different. Is this the source of the console connection problem in version 2.5.4?

However, I was able to connect the console installed on my machine and its agent by changing the server name in the url (https) to its ip address and disabling certificate verification (verify_cert=0).
In the console all stations (in 2.2.3) are disconnected because they are still trying to connect with the FQDN configured in their ini.

What do you advise me to do to solve the problem? Thank you.

Feel free to ask me if you need any further information. Thank you.

Sincerely,

Hello everyone,

for my part, I restored a VM before the update (yes, mea culpa, I should have taken a snapshot... ouch, don't hit me! )
. Then I redeployed an INI file to set these two variables to 0 and then restarted the WAPT service:

`check_certificates_validity=0`
and `verify_cert=0`.

The machines gradually reconnected.
Finally, I also pushed the new version of the agent via GPO.

I think that when I did the first update, I must have left the box checked for the certificate, and that messed things up.
So, a week later, it's stable, but luckily I don't have 3000 machines.

Best regards.