Page 1 of 1

[SOLVED] Nginx “Bad Gateway” error

Published: January 6, 2020 - 11:42 AM
by Raphael
Hello and best wishes.

I'm currently testing Wapt on a Hyper-V VM.
The installation went smoothly, and the workstations are reporting correctly.
However, after a while, the connection to the server is intermittent, failing to connect
via either the console or the web interface.
Access to the repository is fine.
If I restart the virtual machine, it works again.
I've attached screenshots.

Could this be due to insufficient RAM? (My test machine has only 6GB, with 2GB allocated for the VM.)

Thank you in advance.
Raphaël Larronde.

Wapt server 1.7.4 Debian in a Hyper-V VM running Windows Server 2012 R2.
WaptConsole running Windows 10.

Re: Nginx “Bad Gateway” error

Published: January 6, 2020 - 2:33 PM
by dcardon
Hi Raphael,

2GB should be enough for a normal Linux installation. However, with Windows Server 2012 R2 running Windows Update, I'm not sure it will be sufficient, and the OOMkiller might start using a lot of resources. Is there any information in the Event Viewer?

How many user workstations are on the network? If the agent deployment is rapid and all agents try to register and upload their inventory simultaneously, that could also increase RAM consumption.

Best regards,

Denis

Re: Nginx “Bad Gateway” error

Published: January 6, 2020 - 4:27 PM
by Raphael
No, nothing unusual in the observer.
My tests were conducted during the holidays, with virtually no access.
Since this morning, and despite everyone returning to work and numerous connections, it's working.
160 jobs were reported today (I emptied the database on the server).

I'm going to increase the server's RAM anyway; I'll keep you posted.
Thanks for everything

Re: [SOLVED] Nginx “Bad Gateway” error

Published: January 13, 2020 - 4:44 PM
by Raphael
Hello.
I can confirm the RAM is insufficient: 4GB is needed in my case.
Have a good day.