openmediavault-emby plugin (formerly mediabrowser)

  • on my system the emby-plugin 3.0 works great!
    thanks @tekkb :thumbup:

    omv 6.x | 64 bit | omvextrasorg 6.x |
    used plugins: omv-extras | portainer | rsnapshot | antivirus
    used container: portainer/portainer | nextcloud/all-in-one | linuxserver/swag | paperless-ngx | jellyfin/jellyfin | lmscommunity/logitechmediaserver | adguard/adguardhome |

    Einmal editiert, zuletzt von happyreacer ()

  • Short time ago, I reinstalled openmediavault. The following things were installed after the installation:


    1. backports kernel 4.4
    2. openmediavault-extrasorg 3.0.11
    3. openmediavault-zfs 3.0


    So, at the moment the only installed plugin is zfs.


    Purging libmono* and cli-common-dev brings nothing to remove, but mono+ brings up the following message:



    Greetings Hoppel

    ----------------------------------------------------------------------------------
    openmediavault 6 | proxmox kernel | zfs | docker | kvm
    supermicro x11ssh-ctf | xeon E3-1240L-v5 | 64gb ecc | 8x10tb wd red | digital devices max s8
    ---------------------------------------------------------------------------------------------------------------------------------------

  • Try purging and reinstalling...


    apt-get purge openmediavault-emby
    apt-get purge emby


    Then try reinstalling from the plugin section. Before you do do an "apt-get update" and make sure you don't have any errors.


    no changes ...
    everything runs fine on my OMV ... except emby ;(
    maybe it's due to the cpu ? It's a J1900 ... ASRock Q1900 ITX
    Is ffmpeg downloaded from the emby-ressources?
    Maybe a way to download it manually from there?

    running OMV 2.2.1
    with : SnapRAID - AUFS - TVheadend

  • @El Muchacho
    The program automatically downloads ffmpeg. It could be issue with the library files too if arch command is not showing that cpu as x86_64. If it is issue with library files I can give you a quick fix. Intel Celeron J1900


    Give me results of:
    arch


    this too:
    ls -la /opt/emby/embylibs

  • @hoppel118
    What do you get with these?


    apt-cache policy libnunit-cil-dev
    apt-cache policy mono-devel


    Have you done all your upgrades in the update manager???



    Yes, everything is up to date, nothing to install. Under plugins I see the omvextrasorg 3.0.10 and not 3.0.11. But there are no updates in the update manager.



    Thanks for your help.

    Bilder

    ----------------------------------------------------------------------------------
    openmediavault 6 | proxmox kernel | zfs | docker | kvm
    supermicro x11ssh-ctf | xeon E3-1240L-v5 | 64gb ecc | 8x10tb wd red | digital devices max s8
    ---------------------------------------------------------------------------------------------------------------------------------------

    Einmal editiert, zuletzt von hoppel118 ()

  • Holy shit.... wheezy jessie repos.. WTF? Just noticed. Should be all Jessie.



    Code
    # mono-project repo
    deb https://dl.bintray.com/openmediavault-plugin-developers/erasmus-mono jessie main
    deb http://download.mono-project.com/repo/debian wheezy main
    deb http://download.mono-project.com/repo/debian wheezy-libjpeg62-compat main


    Be back in a while... Aaron needs to see.


  • Code
    root@mediatank:~# ls -la /etc/apt/sources.list.d
    insgesamt 24
    drwxr-xr-x  2 root root 4096 Apr  9 19:39 .
    drwxr-xr-x 11 root root 4096 Apr  9 19:39 ..
    -rw-rw-rw-  1 root root   15 Apr  9 19:39 omv-extras-org-custom.list
    -rw-rw-rw-  1 root root  502 Apr  9 19:39 omv-extras-org-erasmus.list
    -rw-r--r--  1 root root  667 Jan  2 11:38 openmediavault.list
    -rw-r--r--  1 root root   45 Jan  1 13:05 openmediavault-local.list


    Guten Appetit! ;)

    ----------------------------------------------------------------------------------
    openmediavault 6 | proxmox kernel | zfs | docker | kvm
    supermicro x11ssh-ctf | xeon E3-1240L-v5 | 64gb ecc | 8x10tb wd red | digital devices max s8
    ---------------------------------------------------------------------------------------------------------------------------------------

  • i have a Asrock Q1900-ITX with a j19000 cpu and it work

    omv 6.x | 64 bit | omvextrasorg 6.x |
    used plugins: omv-extras | portainer | rsnapshot | antivirus
    used container: portainer/portainer | nextcloud/all-in-one | linuxserver/swag | paperless-ngx | jellyfin/jellyfin | lmscommunity/logitechmediaserver | adguard/adguardhome |

  • Holy shit.... wheezy jessie repos.. WTF? Just noticed. Should be all Jessie.


    Where did you notice this?


    Edit: I found what you meant:


    Code
    root@mediatank:~# cat /etc/apt/sources.list.d/omv-extras-org-erasmus.list
    # Regular omv-extras.org repo
    deb https://dl.bintray.com/openmediavault-plugin-developers/erasmus jessie main
    # ZFS repo
    deb https://dl.bintray.com/openmediavault-plugin-developers/erasmus-zfs jessie main
    deb http://archive.zfsonlinux.org/debian jessie main
    # mono-project repo
    deb https://dl.bintray.com/openmediavault-plugin-developers/erasmus-mono jessie main
    deb http://download.mono-project.com/repo/debian wheezy main
    deb http://download.mono-project.com/repo/debian wheezy-libjpeg62-compat main

    ----------------------------------------------------------------------------------
    openmediavault 6 | proxmox kernel | zfs | docker | kvm
    supermicro x11ssh-ctf | xeon E3-1240L-v5 | 64gb ecc | 8x10tb wd red | digital devices max s8
    ---------------------------------------------------------------------------------------------------------------------------------------

    2 Mal editiert, zuletzt von hoppel118 ()

    • Offizieller Beitrag

    Holy shit.... wheezy jessie repos.. WTF? Just noticed. Should be all Jessie.


    Nope, it is correct. There is no jessie repo. Read this and look here. That is why wheezy wasn't the RELEASE variable in the mkconf file.

    omv 7.1.0-2 sandworm | 64 bit | 6.8 proxmox kernel

    plugins :: omvextrasorg 7.0 | kvm 7.0.13 | compose 7.2 | k8s 7.1.0-3 | cputemp 7.0.1 | mergerfs 7.0.5 | scripts 7.0.7


    omv-extras.org plugins source code and issue tracker - github - changelogs


    Please try ctrl-shift-R and read this before posting a question.

    Please put your OMV system details in your signature.
    Please don't PM for support... Too many PMs!

  • Yeah, I see all that.. On my vm same pinning value, 500, for jessie and wheezy/xamarin packages. If version number is the same jessie package installs. If not the xamarin package is installing.


    @ryecoaaron
    Any idea why his pinning values are different and the xamarin packages are not installing??? From his pinning values above it seems the xamarin packages have the higher value and it is not allowing him to install because they are wheezy or something.

    • Offizieller Beitrag

    If the pinning is the same, the higher version number should install.


    His Debian pinning is 400. The xamarin is 500. It should install the xamarin and the policy output says it is the candidate to install. No idea why it isn't. Maybe there is a conflicting mono package that has a different name.


    Packages don't know they are from a wheezy repo. They may be in a repo but there is nothing in a .deb that tells the system what distro/repo it is from. It only looks at package dependencies.

    omv 7.1.0-2 sandworm | 64 bit | 6.8 proxmox kernel

    plugins :: omvextrasorg 7.0 | kvm 7.0.13 | compose 7.2 | k8s 7.1.0-3 | cputemp 7.0.1 | mergerfs 7.0.5 | scripts 7.0.7


    omv-extras.org plugins source code and issue tracker - github - changelogs


    Please try ctrl-shift-R and read this before posting a question.

    Please put your OMV system details in your signature.
    Please don't PM for support... Too many PMs!

  • maybe is it a problem when you activate a mono-testing? I have only the mono repro activate

    omv 6.x | 64 bit | omvextrasorg 6.x |
    used plugins: omv-extras | portainer | rsnapshot | antivirus
    used container: portainer/portainer | nextcloud/all-in-one | linuxserver/swag | paperless-ngx | jellyfin/jellyfin | lmscommunity/logitechmediaserver | adguard/adguardhome |

  • maybe is it a problem when the mono-testing is activate, too?? I use only the mono repro.

    omv 6.x | 64 bit | omvextrasorg 6.x |
    used plugins: omv-extras | portainer | rsnapshot | antivirus
    used container: portainer/portainer | nextcloud/all-in-one | linuxserver/swag | paperless-ngx | jellyfin/jellyfin | lmscommunity/logitechmediaserver | adguard/adguardhome |

  • Mono testing repo is not activated. Only the mono repo is used.

    ----------------------------------------------------------------------------------
    openmediavault 6 | proxmox kernel | zfs | docker | kvm
    supermicro x11ssh-ctf | xeon E3-1240L-v5 | 64gb ecc | 8x10tb wd red | digital devices max s8
    ---------------------------------------------------------------------------------------------------------------------------------------

  • I am confused by this too. It looks to me as though it should install.


    His sources.list looks a bit odd. I would try to replace it with standard repos at install and apt-get update. Then try again.


    or fix these lines and comment out backports:

    Code
    deb http://ftp.de.debian.org/debian/ jessie main
    deb-src http://ftp.de.debian.org/debian/ jessie main


    It has to be that he messed with his sources.list.
    @hoppel118 if you want to add to your repos do it with the custom repos in OMV Extras. You don't need to mess with the sources.list file.

Jetzt mitmachen!

Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!