pfSense freezes on Saturdays in the morning and shortly after 4pm.
-
@stephenw10
Nothing in the logs, first thing is a fresh boot.
I also looked at the Monitoring (CPU, memory, temperature...) Everything normal for the past week. -
Hmm, if it's happening frequently you can try connecting a serial console and logging it to see anything is shown there when it resets.
-
@stephenw10, @yaminb
that would interest me aswell, as said I have nothing in my (serial-)logs which makes diagnosing this pretty much guess work. -
Update:
It still happens, now more randomly also on weekdays.
I was fed up enough now to re-deploy my old backup and see if that solves it for now. -
ml350p gen8 with 2x E5-2690 ~200Gb ram, VMware
ESXi, 7.0.3, 19482537Is this your rig (hardware)? Were you taking the ESXi image from HP or the normal one?
Did you set up much apps such as snort, clamav (squid-http)
and/or pfBlocker-NG? And when yes, what is the time to get fresh, rules, signatures or lists? (Update I mean)And the Bell Home Hub 4xxx is a real modem or a router?
Do you set it up in bridged mode? -
@dobby_ T
Yep it ist-
The HP Image is pretty outdated so I used the official one from vmware.
I disabled most of the monitoring stuff but still have: pfBlocker, Snort, Telgraf.My Modem is a Telekom Speedport Smart 3 in modem-mode directly connected to the pfSense.
Also since I reverted to my old backup 10 days ago I had no freezes.
So the error was either introduced during the update or the newest pfSense version has a bug.
-
So the error was either introduced during the update
or the newest pfSense version has a bug.
I don´t know I was really testing and using them here for a week or some days plus or less. All were running fine.APU4C4 as test device, together with;
2.6 CE to 22.01 to 22.05 - without any problems
2.6 CE to 2.7 Devel to 22.09 Devel - without any problemsThe HP Image is pretty outdated so I used the official
one from vmware.Often or better not seldom from this problems came.
My Modem is a Telekom Speedport Smart 3 in
modem-mode directly connected to the pfSense.In Germany it is for a home account or internet connection
normal to have a break every 24 hours, perhaps and if not running in modem mode it comes from there! Something in the set up let your say at witch day or time the break will com or ocours. Have a look there too please. -
@dobby_ said in pfSense freezes on Saturdays in the morning and shortly after 4pm.:
So the error was either introduced during the update
or the newest pfSense version has a bug.
I don´t know I was really testing and using them here for a week or some days plus or less. All were running fine.APU4C4 as test device, together with;
2.6 CE to 22.01 to 22.05 - without any problems
2.6 CE to 2.7 Devel to 22.09 Devel - without any problemsThe HP Image is pretty outdated so I used the official
one from vmware.Often or better not seldom from this problems came.
My Modem is a Telekom Speedport Smart 3 in
modem-mode directly connected to the pfSense.In Germany it is for a home account or internet connection
normal to have a break every 24 hours, perhaps and if not running in modem mode it comes from there! Something in the set up let your say at witch day or time the break will com or ocours. Have a look there too please.Thing is non of these issues appeared one pfSense version prior. It only started after the update and it stopped after reverting is. I am reluctant to see a hardware issue on my end.
Also, yes modem is definitly in modem mode and I am aware of the reconnect and they never coincided with the freezes
-
@nollipfsense said in pfSense freezes on Saturdays in the morning and shortly after 4pm.:
Without showing us a log, we can only speculate...maybe it's allergic to Saturdays...
Probably likes to sleep in too.
-
@jknott said in pfSense freezes on Saturdays in the morning and shortly after 4pm.:
@nollipfsense said in pfSense freezes on Saturdays in the morning and shortly after 4pm.:
Without showing us a log, we can only speculate...maybe it's allergic to Saturdays...
Probably likes to sleep in too.
yep, as I said, no logs that indicate what's going on. I even activated serial logging to see whats happening but even here: 1 sec it's fine, next we are seeing the output of a booting OS
-
@globus243 said in pfSense freezes on Saturdays in the morning and shortly after 4pm.:
next we are seeing the output of a booting OS
To have an OS to boot, it needs to jump through the boot vector.
That's a call that might exist in the OS - and can only be executed by the OS in 'root ' (ring 0) mode. Freezing up is far more common. If it's a OS controlled reboot, there will be a message.That is : if it can store a message on the disk. If the file system is dirty, the disk might even not be writeable ( check that with the help of the official Netgate "fsck" Youtube video ).
It's always good to look at the logs, for 'OOM' messages and the like.
Or other "normally never seen" messages.
If there are none, then there is only one thing to do :
Lower the code foot print : remove all extras, all not really needed software, just the bare bone basics.
Just to be sure that, after a while, the freeze up only happens when you use 'x' (like a package).It still happens ? It's most probably a hardware issue. Or a bad power rail.
I know, this won't help you, but it is important : if I don't touch my pfSense, it runs for weeks if not months ... and I have the logs, better : the images to share with you.
You'll say : wtf, you system restart often !! True, as I reboot often to test things out - or just to be sure a reboot (in my absence) will bring back the Internet online.
-
@globus243 said in pfSense freezes on Saturdays in the morning and shortly after 4pm.:
1 sec it's fine, next we are seeing the output of a booting OS
That sounds like hardware. And if it's something that regular I would not rule out some external influence. It wouldn't be the first time something like this was caused by a neighbour running their drier etc.
Steve
-
@globus243 I've had a similar experience, which may or may not be related. Netgate 5100 locks up shortly after either 6 a.m. or 6 p.m. but not always on the same day of the week. Finally traced the problem to pfblockerng-devel updating its block lists. For some reason this results in "insufficient swap space," even though no swap space is shown in use. My wife first noticed this phenomenon because her Amazon Alexa console, which is connected wirelessly, shows "no network." I'm not competent to delve into what's actually happening, so I just reboot the firewall and everything is fine.
