PFSense 2.0 Beta5 1/19 build system locks up
-
I was running 2.0 built in 1/7/11 with no stability problems and then upgraded to the builds on 1/19/11 both builds caused stability issues where the system would lock up after a few hours. After a reboot the system would work fine again for a while. I'm fairly certain this is a bug in pfsense but I was asked to post this in the forums instead of in the bug tracker.
-
Any idea what may have been happening at the time of the lockup?
I'm running the i386 build from "Wed Jan 19 02:10:47 EST 2011" on my home router and it's been solid for around 24 hours now, and I beat it up pretty harshly.
-
The first two times I was out of the office and only a couple people were web browsing and receiving email (exchange server). Today it locked up right after starting an ftp download.
-
FTP may be somewhat more likely, there have been changes to the in-kernel FTP proxy over the past few days.
-
Can you replicate it by accessing an FTP site? Or is it hit and miss?
Someone else noticed that it might be two FTP connections to the same site one right after another that might be to blame
-
Also, you can try to disable the FTP proxy and see if you can reproduce the lockup:
System > Advanced, System Tunables page. Add one that sets debug.pfftpproxy to 1.
-
One more thing to try if none of that helps, you could switch to a debug kernel:
http://doc.pfsense.org/index.php/Switching_Kernels -
I have had two lockups since the 1/19 update as well. First lockups I have had since I start using the beta over a month ago. I thought this was related to the PPTP VPN fix, but it was suggested that this was a separate issue. I have not used FTP since this update and am still experiencing lock ups.
-
Can you still try to disable the FTP proxy to see if it happens?
You may not know you're using FTP, but there could be something running somewhere on your network that fetches files/updates/packages by FTP that isn't as obvious.
-
OK, it's definitely FTP… I just reproduced it on my home router.
-
OK. I set debug.pfftpproxy to 1 and I can no longer connect to a PPTP VPN. If I set the flag to 0, I can connect, set it back to 1 and cannot connect. I'm not sure why or how these are related, but they appear to be.
-
I checked with Ermal (the author of the FTP and PPTP proxies) and he said at the moment that does disable them both, though it didn't seem to be entirely intentional.
He's working on replicating the issue and fixing it now.
-
I've also had the lockup occur during pptp vpn. I believe it was the pptp connections that triggered the other lockups i reported and not the web browsing.
-
It may be then, but I have no PPTP activity on my network and yet it still locked up, and it locked up precisely when I did a LIST on an FTP site.
A couple more patches hit the repo this afternoon so the next snapshot will be worth trying, but it probably won't be uploaded until later tonight/early tomorrow.
-
FYI- On today's snap, I can no longer induce the lockup with FTP. Haven't tried PPTP yet though.
I still get failed LIST command using passive FTP (and active even more so) but the router isn't seizing, which is a good thing…
-
I just updated to todays snapshot. Should know within a couple of hours if I am still getting the PPTP lockup.
-
Looks like there is a solid lead on the remaining FTP issue(s), so a fix should be coming along before too long.
-
I'm using 2.0-BETA5 (i386) built on Fri Jan 21 09:14:03 EST 2011 and still experiencing the lockups immediately after starting an ftp transfer using filezilla.
-
I'm on the one from overnight:
2.0-BETA5 (i386)
built on Thu Jan 20 20:59:52 EST 2011Can you try to load that one and see if there is any difference?
I tried both active and passive FTP and I was able to use both, but very spotty results.
There are more FTP changes to come though, so it may not really be fixed quite yet. It probably won't be on a snap from today, but maybe one from tomorrow, depending on when the patch goes in.
-
Very UNHAPPY to report my first lockup with PFSENSE since we've been using it.
Something is broken on today's snapshot. Had to power cycle to get it up again. One step forward two steps backward ;D
Does anyone know if this bug is replicated in the 64 version? We are going back to the 64 bit version on a backup box with a week old snapshot and not updating until a fix is confirmed.
