Web interface unresponsive

[mlabenda]

Hi there

I use pfsense quit a while and love it
today i setup a veeam replication from our office in germany to our CoLo in the US
This happens via an IPSec tunnel between pfsense and an Forigate 600 Firewall
we got really good bandwith through this tunnel ~ 18 Mbit sync ~140 ms latency

since the job started (seeding an USB drive backup plus final replication) the webinterface of my pfsense box is unresponsive

the hardware
Supermicro 1HE server
Core2Duo 2,97 GHz
4GB Ram
2 Intel onboard Nics 2 Intel Dual Port PCIe 4x
Transcend 2GB SataDom
pfsense 2.0.02 64bit release embedded

I'm connected on a 34 Mbit line, the other site is on 20Mbit

I can login to SSH but there is no way to get to the webinterface
device polling is not turned on

I guess the hardware should be enough for at least gigabit speed

top does show 100% idle and 0,0% interrupts when login on via ssh

openvpn does work
ipsec tunnels are up (i have 4)

should i go with device polling ?

any idea, what could cause this or where i could look ?

EDIT
fond this command
killall -9 php; killall -9 lighttpd; /etc/rc.restart_webgui

looks like this helped

is this maybe "just 64bit" related ?
#EDIT End#

[cmb]

Has nothing to do with the VPN if you can SSH in (and judging by your CPU load). May be the general problem with fastcgi crashing in 2.0.2 that's fixed in 2.0.3.

[mlabenda]

thx

[RLM]

I see the exact some thing here.
The firewall was running fine, but the GUI crashed about 3 hours after I put the FW into production.
NOT the best start of my pfSense experience :o(

And the double kill command fixed it.

Any way of validating that it is the cgi-crash that causes this?
(In this way I can live with having to restart php and lighttpd sometimes.)

Best

René Markvard

[Nachtfalke]

Try with pfsense 2.0.3 images which will come out soon:
http://forum.pfsense.org/index.php/topic,58203.0.html

[mlabenda]

good to know
will install once it is released

anything else ist fast and rocking stable any far better then any Fortigate we have in the US headquater  ;D

[Clouseau]

Confirm this issue - My firewall GUI just halted totally - Can't access gui at all and console is not awailable. SSH/telnet menu is not enabled. This is a bit problematic issue and must be fixes ASAP :o

[marcelloc]

@Clouseau:

Confirm this issue - My firewall GUI just halted totally - Can't access gui at all and console is not awailable. SSH/telnet menu is not enabled. This is a bit problematic issue and must be fixes ASAP :o

Clouseau, did you read all the topic???

The problem and the solutions is already posted…

@cmb:

May be the general problem with fastcgi crashing in 2.0.2 that's fixed in 2.0.3.

@Nachtfalke:

Try with pfsense 2.0.3 images which will come out soon:
http://forum.pfsense.org/index.php/topic,58203.0.html

[Clouseau]

Yes - I read the topic, BUT I can't fix the situation by killing php and lighttpd and restarting webgui service- I need to fix this NOW, not in next release!

Reboot does not help either.

[marcelloc]

@Clouseau:

I need to fix this NOW, not in next release!

So apply the 2.0.3 pre-release upgrade or buy commercial support to have the instant help you need.

[Clouseau]

:)

There is no comercial support that can fix this issue onsite(s). Now I have lost 4 gui's from pfSense firewalls. Is there any idea what's causing it?

[cmb]

What I said earlier in the thread, some people are hitting fastcgi crashing in 2.0.2, upgrade to 2.0.3 or gitsync.

[Clouseau]

@cmb:

What I said earlier in the thread, some people are hitting fastcgi crashing in 2.0.2, upgrade to 2.0.3 or gitsync.

Yes yes - that's clear - now I just needed to get gui up again. Kill php and lighttpd and double restarting the webConfugurator helped.

[mehov]

Hello,acording to my experience, 2.1 Beta1 still have this issue, the dying webconfigurator thing…