Hello, for the past week my agents have been showing as disconnected in the reachable column, but their status is OK.
Do you have any idea what the problem might be, knowing that I have one workstation that is working correctly?
Thank you for your help.
Error: Agent disconnected, but status is OK
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
-
dcardon
- WAPT Expert
- Messages: 1932
- Registration: June 18, 2014 - 09:58
- Location: Saint Sébastien sur Loire
- Contact :
Hello nemesis2o0o,
Sincerely,
Denis
Which version of WAPT, which server OS, which client OS? cf. viewtopic.php?f=13&t=887nemesis2o0o wrote: ↑January 18, 2019 - 11:25 AM Hello, for the past week my agents have been showing as disconnected in the reachable column, but their status is OK.
Do you have any idea what the problem might be, knowing that I have one workstation that is OK?
Thank you for your help.
Sincerely,
Denis
Denis Cardon - Tranquil IT
Share your experiences on WAPT! Send us your blog and article URLs in the "Your Opinion of the forum, and we'll feature them on the WAPT
Share your experiences on WAPT! Send us your blog and article URLs in the "Your Opinion of the forum, and we'll feature them on the WAPT
-
nemesis2o0o
- Messages: 4
- Registration: January 18, 2019 - 11:22
- Installed WAPT version (1.6)
- Server OS (Linux Debian 9)
- Administration/package creation machine OS (Windows 10)
- Server OS (Linux Debian 9)
- Administration/package creation machine OS (Windows 10)
-
dcardon
- WAPT Expert
- Messages: 1932
- Registration: June 18, 2014 - 09:58
- Location: Saint Sébastien sur Loire
- Contact :
Good evening Nemesis2o0o,
The OK status of machines corresponds to the state they reported during their last inventory.
The connected state corresponds to the successful establishment of the websocket connection from the workstation to the server.
Sincerely,
Denis
The most likely problem is a time difference. By default, WAPT 1.6 allows a maximum time difference of 5 minutes to prevent replay attacks.nemesis2o0o wrote: ↑Jan 18, 2019 - 2:17 PM - WAPT version installed (1.6)
- Server OS (Linux Debian 9)
- Administration/package creation machine OS (Windows 10)
The OK status of machines corresponds to the state they reported during their last inventory.
The connected state corresponds to the successful establishment of the websocket connection from the workstation to the server.
Sincerely,
Denis
Denis Cardon - Tranquil IT
Share your experiences on WAPT! Send us your blog and article URLs in the "Your Opinion of the forum, and we'll feature them on the WAPT
Share your experiences on WAPT! Send us your blog and article URLs in the "Your Opinion of the forum, and we'll feature them on the WAPT
-
nemesis2o0o
- Messages: 4
- Registration: January 18, 2019 - 11:22
Thank you for your feedback, but I've double-checked and the time is correct.
However, I managed to fix the problem by reinstalling the wapt_agent package.
wapt-upgrade was present but wouldn't install.
Do you have any ideas?
Thank you.
However, I managed to fix the problem by reinstalling the wapt_agent package.
wapt-upgrade was present but wouldn't install.
Do you have any ideas?
Thank you.
