Gateway timeout when trying to view Snapshot and Maintenance page

[JesseLambBDK]

I am receiving a 504 gateway and timeout page when trying to access the Snapshot and Maintenance page. I have tried the steps found in other timeout threads on adding

Timeout 600
RequestReadTimeout header=600,minrate=50
RequestReadTimeout body=600,minrate=50
<Proxy "unix:/run/php-fpm/www.sock|fcgi://localhost">
ProxySet timeout=600
</Proxy>

to the php.conf file and restarting the httpd service. That page still times out. Any suggestions?

[jmichaelson]

Edit /var/www/html/nagioslogserver/application.config/config.php. around line 226, replace $config['log_threshold'] = 0; with $config['log_threshold'] = 1; The number can go all the way up to 4 per the comments above it, depending on how verbose you want the logging to be. Lets start with 1 for just error messages. The log files then will be in /var/www/html/nagioslogserver/applicaton/logs. You can scan them for errors when you're looking at that page, or post here for more help.

[halimm]

I'm having the same issue as well. However I tried to enable the logging as per previous comment but no log appeared.

[collapsebells]

I am receiving a 504 gateway and timeout page when trying to access the Snapshot and Maintenance page. I have tried the steps found in other timeout threads on adding

Timeout 600
RequestReadTimeout header=600,minrate=50
RequestReadTimeout body=600,minrate=50
<Proxy "unix:/run/php-fpm/www.sock|fcgi://localhost">
ProxySet timeout=600
</Proxy>

to the php.conf file and restarting the httpd service. That page still times out. Any suggestions?

A 504 here usually isn’t Apache, but PHP-FPM/PHP itself timing out. Try:

In php.ini: max_execution_time = 600

In php-fpm.conf/pool: request_terminate_timeout = 600s

Restart php-fpm + httpd.

Also check logs to see if the snapshot script is stuck or too heavy — might need to run it via CLI.

[shali012]

Hi,mp bhulekh
Thanks for sharing this information.

[shali012]

Hi,
I’m facing a gateway timeout error whenever I try to open the Snapshot and Maintenance page. Can this issue be checked and resolved?

[jmichaelson]

Out of curiosity which version of Log Server are you all using?

Do you know (and you might have to take a guess or look at where the snapshots are stored), how many snapshots you have? Depending on the version of NLS you're using this may be the reason; there was a bug we fixed for this, and I'm trying to find where the fix was, but knowing the version you're on would help determine if that's even a possibility here.