Squidguard update fails after upgrading pfSense 2.4.5-RELEASE-p1
-
@tmsongster This worked for me. Thank you.
-
@tmsongster thanks for your solution it also worked for me too !
-
@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
-
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.
-
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. -
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
-
@pamidou Solved my problem Thanks Bro!
-
Screwed my update completely also.
- killall pkg
- pkg remove the squidpackage
- pkg remove the squidguardpackage
- run the upgrade
- reboot
Done.
Will not run squid on my pfsense again. Lesson learned.
-
@tmsongster Thanks!!! Disabling Squid allowed the upgrade.
-
@tmsongster Worked for me too !! Thanks
-
Thanks for this. This was the only issue I had upgrading my MBT-4220.
-
I also have the same behaviour but with the two following package :
pfSense-pkg-ntopng (rcfa seems to have the same issue.)
pfSense-pkg-haproxyWhen 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.
-
Hello everyone;
Same issue here. But the problem are with the suricata and e2guardian packages. I'm following this to try to solve this issue.
-
Same issue here. Packagemanager has troubles on 2.4.5-p1.
I've upgraded my pfsense boxes to 2.4.5p1 and now i can not remove or add packages.
If i restore my config on an fresh installed 2.4.5p1 - pfsense reboots and hung on
"Packages are currently being reinstalled in the background."
"Do not make changes in the GUI until this is complete." -
After edit manually the config.xml file, and add the suricata entries, this fixed the problem. E2guardian, however, still remains with problems, because isn't possible to install the package. I've made a clean and fresh install of pfsense, and restored the backup, but, with no success.
-
Thanks!!!!! This worked for for each of the 11 Netgate devices I manage.
-
Thanks @tmsongster, solved the issue!
-
I had the same issues. The cause seems to be the update process is waiting for input that is not expected.
If i update via the command line and the updates hangs, i just press enter. The it continues.
-
@tmsongster Thanks This worked for me.
-
Will this be fixed in the next update?