No available packages (empty list)
I'm still finding the following problem since the change of the system upgrade/package management (last year, now based on the slower "pkg" method).
Again, on a fresh 2.3.4-p1 install (it happens on both a VM full install and an embedded device) I encounter a empty list on "available packages", after having already installed some with no errors.
Has anybody any ideas?
Thanks in advance.
I am right in saying that all of this is due to the new pkg-based system & packages install/upgrade method.
Infact, trying manually from the shell, I cannot install anything via pkg too, getting the following error:
pkg: Repository pfSense-core load error: access repo file(/var/db/pkg/repo-pfSense-core.sqlite) failed: No such file or directory
Still, I don't understand why the packaging system isn't creating the new .sqlite file when it relizes it doesn't exist (as it was pointed out in other forum topics).
Not to mention that this is a fresh install and that I've already seen this happening with full installs on a VM and with nanobsd imgs on an embedded device; from my viewpoint it happens randomly.
I think this problem is still to be well analyzed and addressed.
All I can do to fix it quickly it to reinstall… and cross my finger for the next "package install" time.
accessing the 'update' function from the 'system' menu in the gui, it says "up to date", but trying to display the 'update settings" I get a "50 GAteway Time-out" blank screen from ngix (so I cannot try to change the repository source)
Gertjan last edited by
Advice : reboot (the dumb way)
Access console, then telnet or SSH (option 8) and then
and - if present, kill any "pkg" processes.
Also : I advice you to read all those many threads about what to do if updating doesn't work.
the problem was permanent, a simple reboot didn't work.
The problem was (because I've already solved it with a system+package reinstallation, that eventually went fine) due to a pkg-related sqlite database error that - despite applying the raccomandations given in other threads (i.e. forced update/upgrade of the system) - didn't solve the issue (and most of all, they were lenghty to execute).
As the issue was created immediately after installation with no warning, I consider this solution a defeat. As a matter of fact, we still don't know the cause but the reinstallation was surely the fastest way to solve: I already know the beast.
At the current state of the art and from my viewpoint, there has been a considerable loss of performance (mostly on pfsense boxes installed on nanobsd-powered embedded devices) and stability (as it is witnessed by the large number of threads in the forum about this topic) after the introduction of the pkg-based system upgrade/package management method.