Iocage jails not auto starting on boot

[thijsjek]

Hello,

I had an issue on truenas 12.0u8.1 where some jails did not autostart after a reboot/start even tough boot=on 1. I hoped this would resolve at 13.0, but no avail. after updating to 13.0-RELEASE-p11 even more stopped autostarting.
there are currently 2 base jails made somewhere in truenas 11 still able to boot on start. There is no encryption turned on.
New made base jails also do no autostart (devfs_ruleset 4).

It is really annoying because the wireguard vpn jail does not autostart. (12.3-RELEASE-p5)

Show : /var/log/midlewared.log

[2022/05/20 12:09:53] (DEBUG) JailService.start_on_boot():1656 - Starting jails on boot: PENDING
[2022/05/20 12:09:53] (INFO) iocage.callback():71 - Starting nginx
[2022/05/20 12:09:53] (INFO) iocage.callback():71 - * Starting nginx
[2022/05/20 12:09:53] (DEBUG) urllib3.connectionpool._new_conn():227 - Starting new HTTP connection (1): pkg.freebsd.org:80
[2022/05/20 12:09:53] (DEBUG) urllib3.connectionpool._new_conn():227 - Starting new HTTP connection (1): pkg.freebsd.org:80
[2022/05/20 12:09:53] (DEBUG) urllib3.connectionpool._new_conn():227 - Starting new HTTP connection (1): pkg.freebsd.org:80
[2022/05/20 12:09:54] (INFO) iocage.callback():71 - + Started OK
[2022/05/20 12:09:54] (INFO) iocage.callback():71 - + Using devfs_ruleset: 100 0 (iocage generated default)
[2022/05/20 12:09:54] (DEBUG) urllib3.connectionpool._new_conn():227 - Starting new HTTP connection (1): pkg.freebsd.org:80
[2022/05/20 12:09:54] (DEBUG) urllib3.connectionpool._new_conn():227 - Starting new HTTP connection (1): download.truenas.com:80
[2022/05/20 12:09:54] (DEBUG) urllib3.connectionpool._new_conn():227 - Starting new HTTP connection (1): download.truenas.com:80
[2022/05/20 12:09:54] (DEBUG) urllib3.connectionpool._new_conn():227 - Starting new HTTP connection (1): pkg.freebsd.org:80
[2022/05/20 12:09:54] (DEBUG) urllib3.connectionpool._new_conn():227 - Starting new HTTP connection (1): pkg.freebsd.org:80
[2022/05/20 12:09:54] (DEBUG) urllib3.connectionpool._make_request():452 - http: //download.truenas.com:80 "GET /plugins/iconik/stable/12.3-RELEASE/packagesite.t xz HTTP/1.1" 200 62924
[2022/05/20 12:09:54] (DEBUG) iocage.start_network():1129 - Setting default rout e 192.168.0.1
[2022/05/20 12:09:54] (INFO) iocage.callback():71 - + Configuring VNET OK
[2022/05/20 12:09:54] (INFO) iocage.callback():71 - + Using IP options: vnet
[2022/05/20 12:09:55] (DEBUG) urllib3.connectionpool._make_request():452 - http: //pkg.freebsd.org:80 "GET /FreeBSD:12:amd64/latest/packagesite.txz HTTP/1.1" 200 6716172
[2022/05/20 12:09:55] (DEBUG) urllib3.connectionpool._make_request():452 - http: //pkg.freebsd.org:80 "GET /FreeBSD:12:amd64/quarterly/packagesite.txz HTTP/1.1" 200 6712832
[2022/05/20 12:09:55] (DEBUG) urllib3.connectionpool._make_request():452 - http: //pkg.freebsd.org:80 "GET /FreeBSD:12:amd64/latest/packagesite.txz HTTP/1.1" 200 6716172
[2022/05/20 12:10:00] (DEBUG) urllib3.connectionpool._make_request():452 - http: //download.truenas.com:80 "GET /plugins/asigra/stable/12.3-RELEASE/packagesite.t xz HTTP/1.1" 200 16936
[2022/05/20 12:10:00] (DEBUG) urllib3.connectionpool._make_request():452 - http: //pkg.freebsd.org:80 "GET /FreeBSD:13:amd64/latest/packagesite.txz HTTP/1.1" 200 6708396
[2022/05/20 12:10:01] (DEBUG) urllib3.connectionpool._make_request():452 - http: //pkg.freebsd.org:80 "GET /FreeBSD:12:amd64/release_3/packagesite.txz HTTP/1.1" 200 6672632
[2022/05/20 12:10:01] (DEBUG) urllib3.connectionpool._make_request():452 - http: //pkg.freebsd.org:80 "GET /FreeBSD:13:amd64/latest/packagesite.txz HTTP/1.1" 200 6708396
[2022/05/20 12:10:39] (INFO) iocage.callback():71 - + Starting services OK
[2022/05/20 12:10:39] (INFO) iocage.callback():71 - + Executing poststart OK
[2022/05/20 12:10:39] (INFO) iocage.callback():71 - Starting unbound
[2022/05/20 12:10:39] (INFO) iocage.callback():71 - * Starting unbound
[2022/05/20 12:10:39] (INFO) iocage.callback():71 - + Started OK
[2022/05/20 12:10:39] (INFO) iocage.callback():71 - + Using devfs_ruleset: 100 1 (iocage generated default)
[2022/05/20 12:10:40] (DEBUG) iocage.start_network():1129 - Setting default rout e 192.168.0.1
[2022/05/20 12:10:40] (INFO) iocage.callback():71 - + Configuring VNET OK
[2022/05/20 12:10:40] (INFO) iocage.callback():71 - + Using IP options: vnet

 

[ThreeDee]

are these plugins or manual installs?

 

[winnielinnie]

Are you using native ZFS encryption on any dataset(s)?

 

[thijsjek]

These are manual installs, base jail's.
Also like in the start post, there is none encryption, on any pool or hdd

 

[winnielinnie]

I missed that part, my bad!

To rule something out, and as a test (to maybe find a clue), what if you disable any mount points for the jail? Does it autostart then?

 

[thijsjek]

I missed that part, my bad!

To rule something out, and as a test (to maybe find a clue), what if you disable any mount points for the jail? Does it autostart then?

There are some (testing) jails without any mount points attached. also those do not start

 

[Scharbag]

I also have this issue - some jails start, some do not...

 

[thijsjek]

I also have this issue - some jails start, some do not...

It is very frustrating, as is a wireguard jail not autostarting which makes remote management unpossible after a reboot/update
*Edit*
As dirty work around I have a task postinit command: iocage start ALL

 

[keithg]

Same here. I have 2 jails. A std jail with Plex installed in it and another std jail with a cups and a few other programs. Never had a problem before, butr after upgrading to 13.0-U2, I have to manually start them after boot. I did move this to a new location with a new IP subnet and no IPv6. The previous net had functional IPv6. On this one, I set it all up with only ipv4. All jails and the NAS are DHCP with reserved addresses. When they do come up, they get the correct addresses. They just will not auto start...

EDIT: I went through one more time: Turned on then off ipv6 then turned off then then on autostart, started the jails, they grabbed IP addresses. When I rebooted they both came up. Will see if it stays this way

 

[Scharbag]

It is very frustrating, as is a wireguard jail not autostarting which makes remote management unpossible after a reboot/update
*Edit*
As dirty work around I have a task postinit command: iocage start ALL

Sometimes ya just gotta be dirty.

 

[JJT211]

It is very frustrating, as is a wireguard jail not autostarting which makes remote management unpossible after a reboot/update
*Edit*
As dirty work around I have a task postinit command: iocage start ALL

Thanks, for the workaround.

I just upgraded to v13.0-U6.1 from v12 a few days ago and started having issues with Plex jail no longer autostarting. I have several other jails that autostart just fine. Have you find a proper solution or are you still sporting that dirty postinti workaround?

 

[sash]

I have a similar issue when Plex jail fails to start, but this started happening after I restored configuation onto the new boot disk.