Netgate SG-1000 microFirewall

Author Topic: Unable to Check For Updates  (Read 35852 times)

0 Members and 1 Guest are viewing this topic.

Offline dougf4nnie

  • Jr. Member
  • **
  • Posts: 34
  • Karma: +0/-0
    • View Profile
Re: Unable to Check For Updates
« Reply #30 on: April 07, 2016, 08:57:00 am »
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.

Offline jits

  • Full Member
  • ***
  • Posts: 279
  • Karma: +6/-0
    • View Profile
Re: Unable to Check For Updates
« Reply #31 on: April 07, 2016, 09:23:04 am »
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.

Offline p1erre

  • Newbie
  • *
  • Posts: 24
  • Karma: +1/-0
    • View Profile
Re: Unable to Check For Updates
« Reply #32 on: April 07, 2016, 03:11:48 pm »
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.

Offline jits

  • Full Member
  • ***
  • Posts: 279
  • Karma: +6/-0
    • View Profile
Re: Unable to Check For Updates
« Reply #33 on: April 07, 2016, 06:07:12 pm »
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...

Offline cmb

  • Hero Member
  • *****
  • Posts: 11226
  • Karma: +896/-7
    • View Profile
    • Chris Buechler
Re: Unable to Check For Updates
« Reply #34 on: April 07, 2016, 06:13:20 pm »
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?

Offline jits

  • Full Member
  • ***
  • Posts: 279
  • Karma: +6/-0
    • View Profile
Re: Unable to Check For Updates
« Reply #35 on: April 07, 2016, 11:28:13 pm »
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...

Offline scubarob

  • Newbie
  • *
  • Posts: 5
  • Karma: +0/-0
    • View Profile
Re: Unable to Check For Updates
« Reply #36 on: April 08, 2016, 07:25:51 am »
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.



Offline graymattr

  • Newbie
  • *
  • Posts: 11
  • Karma: +0/-0
    • View Profile
Re: Unable to Check For Updates
« Reply #37 on: April 08, 2016, 01:49:13 pm »
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.
« Last Edit: April 08, 2016, 10:27:57 pm by graymattr »

Offline diablo266

  • Jr. Member
  • **
  • Posts: 87
  • Karma: +0/-0
    • View Profile
Re: Unable to Check For Updates
« Reply #38 on: April 12, 2016, 11:19:59 am »
I'm still having this issue. I updated from console and rebooted but the problem still persists in the webgui.

Offline Keyser Soze

  • Newbie
  • *
  • Posts: 20
  • Karma: +5/-0
    • View Profile
Re: Unable to Check For Updates
« Reply #39 on: April 12, 2016, 11:30:58 am »
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.

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

« Last Edit: April 12, 2016, 11:43:14 am by Keyser Soze »

Offline scubarob

  • Newbie
  • *
  • Posts: 5
  • Karma: +0/-0
    • View Profile
Re: Unable to Check For Updates
« Reply #40 on: April 12, 2016, 11:45:47 am »
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-RELEASE

I have tried several different DNS servers. All behave the same

Offline jimp

  • Administrator
  • Hero Member
  • *****
  • Posts: 21747
  • Karma: +1503/-26
    • View Profile
Re: Unable to Check For Updates
« Reply #41 on: April 12, 2016, 11:54:43 am »
If it says "unable to check for updates", look at this output:

Code: [Select]
pkg info -x pfSense
If you do not see pfSense-base, run:

Code: [Select]
pkg install pfSense-base
Need help fast? Commercial Support!

Co-Author of pfSense: The Definitive Guide. - Check the Doc Wiki for FAQs.

Do not PM for help!

Offline scubarob

  • Newbie
  • *
  • Posts: 5
  • Karma: +0/-0
    • View Profile
Re: Unable to Check For Updates
« Reply #42 on: April 12, 2016, 12:01:19 pm »
That was the solution - Thanks
All working well now.

Offline wirerogue

  • Newbie
  • *
  • Posts: 16
  • Karma: +0/-0
    • View Profile
Re: Unable to Check For Updates
« Reply #43 on: April 12, 2016, 08:21:11 pm »
If it says "unable to check for updates", look at this output:

Code: [Select]
pkg info -x pfSense
If you do not see pfSense-base, run:

Code: [Select]
pkg install pfSense-base

that 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.



Offline graymattr

  • Newbie
  • *
  • Posts: 11
  • Karma: +0/-0
    • View Profile
Re: Unable to Check For Updates
« Reply #44 on: April 12, 2016, 09:27:18 pm »
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!