Cannot view installed packages, "Unable to retrieve package information."

[steveharriss]

Reporting the same issue: Installed iPerf from package manager and now get the error message: Unable to retrieve package information.

pkg info shows all installed packages, including iPerf.

My system:2.3.1-RELEASE-p5 (amd64)
built on Thu Jun 16 12:53:15 CDT 2016
FreeBSD 10.3-RELEASE-p3

I'll have to leave the console fix until tomorrow

[steveharriss]

All fixed using SSH and updating

[lab]

@algeriani87:

hello
for lab: you can just ssh to it if you configue it from GUI
then you get the consol even remotely
regards

Fixed with option 13 through ssh. Happy as a bunny.

[Mike5906]

I just ran into the same problem after installing Squid and LightSquid.  All ability to check for packages and update from the GUI failed.

I can confirm that SSH to console, option 13 fixed the problem.  This is going to reboot your router, so make sure you plan appropriately.

[attilahooper]

yup, option 13 Update from console worked a charm. Thanks everyone. Didn't seem to take too long but mine is a hefty system with good inet.

[musicwizard]

Had the same problem.

a update option 13 worked took about 10 min to update the system.

didnt had the latest pfsense yet installed but now i have :)

[lemonkey]

@lemb:

Are you me?

I've found I can still install and remove packages from the command line using pkg, but I get "No packages installed. Packages can be installed here." on the dashboard and "Unable to retrieve package information." at the package manager.

This happened immediately after trying to upgrade the Zabbix-Proxy package.

Ha same thing happened to me yesterday.

"pkg version" is showing that pkg-1.8.7 is the latest version, but I've been told to upgrade to 2.3.2 to fix it.

[luckman212]

I wound up paving and reinstalling.  "It's the only way to be sure" (for the Aliens fans)

[DeLorean]

Update 5 for pfSense 2.3.1 was a waste of time and effort,
this update gave problems on almost every firewall device i worked on.
A clean install with the new version 2.3.2 fixed all those rare problems like :
No packages available after upgrade
2u time for updating from 2.3.1 to 2.3.1.5
PHP errors during bootup
pfSense installation corruption on reboot
etc….
Update 5 should never be released, and they had to stick by 2.3.1 till the next stable version 2.3.2 was ready.
From now on, on Watchguard Firewalls i install only the stable releases and not the crappy updates in between.

Grtz
DeLorean

[dsefcik]

I am another "option 13 fixed my problem"….had 2.3.1 p5 and after any pkg install it broke the dashboard update status and gui pkg manager.

[jimp]

https://forum.pfsense.org/index.php?topic=116227.0