Secondary can't see update info 2.6 (pfSense-core contains no repodata table ???)
-
@MrPete said in Secondary can't see update info 2.6 (pfSense-core contains no repodata table ???):
more to do with the error message saying pfSense-core is missing a repodata table... ie a sqlite database problem.
That's the real issue.
IMHO : don't even try to repair the database issue. It isn't worth the learning curve ^^
That's why I mentioned the more manual 'USB' upgrade.
You can upgrade your master the method you want, although (to be checked) : a new install proposes you the ZFS file system, which is more resilient as the older one that 2.6.0 used.@MrPete said in Secondary can't see update info 2.6 (pfSense-core contains no repodata table ???):
BTW, I didn't "decide
Don't worry, every decision we make is made based on current personal conditions.
Let this one be an easy one for you
-
Hmm, that was running:
pfSense-upgrade -dc? -
@stephenw10 said in Secondary can't see update info 2.6 (pfSense-core contains no repodata table ???):
Hmm, that was running:
pfSense-upgrade -dc?Yep. Just ran it again. NOTE: the first line below (ERROR...) is only in upgrade_log.txt -- not returned by
pfSense-upgrade -dc.ERROR: It was not possible to identify which pfSense meta package is installed >>> Updating repositories metadata... Updating pfSense-core repository catalogue... pfSense-core repository is up to date. Updating pfSense repository catalogue... pfSense repository is up to date. All repositories are up to date. version of pfSense is availableFWIW, as a data guy, it was not hard for me to go find the *.sqlite files and export to *.sql -- I don't know exactly what to expect of course, but they look reasonably similar on both systems.
I get the "cleanest" outcome by setting the target to 2.6 and running
pkg-static -d update... fewer errors but still the result is the same: the system won't actually do an update ("unable to check for updates" in the GUI). And ``pkg-static -d update` produces the same output. Metadata error, and blank version number in the log.FWIW as a reminder, on 100% ok primary configured the same, this is the result of
pkg-static -d update:>>> Updating repositories metadata... Updating pfSense-core repository catalogue... pfSense-core repository is up to date. Updating pfSense repository catalogue... pfSense repository is up to date. All repositories are up to date. 2.7.0 version of pfSense is available@Gertjan is of course correct that I could start from scratch... but I have a hunch this upgrade issue will bite me again in the future. As a SW dev myself, I appreciate having 100% repeatable symptoms
-
Yeah, I'd guess it's pulled in some pkg the other system doesn't have.
Try running:
pkg-static info -x pfsenseon both nodes and comparing.You may need to set it back to 2.6 and force reload something. Either the upgrade or repo pkg I'd guess.
Steve
-
@stephenw10 wow is THAT a revelation! Guess what's missing from secondary... how can it even be running LOL:
pfSense-2.6.0
pfSense-base-2.6.0
pfSense-default-config-2.6.0
pfSense-kernel-pfSense-2.6.0
pfSense-rc-2.6.0
php74-pfSense-module-0.76using
pkg-static install -fy pfSense-2.6.0 pfSense-base-2.6.0 pfSense-default-config-2.6.0 pfSense-kernel-pfSense-2.6.0 pfSense-rc-2.6.0
then will add the new php74... -
It actually doesn't have either of those pkgs?
Make sure the repo is set to 2.6 and install them if so.
-
-
Nice!
-
@stephenw10
Spoke too quickly. System upgrade to 2.7 failed w/ a pile of sqlite3 errors. TIme to install 2.7 from scratch. Something's seriously wrong beyond even those obvious things. -
Hmm, disappointing. It's common to see a lot of errors at upgrade if you're looking at the console. It should still succeed of course!
