pkg-static: warning: database version 36 is newer than libpkg(3) version 35, but still compatible
-
Hello,
i need some help please.
i reinstalled pfSense 2.6 CE today and could not upgrade to pfSense Plus, then i created a ticked and got my problem solved by the support.then i upgraded to 22.01 reboot then upgrade to 22.05
then i checked Confirm that the latest version of pfSense-upgrade is present using
pkg-static info -x pfSense-upgrade
and i get this warning
pkg-static: warning: database version 36 is newer than libpkg(3) version 35, but still compatible pfSense-upgrade-1.0_29
here are my packages
[22.05-RELEASE][admin@pfSense.XXXXXXXX.de]/root: pkg info -x pkg pkg: warning: database version 36 is newer than libpkg(3) version 35, but still compatible pfSense-pkg-LCDproc-0.10.8_9 pfSense-pkg-Notes-0.2.9_3 pfSense-pkg-Status_Traffic_Totals-2.3.2_2 pfSense-pkg-System_Patches-2.0_7 pfSense-pkg-acme-0.7.3 pfSense-pkg-arpwatch-0.2.0_6 pfSense-pkg-darkstat-3.1.3_5 pfSense-pkg-haproxy-devel-0.62_10 pfSense-pkg-iperf-3.0.2_5 pfSense-pkg-nmap-1.4.4_6 pfSense-pkg-openvpn-client-export-1.6_8 pfSense-pkg-pfBlockerNG-devel-3.1.0_9 pkg-1.17.5_3 [22.05-RELEASE][admin@pfSense.XXXXXXXX.de]/root: pkg info -x pfSense pkg: warning: database version 36 is newer than libpkg(3) version 35, but still compatible pfSense-22.05 pfSense-Status_Monitoring-1.7.11_4 pfSense-base-22.05 pfSense-default-config-22.05 pfSense-kernel-pfSense-22.05 pfSense-pkg-LCDproc-0.10.8_9 pfSense-pkg-Notes-0.2.9_3 pfSense-pkg-Status_Traffic_Totals-2.3.2_2 pfSense-pkg-System_Patches-2.0_7 pfSense-pkg-acme-0.7.3 pfSense-pkg-arpwatch-0.2.0_6 pfSense-pkg-darkstat-3.1.3_5 pfSense-pkg-haproxy-devel-0.62_10 pfSense-pkg-iperf-3.0.2_5 pfSense-pkg-nmap-1.4.4_6 pfSense-pkg-openvpn-client-export-1.6_8 pfSense-pkg-pfBlockerNG-devel-3.1.0_9 pfSense-rc-22.05 pfSense-repo-22.05_14 pfSense-upgrade-1.0_29 php74-pfSense-module-0.81
can you guys have a look and tell me what is going on here and maybe how to fix this....
thank you
-
@horstzimmermann I'm having the same issue on a VM that started on 2.6CE and then upgrade to running 22.01 and cannot update beyond that.
pkg-static: warning: database version 36 is newer than libpkg(3) version 35, but still compatible pkg-static: sqlite error while executing INSERT OR IGNORE INTO mtree(content) VALUES(?1) in file pkgdb.c:115: no such table: mtree
-
@lurick said in pkg-static: warning: database version 36 is newer than libpkg(3) version 35, but still compatible:
@horstzimmermann I'm having the same issue on a VM that started on 2.6CE and then upgrade to running 22.01 and cannot update beyond that.
pkg-static: warning: database version 36 is newer than libpkg(3) version 35, but still compatible pkg-static: sqlite error while executing INSERT OR IGNORE INTO mtree(content) VALUES(?1) in file pkgdb.c:115: no such table: mtree
I ended up solving this by running this and rebooting. It also seemed to fix some other issues I was seeing on the GUI with failing to retrieve updates.
pkg install pfSense pfSense-base pfSense-default-config pfSense-kernel-pfSense pfSense-rc pfSense-repo pfSense-upgrade
-
Thank you but did not work for me
[22.05-RELEASE][admin@pfSenseXXXXXXX.de]/root: pkg install pfSense pfSense-base pfSense-default-config pfSense-kernel-pfSense pfSense-rc pfSense-repo pfSense-upgrade 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. pkg: warning: database version 36 is newer than libpkg(3) version 35, but still compatible Checking integrity... done (0 conflicting) The most recent versions of packages are already installed
it is strange, i have the same problems on all boot environments back to 22.01
-
Can be closed.
solved by reinstalling
-
@lurick Huge huge thank you!! I've been banging my head against the wall for weeks (on and off) trying to get a remote install working. No matter what I tried, I kept getting errors that pfSense couldn't find updates and that no packages were installed. Absolutely nothing was working or even giving me clues, but running that command (with -y added to work via the web UI) did the trick.
Thank you!