504 Gateway Timeout-FOG 1.5.2



  • FOG 1.5.2 on Fedora 26…504 error Gateway timeout 8 Gb RAM 8 cores…not being pushed really but can’t get in.

    Gateway Timeout
    The gateway did not receive a timely response from the upstream server or application.

    /var/log/httpd/error_log

    [Fri Apr 20 08:12:44.762878 2018] [proxy_fcgi:error] [pid 19788] (70007)The timeout specified has expired: [client 10.72.2.29:61043] AH01075: Error dispatching request to : (polling), referer: http://10.72.3.50/fog/management/index.php?node=home
    [Fri Apr 20 08:13:11.601087 2018] [proxy_fcgi:error] [pid 46536] (70007)The timeout specified has expired: [client 10.72.2.29:61048] AH01075: Error dispatching request to : (polling), referer: http://10.72.3.50/fog/management/index.php?node=home
    [Fri Apr 20 08:14:39.319873 2018] [proxy_fcgi:error] [pid 46536] (70007)The timeout specified has expired: [client 10.72.2.29:61055] AH01075: Error dispatching request to : (polling), referer: http://10.72.3.50/fog/management/index.php?node=home
    

    /var/log/php-fpm/www-error.log

    [20-Apr-2018 11:57:04 UTC] PHP Notice:  A non well formed numeric value encountered in /var/www/html/fog/status/bandwidth.php on line 109
    [20-Apr-2018 11:57:04 UTC] PHP Notice:  A non well formed numeric value encountered in /var/www/html/fog/status/bandwidth.php on line 110
    [20-Apr-2018 11:57:04 UTC] PHP Notice:  A non well formed numeric value encountered in /var/www/html/fog/status/bandwidth.php on line 110
    

    Please help

    **Update…Turning off support node in same group as master, and upping memory in [FogSettings] to 4096 from 2048 seemed to relieve this issue (guessing here)



  • @tom-elliott I think you can close this…apparently one node (of the 8) missed an upgrade and was still running odler version…I’ll keep an eye on it this week to confirm.


  • Senior Developer

    Unsure how this is a bug.

    Essentially the information is saying it cannot reach the destination. So it’s timing out. Not much I can do programmatically to fix this.


 

443
Online

5.4k
Users

12.6k
Topics

118.8k
Posts