Kernel Panic
-
I was able to make my CARP slave fail again (seems reproducable) - I was changing the mtu's back to default, if making one change and applying it things seemed fine, when I changed a few of them and applied them but applied changes after a few (maybe 5) then it hung.
I will update to the latest snap and see if I can make it fail again…
-
I updated my CARP backup to the latest snap - Thu Feb 17 02:14:25 EST 2011 - and ran through similar motions that caused the panics before with no issues. I have updated my master as well and will update if things fail again.
-
Can any of you with the pf_state_tree_id_RB_REMOVE_COLOR panic
try and set debug.pfpptpproxy=1 and see if they get the panic? -
Sure, let me now how to do it (sorry) and if I get the panic running today's snapshot that can be my next step.
-
Remember messing with the GUI when this happened, and then it stopped working… and then that.
-
Please give info on each screenshot you put in here.
Its absolutely required the date of the snapshot and how the box is cofnigured: carp, vlan, pptp,….@ acherman
Go to system->Advanced->System tunables->Click +(at the end)Tunable: debug.pfpptpproxy
Value: 1
Description: Testing pptp fixClick save and try to see if it panics still.
-
Had 3 panics on my CARP master and 1 on my backup - I assume they were panics, lost comms to them but no physical access, just cycled power remotely. I just entered the tunable requested, I will update when/if something happens. I will upload a drawing of my network config when I get to the office, as well as more config details.
-
Had another panic on my master this morning as I was doing up a quick drawing - looks like the same situation, even with the pptp tunable noted by ermal. It ran fine for almost 14 hours yesterday before the first one last night (from 9:05 am to 10:56 pm). Anyway, screenshots from this mornings panic:
Now, here is a basic layout of my config:
Directly connected to the Sync interface is an identical box with all other interfaces running in parallel. Our WAN is a static connection. DHCP is served out to our corp LAN, remote office LAN, and a couple of our WiSP VLANs (625, 626) - I do not have the CARP backup DHCP turned on. The only VPN I have configured is OpenVPN (one server connection). The only package installed is the OpenVPN client config export utility. I do have a number of virtual IPs configured for inbound and outbound NAT. No traffic shaping turned on. I think that's it for special stuff, let me know if more is required, or I can upload my config files.
I am still running on the build from Thu Feb 17 02:14:25 EST 2011, with the pptp fix tunable noted by ermal.
-
I just put a patch up.
The snapshot has to build but when it comes out try with that. -
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.
