Broken update check & packages list
-
Hello,
After a 'very' chaotic upgrade to 2.4 (several attempts needed then multiple reboot to complete and required to unplug the UPS serial port) I kind of have a running 2.4.0 (kind of as several openvpn sessions are instable now and require a 'route flush' command before restarting the failed daemon.
The more problematic issue I am seeing is the list of installed packages, the list of available packages and the update that are not working.
*** Welcome to pfSense 2.4.0-RELEASE (amd64) on pfSense ***
Enter an option: 13
Updating repositories metadata…
Updating pfSense-core repository catalogue...
pkg: Repository pfSense-core load error: access repo file(/var/db/pkg/repo-pfSense-core.sqlite) failed: No such file or directory
pkg: https://pkg.pfsense.org/pfSense_v2_4_0_amd64-core/meta.txz: Network is unreachable
repository pfSense-core has no meta file, using default settings
pkg: https://pkg.pfsense.org/pfSense_v2_4_0_amd64-core/packagesite.txz: Network is unreachable
Unable to update repository pfSense-core
Updating pfSense repository catalogue...
pkg: Repository pfSense load error: access repo file(/var/db/pkg/repo-pfSense.sqlite) failed: No such file or directory
pkg: https://pkg.pfsense.org/pfSense_v2_4_0_amd64-pfSense_v2_4_0/meta.txz: Network is unreachable
repository pfSense has no meta file, using default settings
pkg: https://pkg.pfsense.org/pfSense_v2_4_0_amd64-pfSense_v2_4_0/packagesite.txz: Network is unreachable
Unable to update repository pfSense
Error updating repositories!Is there any way to fix this issue ?
Thanks,
/M
-
Does your system maybe have an incomplete IPv6 configuration?
Try using 8 to get a shell prompt and then run:
pfSense-upgrade -4 -
Same ….
Enter an option: 8
[2.4.0-RELEASE][******@pfSense.localdomain]/root: pfSense-upgrade -4
Updating repositories metadata…
Updating pfSense-core repository catalogue...
pkg: Repository pfSense-core load error: access repo file(/var/db/pkg/repo-pfSense-core.sqlite) failed: No such file or directory
pkg: https://pkg.pfsense.org/pfSense_v2_4_0_amd64-core/meta.txz: Network is unreachable
repository pfSense-core has no meta file, using default settings
pkg: https://pkg.pfsense.org/pfSense_v2_4_0_amd64-core/packagesite.txz: Network is unreachable
Unable to update repository pfSense-core
Updating pfSense repository catalogue...
pkg: Repository pfSense load error: access repo file(/var/db/pkg/repo-pfSense.sqlite) failed: No such file or directory
pkg: https://pkg.pfsense.org/pfSense_v2_4_0_amd64-pfSense_v2_4_0/meta.txz: Network is unreachable
repository pfSense has no meta file, using default settings
pkg: https://pkg.pfsense.org/pfSense_v2_4_0_amd64-pfSense_v2_4_0/packagesite.txz: Network is unreachable
Unable to update repository pfSense
Error updating repositories! -
Even the list of installed packages is empty, while I do have a couple of package installed and working like Apcupsd or Service Watchdog.
Installed Packages
There are no packages currently installed. -
i had something similar. im only using the intern DNS so it shows 127.0.0.1 so while it was rebooting and trying to install the packaged etc it could not get a connection. So i had to enabled the " Allow DNS server list to be overridden by DHCP/PPP on WAN" and then it worked.
-
If that's the case then somehow your firewall is missing a default route. It's possible something in your VPN config (or something a VPN provider is pushing you) is breaking that but it's impossible to tell what without more information.
What does the routing table look like? ("netstat -rn")
Are those OpenVPN instances using conflicting networks or routes?
What errors, if any, are you seeing in the system logs or openvpn logs?
-
This is a multi-wan setup (cable @Igb0 + 4GLTE @Igb3 backup via a LB1120). The System/Advanced/Miscellaneous "Enable default gateway switching" is checked. For the DNS, 8.8.8.8 & 8.8.4.4 are define and set to none, while there is a specific DNS set for cable and another one for 4GLTE. No gateway was set to be default gateway.
Following you reply, I do have set the cable gateway to be the default gateway and since then the package list are working now. I still don't understand why this was working ok before the upgrade.
Thanks.
/M
-
If either one of your WANs is PPP, then default gateway switching can fail in this way. It's a known issue we've tried fixes for over the years but always ended up backing them out because something else failed.
You must have a default gateway, however. It's possible that in the past the PPP gateway was becoming default even when it wasn't set to be.
