pfsense reboot randomly on vmware
-
The only other thing it looks like it is this: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=239118
But that is old and we have that patch anyway: https://github.com/pfsense/FreeBSD-src/commit/4166913371c9be822cfa34419c397f711de83b49
-
@stephenw10 said in pfsense reboot randomly on vmware:
But that is old and we have that patch anyway
how do i apply the patch? can you help me?
-
@security_sharezone becasue on my system not have directory sys
i have only dev but not present vmware -
@security_sharezone said in pfsense reboot randomly on vmware:
@stephenw10 said in pfsense reboot randomly on vmware:
But that is old and we have that patch anyway
how do i apply the patch? can you help me?
He means the patch is already included in the current pfSense operating system code. It does not need to be applied. That bug is old enough that fix for it was included in the latest pfSense kernel builds.
And binary patches like that at the OS level are not something you can easily apply anyway.
-
That's not a patch you can apply. It's applied to the source and we already have it in. I only pointed that out because that's the only other thing that's close to that backtrace.
-
@bmeeks said in pfsense reboot randomly on vmware:
He means the patch is already included in the current pfSense operating system code. It does not need to be applied. That bug is old enough that fix for it was included in the latest pfSense kernel builds.
And binary patches like that at the OS level are not something you can easily apply anyway.
unfortunately it keeps rebooting. last time it lasted 55 minutes. but could it be that i'm averaging 10mb in wireguard vpn and it's the vpn that's crashing?
-
Possibly. One of the panics shows it's in wg at the time.
Do you have any other crash reports? Does it always show the same backtrace?
-
@stephenw10 in this moment i reset and delete all file and log . i waiting another crash .
-
S stephenw10 moved this topic from Problems Installing or Upgrading pfSense Software on
-
@STEPHENW10 on attacchment crach dump .
I've been waiting to collect some logs and understand the problem. but I can't get to the bottom of it. I'd analyse the wireguard vpn. but I really can't make heads or tails of it :-). can you think of any ideas?crash_dump.txt
-
Only one of those 4 crashes seems to be related to wireguard. Are you able to test just disabling WireGuard?
Another good test here would be swapping the NIC that's on to something other than VMX3 in the hypervisor. That would require quite a few changes though.
-
@stephenw10 said in pfsense reboot randomly on vmware:
Only one of those 4 crashes seems to be related to wireguard. Are you able to test just disabling WireGuard?
Another good test here would be swapping the NIC that's on to something other than VMX3 in the hypervisor. That would require quite a few changes though.
i disabled all backup jobs via veeam that used wireguard. changing vmxnet3 to e1000 would also have a drop in performance
-
Did you actually disable WireGuard befe those crashes? One pf them is in the wg process shortly before it crashes.
It would still be a good test to switch to e1000.
-
@stephenw10 said in pfsense reboot randomly on vmware:
Did you actually disable WireGuard befe those crashes? One pf them is in the wg process shortly before it crashes.
It would still be a good test to switch to e1000.
no disabled now ... monitoring wireguard tunnels without traffic .. switching to e1000 a big job .. i'll make a vm clone and then convert everything
-
Yes, it's a significant task. But it would prove the issue is in the vmxnet3 driver. Or disprove it.
-
I will definitely do it. my steps are
- wireguard down for two days and see if problem backup job
- change e1000
I will give feedback. if a solution is found in the meantime I would be happy
-
@stephenw10 in this moment 20 hours without reboot .
wireguard is up but without backup running . low traffic transit . -
@security_sharezone said in pfsense reboot randomly on vmware:
one day up e running .. today night switch on e1000 network
-
Cool. One of our devs is digging into this. He may reach out to you with a diagnostic kernel.
-
@stephenw10
maximum availability to support you and the community -
i think that for 2 Days 14 Hours 08 Minutes 08 Seconds the firt point of step 1. ( wireguard down for two days and see if problem backup job ) is done
today renable backup job and resubmit result . if crach disable vmxnet3 and enable e1000
