Hello,
I just updated to version 1.5.26 and I'm encountering some problems.
After completing the agent update, the waptupgrade package was automatically updated in the repository. I then tried to apply it to my machines, but none of my actions were being applied (see attached image).
Normally, I have a 1 in "actions," but now it's 0 no matter what I do… And when I go to the "tasks" tab for my machines, I get this message: "Unable to retrieve action. Error on server: Timeout, client did not send result within 5.0 s."
Could I have missed a step?
Thank you in advance.
No action possible after update 1.5.26
Forum Rules
Community Forum Rules
* English support on www.reddit.com/r/wapt
* French community support is available on this forum
* Please prefix the topic title with [RESOLVED] if it is resolved.
* Please do not edit a topic that is tagged [RESOLVED]. Open a new topic referencing the old one.
* Specify the installed WAPT version, full version, and build number (2.2.1.11957 / 2.2.2.12337 / etc.) as well as the Enterprise/Discovery edition.
* Versions 1.8.2 and earlier are no longer supported. The only questions accepted regarding version 1.8.2 are related to upgrading to a supported version (2.1, 2.2, etc.).
* Specify the server OS (Linux/Windows) and version (Debian Buster/Bullseye - CentOS 7 - Windows Server 2012/2016/2019).
* Specify the OS of the administration/package creation machine and the machine with the problematic agent, if applicable (Windows 7/10/11/Debian 11/etc.).
* Avoid asking multiple questions when opening a topic, otherwise it may be ignored. If there are multiple topics, open separate topics, preferably one after the other and not all at the same time (i.e., do not spam the forum).
* Include code snippets, screenshots, and other images directly in the post. Links to Pastebin, Bitly, and other third-party sites will be systematically removed.
* As with any community forum, support is provided voluntarily by members. If you require commercial support, you can contact Tranquil IT's sales department at 02.40.97.57.55
Community Forum Rules
* English support on www.reddit.com/r/wapt
* French community support is available on this forum
* Please prefix the topic title with [RESOLVED] if it is resolved.
* Please do not edit a topic that is tagged [RESOLVED]. Open a new topic referencing the old one.
* Specify the installed WAPT version, full version, and build number (2.2.1.11957 / 2.2.2.12337 / etc.) as well as the Enterprise/Discovery edition.
* Versions 1.8.2 and earlier are no longer supported. The only questions accepted regarding version 1.8.2 are related to upgrading to a supported version (2.1, 2.2, etc.).
* Specify the server OS (Linux/Windows) and version (Debian Buster/Bullseye - CentOS 7 - Windows Server 2012/2016/2019).
* Specify the OS of the administration/package creation machine and the machine with the problematic agent, if applicable (Windows 7/10/11/Debian 11/etc.).
* Avoid asking multiple questions when opening a topic, otherwise it may be ignored. If there are multiple topics, open separate topics, preferably one after the other and not all at the same time (i.e., do not spam the forum).
* Include code snippets, screenshots, and other images directly in the post. Links to Pastebin, Bitly, and other third-party sites will be systematically removed.
* As with any community forum, support is provided voluntarily by members. If you require commercial support, you can contact Tranquil IT's sales department at 02.40.97.57.55
When an action is "Skipped," it generally means the machine you're trying to reach is connected to another server (or appears as such in the database).
Are you sharing the WAPT server database between two WAPT servers, or have you kept the database with the server's UUID?
Check the /var/log/daemon.log file when the machines connect. Any errors will be reported.
When a machine connects (via WebSocket) to a WAPT server, the WAPT server writes the WebSocket session ID and the server's unique ID to the database.
Are you sharing the WAPT server database between two WAPT servers, or have you kept the database with the server's UUID?
Check the /var/log/daemon.log file when the machines connect. Any errors will be reported.
When a machine connects (via WebSocket) to a WAPT server, the WAPT server writes the WebSocket session ID and the server's unique ID to the database.
Tranquil IT
