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

    some services show can't start

    Scheduled Pinned Locked Moved
    Plus 23.09 Development Snapshots (Retired)
    5
    131
    20.2k
    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
      stephenw10 Netgate Administrator
      last edited by

      Ah, interesting. But you only saw this after upgrading to 2.7.1?

      This should probably be in a new thread.

      H 1 Reply Last reply Reply Quote 0
      • H
        hannesclp @stephenw10
        last edited by

        @stephenw10
        Actually it is a fresh install of 2.7.0 and I restored from a backup. Since I immediately updated to 2.7.1 I cannot really tell. Everything worked until the first reboot…

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

          Ah, well it would be interesting to test that if you can. If this is a new issue in 2.7.1 it's probably not the same as the one you linked to.

          H 1 Reply Last reply Reply Quote 0
          • H
            hannesclp @stephenw10
            last edited by

            @stephenw10
            I will give it a try and reinstall the machine. Maybe its the same bug in 2.7.0 and 2.7.1…

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

              It probably is. In which case we have somewhere to start digging and more data points to pin it down. Otherwise if it's a regression in 2.7.1 we need to know about it.

              H 1 Reply Last reply Reply Quote 0
              • H
                hannesclp @stephenw10
                last edited by

                @stephenw10
                I just checked the 2.7.0 as well. The same error occurs after it's first restart. php-wg is offline but wireguard itself seems to be working.

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

                  Ok so it likely is that same issue. You should add any notes you have there.

                  H 1 Reply Last reply Reply Quote 0
                  • H
                    hannesclp @stephenw10
                    last edited by

                    @stephenw10
                    Unfortunately I don't have much more to offer. If you want to have a look at the machine just pm me ;-)

                    1 Reply Last reply Reply Quote 0
                    • yon 0Y
                      yon 0 @stephenw10
                      last edited by

                      @stephenw10

                      pfSense-repoc
                      pfSense-repoc: failed to fetch the repo data
                      failed to read the repo data.
                      pkg-static update
                      Updating pfSense-core repository catalogue...
                      pkg-static: No SRV record found for the repo 'pfSense-core'
                      pkg-static: An error occured while fetching package
                      pkg-static: packagesite URL error for pkg+https://pfsense-plus-pkg.netgate.com/pfSense_plus-v23_09_amd64-core/meta.txz -- pkg+:// implies SRV mirror type
                      repository pfSense-core has no meta file, using default settings
                      pkg-static: packagesite URL error for pkg+https://pfsense-plus-pkg.netgate.com/pfSense_plus-v23_09_amd64-core/packagesite.pkg -- pkg+:// implies SRV mirror type
                      pkg-static: packagesite URL error for pkg+https://pfsense-plus-pkg.netgate.com/pfSense_plus-v23_09_amd64-core/packagesite.txz -- pkg+:// implies SRV mirror type
                      Unable to update repository pfSense-core
                      Updating pfSense repository catalogue...
                      pkg-static: No SRV record found for the repo 'pfSense'
                      pkg-static: An error occured while fetching package
                      pkg-static: packagesite URL error for pkg+https://pfsense-plus-pkg.netgate.com/pfSense_plus-v23_09_amd64-pfSense_plus_v23_09/meta.txz -- pkg+:// implies SRV mirror type
                      repository pfSense has no meta file, using default settings
                      pkg-static: packagesite URL error for pkg+https://pfsense-plus-pkg.netgate.com/pfSense_plus-v23_09_amd64-pfSense_plus_v23_09/packagesite.pkg -- pkg+:// implies SRV mirror type
                      pkg-static: packagesite URL error for pkg+https://pfsense-plus-pkg.netgate.com/pfSense_plus-v23_09_amd64-pfSense_plus_v23_09/packagesite.txz -- pkg+:// implies SRV mirror type
                      Unable to update repository pfSense
                      Error updating repositories!

                      yon 0Y stephenw10S 2 Replies Last reply Reply Quote 0
                      • yon 0Y
                        yon 0 @yon 0
                        last edited by

                        Crash report begins. Anonymous machine information:

                        amd64
                        14.0-CURRENT
                        FreeBSD 14.0-CURRENT amd64 1400094 #0 plus-RELENG_23_09-n256163-2763857e770: Wed Nov 1 21:18:24 UTC 2023 root@freebsd:/var/jenkins/workspace/pfSense-Plus-snapshots-23_09-main/obj/amd64/WrS3lKLo/var/jenkins/workspace/pfSense-Plus-snapshots-23_09-main/

                        Crash report details:

                        PHP Errors:
                        [12-Dec-2023 20:23:00 Asia/Shanghai] PHP Fatal error: Unable to start pfSense module in Unknown on line 0
                        [12-Dec-2023 20:23:01 Asia/Shanghai] PHP Fatal error: Unable to start pfSense module in Unknown on line 0
                        [12-Dec-2023 20:23:08 Asia/Shanghai] PHP Fatal error: Unable to start pfSense module in Unknown on line 0
                        [12-Dec-2023 20:23:34 Asia/Shanghai] PHP Fatal error: Unable to start pfSense module in Unknown on line 0
                        [12-Dec-2023 20:24:00 Asia/Shanghai] PHP Fatal error: Unable to start pfSense module in Unknown on line 0
                        [12-Dec-2023 20:24:36 Asia/Shanghai] PHP Fatal error: Unable to start pfSense module in Unknown on line 0
                        [12-Dec-2023 20:25:00 Asia/Shanghai] PHP Fatal error: Unable to start pfSense module in Unknown on line 0
                        [12-Dec-2023 20:25:05 Asia/Shanghai] PHP Fatal error: Unable to start pfSense module in Unknown on line 0
                        [12-Dec-2023 20:25:38 Asia/Shanghai] PHP Fatal error: Unable to start pfSense module in Unknown on line 0
                        [12-Dec-2023 20:26:00 Asia/Shanghai] PHP Fatal error: Unable to start pfSense module in Unknown on line 0
                        [12-Dec-2023 20:26:40 Asia/Shanghai] PHP Fatal error: Unable to start pfSense module in Unknown on line 0
                        [12-Dec-2023 20:27:00 Asia/Shanghai] PHP Fatal error: Unable to start pfSense module in Unknown on line 0
                        [12-Dec-2023 20:27:42 Asia/Shanghai] PHP Fatal error: Unable to start pfSense module in Unknown on line 0
                        [12-Dec-2023 20:28:00 Asia/Shanghai] PHP Fatal error: Unable to start pfSense module in Unknown on line 0
                        [12-Dec-2023 20:28:44 Asia/Shanghai] PHP Fatal error: Unable to start pfSense module in Unknown on line 0
                        [12-Dec-2023 20:29:00 Asia/Shanghai] PHP Fatal error: Unable to start pfSense module in Unknown on line 0
                        [12-Dec-2023 20:29:46 Asia/Shanghai] PHP Fatal error: Unable to start pfSense module in Unknown on line 0
                        [12-Dec-2023 20:30:00 Asia/Shanghai] PHP Fatal error: Unable to start pfSense module in Unknown on line 0
                        [12-Dec-2023 20:30:49 Asia/Shanghai] PHP Fatal error: Unable to start pfSense module in Unknown on line 0
                        [12-Dec-2023 20:31:00 Asia/Shanghai] PHP Fatal error: Unable to start pfSense module in Unknown on line 0
                        [12-Dec-2023 20:31:51 Asia/Shanghai] PHP Fatal error: Unable to start pfSense module in Unknown on line 0
                        [12-Dec-2023 20:32:00 Asia/Shanghai] PHP Fatal error: Unable to start pfSense module in Unknown on line 0
                        [12-Dec-2023 20:32:53 Asia/Shanghai] PHP Fatal error: Unable to start pfSense module in Unknown on line 0
                        [12-Dec-2023 20:33:00 Asia/Shanghai] PHP Fatal error: Unable to start pfSense module in Unknown on line 0
                        [12-Dec-2023 20:33:55 Asia/Shanghai] PHP Fatal error: Unable to start pfSense module in Unknown on line 0
                        [12-Dec-2023 20:34:00 Asia/Shanghai] PHP Fatal error: Unable to start pfSense module in Unknown on line 0
                        [12-Dec-2023 20:34:58 Asia/Shanghai] PHP Fatal error: Unable to start pfSense module in Unknown on line 0
                        [12-Dec-2023 20:35:00 Asia/Shanghai] PHP Fatal error: Unable to start pfSense module in Unknown on line 0
                        [12-Dec-2023 20:36:00 Asia/Shanghai] PHP Fatal error: Unable to start pfSense module in Unknown on line 0
                        [12-Dec-2023 20:36:00 Asia/Shanghai] PHP Fatal error: Unable to start pfSense module in Unknown on line 0

                        No FreeBSD crash data found.

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

                          @yon-0 said in some services show can't start:

                          Updating pfSense repository catalogue...
                          pkg-static: No SRV record found for the repo 'pfSense'
                          pkg-static: An error occured while fetching package

                          This is a DNS error. Check pfSense can resolve.

                          1 Reply Last reply Reply Quote 0
                          • First post
                            Last post