Hi everyone. I’m trying to update my emby rockon and everytime I do, I keep getting the following trace error:
Traceback (most recent call last):
File “/opt/rockstor/src/rockstor/storageadmin/views/rockon.py”, line 106, in post
self._create_update_meta(r, rockons[r])
File “/opt/rockstor/eggs/Django-1.8.16-py2.7.egg/django/utils/decorators.py”, line 145, in inner
return func(*args, **kwargs)
File “/opt/rockstor/src/rockstor/storageadmin/views/rockon.py”, line 185, in _create_update_meta
handle_exception(Exception(e_msg), self.request)
File “/opt/rockstor/src/rockstor/storageadmin/util.py”, line 46, in handle_exception
raise RockStorAPIException(detail=e_msg, trace=traceback.format_exc())
RockStorAPIException: [‘Duplicate container(embyserver) definition detected. It belongs to another Rock-on(EmbyServer). Uninstall one of them and try again.’, ‘Traceback (most recent call last):\n File “/opt/rockstor/eggs/gunicorn-0.16.1-py2.7.egg/gunicorn/workers/sync.py”, line 34, in run\n client, addr = self.socket.accept()\n File “/usr/lib64/python2.7/socket.py”, line 202, in accept\n sock, addr = self._sock.accept()\nerror: [Errno 11] Resource temporarily unavailable\n’]
The error you are seeing is related to a change in the name of the rock-on we had a little while ago (my doing), but all you need to do is to uninstall and re-install the rock-on. This is actually the recommended way (if not the only one) to update most docker images (on which rock-ons are based).
You will find more details, explanations, and most importantly instructions on how to do so in the post below:
Is there any way to force remove this rockon? Uninstall, update and reinstall isn’t working. it keeps using the old 3.5 image instead of the 4.4 version.
Curious… Let’s try to see what we can do about it.
As I’m unsure of the state of your install exactly, some of the steps I’ll list are probably overkill but hopefully able to reset that for you.
First of all, we need to uninstall any Emby rock-on you might have installed at the moment. To do so, you can simply turn them off in the Rockstor webUI and then click Uninstall. Once that is done, make sure to click on the “Update” button in the top right of the Rockstor webUI. This should refresh the database. You should not see any Emby rock-on listed in the list of installed rock-on (report if you do).
Then, we can see what docker images you have and remove all that is potentially conflicting here.
First, let’s make sure you don’t have any phantom emby container running somehow. Run docker ps -a and see if you have anything related to emby. If you do, remove them with docker rm <container_id> (the <container_id> is as reported by docker ps).
Now, let’s take care of images. To see what you have: docker images. To remove it from here, the easiest way (especially given you are at the cli) is to run docker rmi <imageID> (<imageID> is the id of any emby-related images you see as reported by docker images above).
You should now have nothing related to Emby when running docker ps -a and docker images.
Now, you can go back to Rockstor webUI, click the “Update” button in the top right corner (overkill, but better be safe than sorry), and then you can re-install the Emby rock-on. You should now have the latest image running.
You can check everything is the latest in Emby server dashboard, as well as with docker images. It should list the “Created” time and give you a good idea.
Don’t hesitate to paste here the outputs of the commands above if you’d like, it’ll help see any oddity (if any).
Ok, so I followed your instructions. No issues uninstalling the rockons or updating. I ran the docker commands, but no images were left. Of course I reinstall and its still on version 3.5.3.0 for emby. The only other thing I can check is to see if its a version issue with rockon itself.
Final update, got rockstor up to to 3.8. Still getting the image for version 3.5.3.0 of emby instead of version 4.4.3.0. Maybe I need to modify the config file that pulls the docker images?
Hi @scarybaby, thanks for the details on the different versions… we seem to have something really odd here for several reasons.
First:
The latest versions for Rockstor assuming you are on the CentOS base are either 3.9.1-16 for the Testing channel, or 3.9.2-57 for the Stable channel. Rockstor 3.8 was a very very long time ago and using a much older docker version as well… That might explain some issue on that side. Could you elaborate and confirm your Rockstor version? Please paste the output of the following command:
yum info rockstor
Then, to clarify the docker images, can you paste the outputs of the following commands?