Update fail

johnpoz

"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

updateurl.jpg_thumb

stephenw10

Odd but none the less true! ;)

No directory listing at updates.pfsense.org.

Steve

dynaguy

@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
 *
.....
.....

stephenw10

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

dynaguy

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

stephenw10

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

johnpoz

so for example on my dashboard

MBUF Usage 908/25600

What does your show?

dynaguy

@johnpoz:

so for example on my dashboard

MBUF Usage 908/25600

What does your show?

Mine is:

1304/25600

stephenw10

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

dynaguy

[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