[pfSense] Carp locking up routers.
lists at pingle.org
Fri Jan 6 10:09:07 EST 2012
On 1/6/2012 9:40 AM, Bryant Zimmerman wrote:
> I have had another lockup with CARP. This is on three identical
> suprermicro systems. Running 2.0-RELEASE with 4 intel nic ports in each.
> What happens is the pfSense routers just stop sending or receiving
> traffic on all IP address CARP and non CARP.
> We could not access either unit from the net. I hooked in a console
> cable and the hardware was still responding but I did not have enough
> time to do any diagnostics. I had to reboot all of them to get traffic
> flowing again. And since they are nanobsd I have no saved logs after the
> reboot. This is really rendering CARP useless and I need some ideas on
> how to solve this.
No errors at all on the console?
Only issue I'm aware of that can lock at the moment isn't CARP related,
it's IPv6 related so only affects 2.1.
What kind of network interfaces do you have?
Any bridging, lagg, vlans, etc?
Any indications in the RRD graphs of something leading up to the lock?
Setting up a syslog server is a good suggestion in case something is logged.
You might also try (I can't remember if we enable this and I don't have
a HW firewall with a keyboard I can break at hand) to press ctrl-alt-esc
to see if it breaks into the debugger.
If it does get you to a db prompt, you can get a crash dump like so:
textdump set; capture on; run lockinfo; show pcpu; bt; ps; alltrace;
capture off; call doadump; reset
Then once it reboots it should offer to submit the crash report to us.
You could also try switching to the debug kernel, but make sure you take
a backup first in case it doesn't work as expected:
More information about the List