PFSense 2.0 Beta5 1/19 build system locks up
-
BTW can all here execute sysctl debug.pfftpproxy=1 and report if the hangs continue?
-
doing it now, had two hangs this morning just prior to upgrading to Jan 28 snap. both master and slave pretty much hung at the same time, leading me to believe that it could be traffic type related.
-
also i face this problem, lockups and freeze, I update my server in 21/1/2011,
then i face this problem, and update to Tue Jan 25 06:07:53 EST 2011 and face it also.
i think the problem in Jan 19 and above.
thanks -
-
so is the current thinking on this FTP traffic? I do not have an FTP server so is this outbound FTP connections? Please let me know if there are configs, system logs, pretty much anything I can provide or do to assist in getting this cleared up. If I have any more lockups I will be forced to load up 1.2.3 release unfortunately.
-
I've only been able to replicate it when acting as an FTP client. And it's fairly erratic, I could hang a testing VM up solid earlier today but I came back to get some captures and do some in-depth analysis and now I can't hang it.
-
jimp, just i tell thank all version after 19/1/2011 have this problem.
I back to 2.0-BETA5 (i386) built on Wed Jan 19 02:10:47 EST 2011.
pfSense-Full-Update-2.0-BETA5-i386-20110118-2149.gz <=== this version not has any problem.
thanks -
Just found something else funny, the reason I couldn't hang my VM is that I switched it to the dev kernel. I switched back to the SMP kernel and I can hang it again.
So something about the dev kernel is making it less prone to hangs. (Can't say it's immune, haven't tested it long enough)
-
I switched back to the SMP kernel and I can hang it again.
FYI, the physical machine that was hanging last night was, I believe, running the single processor kernel. It definitely is now after I reinstalled the old snapshot, but since there's just one 2.4GHz P4 in there I did the single proc kernel (not sure if I should use the multi-proc kernel if it's a hyperthreaded proc or not).
-
Generally it's best to use the SMP kernel everywhere, even on single CPU machines. In the past that wasn't recommended, but the limitations don't really exist anymore (we've talked about dropping the UP kernel altogether but haven't yet done it, just in case…)
-
OK I hadn't seen anything about it so I just followed what was physically in the machine during the install process. I will keep that in mind though. Is it worth specifically switching in this case? I know I can drop in the SMP one without reinstalling if I look up the steps.
-
The UP and the SMP kernel probably aren't going to be that different as far as this thread is concerned. It's the developer kernel that seems to fare better, though it will also perform slower due to the other debugging overhead.
-
Just found something else funny, the reason I couldn't hang my VM is that I switched it to the dev kernel. I switched back to the SMP kernel and I can hang it again.
So something about the dev kernel is making it less prone to hangs. (Can't say it's immune, haven't tested it long enough)
Agreed. i have no measurable proof but this matches with my experience on this issue. I can still get a lockup using a FTP client with the dev kernel but on average it takes more tries than with SMP.
-
Commits just went in that should stop the hangs. The next new snapshots should have them. They are building right now, so they won't be uploaded until sometime in the early morning. The current run just finished but it doesn't have these fixes in it.
-
Works like a charm, no more freezes when I try to connect via FTP!
Thanks!
;D ;D ;D
2.0-BETA5 (i386)
built on Fri Jan 28 14:23:00 EST 2011 -
a few days ago I switched from my net5501/nanobsd to a Dell PC running I386 SMP full version. everything was running fine until I upgraded to "Sat Jan 29 01:09:59" and tried to connect to a remote site via IPsec site-site VPN. it immediately hard locked and had to be power cycled.
no packages installed
not using openvpn
no ftp traffic
single WAN and LAN
debug.pfftpproxy set to 1
running 4 Intel Pro 100 NICsEdit: went back to "Fri Jan 28 14:23:00" and everything is back to normal. :)
Roy…
-
Upgraded and have the same problem.
However, it seems to be triggered by several different triggers. Not sure what mine is yet, but it appears to have to do with the webConfigurator. -
Yep know issue.
With the snapshot that will come late today everything has been fixed from what our testing shows. -
Hi,
Just performed an upgrade to this snapshot (have been running one from ~26th).
Now pfsense doesn't boot anymore.It didn't continue after displaying "Configuring Gateway Monitors".
I was continuously pinging the pfsense box from its lan side during boot and got exactly one reply back in between.
I then did a hard reset which led to that pfsense stopped loading further just one output line before configuring gateway monitors (if I remember correctly).
Silly me didn't take a screen capture of the first (regular) boot. I only have one after the reset :(
-
I don't know, maybe it's related to http://forum.pfsense.org/index.php/topic,32767.0.html since I have a few site-to-site ipsec tunnels configured and those remote hosts would try re-connecting all the time.. but I didn't want to hijack that thread..
