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

    many problems after upgrading service watchdog

    Scheduled Pinned Locked Moved
    pfSense Packages
    3
    9
    194
    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.
    • F
      fbrunken
      last edited by

      I uninstalled it because it was just generating an error every minute. Does someone have a similar experience?

      Here the error:

      PHP ERROR: Type: 1, File: /usr/local/pkg/servicewatchdog.inc, Line: 91, Message: Uncaught TypeError: Cannot access offset of type string on string in /usr/local/pkg/servicewatchdog.inc:91
Stack trace:
#0 /usr/local/pkg/servicewatchdog_cron.php(30): servicewatchdog_check_services()
#1 {main}
thrown @ 2024-08-20 08:41:00
      S 1 Reply Last reply Reply Quote 0
      • S
        SteveITS Rebel Alliance @fbrunken
        last edited by

        @fbrunken What version of pfSense?

        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!

        F 1 Reply Last reply Reply Quote 0
        • F
          fbrunken @SteveITS
          last edited by fbrunken

          @SteveITS 24.03-RELEASE (amd64).

          Sorry, and I forgot to mention that it has been working just fine till today when I decided to upgrade to a new version via the package manager.

          F 1 Reply Last reply Reply Quote 0
          • F
            fbrunken @fbrunken
            last edited by

            Since the watchdog runs every minute, I had a few entries in my log and here is some more logs.

            [20-Aug-2024 08:42:00 America/Vancouver] PHP Fatal error:  Uncaught TypeError: Cannot access offset of type string on string in /usr/local/pkg/servicewatchdog.inc:91
Stack trace:
#0 /usr/local/pkg/servicewatchdog_cron.php(30): servicewatchdog_check_services()
#1 {main}
  thrown in /usr/local/pkg/servicewatchdog.inc on line 91
[20-Aug-2024 08:43:00 America/Vancouver] PHP Fatal error:  Uncaught TypeError: Cannot access offset of type string on string in /usr/local/pkg/servicewatchdog.inc:91
Stack trace:
#0 /usr/local/pkg/servicewatchdog_cron.php(30): servicewatchdog_check_services()
#1 {main}
  thrown in /usr/local/pkg/servicewatchdog.inc on line 91
[20-Aug-2024 08:43:13 America/Vancouver] PHP Fatal error:  Uncaught TypeError: Cannot access offset of type string on string in /usr/local/www/services_servicewatchdog.php:172
Stack trace:
#0 {main}
  thrown in /usr/local/www/services_servicewatchdog.php on line 172
            dennypageD 1 Reply Last reply Reply Quote 0
            • dennypageD
              dennypage @fbrunken
              last edited by

              @fbrunken said in many problems after upgrading service watchdog:

              /usr/local/www/services_servicewatchdog.php

              What version number for Service_Watchdog does it show?

              I currently have 1.8.7_2, which as far as I know was the latest issued with 24.03. From the errors/lines you are posting, I would have to guess that you have 1.8.7_3 which I would have expected to only show in testing with 24.08 dev snapshots.

              Are you running dev builds? Or have your package repository pointing at dev packages?

              F 1 Reply Last reply Reply Quote 1
              • F
                fbrunken @dennypage
                last edited by

                @dennypage said in many problems after upgrading service watchdog:

                /usr/local/www/services_servicewatchdog.php

                Don't update!

                I believe I found the issue. I left the update to the latest development snapshot and was offered version 1.8.7_3 of the watchdog. I am not a developer and this is happening on my live system! So, I need now to figure out how to fix it...

                Simply uninstalling and reinstalling did not work. Anyway, this was the problem.

                S 1 Reply Last reply Reply Quote 0
                • S
                  SteveITS Rebel Alliance @fbrunken
                  last edited by

                  @fbrunken Setting to a future branch will detect/install future software. See my sig. You can try to uninstall the package, change branches, and install again. Brute force method is to install 24.03 new then restore your config backup.

                  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!

                  F 1 Reply Last reply Reply Quote 1
                  • F
                    fbrunken @SteveITS
                    last edited by

                    @SteveITS thanks... It is a live system, so I need to think about how to fix this now...

                    F 1 Reply Last reply Reply Quote 0
                    • F
                      fbrunken @fbrunken
                      last edited by

                      @SteveITS All back to normal. And the fix is really simple. I did a restore of my config and everything was back working again... Thanks again.

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