FreeNAS iocage 11.2 after upgrading to Freenas 11.3

cadamwil

Explorer
Joined
Sep 6, 2013
Messages
60
I upgraded my FreeNAS server to 11.3 this morning and everything is working well, well almost. It seems my iocage jail of Plex was 11.2 and not getting upgrades anymore. I successfully updated the jail to 11.3 using iocage upgrade -r 11.3-RELEASE jailname however, I still cannot update pkgs or get iocage update to succeed. I get the images shown below when attempting to update. If I run the suggested fetch command, I get a message tmpy8mwkcgp: SERVERNAME must be given via command line or configuration file

Any suggestions on next steps? I would prefer not to rebuild the jail/plugin.

shot1.jpg
shot2.jpg
shot3.jpg
 

Bibi40k

Contributor
Joined
Jan 26, 2018
Messages
136
Hi,
try to boot again in 11.2 and update all jails before restarting in 11.3
 

cadamwil

Explorer
Joined
Sep 6, 2013
Messages
60
Hi,
try to boot again in 11.2 and update all jails before restarting in 11.3
I have upgraded my storage pools, will it still work?
 

sretalla

Powered by Neutrality
Moderator
Joined
Jan 1, 2016
Messages
9,703
I have upgraded my storage pools, will it still work?
Probably not. You may get away with just some warnings about the pools being unable to access features, but more likely they won't mount without being forced.
 

cadamwil

Explorer
Joined
Sep 6, 2013
Messages
60
other methods for acheiving the same result? The Jail is now 11.3-RELEASE-p6, but won't update.
 
Last edited:

sretalla

Powered by Neutrality
Moderator
Joined
Jan 1, 2016
Messages
9,703
It's now time to start thinking about how much work it would be to just rebuild the jail as a new one... I assume all of your concern is due to having left all of your application data/databases inside the jail?

It may be as simple as building up a new one and just replacing the fresh db and files with the ones from the old jail... just sayin'
 

Bibi40k

Contributor
Joined
Jan 26, 2018
Messages
136
I read your error which is actually not an error but the solution.

1. reboot
2. run /tmp/tmpy8mwkcgp fetch # probably /mnt/pool/iocage/jails/<jailname>/tmp/tmpy8mwkcgp fetch

:)
 

cadamwil

Explorer
Joined
Sep 6, 2013
Messages
60
It's now time to start thinking about how much work it would be to just rebuild the jail as a new one... I assume all of your concern is due to having left all of your application data/databases inside the jail?

It may be as simple as building up a new one and just replacing the fresh db and files with the ones from the old jail... just sayin'
This is the way I ended up going. I built up a new plugin and migrated the data.
 

blanchet

Guru
Joined
Apr 17, 2018
Messages
516
I have encountered the same error with one of my jails. In my case the file /etc/freebsd-update.conf (in the jail) was empty.
I have copied a valid file from another jail, and then I can upgrade with iocage upgrade
 
Last edited:
Top