can't install plugins
I just updated from version 220.127.116.11 to 9.3 via GUI. I tried after the update to install transmission plugin, but got the following error.
Jan 6 15:33:58 freenas warden: Building new Jail... Please wait...
Jan 6 15:33:58 freenas warden: zfs clone Storage/jails/.warden-template-pluginjail@clean Storage/jails/transmission_1
Jan 6 15:33:58 freenas warden: ERROR: Failed creating clean ZFS base clone
Jan 6 15:33:58 freenas manage.py: [middleware.exceptions:38] [MiddlewareError: Failed to install plugin: cannot open 'Storage/jails/.warden-template-pluginjail@clean': dataset does not exist
ERROR: Failed creating clean ZFS base clone
Then I tried to install another plugin which failed with the same message. I already have 3 jails with different plugins that run fine (plex, teamspeak server and AMP server).
#5 Updated by Djordje Kosanovic over 5 years ago
Now when I had some time to investigate, I saw that the 'pluginjail' template was corrupted or not installed correctly during the upgrade to 9.3. So I killed it with warden
warden template delete pluginjail
and reinstalled it
warden template create -nick pluginjail -tar http://download.freenas.org/jails/9.3/x64/freenas-pluginjail-9.3-RELEASE.tgz
again and now it works. Since I am a bit of a newb on BSD I feel pretty proud of myself :)
#6 Updated by Jordan Hubbard over 5 years ago
Good detective work! This does raise questions for us, however, since templates are installed as a stream of bits with no checksumming or validation on our part:
1. Is there any way for us to store a list of checksums to validate a template install with after it's extracted (since we do it as a stream rather than downloading the template file first, there's no way to just validate the file) - seems like a lot of "mystery plugin problems" might be avoided by adding that seatbelt. We could also allow this to be done at any time, just as the system package validation check works now, to detect a jail instance that had gotten altered or corrupted.
Alternately, we could do template installs over SSL, which would catch corruption in the stream itself, and at least unwind a failed template install.
2. Would it be easy for us to add UI for deleting cached templates (in case corruption was suspected in an already-downloaded template) such that the user wouldn't have to go to the CLI and start playing with warden, as this user was forced to do?
#13 Updated by Djordje Kosanovic over 5 years ago
My body just updated his company's server to 9.3 from 9.1.something and he hit the same problem. In his case after the update the whole template directory was almost empty part for some empty folders, so I did once again what I wrote in my last post and now he can install plugins.
Is it possible that during the installation/update another process kills the process of creating the template?