Concerns with certain Reachable positions
Published: May 29, 2018 - 09:07
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:
Does anyone have any idea?
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"