[RESOLVED] Following an upgrade from 2.4.0 to 2.5.5, all clients were disconnected
Published: May 29, 2024 - 3:34 PM
- Installed WAPT version: 2.4.0 for clients, server and admin machine in 2.5.5
- Server OS: Debian 12.5
- Operating system of the administration/package creation machine: Windows 11
Hello, following a question asked yesterday (viewtopic.php?t=3908) and whose fix simply consisted of installing the latest version of WAPT, which we did today, no client can now communicate with the wapt server.
We exhibit similar behavior to these two other subjects:
viewtopic.php?t=3784
viewtopic.php?t=3785
Note that all customers appear in "disconnected", including the one on my administration workstation which I updated manually.
To begin with, running waptdeploy (which is also up to date) fails with the following error:
On my administration workstation with the manually installed 2.5.5 client, I keep getting these messages in a loop in the service logs:
which worked well, my client updated. However, I now see the same thing appearing in the logs as on my admin machine:
I have reviewed the other questions asked on the forum, and we have tried the solutions provided, including 'making sure that the postconf was executed correctly,' but without success so far.
Do you have any idea where this problem might be coming from?
THANKS,
Maxim
- Server OS: Debian 12.5
- Operating system of the administration/package creation machine: Windows 11
Hello, following a question asked yesterday (viewtopic.php?t=3908) and whose fix simply consisted of installing the latest version of WAPT, which we did today, no client can now communicate with the wapt server.
We exhibit similar behavior to these two other subjects:
viewtopic.php?t=3784
viewtopic.php?t=3785
Note that all customers appear in "disconnected", including the one on my administration workstation which I updated manually.
To begin with, running waptdeploy (which is also up to date) fails with the following error:
.\waptdeploy.exe --hash=d1267cb848231ed1c07f831e2883269ae8e2060aa51f4345e45d035a2b4b9440 --minversion=2.5.5.15602 --wait=15 --waptsetupurl=https://waptserveur.dom.local/api/v3/ge ... tagent.exe --setupargs="/LOG=C:\ProgramData\IT\Logs\WAPTAgentGPO.log"
{"hash":"d1267cb848231ed1c07f831e2883269ae8e2060aa51f4345e45d035a2b4b9440","minversion":"2.5.5.15602","wait":"15","waptsetupurl":"https://waptserver.dom.local/api/v3/get ... tputFormat"}
WAPT version: 2.4.0.14080
WAPT required version: 2.5.5.15602
Wapt agent path: C:\Users\ADM-PD~1\AppData\Local\Temp\waptagent.exe
Wget new waptagent from https://waptserver.dom.local/api/v3/get_waptagent_exe/
Trying to reach https://waptserver.dom.local/api/v3/get_waptagent_exe/...
Expecting hash sha256: d1267cb848231ed1c07f831e2883269ae8e2060aa51f4345e45d035a2bxxxx
Using proxy:
Error trying to get https://waptserver.dom.local/api/v3/get_waptagent_exe/ : Error downloading https://waptserver.dom.local/api/v3/get_waptagent_exe/: [EHttpSocket] THttpClientSocket.WGet: waptserver.dom.local:443/api/v3/get_waptagent_exe/ failed as 404 Not Found... sleeping
Delete sheduled task "fullwaptupgrade"
An unhandled exception occurred at $00603D02:
Exception: Error downloading https://waptserver.dom.local/api/v3/get_waptagent_exe/: [EHttpSocket] THttpClientSocket.WGet: waptserver.dom.local:443/api/v3/get_waptagent_exe/ failed as 404 Not Found
$00603D02
$00605402
On my administration workstation with the manually installed 2.5.5 client, I keep getting these messages in a loop in the service logs:
I tried the following commands on another computer:2024-05-29 15:53:14,013 [waptws SocketIOClient 3352] WARNING Exception ConnectionError('One or more namespaces failed to connect'), waiting 60s before retrying
2024-05-29 15:54:14,034 [wapttasks SocketIOClient 3352] INFO Socketio connection params have changed. Socketio needs reconnect
2024-05-29 15:54:14,034 [wapttasks SocketIOClient 3352] INFO Creating socketio client: https://waptserver.dom.local:443 client auth cert: ('C:\\Program Files (x86)\\wapt\\private\\w-adm-mju.si.local.crt', 'C:\\Program Files (x86)\\wapt\\private\\w-adm-mju.si.local.pem') proxies: None verify_cert: True
2024-05-29 15:54:14,034 [wapttasks SocketIOClient 3352] INFO Connecting Socketio to https://waptserver.dom.local:443
2024-05-29 15:54:15,798 [waptws SocketIOClient 3352] WARNING Exception ConnectionError('One or more namespaces failed to connect'), waiting 60s before retrying
Code: Select all
wapt-get update
wapt-get install dgt-waptupgrade[wapttasks SocketIOClient 10092] INFO Creating socketio client: https://waptserver.dom.local:443 client auth cert: ('C:\\Program Files (x86)\\wapt\\private\\w-doh-mju.si.local.crt', 'C:\\Program Files (x86)\\wapt\\private\\w-doh-mju.si.local.pem') proxies: None verify_cert: True
[wapttasks SocketIOClient 10092] INFO Connecting Socketio to https://waptserver.dom.local:443
[waptws SocketIOClient 10092] WARNING Exception ConnectionError('One or more namespaces failed to connect'), waiting 60s before retrying
I have reviewed the other questions asked on the forum, and we have tried the solutions provided, including 'making sure that the postconf was executed correctly,' but without success so far.
Do you have any idea where this problem might be coming from?
THANKS,
Maxim
) of an old remnant in the waptserver.ini server configuration file: