To do 24.11 or not? That's the question.
-
I see only :
Dec 5 09:53:21 syslogd kernel boot file is /boot/kernel/kernel
Dec 5 09:53:21 syslogd exiting on signal 15
Dec 5 09:53:19 root 661 /etc/rc.d/hostid: WARNING: hostid: unable to figure out a UUID from DMI data, generating a new one
Dec 5 09:53:19 sshguard 95442 Exiting on signal.
Dec 5 09:53:19 sshguard 97569 Exiting on signal.See a bunch of:
"sshguard 56735 Exiting on signal."
all dated today, so it's 24.11 specific
What do they mean?
Also see Dec 5
08:47:50 snort 76151 *** Caught Term-Signal
-
Hmm, nothing. Looks like it spontaneously rebooted which is worrying.
Do you have SWAP? Doesn't look like you have RAMdisks which might otherwise lose some logging.
Can you log the console output to see if anything additional is shown there?
-
@stephenw10 said in To do 24.11 or not? That's the question.:
Hmm, nothing. Looks like it spontaneously rebooted which is worrying.
Do you have SWAP? Doesn't look like you have RAMdisks which might otherwise lose some logging.
Can you log the console output to see if anything additional is shown there?
I have SWAP
How do you want me to get the console ?
I was paging 8.8.8.8 from ssh session and saw nothing. Can try again to stay connected and see.
But my pfS is headless and I am remote now ...
-
Hmm, if it crashed and there was a kernel panic it would have created a crash report in swap then. You are not seeing that. It looks more like a hardware reset but I'm not sure why you would see that in 24.11 and not 24.03. In cases like that it might write something to the console when it resets. But you would need a serial terminal connected to it to log that.
Check the monitoring graphs for any resource exhausting or over heating issues.
-
@stephenw10 said in To do 24.11 or not? That's the question.:
Hmm, if it crashed and there was a kernel panic it would have created a crash report in swap then. You are not seeing that. It looks more like a hardware reset but I'm not sure why you would see that in 24.11 and not 24.03. In cases like that it might write something to the console when it resets. But you would need a serial terminal connected to it to log that.
Check the monitoring graphs for any resource exhausting or over heating issues.
I will have access to my box with HDMI connected monitor today or tomorrow.
What do you want me to look at?
Logged issue https://redmine.pfsense.org/issues/15903
-
What temperatures are you seeing? Overheating seems like the most likely cause. The CPU loading in 24.11 will be a bit higher.
-
-
Hmm, and all pretty low.
It looks like that device has a com port so I would be hooking up a serial console, setting that as primary and logging that output.
-
@stephenw10 said in To do 24.11 or not? That's the question.:
Hmm, and all pretty low.
It looks like that device has a com port so I would be hooking up a serial console, setting that as primary and logging that output.
I have never done it before and unsure if have all h/w for it
-
Well I'm not sure what else you could do. Right now it's just hard resetting and giving us no clues.
You could try the debug kernel but I doubt it will log anything additional:
https://docs.netgate.com/pfsense/en/latest/troubleshooting/debug-kernel.html -
@stephenw10 said in To do 24.11 or not? That's the question.:
Well I'm not sure what else you could do. Right now it's just hard resetting and giving us no clues.
You could try the debug kernel but I doubt it will log anything additional:
https://docs.netgate.com/pfsense/en/latest/troubleshooting/debug-kernel.htmlI am surprised we see no other similar complains
-
Indeed if it were something common to the platform or a software bug I'd expect to have seen a lot more reports.
Which implies either something in your config no-one else is doing or something unique to your device, like an overheating component.
-
C chudak referenced this topic
-
@stephenw10 said in To do 24.11 or not? That's the question.:
Indeed if it were something common to the platform or a software bug I'd expect to have seen a lot more reports.
Which implies either something in your config no-one else is doing or something unique to your device, like an overheating component.
This is not true.
Others see similar issueshttps://forum.netgate.com/topic/195436/pfsense-24-11-on-my-1100-reboots-every-couple-of-hours/16
-
@chudak said in To do 24.11 or not? That's the question.:
https://forum.netgate.com/topic/195436/pfsense-24-11-on-my-1100-reboots-every-couple-of-hours/16
Right, where it also looks like a hardware issue. And on the 1100 it's much harder to tell because there's no useful thermal sensor.
-
Have you excluded the 'power brick issue' ?
-
@Gertjan said in To do 24.11 or not? That's the question.:
Have you excluded the 'power brick issue' ?
I don't know what that is :(
Pls educate.
If you are referring to a power supply problem, then yes, it's not the power supply.
It's 24.11 specific.
-
You saw the threads where it was said that the cpu was hotter, or made doing more work etc.
Thus it draws more power.Looking at the image of a QOTOM-Q355G4 I know it has a external power transformer. Something like this - and these aren't always perfect (neither).
You've tried this : goto basic mode.
That is : no more tailscale.
No more snort.
No pfBlockerng.
Etc.
Just 24.11 'clean'.Also : QOTOM devices are used a lot I guess. If 24.11 has an issue with QOTOM or your type specifically, it won't last long before others chime in.
-
@Gertjan said in To do 24.11 or not? That's the question.:
You saw the threads where it was said that the cpu was hotter, or made doing more work etc.
Thus it draws more power.Looking at the image of a QOTOM-Q355G4 I know it has a external power transformer. Something like this - and these aren't always perfect (neither).
You've tried this : goto basic mode.
That is : no more tailscale.
No more snort.
No pfBlockerng.
Etc.
Just 24.11 'clean'.I was thinking to remove snort and psBNG and do upgrade
Can’t do without TS
But did it prove to help in this case?
-
Testing it with as basic a config as you can would be a good test. Hard to imagine it using enough additional power over 24.03 to trigger a PSU issue though.
