Unable to retrieve package information after 2.3.3 reset
-
I've been trying to get e2guardian working and hit a roadblock so I dropped to CLI and did a "4) Reset to factory defaults". It seemed to go OK but when I go to the packages it tells me it's "Unable to Retrieve Package Information". I drop to the CLI and get:
[2.3.3-RELEASE][root@pfSense.localdomain]/root: pkg update 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 Fetching meta.txz: 100% 944 B 0.9kB/s 00:01 Child process pid=85873 terminated abnormally: Segmentation fault
Seems a DB got nuked maybe? pkg info shows a bunch of packages so they are there and running it seems, but unable to make changes. There's nothing I care about but getting a CD to it to reinstall is a bit of a pain. Is there any way to rebuild it or wipe/restart from scratch without using a CD?
-
Hi,
Same here after trying to configure new features and rolling back, by loading last config. Entered shell and this is the result (still in 2.3.1):
[2.3.1-RELEASE][admin@pfSense.casa]/root: pkg update
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
Fetching meta.txz: 100% 944 B 0.9kB/s 00:01
Child process pid=89499 terminated abnormally: Segmentation faultFiles on /var/db/pkg/repo-pfSense-core.sqlite are:
[2.3.1-RELEASE][admin@pfSense.casa]/var/db/pkg: ls -la
total 50804
drwxr-xr-x 2 root wheel 512 Apr 12 12:01 .
drwxr-xr-x 18 root wheel 1536 Apr 12 11:53 ..
-rw-r–r-- 1 root wheel 246 Apr 9 19:12 FreeBSD.meta
-rw-r--r-- 1 root wheel 3561472 Apr 9 19:15 local.sqlite
-rw-r--r-- 1 root wheel 246 Apr 12 12:01 pfSense-core.meta
-rw-r--r-- 1 root wheel 246 Apr 12 11:42 pfSense.meta
-rw-r--r-- 1 root wheel 48362496 Apr 9 19:15 repo-FreeBSD.sqliteAny help very appreciated.
-
I've replaced it with one from another machine and it appears to be working fine so far. Not sure what else it'll break, though. I've attached it here. I'm 2.3.3-RELEASE-p1 (amd64)
-
Same problem… but repalcing it does not help!
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 direct ory
Fetching meta.txz: . done
Child process pid=92875 terminated abnormally: Segmentation fault
*** Welcome to pfSense 2.3.2-RELEASE (amd64 full-install) on FW ***[2.3.2-RELEASE][root@FW]/root: ls -la /var/db/pkg/
total 8304
drwxr-xr-x 2 root wheel 512 Apr 19 15:47 .
drwxr-xr-x 18 root wheel 1024 Apr 19 15:48 ..
-rw-r–r-- 1 root wheel 246 Apr 18 04:07 FreeBSD.meta
-rw-r--r-- 1 root wheel 7559168 Apr 19 15:11 local.sqlite
-rw-r--r-- 1 root wheel 246 Apr 19 15:47 pfSense-core.meta
-rw-r--r-- 1 root wheel 830464 Apr 19 15:44 repo-pfSense.sqlite
[2.3.2-RELEASE][root@FW]/root:Any Ideas?
-
Looks like I uploaded the wrong file. Here it is again.
-
I think some files have already changed in the repo… now i get:
The operation will free 62 MiB.
102 MiB to be downloaded.
[1/98] Fetching strongswan-5.5.1.txz: …....... done
pkg: cached package strongswan-5.5.1: size mismatch, fetching from remote
[2/98] Fetching strongswan-5.5.1.txz: …....... done
pkg: cached package strongswan-5.5.1: size mismatch, cannot continueLocking package pfSense-kernel-pfSense... done.
*** Welcome to pfSense 2.3.2-RELEASE (amd64 full-install) on FW *** -
Can you now try to run:
pkg update -f
and see if it does anything? I think that's the command to update packages. -
I get this: :(
[2.3.2-RELEASE][root@FW]/root: pkg update -f
Updating pfSense-core repository catalogue…
Fetching meta.txz: 100% 944 B 0.9kB/s 00:01
Child process pid=76710 terminated abnormally: Segmentation fault -
Are your files from 2.3.3 or from 2.3.3_1 ? can you try to pkg update -f and resend the both sqlite ?
-
I'm on 2.3.3-RELEASE-p1. Looks like you are on 2.3.2. Maybe those files are different between versions. You could try to spin one up in Virtualbox and extract the files from there. That could get you going.