Concerns with certain Reachable positions

[admin-style]

Good morning,
Following an update from wapt 1.3 to 1.5, I have some posts that continue to appear with the clock in the reachable column.

While browsing the forum I saw that this problem could be caused by a time difference between the wapt server and workstations.
That's not the case for me.

Even after removing the workstation from the inventory, uninstalling the agent, and reinstalling the agent, the problem persists on those workstations

I also notice that in the nginx error.log file I have quite a few lines like:

Code: Select all

2018/05/28 09:15:04 [error] 9967#0: *261412 open() "/var/www/wapt-host/54B94264-
163A-11E5-A793-4C72350A2200.wapt" failed (2: No such file or directory), client:
 10.72.148.36, server: _, request: "GET /wapt-host/54B94264-163A-11E5-A793-4C723
50A2200.wapt HTTP/1.1", host: "10.72.153.6"

Does anyone have any idea?

[sfonteneau]

Can you try doing a wapt-get register and give us the output?

The message you mention simply indicates that the machine package does not exist.

[admin-style]

Hello,
I just tested it on a machine that was having problems and I got the following response:
Host correctly registered against server https://10.72.153.6.

[admin-style]

Okay, I noticed:
- that by first removing the computer from the inventory
- then rebuilding the computer
- then installing the WAPT client,

I no longer had any recheable issues.

I'll continue this process for the few remaining problematic computers.

[CasseThor]

I asked the question, and in version 1.5,
your clients' clocks need to be completely synchronized with your server to be "OK".

[CHISFE]

Hello everyone
- WAPT version installed: 1.7.3.5
- Server OS: Windows 7 Pro
- Client machine OS: Windows 7 Pro 32-bit.

Could someone please help me resolve this "reachable" issue? The client machines in question are set to the same time as the WAPT server. I can't figure out where the problem is coming from.

Thank you in advance
. Sincerely,

[dcardon]

Hello CHISFE,

- WAPT version installed: 1.7.3.5
- Server OS: Windows 7 Pro
- Client machine OS: Windows 7 Pro 32-bit

Can someone please help me fix this reachable problem? The client machines in question are at the same time as the WAPT server. I can't figure out where the problem is coming from.

Could you please start a new thread? The versions are quite different between the 1.5 mentioned by the OP and yours. By the way, there's a new version available, 1.7.4, which fixes a number of bugs from version 1.7.3.

Sincerely,
Denis

[CHISFE]

Hello,

I installed the latest version of Wapt but the problem persists.

Regards