[11.2] iocage jail refuses to start. "/middlewared: [iocage:48] + Start FAILED"

[Sokonomi]

The console at the bottom says "/middlewared: [iocage:48] + Start FAILED" each time I try starting the jail up.

I attempted to stop and start the jail after transmission became unresponsive. It went down but refused to come back on again, rebooting the NAS did not help.

Slightly more alarming would be the fact that the jail no longer shows up with jls. It seems the jail is still in the GUI, but is straight up missing in the shell console. The jail folder is still present in /mnt/iocage/jails

Does anyone know what is happening here?

 

[sretalla]

What about in iocage list ?

 

[Sokonomi]

Code:

+-----+----------------+-------+--------------+---------------+
| JID |	  NAME	  | STATE |   RELEASE	|	  IP4	  |
+=====+================+=======+==============+===============+
| 1   | Cloud		  | up	| 11.2-RELEASE | 192.168.178.5 |
+-----+----------------+-------+--------------+---------------+
| -   | Media_Handling | down  | 11.2-RELEASE | 192.168.178.4 |
+-----+----------------+-------+--------------+---------------+

It appears to be there, but something ate its JID?

 

[sretalla]

It appears to be there, but something ate its JID?

No. Jails that aren't running can't be attached with jexec, etc., so no ID is allocated/needed. (those IDs aren't permanent and change on every restart of a jail).

So if you run iocage -v start Media_Handling , do you see anything useful to point at what's wrong?

EDIT: added -v switch to see if it gives more help

 

[Sokonomi]

It doesnt seem to say much, just

Code:

Version 1.0 ALPHA

 

[sretalla]

And without the -v?

 

[Sokonomi]

I think we are getting somewhere now.

* Starting Media_Handling
+ Start FAILED
jail: mount.fstab: /mnt/iocage/jails/Media_Handling/root/media/Home: No such file or directory
Its missing a directory that is infact present.
I suspect its a mountpoint acting up, but im not sure what to do about it. :')

 

[sretalla]

Permissions?

ls -l in the parent and that directory?

 

[Sokonomi]

Upon removing the faultering mountpoint the jail came back to life again.
Re-adding the mountpoint after starting the jail seems to work just fine as well.
I might have to file a bugreport on this.

 

[Sokonomi]

I created a new jail with default settings (except assigning a static ipv4) and im getting the same error again;

Code:

Aug 26 10:34:35 NASty /middlewared: [iocage:48]   + Start FAILED

The new jail has no mountpoints at all, so theres nothing to remove to make it work again.
Something is definitely screwy..

 

[Architct]

I have seen the same error, also with same one jail up and one down. This is directly related to updating to BETA3. Any more headway on this?