Update fail



  • It's been a while I haven't check my pfSense and today I tried to update and it failed on checking update.

    2.0.1-RELEASE (i386)
    built on Mon Dec 12 18:24:17 EST 2011
    FreeBSD 8.1-RELEASE-p6

    Unable to check for updates.

    On the setting (System: Firmware: Settings) the URL is point to
    http://updates.pfsense.org/_updaters

    When I try using browser to access above URL I got "404 Not Found".

    dig the domain name from the pfSense shell got:

    ;; ANSWER SECTION:
    updates.pfsense.org.	60	IN	A	91.227.27.66
    

    I searched this forum and can't find a solution. So please help me.

    Thanks a lot.


  • Rebel Alliance

    2.0.1-RELEASE (i386)

    2.0.1 is the Latest Stable pfSense Version

    Go to: System –> Firmware --> Updater Settings

    and select the URL according to your pfSense version




  • I am running 2.0.1 and I don't have the pull-down option. See my screen shot:


  • Rebel Alliance

    Strange….  ???

    I'm on

    2.0.1-RELEASE (amd64)
    built on Mon Dec 12 18:16:13 EST 2011
    FreeBSD 8.1-RELEASE-p6

    and have the Drop down list… sorry if i can't be of more help



  • I am on i386. Could this be the problem???

    ![Screenshot from 2012-07-25 16:38:14.png](/public/imported_attachments/1/Screenshot from 2012-07-25 16:38:14.png)
    ![Screenshot from 2012-07-25 16:38:14.png_thumb](/public/imported_attachments/1/Screenshot from 2012-07-25 16:38:14.png_thumb)


  • Netgate Administrator

    The fact you are using i386 is not a problem. In fact your P4 doesn't support 64bit anyway.
    It's very odd that you don't have the dropdown to select the URL but it looks like you have the correct one anyway: http://updates.pfsense.org/_updaters

    Also attempting to view that page in a browser will always result in a 404, that's normal. There's no webpage to view at that address. It also doesn't respond to pings.

    What is the history of your box? Did you install 2.0.1 fresh or upgrade from an earlier version? Have you ever run a beta version/snapshot?

    Steve



  • @stephenw10:

    What is the history of your box? Did you install 2.0.1 fresh or upgrade from an earlier version? Have you ever run a beta version/snapshot?

    My box started with v2.0RC then later upgraded to v2.0, then v2.0.1. When it was v2.0RC, I remember it was a snapshot and it's updated almost daily. After v2.0 it is stable and I don't need to update it.

    Anyway, what can I do now? If it is just a webpage issue, can I just update that page? Do I have to do a fresh reinstall?


  • Netgate Administrator

    As I said it looks like it's already the correct base URL.
    Try downloading: http://updates.pfsense.org/_updaters/version
    It's a file that simply contains the version number:

    2.0.1-RELEASE
    
    

    More information on this here.

    Try fetching that file from your pfSense box:

    [2.0.1-RELEASE][root@pfsense.fire.box]/tmp(4): fetch http://updates.pfsense.org/_updaters/version
    version                                       100% of   14  B   38 kBps
    
    

    If that is working then the box is not looking for the right files. You may have to consider more drastic action.

    Steve


  • LAYER 8 Global Moderator

    "Also attempting to view that page in a browser will always result in a 404, that's normal."

    Really?  Seems odd that the snapshots would use a different method than just looking for release updates.  You can access the snapshots url with a browser just fine.

    So I am on 2.1 myself and if you click the update link you getting this

    A new version is now available

    Current version: 2.1-BETA0
           Built On: Fri Jul 20 01:30:00 EDT 2012
        New version: Thu Jul 26 07:30:02 EDT 2012

    Update source: http://snapshots.pfsense.org/FreeBSD_RELENG_8_3/i386/pfSense_HEAD/.updaters

    now if you look in where the update url is you see this
    http://snapshots.pfsense.org/FreeBSD_RELENG_8_3/i386/pfSense_HEAD/.updaters

    You can directly access that url with a browser and see this



  • Netgate Administrator

    Odd but none the less true!  ;)

    No directory listing at updates.pfsense.org.

    Steve



  • @stephenw10:

    Try fetching that file from your pfSense box:

    [2.0.1-RELEASE][root@pfsense.fire.box]/tmp(4): fetch http://updates.pfsense.org/_updaters/version
    version                                       100% of   14  B   38 kBps
    
    

    If that is working then the box is not looking for the right files. You may have to consider more drastic action.

    Mine is:

    [2.0.1-RELEASE][root@pfsense.my_domain.com]/tmp(3): fetch http://updates.pfsense.org/_updaters/version
    fetch: http://updates.pfsense.org/_updaters/version: No route to host
    

    And when I try traceroute:

    [2.0.1-RELEASE][root@pfsense.my_domain.com]/tmp(5): traceroute updates.pfsense.org
    traceroute to updates.pfsense.org (91.227.27.66), 64 hops max, 40 byte packets
    traceroute: sendto: No buffer space available
     1 traceroute: wrote updates.pfsense.org 40 chars, ret=-1
     *traceroute: sendto: No buffer space available
    traceroute: wrote updates.pfsense.org 40 chars, ret=-1
     *traceroute: sendto: No buffer space available
    traceroute: wrote updates.pfsense.org 40 chars, ret=-1
     *
    traceroute: sendto: No buffer space available
     2 traceroute: wrote updates.pfsense.org 40 chars, ret=-1
     *traceroute: sendto: No buffer space available
    traceroute: wrote updates.pfsense.org 40 chars, ret=-1
     *traceroute: sendto: No buffer space available
    traceroute: wrote updates.pfsense.org 40 chars, ret=-1
     *
    .....
    .....
    

  • Netgate Administrator

    Well there's your problem.  ;)
    Quite what's causing it is another thing.
    Are you running Snort? (or have you ever run Snort?)

    Do you have interet access in general from the box? Can you ping stuff?

    Steve



  • ping from the box also has trouble:

    [2.0.1-RELEASE][root@pfsense.my_domain.com]/root(3): ping 8.8.8.8
    PING 8.8.8.8 (8.8.8.8): 56 data bytes
    ping: sendto: No buffer space available

    However, this box is in production and people in the office has no trouble to connect internet.

    And I don't have Snort….


  • Netgate Administrator

    Common causes of this seem to be running out of mbufs. What does it say on the dashboard?
    Common causes of that appear to be bad cable or NIC not seated correctly. That seems unlikely since forwarded traffic is still working fine.

    Steve


  • LAYER 8 Global Moderator

    so for example on my dashboard

    MBUF Usage 908/25600

    What does your show?



  • @johnpoz:

    so for example on my dashboard

    MBUF Usage 908/25600

    What does your show?

    Mine is:

    1304/25600


  • Netgate Administrator

    Looks fine.
    Try running netstat -m for more detail.

    Though if it were that I'm failing to see how other traffic is still passing.  :-\

    Steve



  • [2.0.1-RELEASE][root@pfsense.my_domain.com]/root(3): netstat -m
    1036/764/1800 mbufs in use (current/cache/total)
    769/599/1368/25600 mbuf clusters in use (current/cache/total/max)
    768/384 mbuf+clusters out of packet secondary zone in use (current/cache)
    0/27/27/12800 4k (page size) jumbo clusters in use (current/cache/total/max)
    0/0/0/6400 9k jumbo clusters in use (current/cache/total/max)
    0/0/0/3200 16k jumbo clusters in use (current/cache/total/max)
    1797K/1497K/3294K bytes allocated to network (current/cache/total)
    0/0/0 requests for mbufs denied (mbufs/clusters/mbuf+clusters)
    0/0/0 requests for jumbo clusters denied (4k/9k/16k)
    0/8/6656 sfbufs in use (current/peak/max)
    0 requests for sfbufs denied
    0 requests for sfbufs delayed
    0 requests for I/O initiated by sendfile
    0 calls to protocol drain routines


Log in to reply