PFSense 2.0 Beta5 1/19 build system locks up

mxx · Jan 29, 2011, 1:20 PM

@ermal:

As i said already it was a known issue and you have to wait for the snapshot of late today to test which
has commit https://rcs.pfsense.org/projects/pfsense-tools/repos/mainline/commits/ff8cebdea1046caacd263cab2b39053b629d3a83 in it.

Hi ermal, is it ok to just manually apply that commit or would this break something as it may depend on something else that's changed?

clahti · Jan 29, 2011, 8:51 PM

so I have been on the Fri Jan 28 05:30:15 EST 2011 snap with the debug.pfftpproxy set to 1 and so far I have an uptime of 27+ hours (woo hoo). I am in the office today to build a 1.2.3 emergency system to slap in if the current 2x cluster goes down again, but as far as I can tell it seems stable at the moment. In reading the recent posts to this thread I gather that I should wait for Sunday snap since today's brings back problems for some people. ermal, you requested configs from people with this lockup issue, do you still need this? I can send to you if so, I am using CARP on two WAN and one LAN interface, but no ipsec or openvpn as our VPN traffic is port-forwarded to a different server inside the firewall.

eri-- · Jan 29, 2011, 10:04 PM

if the hangs do not occur no i do not need the config anymore.

rpsmith · Jan 30, 2011, 6:40 AM

i386, Full, SMP, Sat Jan 29 15:43:14:

So far everything looks solid! No more Hard Locks when using IPsec tunnels!

Roy…

ivanmar · Jan 30, 2011, 7:06 PM

It seems this problem still exists.
Using built on Sat Jan 29 23:42:13 EST 2011 and PPTP VPN server and hat 2 locks during this day.
Now I will disable vpn server until this issue is resolved. Can not do onsite debugging because this is remote production firewall. I need to make it sable for now: Will downgrading to pre 19th help?

eri-- · Jan 30, 2011, 7:24 PM

Just put a debug.pfftpproxy=1 and that will remove the hang.

ivanmar · Jan 31, 2011, 4:05 PM

I had 18h uptime, than again lock.
debug.pfftpproxy is set to 1
and enabled PPTP server

clahti · Jan 31, 2011, 4:35 PM

Running Fri Jan 28 05:30:15 EST 2011, I now have an uptime of 2 days, 23 hours. I am going to hold off upgrading to newer snapshots for the moment :).

clahti · Jan 31, 2011, 4:52 PM

Also as an aside, should we be putting debug.pfftpproxy=1 somewhere in a config file to survive a reboot?

ivanmar · Jan 31, 2011, 5:11 PM

put it in system -> advance -> system tunables

I returned to 18.01 snapshot and hopefully avoid this issue

eri-- · Jan 31, 2011, 7:36 PM

ivan mar are you running amd64 snapshots?

rpsmith · Jan 31, 2011, 7:56 PM

ermal,

does debug.pfftpproxy=1 still disable both the ftp and pptp proxy?

Roy…

ivanmar · Jan 31, 2011, 8:07 PM

No Ermal, it is i386. Last was 29.01 snapshot

mxx · Jan 31, 2011, 8:31 PM

I just tested downloading via ftp does work using a web browser. I can't imagine that noone in the company downloaded files via ftp, but could very well be that there wasn't much ftp traffic in the last days.

How would I properly test this to trigger a lock up? Does it only apply to passive ftp?

eri-- · Jan 31, 2011, 10:10 PM

What hw setup you have there ivanmar?

ChristianHaag · Feb 1, 2011, 9:13 AM

Installed snapshot from January 31st yesterday and system froze after 20 minutes. 4 freezes with 20-60 minutes interval so far. System freezes completely, no keys are accepted anymore. There were no configuration changes when the system froze. Potentially ftp from client side was used as we have a couple of cron’ed jobs.

I’d exclude the hardware. It is a HP server running the late December snapshot without any hassle throughout January. It was running earlier 2.0 version since November and before 1.X versions for 2 years. Nothing has changed concerning hardware.

I have been going back to snapshot from January 6th. I did not add debug.pfftpproxy=1.

Sorry, I can not provide any helpful hints as there was nothing to see on the console. All I can do is provide you with the information that there still seems to be an issue.

Can I access older snapshots?

arthurmolnar · Feb 1, 2011, 1:36 PM

My server freeze an display error.

I have RC5 snapshot 20110121 and update firmware everyday but in all updates freeze the server.

I don't have access via IP and via console. I have shutdown my server via
buttom power-off

I install OS PFSENSE in two servers and do same error

Error in attach

Tks.
Arthur Molnar

ChristianHaag · Feb 1, 2011, 3:06 PM

Arthur,

Probably you check this thread: http://forum.pfsense.org/index.php/topic,31721.0.html

I have some issue with the current release too, this is the thread where I added them: http://forum.pfsense.org/index.php/topic,32458.75.html

Because I am running pfSense 2.0 Beta in production environment (more adrenalin => less coffee required) I went back to the snapshot from January 6th, which is running fine now for the whole day here.

Chris

arthurmolnar · Feb 1, 2011, 4:38 PM

I need to snapshot at January 6th for tests.
In repository of snapshots have January 7th or more recent.

where i find ?

ivanmar · Feb 1, 2011, 5:16 PM

Hi Ermal,
hardware for my firewall is all mainstream (intel chipset, realteck lan…). Locks were occurring on uniprocessor and SMP kernels. Only specific thing is it that pptp vpn server is used and zabbix client was installed. I removed zabbix client and returned on 18.01 snapshot. Now I have 24h uptime. Will report here if something happen. Tomorrow I will try to be more helpful and do some onsite debugging.