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

    25.07 ran for 24 hours and then ????

    Scheduled Pinned Locked Moved General pfSense Questions
    4 Posts 2 Posters 99 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.
    • B Offline
      bbrendon
      last edited by

      I've been running a cluster for many years (ESXi previously and now PVE). Upgraded to 25.07 yesterday morning and this morning the primary node was in a strange state. I could access the web interface but I couldn't ping 8.8.8.8. Also other strange things. I tried stopping pfblocker, reloading filter log, and a few other things. I saved some logs but had to punt because I was in a rush and revert the snapshot.

      Very strange. I've never had this happen.

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

        Hmm, hard to say from that. Do you have any logs from the failed node we can review?

        B 1 Reply Last reply Reply Quote 0
        • B Offline
          bbrendon @stephenw10
          last edited by bbrendon

          @stephenw10 here is something. It died at about 9am. I had to remove a few lines for safety. I should have more time to look at it tonight.

          https://docs.google.com/spreadsheets/d/1WdXVI9-O1V3m0XHQPCDse6P3A--XDm6-ZRFlFG8iRgY/edit?usp=sharing

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

            Hmm, well hard to be sure I'd guess that Unbound was restarted when pfBlocker updated and then failed to restart for some reason.

            However that wouldn't prevent pinging 8.8.8.8. So another possibility is that one of the pfBlocker feeds had some rogue entry blocking far too much when it updated.

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