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

    Squidguard update fails after upgrading pfSense 2.4.5-RELEASE-p1

    Scheduled Pinned Locked Moved Cache/Proxy
    54 Posts 38 Posters 15.3k 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.
    • S
      SaschaITM
      last edited by SaschaITM

      Same issue here on 2.4.5-RELEASE-p1 running in a VMware VM. There doesn't seem to be an easy fix, tried everything in this thread, and some additional stuff. The "killall -9 pkg-static" command (on a second shell) will just interrupt the uninstall procedure, it doesn't continue after issuing that command. I've noticed that when the procedure hangs there are two "pkg" processes which seem to be started close to each other (if not at nearly the same time), maybe that's the issue? Like some kind of race condition, triggered by a typo/special character or something like that in the package itself?

      1 Reply Last reply Reply Quote 0
      • A
        Aiken
        last edited by

        After comment below command in /usr/local/pkg/squidguard.inc

        squid_reconfigure('remove redirector options');
        

        I can remove the old package and install new package manually.

        B A ? 3 Replies Last reply Reply Quote 4
        • B
          biGdada @Aiken
          last edited by

          @Aiken worked for me, thanks alot

          1 Reply Last reply Reply Quote 0
          • A
            alexela @Aiken
            last edited by

            @Aiken said in Squidguard update fails after upgrading pfSense 2.4.5-RELEASE-p1:

            /usr/local/pkg/squidguard.inc

            @Aiken Thank you, this does the trick for me too.

            1 Reply Last reply Reply Quote 0
            • ?
              A Former User @Aiken
              last edited by

              Thank you @Aiken! This is the only solution that has worked for me. After commenting out that line I was able to upgrade squidGuard via the WebGUI

              1 Reply Last reply Reply Quote 0
              • rcfaR
                rcfa
                last edited by

                I have the same issue with 2.4.5, 2.4.5-p1 and 2.5.0-DEVELOPMENT.

                It always involves one or more of the following packages:
                pfSense-pkg-ntopng
                pfSense-pkg-squidGuard
                pfSense-pkg-squid

                Whereby the first two are a recent addition, Squid gave be trouble for a while, in that it would fail upgrading, so each time I had to remove and install as separate steps. Now that fails, too.

                Some of them can be installed on the command line, some hang even there after "Writing configuration... done."

                1 Reply Last reply Reply Quote 0
                • S
                  sisko212
                  last edited by

                  looks to be an issue on latest versions of package manager, not Squid or Squidguard or other packages related.
                  There are also other post claiming same issue:
                  https://forum.netgate.com/topic/154389/2-4-5r1-update-no-package-re-install

                  1 Reply Last reply Reply Quote 0
                  • T
                    tmsongster
                    last edited by tmsongster

                    I was having the same issue. Solved it thusly:

                    • squidGuard re-install was already in progress
                    • Went to Services>Squid Proxy Server (PackageProxy Server: General SettingsGeneral)
                    • UN-checked "Enable Squid Proxy"
                    • Save
                    • Re-install continued and completed
                    • Re-enable Squid.

                    ***This was after several attempts to upgrade, uninstall, reinstall, killall... YMMV.

                    UPDATE - 20200618: Checked the package manager and Squid showed an update. Ran the update and this time Squid encountered the same problem as squidGuard above. Applied the same solution and it worked, again.

                    D P P A C 7 Replies Last reply Reply Quote 4
                    • D
                      dotcom @tmsongster
                      last edited by

                      @tmsongster This worked for me. Thank you.

                      1 Reply Last reply Reply Quote 1
                      • E
                        emeric
                        last edited by

                        @tmsongster thanks for your solution it also worked for me too !

                        1 Reply Last reply Reply Quote 1
                        • P
                          PaMi @tmsongster
                          last edited by

                          @tmsongster Thanks it worked for me too.

                          • Installed Squid (Still "Writing Configuration"...)
                          • Kill install
                          • Disable Squid service
                          • Reinstall Squid => OK
                          • Install SquiGuard => OK
                          • Enable Squid service
                          diegovaz93D 1 Reply Last reply Reply Quote 2
                          • J
                            jonmayer
                            last edited by

                            Manually stopping the services before updating seemed to have work with both Squid and pfBlocker. Updates worked as expected then, but then have to manually start services again as well. Odd bug.

                            1 Reply Last reply Reply Quote 0
                            • M
                              mdalacu
                              last edited by

                              I have the same problem...
                              Last weekend i had to restore the whole machine from backup in order to get it working.
                              So, should i wait for a p2 release which will correct this or should i try again with stopping the services before upgrade? Is this workaround confirmed?
                              Thank you.

                              1 Reply Last reply Reply Quote 0
                              • 4
                                4920441 0
                                last edited by

                                Hi,
                                Seems to be not only squidguard.

                                On my Box i had the same problems with squid and also with upgrading frr.

                                I could get frr installing by killing the running frr daemon, but squid 'wanted' a "killall -9 pkg-static" or it was still stuck...

                                Cheers

                                1 Reply Last reply Reply Quote 0
                                • diegovaz93D
                                  diegovaz93 @PaMi
                                  last edited by

                                  @pamidou Solved my problem Thanks Bro!

                                  1 Reply Last reply Reply Quote 2
                                  • T
                                    tsmalmbe
                                    last edited by

                                    Screwed my update completely also.

                                    1. killall pkg
                                    2. pkg remove the squidpackage
                                    3. pkg remove the squidguardpackage
                                    4. run the upgrade
                                    5. reboot

                                    Done.

                                    Will not run squid on my pfsense again. Lesson learned.

                                    Security Consultant at Mint Security Ltd - www.mintsecurity.fi

                                    1 Reply Last reply Reply Quote 0
                                    • P
                                      paul18 @tmsongster
                                      last edited by

                                      @tmsongster Thanks!!! Disabling Squid allowed the upgrade.

                                      1 Reply Last reply Reply Quote 1
                                      • A
                                        Andrei Stan @tmsongster
                                        last edited by

                                        @tmsongster Worked for me too !! Thanks

                                        1 Reply Last reply Reply Quote 1
                                        • S
                                          smnolde
                                          last edited by

                                          Thanks for this. This was the only issue I had upgrading my MBT-4220.

                                          1 Reply Last reply Reply Quote 1
                                          • BenPiB
                                            BenPi
                                            last edited by

                                            I also have the same behaviour but with the two following package :
                                            pfSense-pkg-ntopng (rcfa seems to have the same issue.)
                                            pfSense-pkg-haproxy

                                            When I try to reinstall or upgrade one of these package it it stays stuck indefinitely after showing "Writing configuration... done." :

                                            Reinstalling pfSense-pkg-haproxy
                                            >>> Upgrading pfSense-pkg-haproxy... 
                                            Updating pfSense-core repository catalogue...
                                            pfSense-core repository is up to date.
                                            Updating pfSense repository catalogue...
                                            pfSense repository is up to date.
                                            All repositories are up to date.
                                            Checking integrity... done (0 conflicting)
                                            The following 1 package(s) will be affected (of 0 checked):
                                            
                                            Installed packages to be REINSTALLED:
                                            	pfSense-pkg-haproxy-0.60_4 [pfSense]
                                            
                                            Number of packages to be reinstalled: 1
                                            [1/1] Reinstalling pfSense-pkg-haproxy-0.60_4...
                                            [1/1] Extracting pfSense-pkg-haproxy-0.60_4: .......... done
                                            Removing haproxy components...
                                            Menu items... done.
                                            Services... done.
                                            Loading package instructions...
                                            Deinstall commands... done.
                                            Syslog entries... done.
                                            Saving updated package information...
                                            overwrite!
                                            Loading package configuration... done.
                                            Configuring package components...
                                            Loading package instructions...
                                            Custom commands...
                                            Executing custom_php_install_command()...done.
                                            Menu items... done.
                                            Services... done.
                                            Writing configuration... done.
                                            

                                            I've upgraded my current installation from 2.4.4-p3 to 2.4.5-p1 and I have the issue.

                                            I've upgraded a fresh install 2.4.5 to 2.4.5-p1 and restored a backup of my configuration after the upgrade and I have the same issue.

                                            So it seems to me that there's a bug preventing the upgrade to finish on multiple packages on the version 2.4.5-p1.

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