Netgate Discussion Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Search
    • Register
    • Login

    weekly crash newsyslog

    Scheduled Pinned Locked Moved General pfSense Questions
    13 Posts 3 Posters 1.5k Views 2 Watching
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • stephenw10S Offline
      stephenw10 Netgate Administrator
      last edited by

      Ok, well 45C at the CPU core would not worry me at all. Some other component might have been overheating but a fan should prevent that.

      1 Reply Last reply Reply Quote 0
      • T Offline
        tomracing
        last edited by

        So have been out for a short holiday and back since last Friday. The firewall crashed on the Wednesday before I got back and didn't have a screen connected yet. Only same syslog notification on the log server.

        Connected a screen and keyboard and restarted the firewall for it to crash again today (Monday) i.e four days ish up time. Screen stil showed the pfsense menu screen, no additions. Ctrl+t no reaction and also numlock etc nothing. Log server same output plus about 25seconds with 3 block logs.

        Any further thoughts?
        Can I script (cronjob?) a daily clear logs as I don't need the history locally anyway since it goes to my log server just to avoiding the log rotate and see if that will help?

        H 1 Reply Last reply Reply Quote 0
        • H Offline
          hescominsoon @tomracing
          last edited by

          @tomracing what kind of nics are in there? bsd doesn't normally lock up unless there's a hardware issue.

          1 Reply Last reply Reply Quote 0
          • stephenw10S Offline
            stephenw10 Netgate Administrator
            last edited by

            Yup, feels like a hardware issue if it locked solid like that with no output at all.

            You might try disabling everything you can in the BIOS. De-rate the TDP, underclock it etc if you can.

            Steve

            1 Reply Last reply Reply Quote 0
            • T Offline
              tomracing
              last edited by

              Intermediate update,
              Turned off log archiving as it is going to a log server anyway before trying to adjust the bios settings.
              Currently 13 days 15hrs uptime.

              1 Reply Last reply Reply Quote 0
              • stephenw10S Offline
                stephenw10 Netgate Administrator
                last edited by

                What exactly did you set to 'turn off log archiving'? Disable rotation? Compression?

                That can use a lot of CPU, I wonder if that was triggering overheating.

                Steve

                1 Reply Last reply Reply Quote 0
                • T Offline
                  tomracing
                  last edited by

                  Ah yes indeed, now I turned off compression to see if that step was causing the locking up.

                  1 Reply Last reply Reply Quote 0
                  • stephenw10S Offline
                    stephenw10 Netgate Administrator
                    last edited by

                    Hmm, that would be interesting if that was the cause but it would also imply that any significant CPU usage might trigger it.

                    T 1 Reply Last reply Reply Quote 0
                    • T Offline
                      tomracing @stephenw10
                      last edited by tomracing

                      @stephenw10 interesting concept but wouldn't booting classify as high cpu load as well preventing the box from even starting?

                      I'm first going to see if it makes it a month without crashing then I will see if I can simulate some processor load from the terminal.

                      1 Reply Last reply Reply Quote 0
                      • stephenw10S Offline
                        stephenw10 Netgate Administrator
                        last edited by

                        Yes, you would think. If it got stuck in a loop compressing the logs it could have high CPU usage for a long while though.

                        1 Reply Last reply Reply Quote 0
                        • First post
                          Last post
                        Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.