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

    Lost power, can't boot!

    Scheduled Pinned Locked Moved General pfSense Questions
    5 Posts 5 Posters 276 Views
    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.
    • N
      netpatje
      last edited by netpatje

      Today my power went off and the ups was going down after 30 minutes..... When the power was up again, my PFSense config wont start anymore.

      I can connect from console but I'm stuck.... I've done a fsck but thats it. Below I wil post the error messages. Does anyone has a clue how to get this config startet again?

      FreeBSD/amd64 (Amnesiac) (ttyu0)

      2024-10-25T22:04:04.916962+02:00 - login 601 - - login on ttyu0 as root

      Fatal error: Uncaught ValueError: Path cannot be empty in /etc/inc/notices.inc:135
      Stack trace:
      #0 /etc/inc/notices.inc(135): fopen('', 'w')
      #1 /etc/inc/config.lib.inc(95): file_notice('config.xml', 'No config.xml f...', 'pfSenseConf)
      #2 /etc/inc/config.gui.inc(53): parse_config()
      #3 /etc/inc/auth.inc(34): require_once('/etc/inc/config...')
      #4 /etc/inc/openvpn.inc(36): require_once('/etc/inc/auth.i...')
      #5 /etc/inc/filter.inc(30): require_once('/etc/inc/openvp...')
      #6 /etc/inc/ipsec.inc(25): require_once('/etc/inc/filter...')
      #7 /etc/inc/gwlb.inc(27): require_once('/etc/inc/ipsec....')
      #8 /etc/inc/functions.inc(35): require_once('/etc/inc/gwlb.i...')
      #9 /etc/inc/notices.inc(26): require_once('/etc/inc/functi...')
      #10 /etc/inc/config.inc(37): require_once('/etc/inc/notice...')
      #11 /etc/rc.banner(27): require_once('/etc/inc/config...')
      #12 {main}
      thrown in /etc/inc/notices.inc on line 135
      PHP ERROR: Type: 1, File: /etc/inc/notices.inc, Line: 135, Message: Uncaught ValueError: Pat5
      Stack trace:
      #0 /etc/inc/notices.inc(135): fopen('', 'w')
      #1 /etc/inc/config.lib.inc(95): file_notice('config.xml', 'No config.xml f...', 'pfSenseConf)
      #2 /etc/inc/config.gui.inc(53): parse_config()
      #3 /etc/inc/auth.inc(34): require_once('/etc/inc/config...')
      #4 /etc/inc/openvpn.inc(36): require_once('/etc/inc/auth.i...')
      #5 /etc/inc/filter.inc(30): require_once('/etc/inc/openvp...')
      #6 /etc/inc/ipsec.inc(25): require_once('/etc/inc/filter...')
      #7 /etc/inc/gwlb.inc(27): require_once('/etc/inc/ipsec....')
      #8 /etc/inc/functions.inc(35): require_once('/etc/inc/gwlb.i...')
      #9 /etc/inc/notices.inc(26): require_once('/etc/inc/functi...')
      #10 /etc/inc/config.inc(37): require_once('/etc/inc/notice...')
      #11 /etc/rc.banner(27): require_once('/etc/inc/config...')
      #12 {main}
      thrown
      Fatal error: Uncaught ValueError: Path cannot be empty in /etc/inc/notices.inc:135
      Stack trace:
      #0 /etc/inc/notices.inc(135): fopen('', 'w')
      #1 /etc/inc/config.lib.inc(1154): file_notice('phperror', 'PHP ERROR: Type...', 'PHP errors')
      #2 [internal function]: pfSense_clear_globals()
      #3 {main}
      thrown in /etc/inc/notices.inc on line 135

      1. Logout (SSH only) 9) pfTop
      2. Assign Interfaces 10) Filter Logs
      3. Set interface(s) IP address 11) Restart webConfigurator
      4. Reset webConfigurator password 12) PHP shell + pfSense tools
      5. Reset to factory defaults 13) Update from console
      6. Reboot system 14) Enable Secure Shell (sshd)
      7. Halt system 15) Restore recent configuration
      8. Ping host 16) Restart PHP-FPM
      9. Shell

      Enter an option:

      GertjanG bmeeksB S 3 Replies Last reply Reply Quote 0
      • stephenw10S
        stephenw10 Netgate Administrator
        last edited by

        The fastest way back from that is usually just to reinstall and restore the config.

        If you have network access still (or can manually add it) you might be able to run a pkg re-install to pull back in the files it can't access:
        https://docs.netgate.com/pfsense/en/latest/troubleshooting/upgrades.html#upgrade-not-offered-library-errors

        Steve

        1 Reply Last reply Reply Quote 0
        • GertjanG
          Gertjan @netpatje
          last edited by

          @netpatje said in Lost power, can't boot!:

          Today my power went off and the ups was going down after 30 minutes.....

          The UPS didn't tell pfSense to shut down safely ?

          No "help me" PM's please. Use the forum, the community will thank you.
          Edit : and where are the logs ??

          1 Reply Last reply Reply Quote 0
          • bmeeksB
            bmeeks @netpatje
            last edited by

            @netpatje said in Lost power, can't boot!:

            Today my power went off and the ups was going down after 30 minutes....

            Do you not have either of the apcupsd or nut packages installed? If not, you should install one of those and configure it. Those packages communicate with the UPS, and when the battery is expiring during a power loss run, will gracefully issue a shutdown command to pfSense. That way, you won't experience disk corruption like you have now.

            If your UPS is an APC model, then install the apcupsd package. If using another brand of UPS, then the nut package is probably better. You can install either package from the SYSTEM > PACKAGE MANAGER menu in pfSense.

            1 Reply Last reply Reply Quote 1
            • S
              SteveITS Galactic Empire @netpatje
              last edited by

              @netpatje said in Lost power, can't boot!:

              No config.xml f...

              See if you have a config file in /conf/backup...menu option 15 if it lets you use that.

              A reinstall will use ZFS which is more resilient towards power loss.

              Pre-2.7.2/23.09: Only install packages for your version, or risk breaking it. Select your branch in System/Update/Update Settings.
              When upgrading, allow 10-15 minutes to restart, or more depending on packages and device speed.
              Upvote 👍 helpful posts!

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