Package reinstallation post-config restore hangs if no Internet connectivity
If you restore a config, and upon reboot the system doesn't have Internet connectivity when trying to update metadata for packages, it'll get stuck during boot. It needs to timeout and continue with the boot in that circumstance like <=2.2.x.
#3 Updated by Chris Buechler 7 months ago
- Description updated (diff)
- Priority changed from Normal to High
It's still the package reinstall that gets hung up, regardless of whether or not you have packages installed. It sets needs_package_sync_after_reboot regardless of whether there are packages in the config, which is where it gets hung.
#4 Updated by Kevin Wojniak about 2 months ago
I'm running into this right now. Not a big network guy, just trying to replace our small business' router with a SG-4860 1U and twiddling my thumbs while the router sits and attempts to access WAN even though interfaces haven't been assigned (I did a restore of the config from the web).
I think changing it to not attempt 3 (?) times and use a lower timeout would greatly help. Then I could be on my way home sooner :)
#5 Updated by Pig Monkey about 2 months ago
I was just hit by this as well. In my case I am preparing to replace a device at a remote site. I used pfsense's restore functionality to upload the configuration from the old device to the new device, and rebooted. Then wondered why it seemed to still be hanging 15 minutes later.
After throwing in a serial cable and power cycling the new device, I saw the "Waiting for Internet connection to update pkg metadata and finish package reinstallationUpdating pfSense-core repository catalogue..." message. After hanging there for a while it moves on to "Updating pfSense repository catalogue..." and then hangs again. It finally errors there, and then moves on to hanging at "Updating pfSense-core repository catalogue..." And then it loops back to "pfSense repository catalogue...". It does the loop 3 or 4 times.
A shorter timeout is definitely appropriate. If the first check fails, it would be nice if it did not attempt the subsequent updates. Perhaps there should be some sort of "offline" boot option that we can use to prevent any connection attempts if we know we're going to bring the device up without WAN.