2.3.1.5 Unable to check for updates

D0X

Without changing anything overnight, my box shows "Unable to check for updates" and "Unable to retrieve package information."

Found this topic: https://forum.pfsense.org/index.php?topic=109690.0

So I ran "pkg info -x pfSense" with the following output:

Shell Output - pkg info -x pfSense
pfSense-2.3.1_5
pfSense-Status_Monitoring-1.4.2_1
pfSense-base-2.3.1_5
pfSense-default-config-2.3.1_5
pfSense-kernel-pfSense_wrap_vga-2.3.1_5
pfSense-pkg-Lightsquid-3.0.4
pfSense-pkg-snort-3.2.9.1_14
pfSense-pkg-squid-0.4.21
pfSense-pkg-squidGuard-1.14_3
pfSense-rc-2.3.1_5
pfSense-repo-2.3.1_5
php56-pfSense-module-0.12

So that's fine.

Tried to force a package update with "pkg update -f":

Shell Output - pkg update -f
Updating pfSense-core repository catalogue...
Fetching meta.txz: . done
Fetching packagesite.txz: . done
Processing entries: .. done
pfSense-core repository update completed. 13 packages processed.
Updating pfSense repository catalogue...
Fetching meta.txz: . done
Fetching packagesite.txz: .......... done
Processing entries: .......... done
pfSense repository update completed. 404 packages processed.

Still no luck. Checked update settings tab; all fine. What to try next?

keen

try to reboot and upgrade from ssh option 13.
on my embeddeb installation works well

D0X

That doesn't look like a solution to the problem to me. It's not that I was trying to update the system, the issue is that my install is broken without me actually changing anything. Would like to fix this and stay on 2.3.1.5 for a while.

I can't even see my installed packages anymore.

jasch

Exactly the same happend to me Today.

jimp

There are some changes in pkg that can, in some cases, make updating from the console necessary instead of the GUI. If the "pkg" package was updated to a later version, then it won't be able to parse the older pkg data from the version you're on.

try this:

pkg info -x pkg

If you see pkg 1.8.7, then you're probably in that state and you'll have to update. 2.3.1_5 to 2.3.2 is a fairly minor update, we wanted to get it out quick so that we'd have one last full release while cmb was still here. It's really closer to 2.3.1_6 with a few bonus add-ons.

D0X

@jimp:

There are some changes in pkg that can, in some cases, make updating from the console necessary instead of the GUI. If the "pkg" package was updated to a later version, then it won't be able to parse the older pkg data from the version you're on.

try this:
pkg info -x pkg
If you see pkg 1.8.7, then you're probably in that state and you'll have to update. 2.3.1_5 to 2.3.2 is a fairly minor update, we wanted to get it out quick so that we'd have one last full release while cmb was still here. It's really closer to 2.3.1_6 with a few bonus add-ons.

It outputs this:

pfSense-pkg-Lightsquid-3.0.4
pfSense-pkg-snort-3.2.9.1_14
pfSense-pkg-squid-0.4.21
pfSense-pkg-squidGuard-1.14_3
pkg-1.8.7
pkgconf-0.9.12_1

D0X

Did update using a SSH tunnel, and all was fine. Again, was. Now again, without changing a singe thing, the same issue rises. What is going on here?

Tubal

I believe their servers are under heavy load and the issues are on their end. Not yours.

I've been having the problem on and off since last night.

I also haven't been able to install any packages to any of our installations this morning. It partially downloads and then times out. Since this is happening at multiple installations in multiple states, I suspect this is an issue on their end.

Jamerson

@Tubal:

I believe their servers are under heavy load and the issues are on their end. Not yours.

I've been having the problem on and off since last night.

I also haven't been able to install any packages to any of our installations this morning. It partially downloads and then times out. Since this is happening at multiple installations in multiple states, I suspect this is an issue on their end.

I think so too, today my hardware firewall crashed during the update.

2.3.1-RELEASE-p5 (i386)
built on Thu Jun 16 12:53:31 CDT 2016
FreeBSD 10.3-RELEASE-p3

Unable to check for updates

So I don't wanna open a new post,
Ill have to wait for later probably their servers are under load because everyone is trying to receive the updates.

pastro50

Had a similar problem. Everything was fine and installed the openvpn export client package. After that, no packages could be retrieved and the check for update didn't work.
Not sure if this is the right thing to do but I ssh'ed to it and did a
pkg update -f
pkg upgrade -f

When it was done, I had the latest version and the packages and update showed I was on the current version.
It took an hour or so to do the upgrade since it had 135 packages to reinstall or upgrade.
YMMV - I was at the point where I was going to reinstall and decided to try this and it appeared to work.

D0X

I am reverting back to 2.2.6 a.s.a.p. This thing is driving me nuts, never had issues with pfsense or m0n0wall before it.
Nothing but problems with it now, reading far too much about it here on the forums too. >:(

edit:

http://mirror.myip.be/pub/pfsense/downloads/old/

Jamerson

@D0X:

I am reverting back to 2.2.6 a.s.a.p. This thing is driving me nuts, never had issues with pfsense or m0n0wall before it.
Nothing but problems with it now, reading far too much about it here on the forums too. >:(

edit:

http://mirror.myip.be/pub/pfsense/downloads/old/

How are you gonna revert back ?

D0X

@Jamerson:

@D0X:

I am reverting back to 2.2.6 a.s.a.p. This thing is driving me nuts, never had issues with pfsense or m0n0wall before it.
Nothing but problems with it now, reading far too much about it here on the forums too. >:(

edit:

http://mirror.myip.be/pub/pfsense/downloads/old/

How are you gonna revert back ?

Just a clean install.

Waqar.UK

@Jamerson:

@Tubal:

I believe their servers are under heavy load and the issues are on their end. Not yours.

I've been having the problem on and off since last night.

I also haven't been able to install any packages to any of our installations this morning. It partially downloads and then times out. Since this is happening at multiple installations in multiple states, I suspect this is an issue on their end.

I think so too, today my hardware firewall crashed during the update.

2.3.1-RELEASE-p5 (i386)
built on Thu Jun 16 12:53:31 CDT 2016
FreeBSD 10.3-RELEASE-p3

Unable to check for updates

So I don't wanna open a new post,
Ill have to wait for later probably their servers are under load because everyone is trying to receive the updates.

I am based in the UK. I am getting the same problem. I cannot update from web interface & from console option 13 which downloads all the update "says fine" then says "welcome to pfsense 2.3.1-releasep5 (amd64 full install) on pfsense ***"
I have downloaded the update pfSense-CE-Full-Update-2.3.2-RELEASE-amd64.tgz - so how do I do the update using "pfSense-CE-Full-Update-2.3.2-RELEASE-amd64.tgz"?

Tubal

I'm guessing the servers are just overloaded right now.

Once it dies down everything should be working again. Give it a day or two.

Waqar.UK

Will try again. But from pfSense-CE-Full-Update-2.3.2-RELEASE-amd64.tgz - how do I update from this?

RPX_D

Im sure this was already mentioned, but I ran into the same issue today (can't check for updates, can't check for packages). The resolution required me to SSH into the console, option 8 (Shell), then run "pfSense-upgrade -d". It brought me to 2.3.2 and all is working fine now. Hope this helps anyone else in the same boat.

jimp

There was a problem with the update server earlier, it's fixed now. It's been solid for almost an hour now and running faster than ever. Anyone who had a problem should try again, and use the ssh/console/shell update method if the GUI fails.

Heimire

This time the update worked from 2.2.6 but it installed 2.3.1.
When I ran the update again from the console it crashed the unit.

Not onsite to see error but its not coming backup even after reboot.

Waqar.UK

Just upgraded via console (option 13) - since I use a SSD it updated very quickly 8)