frozen package update

adamw

Hi all,

I've just updated Netgate SG-3100 from 2.4.4-p3 to 2.4.5-p1 through web GUI. I had a "Success" message followed by a reboot. The firewall is working and accessible.

The problem is when I try updating 2 outdated packages (bandwidthd and openvpn-client-export) in /pkg_mgr_install.php I get:

Package Reinstallation
Please wait while the update system initializes

30 mins later there is no progress and when I check package version in a new tab the old versions are still reported.

What shall I do about it at this stage (ideally without rebooting the device)?

Regards,
Adam

adamw

Also - is this warning related and something to worry about?

# pkg info | grep openvpn
pkg: Warning: Major OS version upgrade detected.  Running "pkg bootstrap -f" recommended
openvpn-2.4.9                  Secure IP/Ethernet tunnel daemon
openvpn-auth-script-1.0.0.3    Generic script-based deferred auth plugin for OpenVPN
openvpn-client-export-2.5.0    OpenVPN Client Export
pfSense-pkg-openvpn-client-export-1.4.19_1 pfSense package openvpn-client-export

Gertjan

@adamw said in frozen package update:

old versions are still reported.

... and still shown as "running" ?
That that's a problem.

@adamw said in frozen package update:

bandwidthd

stop it - stop the service.
Then do a reboot.

"openvpn-client-export" isn't a process or daemon. Just a bunch of GUI scripts and support files.

adamw

Manually stopping bandwidthd service made no difference.

An hour later /pkg_mgr_install.php is still stuck on "Please wait while the update system initializes".

Would it be reasonable to try updating both bandwidthd and openvpn-client-export from the shell?

I would rather avoid having to stop openvpn service or rebooting the entire device if possible.

SteveITS

@adamw I don't have a link for you but I seem to recall several posts about package installation/updates getting stuck after upgrading to 2.4.5. You might look back through posts from this spring/summer. I seem to recall discussion of killing a process? I just never ran into it myself.

RonpfS

@teamits
Check if Unbound is running. We have to restart Unbound after upgrading pfblockerNG.

Disabling package before upgrading might be good. I also disable Auto Config Backup to prevent timeout if DNS services goes down.

adamw

@gertjan

A reboot alone fixed it. Both outdated packages now report the latest versions. I've checked in web GUI and from the shell.

Thanks and happy 2021!

adamw

The real solution was not a process kill or reboot but switching to the correct branch!

System -> Update -> Branch -> Previous stable version (2.4.5 DEPRECATED)

SteveITS

@adamw Yes, you always need to be on the correct version or else an install attempt will try to upgrade the package manager software, in this case to 21.02.
https://redmine.pfsense.org/issues/10464