Crash/kernel panic - reboot twice in short time
-
Hi there.
What about loading pfSense in a stand alone 'PC' ?
This will rule out the VM and hardware factor. -
Real HW is not possible for us. In VM we use Pfsense for few years without any issue - until 2.0.2 and 2.0.3.
-
there is no real OS difference between any of the 2.0.x versions so it's unlikely to be any difference between 2.0.1 and 2.0.2 or 2.0.3.
-
2.0.1 crashes again, in next days we try new install 2.1 RC (i386) with config migration.
-
We had Pfsense 2.1 RC1 installed for 3 days and crash reboot again :(
No option to send debug logs.
Now we are trying to delete Traffic Shapper.Next step (after another crash reboot) will be load KVM Virtio support.
We have only one additional package innstalled: Zabbix package
We have a few IPSEC tunnels.
We use URL table aliases.
We use some firewall rules with "Advaced settings": different values in "Maximum new connections / per second(s)" - also now disabled. -
We have two physical identical servers with KVM (Ubuntu 12.04 x64, default package qemu 1.0+noroms-0ubuntu14.7). Both recently sucessfully tested (more then 70 passes) with Memtest. Pfsense 2.1 RC i386 after few weeks got into strange state PAUSED not usual RUNNING (few days ago). This is different behavior than previous automatically reboot. We rebooted Pfsense by hand and updated it to current 2.1.
After next unexpected behavior we plan clean install x64 Pfsense 2.1
… to be continued -
I agree with above. Go straight hardware if feasible.
Is your pfsense 64 bits? How many WAN interfaces or WAN IPs do you have?
How much RAM is allocated to pfsense? -
I agree with above. Go straight hardware if feasible.
Is your pfsense 64 bits? How many WAN interfaces or WAN IPs do you have?
How much RAM is allocated to pfsense?Direct hardware install is not possible for us. Our pfSense is i386 with 2Gigs of RAM (a lot of RAM is free). We have one WAN with one IP.
After deleting all rule's "Advanced settings - Maximum new connections / per second" (approx. by 15 rules) we have only one reboot and one freeze. Before that, it happened more often.After next reboot/freeze we will install x64bit version. Virtual host is also x64bit architecture (Linux KVM).
-
This may seem like a counter-intuitive solution, but - Is 2.1 bringing you something you need that 2.03 wasn't? You could always use 2.03 until 2.1 gets a patch that makes it stable for you?
-
Troubles solved. :)
When virtualization host has heavy I/O load (due other virtual guest), pfsense on IDE virtual controller has troubles and fall into reboot or other unexpected state. After we load VirtIO drivers https://doc.pfsense.org/index.php/VirtIO_Driver_Support, pfsense is happy and we too.
But don't allow all VirtIO drivers! VTNET in our case slown down net traffic after few days rapidly.Working configs
virtual guest pfsense:
pfSense 2.1-RELEASE-pfSense (amd64)
cat /boot/loader.conf.local
virtio_load="YES"
virtio_pci_load="YES"
#if_vtnet_load="YES"
virtio_balloon_load="YES"
virtio_blk_load="YES"
virtualization host Ubuntu 12.04 64bit:
Linux xxx 3.2.0-54-generic #82-Ubuntu SMP Tue Sep 10 20:08:42 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux
qemu 1.0+noroms-0ubuntu14.11
