Posts by Akeem

    Just installed the Plex 1.0.15 update though the update manager.
    However, Plex server is still on version 0.9.16.6; even after a reboot of OMV.


    I am a Plex pass member, but I follow the public releases through the update manager.
    Normally these updates work fine; however this is the first major version increase.

    ;)
    would reinstalling OMV solve the underlying problem? Is there an easier method? A guide I should look into?


    sincerely

    Thank you ryecoaaron.


    I updated to 1.0.14
    and @PillyWilly only could see the new buttons after restarting OMV
    this should work for you?


    however, after I click "save" and "apply" in the header bar,
    I get the "please wait - apply configuration changes" popup which keeps running
    which brings me back to this problem.
    @ryecoaaron is it a lot of work to make that special permissions version? Or should I try to solve the underlying problem?

    root@OMV:/# dpkg -l | grep openm
    ii openmediavault 2.1.23 all Open network attached storage solution
    ii openmediavault-backup 1.0.11 all backup plugin for OpenMediaVault.
    ii openmediavault-extplorer 1.1 all OpenMediaVault eXtplorer plugin
    ii openmediavault-keyring 0.4 all GnuPG archive keys of the OpenMediaVault archive
    ii openmediavault-lvm2 2.1 all OpenMediaVault Logical Volume Manager (LVM2) plugin
    ii openmediavault-omvextrasorg 2.13.1 all OMV-Extras.org Package Repositories for OpenMediaVault
    ii openmediavault-openvpn 1.1 all OpenVPN plugin for OpenMediaVault.
    ii openmediavault-plexmediaserver 1.0.12 all OpenMediaVault Plex Media Server plugin
    ii openmediavault-pyload 1.0.4 all OpenMediaVault pyLoad plugin
    ii openmediavault-shellinabox 1.2 all Web-based SSH client.
    ii openmediavault-sickbeard 1.0.14 all OpenMediaVault Sick Beard plugin
    ii openmediavault-syncthing 1.9.2 all Syncthing plugin for OpenMediaVault.
    ii openmediavault-transmissionbt 1.4 all OpenMediaVault Transmission (BitTorrent client) plugin.
    ii openmediavault-vdr 1.2 all VDR plugin for OpenMediaVault.
    ii openmediavault-vdr-extras 1.3 all Extras plugin for openmediavault-vdr.
    ii openmediavault-virtualbox 1.3 all VirtualBox plugin for OpenMediaVault.
    root@OMV:/#


    and openmediavault-omvextrasorg is 2.13.1

    So the current OMV PMS package contains extra options in the OMV GUI to enable PlexPy?


    I don't see a "enable PlexPy" setting/button. I'm on openmediavault-plexmediaserver 1.0.12
    @ryecoaaron , a few months ago you provided me with a special OMV PMS 1.0.10 package because I had permission troubles.
    It would be logical for me not to see the PlexPy button if I were still on this special 1.0.10 version, but apparently I have updated to 1.0.12 (I see the checkmark in the plugin section)
    @ryecoaaron or @jhmiller any advice?

    tekbb,


    Thank you for your continued efforts.
    This weekend, I'll read up on the thread you mentioned and try to use privileges instead of ACL to solve my problems.


    I think I have
    drwxr-xr-x 5 root root 4096 Nov 19 2014 .
    instead of
    drwxrwsr-x 16 root users 4096 May 10 00:25 .
    of @zios007
    so probably the problem you described didn't exactly apply to me.

    http://i.imgur.com/DofGXDH.png


    Last login: Tue Jun 9 20:18:00 2015 from localhost
    root@OMV:~# cd /media/f4a1-xxx-6757/
    root@OMV:/media/f4a1-xxx-6757# ls -la
    total 68
    drwxr-xr-x 12 root root 4096 Mar 27 15:47 .
    drwxr-xr-x 5 root root 4096 Nov 19 2014 ..
    drwxrwsr-x 2 root users 6 Nov 19 2014 8tbjbod
    drwxrwsrwx+ 14 calibre users 4096 Jun 9 14:11 Backup
    drwxrwsrwx+ 8 root users 4096 Apr 25 15:07 Download
    drwxrwsrwx 42 root users 4096 Nov 23 2014 Games
    drwxrwsrwx+ 434 root users 16384 May 23 12:37 Music
    drwxrwxrwx 15 root root 4096 Apr 7 10:47 omvbackup
    drwxrwsrwx+ 80 root users 4096 Jun 4 08:18 Photos
    drwxrwxrwx 3 plex nogroup 20 Nov 22 2014 plexmediaserver
    drwxrwsrwx+ 18 root users 4096 Jun 1 23:14 Video
    drwxrws---+ 2 vbox vboxusers 6 Mar 30 20:43 VMs

    root@OMV:/media/f4a1-xxx-6757# cd ..
    root@OMV:/media# ls -la
    total 20
    drwxr-xr-x 5 root root 4096 Nov 19 2014 .
    drwxr-xr-x 24 root root 4096 Jun 3 10:17 ..
    drwxr-xr-x 2 root root 4096 Nov 18 2014 cdrom
    drwxr-xr-x 12 root root 4096 Mar 27 15:47 f4a1-xxx-6757
    lrwxrwxrwx 1 root root 4 Nov 18 2014 usb -> usb0
    drwxr-xr-x 2 root root 4096 Nov 18 2014 usb0
    root@OMV:/media#


    I have used ACL before to give read+write permissions [+] Replace all existing permissions [+] recursively apply to all files and subfolders
    to a few system users(+services) and general users(+services)
    i.e. when eXtplorer fails to move files between 2 of these shared folders, I use ACL to (re-)give eXtplorer all permissions to these shares
    I have most probably also used ACL to give sickbeard and syncthing permissions

    ryecoaaron,
    with the modified version, enabling and applying worked perfectly from the web interface.
    The Dashboard Service status toggle for plexmediaserver is now enabled.
    Thank you.


    tekkb,


    Update manager now lists 2 updates:
    openmediavault-plexmediaserver 1.0.10
    plexmediaserver 0.9.12.3.1173.937aac3.debian
    Can I install those?

    nope, I did not.
    I patiently await the updates provided in the OMV update manager.
    I'm not such a cutting edge user that I can't wait a few days, and wouldn't know how to install updates manually.


    Should I try to uninstall and re-install the plugin? Or do I risk not being able to start pms and use my current library again?
    Would it be a solution to run "sudo service plexmediaserver start" automatically in some startup script and give up on trying to enable pms althogether?

    I have only ever had that one volume in OMV.
    So I did not select a different volume.


    I wouldn't know how to install plex without the plugin.
    So I have only used the plexmediaserver plugin.
    There's a very small chance I have, once upon a time, uninstalled and reinstalled the plugin in an attempt to solve this problem


    Even if a solution cannot be found, I appreciate the effort you make.
    Might upgrading to OMV 2.0 solve this issue? are there additional steps I should take to protect my pms database/library before upgrading when 2.0 is ready?