Jails close by themselves

[vicmarto]

Hi.

I have created several jails using iocage (FreeNAS-11.2-RELEASE-U1) and sometimes they close by themselves. All of them, together. I have not found a patter.

Which may be due to?

Thank you!

 

[Basil Hendroff]

A context would be helpful. Please provide details of your FreeNAS hardware as this may provide useful clues. Refer to the Forum Guidelines for tips on what to include.

 

[vicmarto]

Yes, of course:

• motherboard make and model: Supermicro X10SLM+-F
• CPU make and model: Intel Core i3-4130T
• RAM quantity: 32GB ECC (Hynix HMT41GU7AFR8A)
• hard drives, quantity, model numbers, and RAID configuration, including boot drives: Seagate ST4000DM004 x 10
• hard disk controllers: LSI SAS 9211-4i + LSI SAS 9212-4i4e
• network cards: Intel X550-T1

The jail configuration is completely standard, I think:

Code:

CONFIG_VERSION:14
allow_chflags:0
allow_mlock:0
allow_mount:0
allow_mount_devfs:0
allow_mount_nullfs:0
allow_mount_procfs:0
allow_mount_tmpfs:0
allow_mount_zfs:0
allow_quotas:0
allow_raw_sockets:0
allow_set_hostname:1
allow_socket_af:0
allow_sysvipc:0
allow_tun:0
available:readonly
basejail:no
boot:on
bpf:no
children_max:0
cloned_release:11.2-RELEASE
comment:none
compression:lz4
compressratio:readonly
coredumpsize:off
count:1
cpuset:off
cputime:off
datasize:off
dedup:off
defaultrouter:none
defaultrouter6:none
depends:none
devfs_ruleset:4
dhcp:off
enforce_statfs:2
exec_clean:1
exec_fib:0
exec_jail_user:root
exec_poststart:/usr/bin/true
exec_poststop:/usr/bin/true
exec_prestart:/usr/bin/true
exec_prestop:/usr/bin/true
exec_start:/bin/sh /etc/rc
exec_stop:/bin/sh /etc/rc.shutdown
exec_system_jail_user:0
exec_system_user:root
exec_timeout:60
host_domainname:none
host_hostname:video-remux
host_hostuuid:video-remux
host_time:yes
hostid:00000000-0000-0000-0000-0CC47A0E6A4A
hostid_strict_check:off
interfaces:vnet0:bridge0
ip4:new
ip4_addr:none
ip4_saddrsel:1
ip6:new
ip6_addr:none
ip6_saddrsel:1
jail_zfs:off
jail_zfs_dataset:iocage/jails/video-remux/data
jail_zfs_mountpoint:none
last_started:2019-03-12 03:26:01
login_flags:-f root
mac_prefix:02ff60
maxproc:off
memorylocked:off
memoryuse:off
mount_devfs:1
mount_fdescfs:1
mount_linprocfs:0
mount_procfs:0
mountpoint:readonly
msgqqueued:off
msgqsize:off
nmsgq:off
notes:none
nsemop:off
nshm:off
nthr:off
openfiles:off
origin:readonly
owner:root
pcpu:off
priority:99
pseudoterminals:off
quota:none
release:11.2-RELEASE-p9
reservation:none
resolver:/etc/resolv.conf
rlimits:off
securelevel:2
shmsize:off
stacksize:off
state:up
stop_timeout:30
swapuse:off
sync_state:none
sync_target:none
sync_tgt_zpool:none
sysvmsg:new
sysvsem:new
sysvshm:new
template:no
type:jail
used:readonly
vmemoryuse:off
vnet:off
vnet0_mac:02ff60f851ca 02ff60f851cb
vnet1_mac:none
vnet2_mac:none
vnet3_mac:none
vnet_default_interface:none
vnet_interfaces:none
wallclock:off

 

[Basil Hendroff]

I note you're on 11.2-U1. There's a known impact for 11.2-U2. See https://www.ixsystems.com/blog/library/freenas-11-2-u2/. I'm not sure if the issue was also present in U1. It may be worthwhile retesting the jails with:

Code:

vnet_default_interface:auto

If you're thinking of updating to U2.1, make sure you have a backup plan. There have been reports of data loss. For details, refer to https://www.ixsystems.com/community/threads/lost-data-in-upgrade-to-11-2.71585/

 

[SweetAndLow]

I note you're on 11.2-U1. There's a known impact for 11.2-U2. See https://www.ixsystems.com/blog/library/freenas-11-2-u2/. I'm not sure if the issue was also present in U1. It may be worthwhile retesting the jails with:

Code:

vnet_default_interface:auto

If you're thinking of updating to U2.1, make sure you have a backup plan. There have been reports of data loss. For details, refer to https://www.ixsystems.com/community/threads/lost-data-in-upgrade-to-11-2.71585/

U1 did but have the problems U2 has when it comes to jails.

 

[vicmarto]

I note you're on 11.2-U1. There's a known impact for 11.2-U2. See https://www.ixsystems.com/blog/library/freenas-11-2-u2/. I'm not sure if the issue was also present in U1. It may be worthwhile retesting the jails with:

Code:

vnet_default_interface:auto

If you're thinking of updating to U2.1, make sure you have a backup plan. There have been reports of data loss. For details, refer to https://www.ixsystems.com/community/threads/lost-data-in-upgrade-to-11-2.71585/

Thanks Seymour Butt.

But some of the jails that closes, are not even using VNET...

 

[Basil Hendroff]

Understood. You may find that updating the jails that do require it resolves the issue anyway. No harm in trying.

 

[vicmarto]

Understood. You may find that updating the jails that do require it resolves the issue anyway. No harm in trying.

Thank Seymour Butt, let's try then. How can I do this modification? Maybe editing the "config.json" file in the jail dataset?

 

[Basil Hendroff]

From the UI, Jails > Edit > Network Properties > vnet_default_interface

 

[vicmarto]

Yes, the problem is that using the UI the "auto" configuration is not available, only the real interface names are available (ix0, igb0, igb1 and bridge0)

 

[Basil Hendroff]

Interesting. Either it was not a switch available in U1, or not a switch that was exposed in the UI. Using the Shell, check if the switch is available in U1 for a specified jail:

Code:

iocage get all <jail>

If it is there, try setting the option. Hopefully, auto is an option for the switch in U1.

Code:

iocage set vnet_default_interface=auto <jail>

Failing that, you may need to update to U2.1 to enable the option.

 

[vicmarto]

Thanks for your help. Seems I need to update, because I'm getting:

Please provide a valid NIC to be used with vnet

If you're thinking of updating to U2.1, make sure you have a backup plan. There have been reports of data loss. For details, refer to https://www.ixsystems.com/community/threads/lost-data-in-upgrade-to-11-2.71585/

Didn't know about this problem. It's safe to upgrade from 11.2-RELEASE-U1 (clean install, clean configuration) to 11.2-RELEASE-U2.1?

 

[Basil Hendroff]

Please read that post carefully and follow the recommendations. The source of the data loss has not been identified. It hasn't affected all users, but enough to warrant some concern. My update from 11.1 to 11.2 was fine on my backup servers, but this issue has made me hold off updating my primary server. Better to be safe than sorry. Proceed at your own risk though.

 

[vicmarto]

Well, finally found a patter: always that a pool is detached, the jails automatically shut down. All of them. Of course, the detached pool has no relation with any jail.

Which may be due to? Any idea?

 

[SweetAndLow]

Lol

Well, finally found a patter: always that a pool is detached, the jails automatically shut down. All of them. Of course, the detached pool has no relation with any jail.

Which may be due to? Any idea?

Your jails are in your pool. If your pool goes away so do your jails.

 

[adrianwi]

Which begs the question, why is the pool being detatched?

 

[vicmarto]

Obviously, the detached pool is another one, not the main where the jails are located.
Lol!

 

[fracai]

I think then you'll be helped by 11.2-U3 when it is released.
https://redmine.ixsystems.com/issues/76162

 

[vicmarto]

Thanks fracai, that was really helpful! And good news too!