Bug #16367
closed
Reinstall Packages button reports another instance of ``pfSense-upgrade`` is running (Not a duplicate of #15494)
0%
Description
This is a simple disaster recovery test restore where the static WAN IP is the only item changing from the original configuration. The same hardware NICs are used in both installations.
The Netgate installer runs perfectly using an IP that is not the same as what is used in the original configuration. The LAN IP is not assigned on purpose.
At the end of the installation, the original configuration file is copied to the new installation. There are no errors to report and the firewall is rebooted.
Upon reboot, the following message is displayed:
Package reinstall process was ABORTED due to lack of internet connectivity @ 2025-08-12 13:00:22
This is normal: the original WAN IP is invalid in the new environment. The WAN IP is updated using option 2 of the startup menu.
At this point, the firewall is reachable via WAN but no packages are installed.
Pushing the "Reinstall Packages" button yields the message:
Another instance of pfSense-upgrade is running. Try again later
The interesting part occurs on the next reboot.
First, the WAN IP reverts to the original IP. In the list of available bakcups, I find:
...
03. 8/12/25 16:10:15 v24.0 admin@... (Local Database)
Creating restore point before package installation.
02. 8/12/25 16:14:15 v24.0 admin@... (Local Database)
Upgraded config version level from 23.3 to 24.0
01. 8/12/25 16:14:53 v24.0 admin@... (Local Database)
Removed nmap package.
Of course, nmap was not installed to begin with. The original configuration file is available from a FAT32 partition that was used during the ISO install and it is unclear why it is being fetched again.
Second, the "Reinstall Packages" button is no longer available.
I can force the display of the reinstall page with [[https://WAN_IP/pkg_mgr_install.php]] and I get
Please wait while the update system initializes
but nothing else happens.
In this test, only three packages were to be reinstalled: acme, nmap, and system_patches.
Regards,
Updated by Serge Caron 30 days ago
Add-on note:
This firewall is running as a virtual machine on Hyper-V.
The configuration file to be restored is placed on a 16GB virtual disk (MBR, FAT32).
In order to avoid the duplicate copy of the configuration file on the second reboot, the firewall is powered off at the end of the installation ("[Shell], poweroff" instead of "[Reboot]"). The ISO and the virtual disk are removed from the VM config.
However, this is a side issue. On the initial boot, after updating the WAN IP, the packages are not reloaded when pushing the "Reinstall Packages" button.
Regards,
Updated by Serge Caron 30 days ago
Add-on note:
I noticed that DNS resolution is not working after updating the WAN IP.
If I reboot the system immediately after updating the WAN IP, all configuration data is removed from the configuration as soon as the system is restarted!!!
8/13/25 10:54:21 24.0 221 KiB (system): Removed acme package. Current configuration
8/13/25 10:54:21 24.0 222 KiB (system): Removed nmap package.
8/13/25 10:53:21 24.0 0 B (system): wan IP configuration from console menu
8/13/25 10:51:34 24.0 222 KiB (system): Configured default pkg repo after restore
8/13/25 10:50:43 24.0 222 KiB (system): Upgraded config version level from 23.3 to 24.0
8/11/25 15:15:08 23.3 222 KiB admin@[IP] (Local Database): Saved configuration changes for IPsec tunnels.
This is a severe regression.
Regards,
Updated by Jim Pingle 28 days ago
- Status changed from New to Rejected
I can't reproduce this as stated. Most likely the problem is a lack of WAN connectivity when it comes back up, hence the initial error about the package reinstall being aborted. Just changing the IP address in the backup had zero effect for me so long as it was otherwise valid (good gateway, subnet mask, WAN L1/L2 config, etc).
Even when I deliberately broke the connectivity I received the "aborted" error but then later when restoring connectivity I was able to reinstall packages without issue using the "reinstall all packages" button.
So it's unclear what is happening to your setup in your environment but there isn't enough here to go by. This site is not for support or diagnostic discussion.
For assistance in solving problems, please post on the Netgate Forum .
See Reporting Issues with pfSense Software for more information.
Updated by Serge Caron 28 days ago
Thank you for your time.
As reported, issue #16374 is the detailled process to reproduce this condition. I understand that this site is not for support or diagnostic discussion.
I am waiting for a physical replacement to one of our firewalls to reproduce this setup "in the real world" using the same recipe.
Regards,