Since upgrade from 2.4.4 to 2.4.5 : upgrading or reinstalling packages seems to have stopped working?
-
Hi,
I upgraded from 2.4.4 to 2.4.5 through the GUI. That went well, no issues.
After the upgrade, I tried to upgrade some of the packages which showed as upgrade available.
That does not work, when I confirm, it says "Initializing ... " nothing else happens.I followed the instructions here :
https://docs.netgate.com/pfsense/en/latest/install/upgrade-troubleshooting.html
I did :
pkg-static clean -ay; pkg-static install -fy pkg pfSense-repo pfSense-upgrade
pkg-static update -fWith pkg-static update -f it says
Installed packages to be UPGRADED: pfSense-pkg-acme: 0.6.8 -> 0.6.8_2 [pfSense] pfSense-pkg-arpwatch: 0.2.0_3 -> 0.2.0_4 [pfSense] pfSense-pkg-pfBlockerNG-devel: 2.2.5_33 -> 2.2.5_34 [pfSense] pfSense-pkg-snort: 3.2.9.13 -> 3.2.9.14_1 [pfSense] pfSense-pkg-squid: 0.4.44_28 -> 0.4.44_30 [pfSense] Installed packages to be REINSTALLED: (long list) .... socat-1.7.3.3_1 [pfSense] sqlite3-3.30.1 [pfSense] squid-4.10 [pfSense] squidGuard-1.4_15 [pfSense] squid_radius_auth-1.10 [pfSense] ..... Number of packages to be upgraded: 6 Number of packages to be reinstalled: 274
So I confirm to continue.
Then it seems to hang on the re-installation/upgrade of squidguard :[245/280] Extracting pfSense-pkg-suricata-5.0.3: 100% Removing suricata components... Menu items... done. Services... done. Loading package instructions... Saving updated package information... overwrite! Loading package configuration... done. Configuring package components... Loading package instructions... Custom commands... Executing custom_php_install_command()...Saved settings detected... Migrating settings to new configuration... done. Downloading Emerging Threats Open rules md5 file... done. There is a new set of Emerging Threats Open rules posted. Downloading... done. Downloading Snort VRT rules md5 file... done. There is a new set of Snort rules posted. Downloading... done. Downloading Snort GPLv2 Community Rules md5 file... done. There is a new set of Snort GPLv2 Community Rules posted. Downloading... done. Installing Emerging Threats Open rules... done. Installing Snort rules...tar: rules: Not found in archive tar: Error exit delayed from previous errors. tar: etc: Not found in archive tar: Error exit delayed from previous errors. done. Installing Snort GPLv2 Community Rules... done. Updating rules configuration for: LAN ... done. Updating rules configuration for: WAN ... done. Cleaning up after rules extraction... done. The Rules update has finished. Generating suricata.yaml configuration file from saved settings. Generating YAML configuration file for LAN... done. Generating YAML configuration file for WAN... done. Finished rebuilding Suricata configuration from saved settings. Setting package version in configuration file. done. Executing custom_php_resync_config_command()...done. Menu items... done. Services... done. Writing configuration... done. [246/280] Upgrading pfSense-pkg-squidGuard from 1.16.18_6 to 1.16.18_7... [246/280] Extracting pfSense-pkg-squidGuard-1.16.18_7: 100% Removing squidGuard components... Menu items... done. Services... done. Loading package instructions... Deinstall commands... done.
it does not continue after "Deinstall commands... done."
(note : suricata is installed but disabled/not in use)I rebooted a few times, retried pkg-static update -f
same result every time.Anyone who can provide some light on this or help?
Thanks
L
-
Look at the CLI with ps -ax | grep pkg if you have a process pkg-static already running and kill him. Then try again.
My 2 cents,
fireodo -
@fireodo said in Since upgrade from 2.4.4 to 2.4.5 : upgrading or reinstalling packages seems to have stopped working?:
ps -ax | grep pkg
I already tried that also a few times :
[2.4.5-RELEASE][root@aureliusgate01.loftnet.intra]/root: [2.4.5-RELEASE][root@aureliusgate01.loftnet.intra]/root: ps -ax | grep pkg 22125 - S 0:01.02 /usr/local/bin/php -f /usr/local/pkg/pfblockerng/pfblockerng.inc queries 75583 0 I 0:24.63 pkg-static upgrade -f 93951 0 I 0:00.04 /bin/sh /usr/local/pkg/sqpmon.sh 19742 1 S+ 0:00.00 grep pkg [2.4.5-RELEASE][root@aureliusgate01.loftnet.intra]/root: kill 75583 [2.4.5-RELEASE][root@aureliusgate01.loftnet.intra]/root: ps -ax | grep pkg 22125 - S 0:01.02 /usr/local/bin/php -f /usr/local/pkg/pfblockerng/pfblockerng.inc queries 93951 0 I 0:00.04 /bin/sh /usr/local/pkg/sqpmon.sh 28921 1 S+ 0:00.00 grep pkg [2.4.5-RELEASE][root@aureliusgate01.loftnet.intra]/root: pkg-static upgrade -f 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 for upgrades (285 candidates): 100% Processing candidates (285 candidates): 100% Checking integrity... done (0 conflicting) The following 280 package(s) will be affected (of 0 checked): Installed packages to be UPGRADED: pfSense-pkg-acme: 0.6.8 -> 0.6.8_2 [pfSense] pfSense-pkg-arpwatch: 0.2.0_3 -> 0.2.0_4 [pfSense] pfSense-pkg-pfBlockerNG-devel: 2.2.5_33 -> 2.2.5_34 [pfSense] pfSense-pkg-snort: 3.2.9.13 -> 3.2.9.14_1 [pfSense] pfSense-pkg-squid: 0.4.44_28 -> 0.4.44_30 [pfSense] pfSense-pkg-squidGuard: 1.16.18_6 -> 1.16.18_7 [pfSense] Installed packages to be REINSTALLED: arc-5.21p [pfSense] arj-3.10.22_8 [pfSense] arping-2.19 [pfSense] arpwatch-3.0_3 [pfSense] ................... [245/280] Extracting pfSense-pkg-suricata-5.0.3: 100% Removing suricata components... Menu items... done. Services... done. Loading package instructions... Saving updated package information... overwrite! Loading package configuration... done. Configuring package components... Loading package instructions... Custom commands... Executing custom_php_install_command()...Saved settings detected... Migrating settings to new configuration... done. Downloading Emerging Threats Open rules md5 file... done. There is a new set of Emerging Threats Open rules posted. Downloading... done. Downloading Snort VRT rules md5 file... done. There is a new set of Snort rules posted. Downloading... done. Downloading Snort GPLv2 Community Rules md5 file... done. There is a new set of Snort GPLv2 Community Rules posted. Downloading... done. Installing Emerging Threats Open rules... done. Installing Snort rules...tar: rules: Not found in archive tar: Error exit delayed from previous errors. tar: etc: Not found in archive tar: Error exit delayed from previous errors. done. Installing Snort GPLv2 Community Rules... done. Updating rules configuration for: LAN ... done. Updating rules configuration for: WAN ... done. Cleaning up after rules extraction... done. The Rules update has finished. Generating suricata.yaml configuration file from saved settings. Generating YAML configuration file for LAN... done. Generating YAML configuration file for WAN... done. Finished rebuilding Suricata configuration from saved settings. Setting package version in configuration file. done. Executing custom_php_resync_config_command()...done. Menu items... done. Services... done. Writing configuration... done. [246/280] Upgrading pfSense-pkg-squidGuard from 1.16.18_6 to 1.16.18_7... [246/280] Extracting pfSense-pkg-squidGuard-1.16.18_7: 100% Removing squidGuard components... Menu items... done. Services... done. Loading package instructions... Deinstall commands... done.
Same result
-
@lightningbit Do you have Snort AND Suricata installed?
You could uninstall all packages and make the pfsense update and reinstall the packages after the update is done (If you set on the packages who allowed this to keep the settings you dont lose settings after uninstall) -
I had the same issue. I reverted to 2.4.4p3 and all packages downloaded and installed smoothly. Package upgrades also worked fine.
As a check I backed up my config, did a fresh install of pfSense 2.4.5p1 and reapplied my config. Packages downloaded and installed up to and including squid; after that the package install process appeared to go no further, according to System logs. No errors reported, but no progress either.
See https://forum.netgate.com/topic/156380/clear-package-lock-not-working-etc-rc-package_reinstall_all-still-running
-
so it is not just me, there seem to be issues with the package manager in 2.4.5p1
-
https://forum.netgate.com/topic/154403/squidguard-update-fails-after-upgrading-pfsense-2-4-5-release-p1/52
hope it gets fixed in the next update