Plex Update

    • OMV 4.x
    • Plex Update

      Hi,
      since the Plex Media Server Plugin seems to be dead and i don't want to switch over to Docker with my Plex installation, i'm looking for a way to update my current Plex installation to the latest Version.

      What will be the best way to self maintain my PLex Installation without breaking anything?

      Would it be that easy, i only have to add the official Plex Repo to my OMV Installation, like described here: support.plex.tv/articles/23597…nux-server-distributions/
    • vcdwelt wrote:

      What will be the best way to self maintain my PLex Installation without breaking anything?

      Would it be that easy, i only have to add the official Plex Repo to my OMV Installation, like described here: support.plex.tv/articles/23597…nux-server-distributions/
      *** My comments below only apply to non-arm systems - use docker if you are on arm**

      Following that plex guide is the best way. When you enable the plex repo in omv-extras, it add the repo pretty much the same as the guide. Updates will show up in the Updates tab when using either. Just don't install the plugin. apt-get install plexmediaserver is all you need to install the package.
      omv 4.1.22 arrakis | 64 bit | 4.15 proxmox kernel | omvextrasorg 4.1.15
      omv-extras.org plugins source code and issue tracker - github

      Please read this before posting a question and this and this for docker questions.
      Please don't PM for support... Too many PMs!
    • Hallo,
      ich habe ein Debian-Strech mit OMV 4.x neu am leufen.
      Nun erhalte ich per Webinterface vom Plexserver folgende Meldung:

      Ein Plex Media Server Update für OMV-NAS-i7-4770 steht bereit! 1.15.2.793 Jetzt herunterladen - Diese Version überspringen


      Nun ergibt sich für mich die Frage, sollte man dies aktualisieren, oder lieber warten bis es von den OMV-Extra selbst angeboten wird?

      Oder macht es evtl. Sinn zu meinem Repository diese Zeilen noch mit einzufügen?

      Source Code

      1. echo deb https://downloads.plex.tv/repo/deb public main | sudo tee /etc/apt/sources.list.d/plexmediaserver.list




      Translated with DeepL.com/Translator

      Hello,

      i have a Debian-Strech with OMV 4.x new on run.
      Now I get the following message from the Plex server via web interface:

      A Plex Media Server update for OMV-NAS-i7-4770 is ready! 1.15.2.793 Download now - Skip this version

      Now the question arises for me, should one update this, or rather wait until it is offered by the OMV-Extra itself?

      Or does it make sense to add these lines to my repository?


      Source Code

      1. echo deb https://downloads.plex.tv/repo/deb public main | sudo tee /etc/apt/sources.list.d/plexmediaserver.list
    • EgLe wrote:

      until it is offered by the OMV-Extra itself?
      omv-extras doesn't have any plex packages. omv-extras enables the official plex repo. So, if there is an update in the Updates tab, install that. Otherwise, you should wait until plex puts it in the repo.

      EgLe wrote:

      Or does it make sense to add these lines to my repository?
      Enabling the plex repo in omv-extras add that exact same repo.
      omv 4.1.22 arrakis | 64 bit | 4.15 proxmox kernel | omvextrasorg 4.1.15
      omv-extras.org plugins source code and issue tracker - github

      Please read this before posting a question and this and this for docker questions.
      Please don't PM for support... Too many PMs!
    • Hello @ryecoaaron

      ryecoaaron wrote:


      EgLe wrote:

      Or does it make sense to add these lines to my repository?
      Enabling the plex repo in omv-extras add that exact same repo.


      Hmm, i think i understand....
      But on my OMV 4.x is Plex activated and install from OMV-Extra and i think there is no real repo inside ?(

      Source Code

      1. https://downloads.plex.tv/repo/deb/ ./public main



      So i have a screencapture from this,...
      Images
      • OMV-Plex-repo.jpg

        198.64 kB, 1,911×1,119, viewed 119 times
    • I've updated it manually.
      1. Have Plex plugin installed.
      2. Go to plex.tv/media-server-downloads/#plex-media-server and select platform from the 'Choose distribution' dropdown. I picked 'Ubuntu (16.04+) / Debian (8+) - Intel/AMD 64-bit' for an Intel CPU and copyed the link to the .deb file.
      3. Connect to OMV box via ssh (Putty or similar from Windows)
      4. Download the .deb file to a temporary folder on the NAS:
      cd /temp; wget https://downloads.plex.tv/plex-media-server-new/1.15.2.793-782228f99/debian/plexmediaserver_1.15.2.793-782228f99_amd64.deb
      5. Update the package:
      sudo apt install ./plexmediaserver_1.15.2.793-782228f99_amd64.deb
      6. Remove the file:
      rm plexmediaserver_1.15.2.793-782228f99_amd64.deb

      That is it.
    • Hello,

      Thanks i have now update this manually too.

      But by install i get some "Error", is this bad?

      Source Code

      1. root@OMV-NAS-i7-4770:/tmp# apt install ./plexmediaserver_1.15.2.793-782228f99_amd64.deb
      2. Paketlisten werden gelesen... Fertig
      3. Abhängigkeitsbaum wird aufgebaut.
      4. Statusinformationen werden eingelesen.... Fertig
      5. Hinweis: »plexmediaserver« wird an Stelle von »./plexmediaserver_1.15.2.793-782228f99_amd64.deb« gewählt.
      6. Die folgenden Pakete werden aktualisiert (Upgrade):
      7. plexmediaserver
      8. 1 aktualisiert, 0 neu installiert, 0 zu entfernen und 0 nicht aktualisiert.
      9. Es müssen noch 0 B von 81,1 MB an Archiven heruntergeladen werden.
      10. Nach dieser Operation werden 9.132 kB Plattenplatz zusätzlich benutzt.
      11. Holen:1 /tmp/plexmediaserver_1.15.2.793-782228f99_amd64.deb plexmediaserver amd64 1.15.2.793-782228f99 [81,1 MB]
      12. (Lese Datenbank ... 60476 Dateien und Verzeichnisse sind derzeit installiert.)
      13. Vorbereitung zum Entpacken von .../plexmediaserver_1.15.2.793-782228f99_amd64.deb ...
      14. Removed /etc/systemd/system/multi-user.target.wants/plexmediaserver.service.
      15. Entpacken von plexmediaserver (1.15.2.793-782228f99) über (1.14.1.5488-cc260c476) ...
      16. Trigger für mime-support (3.60) werden verarbeitet ...
      17. Trigger für libc-bin (2.24-11+deb9u4) werden verarbeitet ...
      18. plexmediaserver (1.15.2.793-782228f99) wird eingerichtet ...
      19. Neue Version der Konfigurationsdatei /etc/init/plexmediaserver.conf wird installiert ...
      20. Created symlink /etc/systemd/system/multi-user.target.wants/plexmediaserver.service → /lib/systemd/system/plexmediaserver.service.
      21. Trigger für libc-bin (2.24-11+deb9u4) werden verarbeitet ...
      22. Exception ignored in: <function WeakValueDictionary.__init__.<locals>.remove at 0x7f78256237b8>
      23. Traceback (most recent call last):
      24. File "/usr/lib/python3.5/weakref.py", line 117, in remove
      25. TypeError: 'NoneType' object is not callable
      26. Exception ignored in: <function WeakValueDictionary.__init__.<locals>.remove at 0x7f78256237b8>
      27. Traceback (most recent call last):
      28. File "/usr/lib/python3.5/weakref.py", line 117, in remove
      29. TypeError: 'NoneType' object is not callable
      30. root@OMV-NAS-i7-4770:/tmp#
      Display All
    • python error is not an error, please search forum for it, and found some workarrounds.
      OMV 4.1.11 x64 on a HP T510, 16GB CF as Boot Disk & 32GB SSD 2,5" disk for Data, 4 GB RAM, CPU VIA EDEN X2 U4200 is x64 at 1GHz

      Post: HPT510 SlimNAS ; HOWTO Install Pi-Hole ; HOWTO install MLDonkey ; HOHTO Install ZFS-Plugin ; OMV_OldGUI ; ShellinaBOX ;
      Dockers: MLDonkey ; PiHole ; weTTY
      Videos: @TechnoDadLife
    • EgLe wrote:

      i think there is no real repo inside
      Not much I can do if Plex has taken the repo down. No idea if it will be back. Just another reason to use docker.
      omv 4.1.22 arrakis | 64 bit | 4.15 proxmox kernel | omvextrasorg 4.1.15
      omv-extras.org plugins source code and issue tracker - github

      Please read this before posting a question and this and this for docker questions.
      Please don't PM for support... Too many PMs!
    • EgLe wrote:

      Source Code

      1. https://downloads.plex.tv/repo/deb/ ./public main
      It is the wrong Path
      Correct one is:

      Source Code

      1. deb [url]https://downloads.plex.tv/repo/deb[/url] public main



      To fix the Python problem just edit the weakref.py

      1. cd /usr/lib/python3.5/
      2. nano weakref.py


      replace new lines fixed it:

      Source Code

      1. line 109: def remove(wr, selfref=ref(self)): [b]replace with:[/b] def remove(wr, selfref=ref(self), _atomic_removal=_remove_dead_weakref):
      2. line 117: _remove_dead_weakref(d, wr.key) [b]replace with:[/b] _atomic_removal(d, wr.key)


      @RazvanS
      Exactly what i did :)
      Working fine!
    • vcdwelt wrote:

      It is the wrong Path
      Correct one is:
      They are the same repo. The extra ./ before public doesn't affect anything. Either one works.
      omv 4.1.22 arrakis | 64 bit | 4.15 proxmox kernel | omvextrasorg 4.1.15
      omv-extras.org plugins source code and issue tracker - github

      Please read this before posting a question and this and this for docker questions.
      Please don't PM for support... Too many PMs!
    • Hello @vcdwelt

      The change was not a googd idea, after the next update i got more Error.
      So i change the Line back in weakref.py

      Source Code

      1. line 109: def remove(wr, selfref=ref(self)):
      2. line 117: _remove_dead_weakref(d, wr.key)


      but now the system is Bullshit X(


      Source Code

      1. root@OMV-NAS-i7-4770:~# apt-get install python3.5
      2. Paketlisten werden gelesen... Fertig
      3. Abhängigkeitsbaum wird aufgebaut.
      4. Statusinformationen werden eingelesen.... Fertig
      5. python3.5 ist schon die neueste Version (3.5.3-1+deb9u1).
      6. 0 aktualisiert, 0 neu installiert, 0 zu entfernen und 0 nicht aktualisiert.
      7. 1 nicht vollständig installiert oder entfernt.
      8. Nach dieser Operation werden 0 B Plattenplatz zusätzlich benutzt.
      9. Möchten Sie fortfahren? [J/n] j
      10. openmediavault (4.1.21-1) wird eingerichtet ...
      11. Updating configuration database ...
      12. Traceback (most recent call last):
      13. File "/usr/sbin/omv-confdbadm", line 24, in <module>
      14. import openmediavault.confdbadm
      15. File "/usr/lib/python3/dist-packages/openmediavault/confdbadm.py", line 24, in <module>
      16. import argparse
      17. File "/usr/lib/python3.5/argparse.py", line 87, in <module>
      18. import copy as _copy
      19. File "/usr/lib/python3.5/copy.py", line 51, in <module>
      20. import types
      21. File "/usr/lib/python3.5/types.py", line 166, in <module>
      22. import functools as _functools
      23. File "/usr/lib/python3.5/functools.py", line 23, in <module>
      24. from weakref import WeakKeyDictionary
      25. File "/usr/lib/python3.5/weakref.py", line 109
      26. def remove(wr, selfref=ref(self)):
      27. ^
      28. IndentationError: unindent does not match any outer indentation level
      29. dpkg: Fehler beim Bearbeiten des Paketes openmediavault (--configure):
      30. Unterprozess installiertes post-installation-Skript gab den Fehlerwert 1 zurück
      31. Fehler traten auf beim Bearbeiten von:
      32. openmediavault
      33. Traceback (most recent call last):
      34. File "/usr/sbin/omv-mkaptidx", line 35, in <module>
      35. import apt
      36. File "/usr/lib/python3/dist-packages/apt/__init__.py", line 26, in <module>
      37. from apt.package import Package
      38. File "/usr/lib/python3/dist-packages/apt/package.py", line 28, in <module>
      39. import socket
      40. File "/usr/lib/python3.5/socket.py", line 53, in <module>
      41. from enum import IntEnum
      42. File "/usr/lib/python3.5/enum.py", line 3, in <module>
      43. from types import MappingProxyType, DynamicClassAttribute
      44. File "/usr/lib/python3.5/types.py", line 166, in <module>
      45. import functools as _functools
      46. File "/usr/lib/python3.5/functools.py", line 23, in <module>
      47. from weakref import WeakKeyDictionary
      48. File "/usr/lib/python3.5/weakref.py", line 109
      49. def remove(wr, selfref=ref(self)):
      50. ^
      51. IndentationError: unindent does not match any outer indentation level
      52. E: Sub-process /usr/bin/dpkg returned an error code (1)
      53. root@OMV-NAS-i7-4770:~#
      Display All



      Hello @raulfg3

      @raulfg3 wrote:

      python error is not an error, please search forum for it, and found some workarrounds.


      So this statement is by far the biggest bullshit I've ever read.

      If I install from Debian Phython3.5 and then get OMV4.x and OMV-extra and then get this message it is an error from OMV4.x or OMV4-extra.......

      I myself installed Debian Stable on one machine and Debian Buster on another and now have a NUC with Debian Buster and OMV5 as test and everywhere I get no Python error messages, so this is a bug :!: :!: :!:


      Translated with DeepL.com/Translator
    • EgLe wrote:

      So this statement is by far the biggest bullshit I've ever read.
      It is not bullshit. What he is trying to tell you that while python is reporting an error, it will not cause any issues with OMV. This is python bug that has been mentioned many times on the forum but Debian has not fixed it in Debian 9. It is just an annoying message. forum.openmediavault.org/index…22805-OMV-4-Python-error/

      EgLe wrote:

      I myself installed Debian Stable on one machine and Debian Buster on another and now have a NUC with Debian Buster and OMV5 as test and everywhere I get no Python error messages, so this is a bug
      This means Debian has probably fixed it in Debian 10.

      This line should replace the file that you were trying to edit with the actual python fix in their repo - crash omv-mkconf and omv-update which is much safer than editing by hand. Just remember that some python package updates will overwrite it.
      omv 4.1.22 arrakis | 64 bit | 4.15 proxmox kernel | omvextrasorg 4.1.15
      omv-extras.org plugins source code and issue tracker - github

      Please read this before posting a question and this and this for docker questions.
      Please don't PM for support... Too many PMs!
    • Tuppe wrote:

      Is the Plex plugin still OK to use please, as it's listed on OMV-extras but there's a post on Plex forums saying it's no longer maintained.
      It might still work on amd64 and i386 systems but I'm done maintaining it. I didn't pull it from the repos because I figured people would complain. Docker is the way to go - Installation and Setup Videos - Beginning, Intermediate and Advanced
      omv 4.1.22 arrakis | 64 bit | 4.15 proxmox kernel | omvextrasorg 4.1.15
      omv-extras.org plugins source code and issue tracker - github

      Please read this before posting a question and this and this for docker questions.
      Please don't PM for support... Too many PMs!
    • ryecoaaron wrote:

      Tuppe wrote:

      Is the Plex plugin still OK to use please, as it's listed on OMV-extras but there's a post on Plex forums saying it's no longer maintained.
      It might still work on amd64 and i386 systems but I'm done maintaining it. I didn't pull it from the repos because I figured people would complain. Docker is the way to go - Installation and Setup Videos - Beginning, Intermediate and Advanced
      Is there any way to migrate an existing Plex plugin installation to a dockerized installation? The linked video doesn't really cover that. Obviously my media is safe but I've spent a lot of time picking cover art and what not I would hate to lose all that work.
    • speed7 wrote:

      Is there any way to migrate an existing Plex plugin installation to a dockerized installation? The linked video doesn't really cover that. Obviously my media is safe but I've spent a lot of time picking cover art and what not I would hate to lose all that work.
      There is no difficulty in migrating an existing Plex plugin installation to docker. But doing so requires a basic understanding of Docker principles with an emphasis on filesystem ownership and permissions that must be compatible with the running container.

      For your particular concern, the container host path /config needs to point to your existing Plex Media Server Library location, and the docker MUST be able to read and write there.
      --
      Google is your friend and Bob's your uncle!

      OMV 4.x - ASRock Rack C2550D4I - 16GB ECC - Silverstone DS380
    • ryecoaaron wrote:

      Tuppe wrote:

      Is the Plex plugin still OK to use please, as it's listed on OMV-extras but there's a post on Plex forums saying it's no longer maintained.
      It might still work on amd64 and i386 systems but I'm done maintaining it. I didn't pull it from the repos because I figured people would complain. Docker is the way to go - Installation and Setup Videos - Beginning, Intermediate and Advanced
      OK, I am not an expert in Linux, Debian, Openmediavault or anything else in this particular circumstance.
      I run OMV now in version 4 and recognized this Plex Update issue.
      What does it mean "Docker is the way to go"? Is Docker a replacement for the Repo in OMV-Extras?
      Can I use my "original" Plex database anyhow when moving to the Docker image installation for Plex (new)?
      And: Is there a step-for-step-guide for Dummies (like me)?
      Hope there is...

      thanks

      Dietmar