Hello,
Following the WAPT update from 1.5.1.22 to 1.5.1.23 on my Debian 9 Linux server,
all my machines appear as DISCONNECTED even though the status under 'Last seen on' indicates today's date.
The 1.5.1.23 agent has been successfully deployed, as well as the console.
WAPT Server version: 1.5.1.23
WAPT Agent version: 1.5.1.23
WAPT Setup version: 1.5.1.23
WAPT Deploy version: 1.5.1.23
Database status: OK (1.5.1.22)
Any ideas?
Thank you
[RESOLVED] Reachable DISCONNECTED following update
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
-
sfonteneau
- WAPT Expert
- Messages: 2318
- Registered: July 10, 2014 - 11:52 PM
- Contact :
Hello,
there's a problem with the clocks not being set correctly: viewtopic.php?f=10&t=1057&p=3372&hilit=horloge#p3372 ?
Simon
there's a problem with the clocks not being set correctly: viewtopic.php?f=10&t=1057&p=3372&hilit=horloge#p3372 ?
Simon
-
julienlevi
- Messages: 10
- Registration: May 4, 2018 - 09:18
Thank you so much!
After asking, I installed the NTP service, but it still didn't work.
So I added `signature_clockskew = 72000`
and it works!
After asking, I installed the NTP service, but it still didn't work.
So I added `signature_clockskew = 72000`
and it works!
-
sfonteneau
- WAPT Expert
- Messages: 2318
- Registered: July 10, 2014 - 11:52 PM
- Contact :
It would seem that either your server or your clients are not on time.
-
julienlevi
- Messages: 10
- Registration: May 4, 2018 - 09:18
Yes, it's strange. The BIOS clock is correct, but my Debian system is 2 hours ahead, even with the NTP service installed.
I manually reset the time on my Debian server, but the 'last seen on' timestamps are still 2 hours ahead.
I manually reset the time on my Debian server, but the 'last seen on' timestamps are still 2 hours ahead.
