Kernel Panic
-
Thanks very much for the efforts…
2.0-BETA5 (i386)
built on Thu Feb 17 02:14:25 EST 2011
Dell Poweredge 860
Intel Pentium D CPU 2.80GHz
2 gigs ram.
Openvpn client export plugin is the only plugin installed.
pptp server for remote clients.
1 Wan, 1 LAN, no CARP, 4 IP Alias VIPs
1 ipsec tunnel to other another pfsense endpoint
2 ipsec tunnels to cisco routersCrash happened during normal operations with no changes being made. I did have a browser tab connected to the GUI with the dashboard page up. there are two
-
@ermal:
I just put a patch up.
The snapshot has to build but when it comes out try with that.I was taking a peek at the repository and noticed the last commit by ermal was on Feb 16.
Is this the correct URL to find out what went into the latest snapshot?
https://rcs.pfsense.org/projects/pfsenseThis is the only commit on Feb 18 (as of 4:29 PM CST):
06:42 cmb pushed c7d56176 to pfsense/mainline on branch master -
It's in the pfsense-tools repo, not just pfsense.
-
It's in the pfsense-tools repo, not just pfsense.
Thanks! Seems I was missing half the action!
-
Now I feel like I'm missing the action. I still can't find a new snapshot.
-
I just upgraded from 1.3 to the latest 2.0 RC1 snapshot and I'm getting the dreaeded malloc kernel panic. This is happening on two machines in a vmware esxi environment. It basically just keeps rebooting. I see there is a bug report about vmware tools causing the issue. How do I go about uninstalling vmtools?
Thanks! -
My 2 CARP boxes have been running on the Beta5 build from Mon Feb 21 19:15:26 EST 2011 without any issues for 9 days, 14:12.
-
Per Jim P, I followed his comment: "Boot to single user mode, touch /conf/needs_package_sync, and then reboot."
That seems to have fixed the issue.
-
i just installed snort package today. it seems to be working fine but after some time causes kernel panic. i remove snort and observe the box to see what happened. if the panic will occur again i take a pic.
i use the latest RC1 build.
-
locking this thread because people keep hijacking it, the original issue is resolved, start a new thread if you have an issue.