[SOLVED] Web Gui does not show 15.1.7.1 update as being available.

[Davesworld]

No matter how many times I tell it to check, I get: At Sat Mar 7 14:45:55 PST 2015 no updates found.

I am using a fresh install of 15.1.7-78bdb9aef (amd64) .

No, I did not get ahead of myself and do the command line update as I know that comes after. My guess is that the gui update is supposed to change the file names and checksums so that the command line program knows what to grab and install.

This is baffling me.

[weust]

Are you using the LibreSSL version? The update to that one isn't released till Sunday.

[Davesworld]

No, I'm using the standard version.

[franco]

Both mirrors are in sync, I just checked. pkgng works on top of HTTP, maybe you have a proxy that caches the remote content?

On the root console try:

Code Select Expand

# pkg update -f
# pkg upgrade -y

Does this help to move to 15.1.7.1? Let use see the output if it's not helping.

Edit: Or maybe your Internet connectivity is not working as expected.

[cibomato]

I have the same problem: I've installed 15.1.6.1-e7916b44d (amd64) / FreeBSD 10.1-RELEASE-p5 and clicking on 'click to check now' in the WebGUI results in 'At Sun Mar 8 21:16:16 CET 2015 no updates found'

At the shell I've tried to opnsense-update but after the reboot the version is still the same.
Also pkg update -f and pkg upgrade -y did upgrade the opnsense version

Did I do something wrong or is there a problem with the system?

Thanks in advance and best regards,
Jochen

[slackadelic]

Firmware upgrade from the GUI works for me.

[Davesworld]

Both mirrors are in sync, I just checked. pkgng works on top of HTTP, maybe you have a proxy that caches the remote content?

On the root console try:

Code Select Expand

# pkg update -f
# pkg upgrade -y

Does this help to move to 15.1.7.1? Let use see the output if it's not helping.

Edit: Or maybe your Internet connectivity is not working as expected.

root@zeuss:~ # pkg update -f
Updating OPNsense repository catalogue...
Fetching meta.txz: 100%    260 B   0.3kB/s    00:01
Fetching packagesite.txz: 100%   39 KiB  39.9kB/s    00:01
Processing entries: 100%
OPNsense repository update completed. 150 packages processed

root@zeuss:~ # pkg upgrade -y
Updating OPNsense repository catalogue...
OPNsense repository is up-to-date.
All repositories are up-to-date.
Checking for upgrades (0 candidates): 100%
Processing candidates (0 candidates): 100%
Checking integrity... done (0 conflicting)
Your packages are up to date.


If I go to https://pkg.opnsense.org/sets/ I also do not see 15.1.7.1 there either. As one would imagine, /usr/local/etc/version still shows 15.1.7 as well as /usr/local/sbin/opnsense-update still showing 15.1.7 and the respective file names. Since the update script points to https://pkg.opnsense.org/sets/ I figured that 15.7.1 files should be in the sets folder.

[franco]

The base system did not change, so opnsense-update does nothing (except reinstall, because the 15.1.6.1 version does not yet remember the version it installed).

I have checked both package mirrors, they can be found here:

https://pkg.opnsense.org/FreeBSD:10:amd64/latest/All/
https://pkg.opnsense.org/FreeBSD:10:i386/latest/All/

In this directory, there is an opnsense-15.1.7.1.txz, which is the latest version. It may very well be the database index files being cached by a proxy in your network then.

I need more info on the version you are using, Are you using LibreSSL? Are you using i386 or amd64?

I will double check with an older system upgrade in a bit and let you know if there is something else going on. Thank you all for your help in tracing this down. :)

[Davesworld]

Ok, I'm using a 64 bit version but using the 386 version on other hardware did the same thing. The wan of this box is connected directly to a bridged adsl modem and wan does indeed have an internet address that is reachable from the internet. If there were a proxy on my end, it would only be on this box but we know that Opnsense doesn't have it yet.

No libressl here.

The links you provided do indeed have the latest version in them. The file  /usr/local/etc/pkg/repos/OPNsense.conf shows as :

OPNsense: {
  url: "pkg+http://pkg.opnsense.org/${ABI}/latest",
  mirror_type: "srv",
  priority: 11,
  enabled: yes
}

Is the value ${ABI} supposed to tell it that this is supposed to be FreeBSD:10:amd64?

[franco]

Yeah, ABI expands to FreeBSD:version:architecture. The setup is completely normal, but we have multiple accounts of this happening.

I just tested the upgrade from 15.1.6.1 on i386 and it works as expected. I am starting to suspect the ADSL provider does content caching, whether you are aware or not (that would be really bad for a number of reasons). What is your ISP, if you are willing to share this info?

[franco]

After talking with Jos we suspect the pkgng database "disappeared" from the system. This is easily confirmed by:

# pkg info

It should tell you there are no packages installed, even though they are all there. A preliminary fix is

# pkg install opnsense

But the system is not 100% consistent after that. We recommend a clean install using the config import and try to narrow this down further.

[Davesworld]

After talking with Jos we suspect the pkgng database "disappeared" from the system. This is easily confirmed by:

# pkg info

It should tell you there are no packages installed, even though they are all there. A preliminary fix is

# pkg install opnsense

But the system is not 100% consistent after that. We recommend a clean install using the config import and try to narrow this down further.

# pkg info did not echo anything at all. # pkg install opnsense actually did pull 15.1.7.1 though. Was this expected?

[franco]

Expected and a wee bit dreaded. I am hunting for the cause now and already spoke with FreeBSD/pkgng devs why this is happening. It might have to do with our system setup that has an edge case or legacy code causing this after all. pkgng is new and some old code might be colliding with its operation.

Did you import a pfSense config with packages? Did you enable MFS for /var? Any help with tracking this down is highly appreciated.

[franco]

I have found what looks like the issue in conjunction with MFS for /var. A fix has been pushed to the repository already and will be part of 15.1.7.2. Please let me know if you did use MFS. :)

[Davesworld]

No on the pfsense config, yes on mfs for /var. Speaking of the latter, on other systems, to save flash drives, only /tmp, and only some directories in /var were mounted using MFS or even better TMPFS.