Restoring from Auto Cloud Backup does not reinstall packages
-
Hi, something strange is going on, or maybe i'm doing something wrong.
The eSata drive in my firewall failed unexpectedly a couple of days ago. I was at the time running the last of the 2.6RC versions.
I've re-installed pfsense with 2.6 release, and tried to do the restore from the auto config backup.
The first time I tried, i was left with a non functional web interface. I figured maybe the config was corrupt so I did a factory reset and tried a second time, with a slightly older config version.This firewall now appears to work in so far as the web UI is functional, but none of the packages
In the config version history on the box, it shows the system uninstalling packages? But it's not a comprehensive list of the missing packages, only some of them.
I thought there was an option somewhere to "reinstall all packages" but I can't seem to find it, has this been removed?
I'm just not sure i trust the restore even if I manually install all the packages.
-
It's in Diag > Backup & Restore. But it will only reinstall packages you have marked as installed. Which may not be any.
Since you came from a 2.6RC backup you may also be hitting a repo branch issue. RC is considered the 'Next' branch and when it's released that is removed. The pkg system will automatically move to the default branch which is now 2.6 but maybe not before it checks and sees packages are not available.
What I would do here is download the config you need and remove the repo line from it:
<pkg_repo_conf_path>/usr/local/share/pfSense/pkg/repos/pfSense-repo-next.conf</pkg_repo_conf_path>Then restore it locally.
Steve
-
@stephenw10 said in Restoring from Auto Cloud Backup does not reinstall packages:
It's in Diag > Backup & Restore. But it will only reinstall packages you have marked as installed. Which may not be any.
Since you came from a 2.6RC backup you may also be hitting a repo branch issue. RC is considered the 'Next' branch and when it's released that is removed. The pkg system will automatically move to the default branch which is now 2.6 but maybe not before it checks and sees packages are not available.
What I would do here is download the config you need and remove the repo line from it:
<pkg_repo_conf_path>/usr/local/share/pfSense/pkg/repos/pfSense-repo-next.conf</pkg_repo_conf_path>Then restore it locally.
Steve
Thanks. Will try a restore again without that line and report back.
I also learnt that the "reinstall package" option isn't there until it thinks that i have packages.
-
@stephenw10 Thanks, that appeared to work with the exception of Avahi but at least it let me about it
Package avahi-daemon does not exist in current pfSense version and it has been removed. @ 2022-02-20 14:58:22
Package reinstall process finished successfully @ 2022-02-20 15:03:18 -
Yeah, there is a separate issue with Avahi but you should just be able to reinstall in.
Steve
-
@stephenw10 Yes thanks a simple re-install solved the issue.
But i've ended up having to factory reset it again. Internet browsing was just... slow and troublesome. Speedtests were fine but pages would stall, not load etc.
It felt like a DNS or state issue of some kind, but I could not work it out. Switching the DNS from Resolver to Forwarded made no difference, so I'm ruling out DNS.
The firewall state table seemed to have excessing numbers of connection in fin_wait_2 and syn_sent, time_wait etc.Is there an easy place for me to find what changed between the last RC and Release? I'm wondering if there's some asymmetric routing issue with the policy routing or a shaper issue of some kind, but I never had a problem with any of the RC releases.
Troubleshooting can only be done late at night as we are all working from home so that complicates things so if I can focus on what parts of pfsense changed it might give me some direction. -
Hmm, there was no significant change I can think of between the last 2.6RC and 2.6-REL.
One thing that can present like that is partial IPv6 connectivity. If pfSense is handing out v6 IPs to clients but not passing v6 traffic they will try to use it and have to timeout each time. But actual connection speeds once they fall back to v4 will be fine.
Steve
-
@stephenw10 said in Restoring from Auto Cloud Backup does not reinstall packages:
Hmm, there was no significant change I can think of between the last 2.6RC and 2.6-REL.
One thing that can present like that is partial IPv6 connectivity. If pfSense is handing out v6 IPs to clients but not passing v6 traffic they will try to use it and have to timeout each time. But actual connection speeds once they fall back to v4 will be fine.
Steve
Legend. You're bang on target with your ipv6 guess. Neither my previous config or a default config are working with IPv6. Clients get address from RA and WAN has correct address from ISP but the firewall appears to be dropping. I see traffic on the WAN side go out and come back but on the LAN side it's all re-transmits.
-
Ah, yup that will do it. And it sure makes for a crappy experience at the client end!
Disabling v6 on the LAN in pfSense will prevent it. Or setting it up correctly if your ISP gives you a PD you can use.
Steve
