Owncloud pluging update 7.0.2 to 8.0.2

[Clouseau]

I tryed to update Owncloud plugin from verison 7.0.2 to 8.0.2 but this fails without noticable reason. Have anyone done pluginupdate for Owncloud?

If yes - could you show all the steps needed to do. If no - is the clean install only way to go?

 

[Joshua Parker Ruehlig]

I tryed to update Owncloud plugin from verison 7.0.2 to 8.0.2 but this fails without noticable reason. Have anyone done pluginupdate for Owncloud?

If yes - could you show all the steps needed to do. If no - is the clean install only way to go?

I was able to do it in testing. But, plugin updates are pretty finicky and don't work all the time.
You could always install a second owncloud plugin, then copy over the /media directory.

 

[nivarox]

Same here. The update downloads but doesn't install. Could you please explain the workaround more precisely?

 

[nivarox]

That's what the console says:

Apr 6 07:41:51 freenas manage.py: [common.pipesubr:59] Popen()ing: /sbin/umount -f '/mnt/vol1/jails/owncloud_1/usr/local/owncloud'
Apr 6 07:41:51 freenas manage.py: [middleware.exceptions:38] [MiddlewareError: umount: /mnt/vol1/jails/owncloud_1/usr/local/owncloud: statfs: No such file or directory
umount: /mnt/vol1/jails/owncloud_1/usr/local/owncloud: unknown file system

 

[Joshua Parker Ruehlig]

Same here. The update downloads but doesn't install. Could you please explain the workaround more precisely?

• Install a second instance of ownoloud
• Copy over your /media directory

Code:

cp -r /mnt/tank/jails/owncloud_1/media/* /mnt/tank/jails/owncloud_2/media/
chown -R www:www /mnt/tank/jails/owncloud_2/media

• start the new plugin
• delete the first owncloud instance

 

[Joshua Parker Ruehlig]

That's what the console says:

Apr 6 07:41:51 freenas manage.py: [common.pipesubr:59] Popen()ing: /sbin/umount -f '/mnt/vol1/jails/owncloud_1/usr/local/owncloud'
Apr 6 07:41:51 freenas manage.py: [middleware.exceptions:38] [MiddlewareError: umount: /mnt/vol1/jails/owncloud_1/usr/local/owncloud: statfs: No such file or directory
umount: /mnt/vol1/jails/owncloud_1/usr/local/owncloud: unknown file system

I'm not sure what's going on here. Though I keep seeing people with this or similar error when trying to delete jails/plugins so I have a feeling it's a bug.

 

[nivarox]

Thank you for the instructions. I tried to copy the media folder to the new owncloud plugin but I do receive an error message which says that the folder (the one in the owncloud_2 jail) doesn't exist. Is it possible that I have to start it once, so the folder will be created?

Inside /mnt/ there is just md_size vol1 ?

 

[Joshua Parker Ruehlig]

Thank you for the instructions. I tried to copy the media folder to the new owncloud plugin but I do receive an error message which says that the folder (the one in the owncloud_2 jail) doesn't exist. Is it possible that I have to start it once, so the folder will be created?

Inside /mnt/ there is just md_size vol1 ?

no you don't need to start it, but you do need to replace 'tank' with your actually zpool name.

 

[nivarox]

Up and running.

I didn't quite catch one thing. I've copied the media folder and thought that this contains my user account and so on but anyhow it's a clean install? I even added the same storage but can't see any of my files?

 

[Joshua Parker Ruehlig]

Sorry for my dumbness... it worked. After that I've added the same storage to owncloud_2 as I did with owncloud_1. Now I have the problem that the plugin won't start because of several errors.
The last time I had this problem apache wasn't running (https://forums.freenas.org/index.php?threads/owncloud-wont-start.27700/) and your guidance helped a lot but now the trick doesn't seem to work.

the log file writes this all the time:

Apr 6 17:49:29 freenas manage.py: [common.pipesubr:59] Popen()ing: /sbin/zfs get -H origin '/mnt/vol1/jails/owncloud_1'
Apr 6 17:49:29 freenas manage.py: [common.pipesubr:59] Popen()ing: /sbin/zfs get -H origin '/mnt/vol1/jails/owncloud_2'
Apr 6 17:49:29 freenas manage.py: [common.pipesubr:59] Popen()ing: /sbin/zfs list -H -o name '/mnt/vol1/jails/.warden-template-pluginjail'
Apr 6 17:49:30 freenas manage.py: [common.pipesubr:59] Popen()ing: /sbin/zfs get -H origin '/mnt/vol1/jails/owncloud_1'
Apr 6 17:49:30 freenas manage.py: [common.pipesubr:59] Popen()ing: /sbin/zfs get -H origin '/mnt/vol1/jails/owncloud_2'
Apr 6 17:51:58 freenas manage.py: [plugins.utils:92] Konnte http://192.168.2.99/plugins/owncloud/2/_s/status nicht empfangen: No JSON object could be decoded

looks like it's something with the Python api which controls the plugin.
you could try restarting the jail send see if that fixes it.

 

[nivarox]

looks like it's something with the Python api which controls the plugin.
you could try restarting the jail send see if that fixes it.

Sorry, my mistake. 5 minutes after my reply I restarted the jail and it immediately wotked. Now I just have to manage importing my files from the old storage. Any suggests?

 

[Joshua Parker Ruehlig]

Sorry, my mistake. 5 minutes after my reply I restarted the jail and it immediately wotked. Now I just have to manage importing my files from the old storage. Any suggests?

ohh, I though copying over the contents of the /media directory would do this. was there
this where you kept your files (the default)?

 

[cyberjock]

I'm not sure what's going on here. Though I keep seeing people with this or similar error when trying to delete jails/plugins so I have a feeling it's a bug.

I'm kind of thinking the same thing.

 

[DaPlumber]

Add another victim of an upgrade symptom was no apparent problems but OwnCloud stopped working. About to reinstall and copy /media. Sigh.

 

[cyberjock]

Have you wiped the old jail yet DaPlumber? If not, any chance we can do a remote session so I can look at what is going on?

 

[DaPlumber]

Have you wiped the old jail yet DaPlumber? If not, any chance we can do a remote session so I can look at what is going on?

Nope, and the install of a second instance just failed. In the process of rebooting FreeNAS. Switching to PM so we can arrange a remote session.

 

[cyberjock]

So here's some tidbits of info that I gleaned from a remote session with DaPlumber, one of the iXsystems devs, and myself:

1. When doing an upgrade, it make sense that the plugin will have to do more work when the services are starting. For example, Owncloud might want to do a database check.

the FreeNAS WebGUI talks to the jails via django and json objects. Inside the jail there is a django service that handles the communication between Owncloud and the django service outside the jail. If the Owncloud service takes too long to come up, then the communication times out and the plugin is considered to have "failed to start". So you do have certain time constraints on how much time you have to "stand up your Owncloud service and go". If you exceed that time, even if things do continue to start up properly, they have already missed the window of opportunity. This is just a frailty of plugins, and its something that you may have to deal with. I imagine if you have a service like Owncloud with a ton of users and lots of data, it could almost be a given that you'd exceed this time limit. So you don't have much choice in this situation except to manually hack your way through getting the jail working enough that you can stop and start the plugin from the WebGUI and it work. For some situations, you might be lucky and if you try to start the plugin 2 or 3 times it just *might* finish. But this depends on if the program actually makes progress or not. If it's starting and immediately expecting you to authorize the update, you might just be screwed forever.

2. Something is a bit off with templates. In DaPlumber's case he has old templates from 9.2 (his FreeNAS version is 9.3) but:

- "warden template list" shows only 1 template, his virtualbox template
- If you do an ls -l of the jails directory, it clearly shows that a few templates exist, but they weren't listed under "warden template list"
- A zpool history doesn't show any template dataset being deleted in the last 2-3 weeks (we didn't go back farther).

3. If he tried to create a new jail, it only gave him one template to choose from, the virtualbox template. Obviously this isn't correct as the "standard" template should have been an option, even if it hadn't been downloaded before. FreeNAS should have simply downloaded the required template.

A bug has been filed (# 9132).

In the meantime, I'd recommend people not upgrade Owncloud until we have more info on what is going on.

 

[Joshua Parker Ruehlig]

So here's some tidbits of info that I gleaned from a remote session with DaPlumber, one of the iXsystems devs, and myself:

1. When doing an upgrade, it make sense that the plugin will have to do more work when the services are starting. For example, Owncloud might want to do a database check.

the FreeNAS WebGUI talks to the jails via django and json objects. Inside the jail there is a django service that handles the communication between Owncloud and the django service outside the jail. If the Owncloud service takes too long to come up, then the communication times out and the plugin is considered to have "failed to start". So you do have certain time constraints on how much time you have to "stand up your Owncloud service and go". If you exceed that time, even if things do continue to start up properly, they have already missed the window of opportunity. This is just a frailty of plugins, and its something that you may have to deal with. I imagine if you have a service like Owncloud with a ton of users and lots of data, it could almost be a given that you'd exceed this time limit. So you don't have much choice in this situation except to manually hack your way through getting the jail working enough that you can stop and start the plugin from the WebGUI and it work. For some situations, you might be lucky and if you try to start the plugin 2 or 3 times it just *might* finish. But this depends on if the program actually makes progress or not. If it's starting and immediately expecting you to authorize the update, you might just be screwed forever.

2. Something is a bit off with templates. In DaPlumber's case he has old templates from 9.2 (his FreeNAS version is 9.3) but:

- "warden template list" shows only 1 template, his virtualbox template
- If you do an ls -l of the jails directory, it clearly shows that a few templates exist, but they weren't listed under "warden template list"
- A zpool history doesn't show any template dataset being deleted in the last 2-3 weeks (we didn't go back farther).

3. If he tried to create a new jail, it only gave him one template to choose from, the virtualbox template. Obviously this isn't correct as the "standard" template should have been an option, even if it hadn't been downloaded before. FreeNAS should have simply downloaded the required template.

A bug has been filed (# 9132).

In the meantime, I'd recommend people not upgrade Owncloud until we have more info on what is going on.

thanks for the analysis.

I tested upgrades to the owncloud plugin that worked from 7.0.2 > 8.0.0
but, these were fresh install of 7.0.2 on freenas 9.3

 

[Nigel]

I tryed to update Owncloud plugin from verison 7.0.2 to 8.0.2 but this fails without noticable reason. Have anyone done pluginupdate for Owncloud?

If yes - could you show all the steps needed to do. If no - is the clean install only way to go?

I tried to update, but failed. In the end, I did an un-install re-install; it doesn't take that much longer!

 

[DaPlumber]

So here's some tidbits of info that I gleaned from a remote session with DaPlumber, one of the iXsystems devs, and myself:

1. When doing an upgrade, it make sense that the plugin will have to do more work when the services are starting. For example, Owncloud might want to do a database check.

the FreeNAS WebGUI talks to the jails via django and json objects. Inside the jail there is a django service that handles the communication between Owncloud and the django service outside the jail. If the Owncloud service takes too long to come up, then the communication times out and the plugin is considered to have "failed to start". So you do have certain time constraints on how much time you have to "stand up your Owncloud service and go". If you exceed that time, even if things do continue to start up properly, they have already missed the window of opportunity. This is just a frailty of plugins, and its something that you may have to deal with. I imagine if you have a service like Owncloud with a ton of users and lots of data, it could almost be a given that you'd exceed this time limit. So you don't have much choice in this situation except to manually hack your way through getting the jail working enough that you can stop and start the plugin from the WebGUI and it work. For some situations, you might be lucky and if you try to start the plugin 2 or 3 times it just *might* finish. But this depends on if the program actually makes progress or not. If it's starting and immediately expecting you to authorize the update, you might just be screwed forever.

2. Something is a bit off with templates. In DaPlumber's case he has old templates from 9.2 (his FreeNAS version is 9.3) but:

- "warden template list" shows only 1 template, his virtualbox template
- If you do an ls -l of the jails directory, it clearly shows that a few templates exist, but they weren't listed under "warden template list"
- A zpool history doesn't show any template dataset being deleted in the last 2-3 weeks (we didn't go back farther).

3. If he tried to create a new jail, it only gave him one template to choose from, the virtualbox template. Obviously this isn't correct as the "standard" template should have been an option, even if it hadn't been downloaded before. FreeNAS should have simply downloaded the required template.

A bug has been filed (# 9132).

In the meantime, I'd recommend people not upgrade Owncloud until we have more info on what is going on.

So the Excrement has impacted the rotating air extractor.

In a fit of forgetfulness/lack of caffeine I triggered a Transmission update and it appears to have not installed the new version leaving the Plugin but not the jail broken. I still can't install any plugins either. OwnCloud doesn't suffer from this as you can update itself from inside the jail by itself with a bit of permission twiddling.

At this point I'm not really interested in how the system got to this state, but fixing it. Can someone tell me the idiots guide to re-installing just the plugins related packages so I can get this working again? Failing that is there a way of effectively re-install the current STABLE version that leaves the plugin jail contents unmolested?

I am unfortunately short on time to futz with things at the moment.