No plugins shown after upgrade

[avalon60]

Prior to updating FreeNAS to the current version (9.2.1.5), I installed 2 plugins and they were created under the Jails directory.

Now , since the upgrade, the 2 plugins are not shown, ie not installed, but they are there. I cannot delete the Jails directory nor either the 2 plugins.

Is there anyway round this so that the previous Jails directory can be removed.

 

[joeschmuck]

What version of FreeNAS did you upgrade from?

Yes, you should be able to delete the jails fairly easily I would think since they are not listed in the GUI.

 

[avalon60]

I upgraded from FreeNAS 9.2.0 where I installed the 2 plugins, which are shown under \Jails\owncloud_1, and \Jails\bacula-sd_1 in windows explorer.
But as I said, not showing in FreeNAS 9.2.1.5.

When I try to delete them in Windows, I get a message saying I need admin permission, then 'I need admin permission from \FREENAS\root'

 

[joeschmuck]

You cannot delete them from windows, you need to open up the shell in the GUI and do it from there.

 

[avalon60]

In a shell from FreeNAS GUI, I do: jls -v, no plugins or jails are listed, so technically I can't delete or remove anything.

 

[joeschmuck]

Of course it wouldn't show up as a jail, you already stated that.
Since I don't know your drive structure I'll take a guess at it...

Code:

cd /mnt/pool/
ls

Do you see your Jails directory?

 

[avalon60]

From the first command line I get no such file or directory.

Yet if I do: cd /mnt/
then ls
I get a list of folders: WinShare md_size
Then: cd /mnt/WinShare/
Then: ls

I do see the Jails directory, so I do rmdir jails
Device is busy

What next?

 

[joeschmuck]

Once you have removed your jails, you are done. You can now either install new jails or plugins as you like through the GUI and they should be properly registered.

 

[avalon60]

Yes I realise that, but because I get a message saying they are busy, I cannot delete them

 

[joeschmuck]

Maybe you could post exactly what you are doing, step by step and the exact error message. Write it so that I could do the same steps on my machine if I had a clone of your machine.

 

[avalon60]

Login to freenas webgui 192.168.0.13. Yours may well be a different IP address
Open up a shell from the left hand menu column
[root@freenas ~]# cd /mnt/WinShare/
[root@freenas /mnt/WinShare/]# ls
.cshrc .mail_aliases .rhosts .windows jails_2
.login .mailrc .shrc WinShare
.login_conf .profile .system jails

[root@freenas /mnt/WinShare]# cd /mnt/WinShare/jails/
[root@freenas /mnt/WinShare/jails]# ls
.bacula-sd_1.meta .warden-template-pluginjail
.owncloud_1.meta bacula-sd_1
.plugins owncloud_1
.warden-files-cache
[root@freenas /mnt/WinShare/jails]# rmdir owncloud_1
rmdir: owncloud_1: Device busy
[root@freenas /mnt/WinShare/jails]#

The jails directory is the one created under Freenas 9.2.0.0, which Freenas 9.2.1.5 does not see

 

[joeschmuck]

So it looks like you have jails possibly running but for some odd reason they are not recognized, very odd.

Did you try

Code:

cd/mnt/WinShare/jails
rm -rf owncloud_1

and then reboot and do it again if needed to clean up any remaining files?

Option 1: Disable the plugin from within the jail...

Code:

cd /mnt/WinShare/jails/owncloud_1/etc
mv rc.conf rcold.conf

or you could just delete rc.conf, then reboot and try to delete the owncloud_1 directory.

Option 2: Try to identify the services running and stop them...
I'm in new territory as I've never experienced this before but you could try this:

Code:

ps -A

Now look for the IDs that are associated with a path to your jails, write down the ID numbers. Next you will pkill each ID number. For example:

Code:

pkill -U 4545

Hopefully you are able to kill a process which is keeping you from removing the directory. You may not be able to stop all the suspect processes but don't let that stop you from trying to delete that directory.

Option 3: Brute Force Attack...
Also, you can go into the jail directory /mnt/WinShare/jails/owncloud_1/ and just start deleting files. Eventually you are likely to delete something that will cause the program to fail during a reboot and once that program isn't running again, you should be able to delete it all. This could take a while. I would focus on the etc/rc.conf

 

[avalon60]

[root@freenas /mnt/WinShare]# ls
.cshrc .mail_aliases .rhosts .windows jails_2
.login .mailrc .shrc WinShare
.login_conf .profile .system jails

[root@freenas /mnt/WinShare]# cd /mnt/WinShare/jails/owncloud_1
[root@freenas /mnt/WinShare/jails/owncloud_1]# ls
bin lib libexec sbin usr var

[root@freenas /mnt/WinShare/jails/owncloud_1]# rm bin
rm: bin: is a directory
[root@freenas /mnt/WinShare/jails/owncloud_1]# rmdir bin
rmdir: bin: Directory not empty
/mnt/WinShare/jails/owncloud_1
/bin/

[root@freenas /mnt/WinShare/jails/owncloud_1/bin]# ls
rcp
[root@freenas /mnt/WinShare/jails/owncloud_1/bin]# rm rcp
override r-sr-xr-x root/wheel schg for rcp?
[root@freenas /mnt/WinShare/jails/owncloud_1/bin]# ls
rcp

[root@freenas /mnt/WinShare/jails/owncloud_1/bin]# rm rcp
override r-sr-xr-x root/wheel schg for rcp? y
rm: rcp: Operation not permitted
[root@freenas /mnt/WinShare/jails/owncloud_1/bin]#

When I do:
ps -A
This list appears:

342 ?? DL 0:00.00 [g_eli[3] ada2p1]
344 ?? DL 0:00.00 [g_eli[0] ada1p1]
345 ?? DL 0:00.00 [g_eli[1] ada1p1]
346 ?? DL 0:00.00 [g_eli[2] ada1p1]
347 ?? DL 0:00.00 [g_eli[3] ada1p1]
349 ?? DL 0:00.00
[g_eli[0] ada3p1]
350 ?? DL 0:00.00 [g_eli[1] ada3p1]
351 ?? DL 0:00.00 [g_eli[2] ada3p1]
352 ?? DL 0:00.00 [g_eli[3] ada3p1]
354 ?? DL 0:00.00 [g_eli[0] ada4p1]
355 ?? DL 0:00.00 [g_eli[1] ada4p1]
356 ?? DL 0:00.00 [g_eli[2] ada4p1]
357 ?? DL 0:00.00 [g_eli[3] ada4p1]
725 ?? DL 0:00.00 [ftcleanup]
1038 ?? Is 0:00.00 dhclient: re0 [priv] (dhclient)
1087 ?? Is 0:00.00 dhclient: re0 (dhclient)
1538 ?? Ss 0:00.00 /sbin/devd
1873 ?? Ss 0:00.03 /usr/sbin/syslogd -s -C
2103 ?? Ss 0:00.18 /usr/sbin/ntpd -g -c /etc/ntp.conf -p /var/run/ntpd.pid -f /var/db/ntpd.drift 2345 ?? Ss 0:00.24 /usr/local/sbin/nmbd --daemon --configfile=/usr/local/etc/smb4.conf
2348 ?? Is 0:00.09 /usr/local/sbin/smbd --daemon --configfile=/usr/local/etc/smb4.conf
2351 ?? Ss 0:00.03 /usr/local/sbin/winbindd --daemon --configfile=/usr/local/etc/smb4.conf
2355 ?? S 0:00.01 /usr/local/sbin/winbindd --daemon --configfile=/usr/local/etc/smb4.conf
2357 ?? I 0:00.00 /usr/local/sbin/smartd -i 1800 -c /usr/local/etc/smartd.conf -p /var/run/smartd.pid
2500 ?? S 0:28.47 /usr/local/bin/python /usr/local/www/freenasUI/manage.py runfcgi method=threaded host=127.0.0.1 port=9042 pi
2612 ?? Is 0:00.00 nginx: master process /usr/local/sbin/nginx
2619 ?? Is 0:00.00 /usr/local/sbin/mdnsd
2643 ?? Is 0:00.00 /usr/local/bin/dbus-daemon --system
2656 ?? Ss 0:06.18 /usr/local/sbin/collectd
2661 ?? Is 0:00.00 daemon: /usr/local/libexec/nas/register_mdns.py[2662] (daemon)
2662 ?? I 0:00.34 /usr/local/bin/python /usr/local/libexec/nas/register_mdns.py (python2.7)
3053 ?? Is 0:00.02 /usr/sbin/cron -s
3326 ?? S 1:57.10 /usr/local/sbin/smbd --daemon --configfile=/usr/local/etc/smb4.conf
3327 ?? S 0:00.03 /usr/local/sbin/winbindd --daemon --configfile=/usr/local/etc/smb4.conf
3349 ?? S 0:00.32 /usr/local/sbin/smbd --daemon --configfile=/usr/local/etc/smb4.conf
3500 ?? S 0:16.35 python: webshelld (python2.7)
5293 ?? S 0:00.46 nginx: worker process (nginx)
6844 ?? IN 0:00.00 sleep 300
2376 v0- IN 0:00.02 /bin/sh /usr/local/sbin/pbid
3191 v0 Is+ 0:00.33 python /etc/netcli (python2.7)
3192 v1 Is+ 0:00.00 /usr/libexec/getty Pc ttyv1 3193 v2 Is+ 0:00.00 /usr/libexec/getty Pc ttyv2
3194 v3 Is+ 0:00.00 /usr/libexec/getty Pc ttyv3 3195 v4 Is+ 0:00.00 /usr/libexec/getty Pc ttyv4 3196 v5 Is+ 0:00.00 /usr/libexec/getty Pc ttyv5 3197 v6 Is+ 0:00.00 /usr/libexec/getty Pc ttyv6 3198 v7 Is+ 0:00.00 /usr/libexec/getty Pc ttyv7 3502 0 Ss 0:00.04 bash 6895 0 R+ 0:00.00
ps -A
[root@freenas /mnt/WinShare]#


No IDs with a path to the jails directory

Something I have just found is that when I select the Storage tab then Active Volumes,
there is an entry under WinShare for jails.
Then under jails there is jails /.warden-template-pluginjail

When I select the jails line or row, I get a menu at the bottom, and one of the items is:
'Destroy dataset'.
Does that destroy all data on the said volume, or just the jails data

 

[avalon60]

I have just tried removing/deleting all files and subdirectories under /jails, and this is the output as it were:

[root@freenas /mnt/WinShare/jails/owncloud_1]# rmdir * rmdir: bin:
Directory not empty rmdir: lib:
Directory not empty rmdir: libexec:
Directory not empty rmdir: sbin:
Directory not empty rmdir: usr:
Directory not empty rmdir: var:
Directory not empty [root@freenas /mnt/WinShare/jails/owncloud_1]#
cd /mnt/WinShare/jails/bin/ bash:
cd: /mnt/WinShare/jails/bin/: No such file or directory
[root@freenas /mnt/WinShare/jails/owncloud_1]# rm * rm: bin: is a directory rm: lib: is a directory rm: libexec: is a directory rm: sbin: is a directory rm: usr: is a directory rm: var: is a directory [root@freenas /mnt/WinShare/jails/owncloud_1]#
cd /mnt/WinShare/jails/bin/ bash: cd: /mnt/WinShare/jails/bin/: No such file or directory [root@freenas /mnt/WinShare/jails/owncloud_1]#

First it tells me it is a directory, then says it doesn't exist! Confusing or what.

 

[avalon60]

I changed to Jail root path for the jails directory , and then Freenas could see the 2 plugins, and from there I deleted them. Now I am left with a jails directory which is empty but cannot delete as it is busy:

[root@freenas ~]# cd /mnt/WinShare/ [root@freenas /mnt/WinShare]# ls
.cshrc .mail_aliases .rhosts .windows jails_2
.login .mailrc .shrc WinShare .login_conf .profile .system jails
[root@freenas /mnt/WinShare]# rmdir jails
rmdir: jails: Device busy

EDIT:
the jails folder is NOT empty as I saw in windows explorer, and it seems there are hidden files in it:

[root@freenas /mnt/WinShare/jails]# ls
.plugins .warden-template-pluginjail .warden-files-cache
[root@freenas /mnt/WinShare/jails]#

 

[joeschmuck]

use rm -rf to delete the files and directory, like in my first example. Then tell me how it's working.

 

[avalon60]

I managed to delete 2 files from the /jails directory using rm -rf command. The remaining file is actually a directory, as per this output after rm -rf .warden-template-pluginjail

rm: .warden-template-pluginjail/usr/bin/crontab: Operation not permitted
rm: .warden-template-pluginjail/usr/bin/ypchsh: Operation not permitted
rm: .warden-template-pluginjail/usr/bin/rsh: Operation not permitted
rm: .warden-template-pluginjail/usr/bin/chfn: Operation not permitted
rm: .warden-template-pluginjail/usr/bin/ypchpass: Operation not permitted
rm: .warden-template-pluginjail/usr/bin/login: Operation not permitted
rm: .warden-template-pluginjail/usr/bin/su: Operation not permitted
rm: .warden-template-pluginjail/usr/bin/passwd: Operation not permitted
rm: .warden-template-pluginjail/usr/bin/chsh: Operation not permitted
rm: .warden-template-pluginjail/usr/bin/chpass: Operation not permitted
rm: .warden-template-pluginjail/usr/bin/opieinfo: Operation not permitted
rm: .warden-template-pluginjail/usr/bin/yppasswd: Operation not permitted
rm: .warden-template-pluginjail/usr/bin/rlogin: Operation not permitted
rm: .warden-template-pluginjail/usr/bin: Directory not empty
rm: .warden-template-pluginjail/usr/lib32/libc.so.7: Operation not permitted
rm: .warden-template-pluginjail/usr/lib32/libcrypt.so.5: Operation not permitted
rm: .warden-template-pluginjail/usr/lib32/libthr.so.3: Operation not permitted
rm: .warden-template-pluginjail/usr/lib32/librt.so.1: Operation not permitted
rm: .warden-template-pluginjail/usr/lib32: Directory not empty
rm: .warden-template-pluginjail/usr/lib/librt.so.1: Operation not permitted
rm: .warden-template-pluginjail/usr/lib: Directory not empty
rm: .warden-template-pluginjail/usr: Directory not empty
rm: .warden-template-pluginjail: Device busy

[root@freenas /mnt/WinShare/jails]#
[root@freenas /mnt/WinShare/jails]# rmdir .warden-template-pluginjail
rmdir: .warden-template-pluginjail: Device busy
[root@freenas /mnt/WinShare/jails]#