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.
HTTP/1.1 504 Gateway Timeout
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
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,
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,
-
dcardon
- WAPT Expert
- Messages: 1932
- Registration: June 18, 2014 - 09:58
- Location: Saint Sébastien sur Loire
- Contact :
Hello verdierr,
We will look into enabling a simple partial JSON extraction to retrieve the posts in the case you indicate.
Sincerely,
Denis
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.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.
We will look into enabling a simple partial JSON extraction to retrieve the posts in the case you indicate.
Did you encounter these problems after upgrading from 1.5 to 1.7.3?
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
Hello Denis,
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
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
