Unable to Check For Updates
-
@cmb:
Doesn't matter whether it was upgraded. My next guess is the first server in resolv.conf isn't responding to DNS queries and the GUI doesn't wait long enough for it to get through the timeout and try enough subsequent options for it to work. What's in /etc/resolv.conf, and do all those IPs resolve beta.pfsense.org?
I have only one nameserver configured in /etc/resolv.conf and it resolves beta.pfsense.org perfectly.
-
I have also tried all of the suggestions with no success.
I don't know if this is related, but if you look at my previous post with the packet capture from the dashboard, you will notice that DNS lookup for updates are resolving to … updates.nyi.pfsense.org
This is where I downloaded the upgrade to 2.3 from.
Also, in the packet capture, when doing upgrades from SSH, you will notice DNS resolves to … beta.pfsense.org.
-
I can confirm this issue with enabled RAM Disks. I disabed the use of RAM Disks and my system is able to check for updates.
-
I can confirm this issue with enabled RAM Disks. I disabed the use of RAM Disks and my system is able to check for updates.
Nope. Still can't update…
-
I don't know if this is related, but if you look at my previous post with the packet capture from the dashboard, you will notice that DNS lookup for updates are resolving to … updates.nyi.pfsense.org
This is where I downloaded the upgrade to 2.3 from.
That's where everyone downloaded their upgrade to 2.3 from.
What it's trying to do there is fetch the manifest file. You're sending a SYN to that server on 443, and it apparently never reaches us since it seems you never get a SYN ACK in response. But your IP has successfully fetched that manifest file from us many times in the past days, weeks, and months. Including 10 times today (7th, US EST) alone. With no failures.
That the same thing the capture looks like if you do it again while it fails to check?
-
@cmb:
I don't know if this is related, but if you look at my previous post with the packet capture from the dashboard, you will notice that DNS lookup for updates are resolving to … updates.nyi.pfsense.org
This is where I downloaded the upgrade to 2.3 from.
That's where everyone downloaded their upgrade to 2.3 from.
What it's trying to do there is fetch the manifest file. You're sending a SYN to that server on 443, and it apparently never reaches us since it seems you never get a SYN ACK in response. But your IP has successfully fetched that manifest file from us many times in the past days, weeks, and months. Including 10 times today (7th, US EST) alone. With no failures.
That the same thing the capture looks like if you do it again while it fails to check?
69.50.67.102 is the problem IP.
I'll check in the morning. Right now, I'm looking for a sledge hammer to free openvpn from the edgerouter. arrgh…
-
I am still unable to update despite trying all the stated recommendations.
Any other thoughts? Updating via the console from SSH works with option 13, or option 8 then pfSense-upgrade -4.
The version form the Dashboard GUI is Tue Apr 05 20:24:50 CDT 2016. -
I also am having issues with the update function. I just (30 mins ago) formatted/reinstalled with the 0406 snapshot (latest as of this morning) from USB, and with no changes or settings restore, I am unable to check for or manually install updates.
EDIT: I just ssh'd in, and was able to successfully update with pfSense-upgrade -4 (it found several new packages).
LMK if I can help track this down with logs or repro steps. I am really excited to get 2.3 up and running.
-
I'm still having this issue. I updated from console and rebooted but the problem still persists in the webgui.
-
The solution posted in the following thread worked for me when I had this problem, and turning the ram disk off and rebooting made no difference.
-
I am not using the RAMDISK option and still have this update issue.
I have been updating via the Console.
The Version Number/Built ON date has not been changing. It still shows 2.3-RC (i386)
built on Tue Apr 05 20:24:50 CDT 2016
FreeBSD 10.3-RELEASEI have tried several different DNS servers. All behave the same
-
If it says "unable to check for updates", look at this output:
pkg info -x pfSenseIf you do not see pfSense-base, run:
pkg install pfSense-base -
That was the solution - Thanks
All working well now. -
If it says "unable to check for updates", look at this output:
pkg info -x pfSenseIf you do not see pfSense-base, run:
pkg install pfSense-basethat worked for me too but it seems i've overshot the mark.
now on 2.3.1-DEVELOPMENT.
my update settings were set to automatically move to release.
is there any easy way to go back?
no big deal if not. just wanted to see the 2.3 release on the dash board.
-
Installing pfSense-base worked here as well (thank you!!!), and now I am in the same state as wireogue (on dev build 2.3.1.a.20160412.1222).
Is there a way to get back on the release train without a full reinstall?
Many thanks, and congratulations on getting a great release out the door!
-
i think the real question is… why are you guys still working?
shouldn't you take at least a week off to celebrate the 2.3 release?
get some cocaine and hookersplay some video games and watch porn?you're setting the bar kinda high. making the rest of us look bad.
just sayin'.
-
If it says "unable to check for updates", look at this output:
pkg info -x pfSenseIf you do not see pfSense-base, run:
pkg install pfSense-baseShould I do this also on the nanobad platform?
-
I'm in the same boat, can't update from 2.3 RC (2.3.r.20160406.0534) to 2.3 Release.
If I select "Keep following 2.3 dev snapshots" I can update past 2.3 Release. (2.3.1.a.20160412.1222 as of tis morning)
If I select "follow 2.3 snaps and move to release (default)" I get errors.I'm guessing that I have no IPV6 or other network issues since the stay dev option works.
Any ideas?
Can I just DL 2.3 Release manually and do an upgrade that way?
-
If you were on an RC or earlier, it's normal for it to offer 2.3.1.a. When you choose to upgrade, it will see -RELEASE and use that instead. There's an open ticket to fix that for the next version.
-
I did a clean install and came across as the same problem "Unable to Check For Updates":
I had to install the sarg manually, but before you install, it was necessary to update the package pkg-1.6.2 for pkg-1.7.2. After I upgraded this package the message "Unable to Check For Updates" appeared (even in a clean installation).
