Fault in autoupdate!!

peehoo

It seems that there is typo in configuration section of autoupdate!?

Autoupdate is trying to get file from address:

http://updates.pfsense.org/_updaters /latest.tgz (see there is space) but correct address is:

http://updates.pfsense.org/_updaters/latest.tgz

This can be solved with upgrade from console and copying right address but this is annoying.

Br,

stephenw10

Which pfSense version is this? Which install type? 32 or 64bit?

I'm not seeing that.

Steve

peehoo

After manually edit correct update address:

2.1.5-RELEASE (i386)
built on Mon Aug 25 07:44:26 EDT 2014
FreeBSD 8.3-RELEASE-p16

Unable to check for updates.

cmb

There isn't anything wrong with the autoupdate URL. Where are you seeing the space? It sounds like you're manually setting it to the wrong location, latest.tgz does not belong in the autoupdate URL.

peehoo

without any modification there was:

http://updates.pfsense.org/_updaters /latest.tgz (see there is space).

This address was also used in terminal update but when I remove that space away before /latest…. then it worked. Do not know how it came but anyway... And just because I wasn't changed anything I thought it was there - which means fault in coding.... If not... I am sorry...

btw. it seems there is more this kind of problem also with others....

stephenw10

This is a full install on HD, yes?

Where are you seeing this string? In the logs? Only the base URL should appear in the autoupdate settings. That does mean a space would be very easy to overlook though.

Steve

cmb

@stephenw10:

Where are you seeing this string? In the logs? Only the base URL should appear in the autoupdate settings. That does mean a space would be very easy to overlook though.

That's exactly what I was thinking, given that is separate, it'd be easy to slip an extra space into a log somewhere. But grepping through the source, I don't see anywhere that would happen.

It definitely doesn't happen in any of the code that actually downloads and installs the updates. There might be a cosmetic bug somewhere where it's slipping in a space in the displayed URL, but I'm not seeing that either.