Re: [pfSense] 502 Bad Gateway

2016-07-07 Thread J. Echter
i forgot to mention:

pfSense 2.3.1.

It works again if i restart php-fm.

J
___
pfSense mailing list
https://lists.pfsense.org/mailman/listinfo/list
Support the project with Gold! https://pfsense.org/gold


Re: [pfSense] 502 Bad Gateway

2016-07-07 Thread J. Echter


Am 05.07.2016 um 19:19 schrieb Bill Arlofski:
> Hi everyone...
> 
> I noticed after one of the recent upgrades to the 2.2.x "RELEASE" series
> everything works perfectly fine for a while but then, I get "502 Bad Gateway"
> message when I attempt to access the web GUI.
> 
> Up until recently, I had been "fixing" this by physically powering off the
> firewall by pushing the power button which causes a clean shutdown. Then I
> would power it back up and it works fine for a random amount of time - usually
> days or weeks, sometimes even months - but this last time it only lasted about
> 23 hours.
> 
> I am currently running the 2.3.1-RELEASE-p5 (amd64) nanobsd (4g) distribution.
> 
> Today, I have enabled the ssh service and checked the nginx*.log files and I 
> see:
> 
> [2.3.1-RELEASE][usern...@vai.revpol.com]: clog -f /var/log/nginx-error.log
> 
> 8<
> 2016/07/05 12:40:01 [error] 48883#0: *257237 upstream timed out (60: Operation
> timed out) while reading response header from upstream, client: 192.168.254.4,
> server: , request: "GET /getstats.php HTTP/1.1", upstream:
> "fastcgi://unix:/var/run/php-fpm.socket", host: "vai.revpol.com:4443",
> referrer: "https://vai.revpol.com:4443/";
> clog: ERROR: could not write output (Bad address)
> 8<
> 
> 
> At that same time, system.log shows that the php-fpm.socket socket does not 
> exist:
> 8<
> Jul 5 12:47:00 vai vai.revpol.com nginx: 2016/07/05 12:47:00 [crit] 48883#0:
> *257442 connect() to unix:/var/run/php-fpm.socket failed (2: No such file or
> directory) while connecting to upstream, client: 192.168.254.4, server: ,
> request: "GET /getstats.php HTTP/1.1", upstream:
> "fastcgi://unix:/var/run/php-fpm.socket:", host: "vai.revpol.com:4443",
> referrer: "https://vai.revpol.com:4443/";
> 8<
> 
> 
> From the console menu, I can choose option 16 (Restart PHP-FPM), and then the
> web gui is accessible again.
> 
> Enter an option: 16
> 8<
 Killing php-fpm
 Starting php-fpm
> *** Welcome to pfSense 2.3.1-RELEASE-p5 (amd64 nanobsd) on vai ***
> 8<
> 
> So, I am suspecting that the php-fpm process is dying (forgot to run a ps
> command before restarting it).
> 
> Right now, /tmp/php_errors.txt is a zero byte file but I suspect that may be
> due to the restart of php-fpm due to its timestamp. I will take a look at this
> file the next time the gui dies.
> 
> 
> Is there anything I can do to increase debugging to help identify why this
> process is dying?
> 
> Additional info:  Typically I have a Firefox tab "idling" on the dashboard
> page which includes the "Traffic Graphs" widget with 4 graphs,
> Autoscale=Follow and 1 second updates.
> 
> 
> Thanks!
> 
> Bill
> 

Hi,

same issue here. I cannot access OpenVPN after a while and locally i get
bad gateway when connecting to pfSense webui.

J
___
pfSense mailing list
https://lists.pfsense.org/mailman/listinfo/list
Support the project with Gold! https://pfsense.org/gold


Re: [pfSense] 502 Bad Gateway

2016-07-07 Thread Jim Thompson
I run the widget on my dashboard without issue. 

Please stop assuming there is a problem, and take steps to prove it instead. 

-- Jim

> On Jul 7, 2016, at 1:16 PM, Bill Arlofski  wrote:
> 
>> On 07/07/2016 08:09 AM, Jon Gerdes wrote:
>> Bill
>> 
>> I maybe off target here but the IPSEC widget used to cause php-fpm
>> daemon to die after a few days.  
>> 
>> I haven't looked into it since but removing that widget fixed it for me
>> on two pfSenses.
>> 
>> Cheers
>> Jon
> 
> Hi Jon,
> 
> Hmmm, I do have the IPsec widget on my dashboard, so this is at least
> somewhere to start. :)
> 
> I guess I will remove it the next time this happens and see if there is any
> change.
> 
> Do you know if this is a known (and reported) issue?
> 
> Thanks for the response.
> 
> Best regards,
> 
> Bill
> 
> 
> -- 
> Bill Arlofski
> Reverse Polarity, LLC
> http://www.revpol.com/
> -- Not responsible for anything below this line --
> ___
> pfSense mailing list
> https://lists.pfsense.org/mailman/listinfo/list
> Support the project with Gold! https://pfsense.org/gold
___
pfSense mailing list
https://lists.pfsense.org/mailman/listinfo/list
Support the project with Gold! https://pfsense.org/gold


Re: [pfSense] 502 Bad Gateway

2016-07-07 Thread Vick Khera
On Thu, Jul 7, 2016 at 2:16 PM, Bill Arlofski 
wrote:

> I guess I will remove it the next time this happens and see if there is any
> change.
>

It seems to me you should remove it *before* to see if you avoid it
happening.
___
pfSense mailing list
https://lists.pfsense.org/mailman/listinfo/list
Support the project with Gold! https://pfsense.org/gold


Re: [pfSense] 502 Bad Gateway

2016-07-07 Thread Bill Arlofski
On 07/07/2016 08:09 AM, Jon Gerdes wrote:
> Bill
> 
> I maybe off target here but the IPSEC widget used to cause php-fpm
> daemon to die after a few days.  
> 
> I haven't looked into it since but removing that widget fixed it for me
> on two pfSenses.
> 
> Cheers
> Jon

Hi Jon,

Hmmm, I do have the IPsec widget on my dashboard, so this is at least
somewhere to start. :)

I guess I will remove it the next time this happens and see if there is any
change.

Do you know if this is a known (and reported) issue?

Thanks for the response.

Best regards,

Bill


-- 
Bill Arlofski
Reverse Polarity, LLC
http://www.revpol.com/
-- Not responsible for anything below this line --
___
pfSense mailing list
https://lists.pfsense.org/mailman/listinfo/list
Support the project with Gold! https://pfsense.org/gold


Re: [pfSense] 502 Bad Gateway

2016-07-07 Thread Jon Gerdes
On Tue, 2016-07-05 at 13:19 -0400, Bill Arlofski wrote:
> Hi everyone...
> 
> I noticed after one of the recent upgrades to the 2.2.x "RELEASE"
> series
> everything works perfectly fine for a while but then, I get "502 Bad 


--- snip 

> 
> So, I am suspecting that the php-fpm process is dying (forgot to run
> a ps
> command before restarting it).
> 
> Right now, /tmp/php_errors.txt is a zero byte file but I suspect that
> may be
> due to the restart of php-fpm due to its timestamp. I will take a
> look at this
> file the next time the gui dies.
> 
> 
> Is there anything I can do to increase debugging to help identify why
> this
> process is dying?
> 
> Additional info:  Typically I have a Firefox tab "idling" on the
> dashboard
> page which includes the "Traffic Graphs" widget with 4 graphs,
> Autoscale=Follow and 1 second updates.
> 

Bill

I maybe off target here but the IPSEC widget used to cause php-fpm
daemon to die after a few days.  

I haven't looked into it since but removing that widget fixed it for me
on two pfSenses.

Cheers
Jon



 
___
pfSense mailing list
https://lists.pfsense.org/mailman/listinfo/list
Support the project with Gold! https://pfsense.org/gold