Tranquil IT Forum

Hello,

- WAPT version installed: 1.7.3.3
- Server OS Windows
- Administration/package creation machine OS: Windows 7


We are experiencing the exact same problem accessing the WAPT console described in the forum thread:
viewtopic.php?f=13&t=1698

We have run all the commands mentioned and updated the server as instructed, but nothing works.

Thank you for your help.

Hello,

Having received no information on how to resolve this issue, we were forced to completely uninstall WAPT after copying the "repository" folder. We then reinstalled WAPT 1.7.3.5 and copied the folder back.

The console is working again, but despite copying the folder, we didn't get the list of hosts with their information "directly." However, they reappear in the console as the PCs are powered on, and they are communicating with the server correctly. The problem seems to be resolved for now.

Do you have any idea what might have happened to prevent this from happening again, as we hadn't made any changes?

Sincerely,

Hello verdierr,

verdierr wrote: ↑May 3, 2019 - 9:46 AM Having received no information on how to resolve this issue, we were forced to completely uninstall WAPT after making a copy of the "repository" folder. We then reinstalled WAPT 1.7.3.5 and copied the folder back.

The console is working again, but despite copying the folder, we didn't get the list of hosts with their information "directly." However, they reappear in the console as the PCs are powered on, and they are communicating with the server correctly. The problem therefore seems to be resolved for now.

The display of workstations in the console is based on the contents of the PostgreSQL database. The workstation configuration is contained within the WAPT packages. Therefore, it's normal that you no longer see the workstations after the reinstallation. However, as you mentioned, the inventory is automatically recreated when workstations reconnect. You could have potentially performed a dump of the PostgreSQL database and reloaded it afterward.

We will look into enabling a simple partial JSON extraction to retrieve the posts in the case you indicate.

verdierr wrote: ↑May 3, 2019 - 9:46 AM Do you have any idea what might have happened so that it doesn't happen again, since we hadn't made any changes?

Did you encounter these problems after upgrading from 1.5 to 1.7.3?

Sincerely,

Denis

Hello Denis,

dcardon wrote: ↑May 3, 2019 - 5:56 PM Did you encounter these problems after upgrading from 1.5 to 1.7.3?

No, we were on version 1.7.3; the problem occurred without any changes being made to the WAPT server

This WAPT server is hosted on a new ESX host, and we had almost the same problem with another virtual server hosted on that same ESX host
I think the problem was more likely with the ESX and a power outage