Update 11.2U5 release to 11.2U7 and facing iocage jail update issues

ninjai

Explorer
Joined
Apr 6, 2015
Messages
98
Hi,

So I completed the update from 11.2-U5 to 11.2-U7 and when I run pkg update I get this:
Code:
To ignore this error set IGNORE_OSVERSION=yes
- package: 1103000
- running kernel: 1102000
Ignore the mismatch and continue? [Y/n]: n
pkg: repository FreeBSD contains packages for wrong OS version: FreeBSD:11:amd64
Processing entries: 100%
Unable to update repository FreeBSD
Error updating repositories!
root@dns_1:~ # uname -a
FreeBSD dns_1 11.2-STABLE FreeBSD 11.2-STABLE #0 r325575+c9231c7d6bd(HEAD): Mon Nov 18 22:46:47 UTC 2019     root@nemesis:/freenas-releng/freenas/_BE/objs/freenas-releng/freenas/_BE/os/sys/FreeNAS.amd64  amd64
root@dns_1:~ # uname -r
11.2-STABLE


I have faced this problem in the past, and from what I understand the jail thinks its on 11.2 and the update server being queried has updates for 11.3. Do I understand correctly?

Oddly enough, if I select "n" to not update, then run pkg update again, it just says there are no updates. I forget all relevant files involved, but here's the 2 I do remember were pertinent last time:

Code:
root@dns_1:~ # cat /etc/pkg/FreeBSD.conf
# $FreeBSD: releng/11.2/etc/pkg/FreeBSD.conf 333474 2018-05-10 23:58:33Z gjb $
#
# To disable this repository, instead of modifying or removing this file,
# create a /usr/local/etc/pkg/repos/FreeBSD.conf file:
#
#   mkdir -p /usr/local/etc/pkg/repos
#   echo "FreeBSD: { enabled: no }" > /usr/local/etc/pkg/repos/FreeBSD.conf
#

FreeBSD: {
  url: "pkg+http://pkg.FreeBSD.org/${ABI}/quarterly",
  mirror_type: "srv",
  signature_type: "fingerprints",
  fingerprints: "/usr/share/keys/pkg",
  enabled: yes
}


Code:
root@dns_1:~ # cat /usr/local/etc/pkg.conf
# System-wide configuration file for pkg(8)
# For more information on the file format and
# options please refer to the pkg.conf(5) man page

# Note: you don't need to have a pkg.conf file.  Many installations
# will work well with no pkg.conf at all or with an empty pkg.conf
# (other than comment lines).  You can also override any of these
# settings from the environment.

# Configuration options -- default values.

#PKG_DBDIR = "/var/db/pkg";
#PKG_CACHEDIR = "/var/cache/pkg";
#PORTSDIR = "/usr/ports";
#INDEXDIR = "";
#INDEXFILE = "INDEX-10";        # Autogenerated
#HANDLE_RC_SCRIPTS = false;
#DEFAULT_ALWAYS_YES = false;
#ASSUME_ALWAYS_YES = false;
#REPOS_DIR [
#    "/etc/pkg/",
#    "/usr/local/etc/pkg/repos/",
#]
#PLIST_KEYWORDS_DIR = "";
#SYSLOG = true;
#ABI = "freebsd:10:x86:64";     # Autogenerated
#DEVELOPER_MODE = false;
#VULNXML_SITE = "http://vuxml.freebsd.org/freebsd/vuln.xml.bz2";
#FETCH_RETRY = 3;
#PKG_PLUGINS_DIR = "/usr/local/lib/pkg/";
#PKG_ENABLE_PLUGINS = true;
#PLUGINS [
#]
#DEBUG_SCRIPTS = false;
#PLUGINS_CONF_DIR = "/usr/local/etc/pkg/";
#PERMISSIVE = false;
#REPO_AUTOUPDATE = true;
#NAMESERVER = "";
#HTTP_USER_AGENT = "Custom_User_Manager";
#EVENT_PIPE = "";
#FETCH_TIMEOUT = 30;
#UNSET_TIMESTAMP = false;
#SSH_RESTRICT_DIR = "";
#PKG_ENV {
#}
#PKG_SSH_ARGS = "";
#DEBUG_LEVEL = 0;
#ALIAS {
#}
#CUDF_SOLVER = "";
#SAT_SOLVER = "";
#RUN_SCRIPTS = true;
#CASE_SENSITIVE_MATCH = false;
#IP_VERSION = 0

# Sample alias settings
ALIAS              : {
  all-depends: query %dn-%dv,
  annotations: info -A,
  build-depends: info -qd,
  cinfo: info -Cx,
  comment: query -i "%c",
  csearch: search -Cx,
  desc: query -i "%e",
  download: fetch,
  iinfo: info -ix,
  isearch: search -ix,
  prime-list: "query -e '%a = 0' '%n'",
  prime-origins: "query -e '%a = 0' '%o'",
  leaf: "query -e '%#r == 0' '%n-%v'",
  list: info -ql,
  noauto = "query -e '%a == 0' '%n-%v'",
  options: query -i "%n - %Ok: %Ov",
  origin: info -qo,
  provided-depends: info -qb,
  rall-depends: rquery %dn-%dv,
  raw: info -R,
  rcomment: rquery -i "%c",
  rdesc: rquery -i "%e",
  required-depends: info -qr,
  roptions: rquery -i "%n - %Ok: %Ov",
  shared-depends: info -qB,
  show: info -f -k,
  size: info -sq,
  }


It's been quite a while since I've checked for updates on my jails so I'm pretty surprised that there are none. For example, my plex jail shows no updates, but I'm running version 1.18.2.1973_1:
Code:
root@pms:~ # pkg info plexmediaserver-plexpass
plexmediaserver-plexpass-1.18.1.1973_1
Name           : plexmediaserver-plexpass
Version        : 1.18.1.1973_1
Installed on   : Thu Oct 31 06:58:06 2019 PDT
Origin         : multimedia/plexmediaserver-plexpass
Architecture   : FreeBSD:11:amd64
Prefix         : /usr/local
Categories     : multimedia
Licenses       :
Maintainer     : feld@FreeBSD.org
WWW            : https://plex.tv
Comment        : Plex Media Server component
Options        :
        RELAY          : on
Annotations    :


and freshports shows:
1.18.2.2041

I believe there was a way to download releases for iocage from the CLI but I forget what that was and how to do it, and I don't recall in the past that the "iocage list" command showing this:
Code:
| 8   | pms          | up    | 11.2-RELEASE | 


Normally it would have said 11.2-RELEASE-P5 or something similar, which I assumed was patch level (11.2-U5).

So because of that I think is why I'm getting this:
Code:
root@pms:~ # freebsd-update fetch
Looking up update.FreeBSD.org mirrors... 3 mirrors found.
Fetching metadata signature for 11.2-STABLE from update4.freebsd.org... failed.
Fetching metadata signature for 11.2-STABLE from update2.freebsd.org... failed.
Fetching metadata signature for 11.2-STABLE from update1.freebsd.org... failed.
No mirrors remaining, giving up.
 

planet86

Cadet
Joined
Feb 17, 2018
Messages
1
The jail is still running 11.2 which is no longer supported, you need to upgrade the jail to 11.3. With FreeNAS 11.2 U7 you are able to run a newer version of FreeBSD in jails.

Make a snapshot of your jail then you can use the below to update the jail to 11.3.
Code:
iocage upgrade -r 11.3-RELEASE jailname
 

ninjai

Explorer
Joined
Apr 6, 2015
Messages
98
Thank you, I didn't realize I had to do this manually. Last time I updated FreeNAS the jails went with it.
 

Jailer

Not strong, but bad
Joined
Sep 12, 2014
Messages
4,977
Thank you, I didn't realize I had to do this manually. Last time I updated FreeNAS the jails went with it.
Jails are not touched in a system update and never have been for as long as I've been using FreeNAS. In the past when warden was the jail manager they had to be rebuilt every time you updated if you wanted a newer jail version. The switch to iocage brought us the ability to upgrade jails.
 

adrianwi

Guru
Joined
Oct 15, 2013
Messages
1,231
The jail is still running 11.2 which is no longer supported, you need to upgrade the jail to 11.3. With FreeNAS 11.2 U7 you are able to run a newer version of FreeBSD in jails.

Make a snapshot of your jail then you can use the below to update the jail to 11.3.
Code:
iocage upgrade -r 11.3-RELEASE jailname

Have may people tried this? Are the EOL issues upgrading the packages within the jails resolved once the jail has been upgraded to 11.3?
 

Jailer

Not strong, but bad
Joined
Sep 12, 2014
Messages
4,977
Have may people tried this? Are the EOL issues upgrading the packages within the jails resolved once the jail has been upgraded to 11.3?
I upgraded one of my jails to 11.3 and it's working fine.
 

ninjai

Explorer
Joined
Apr 6, 2015
Messages
98
Mine working fine as well. Might make a script to do this next time lol. Updgrade all jails, update packages
 
Top