Jump to content

Search the Community

Showing results for tags 'Pi'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • General
    • Announcements
    • Emby Premiere Purchase/Subscription Support
    • Feature Requests
    • Tutorials and Guides
  • Emby Server
    • General/Windows
    • Android Server
    • Asustor
    • FreeBSD
    • Linux
    • NetGear ReadyNAS
    • MacOS
    • QNAP
    • Synology
    • TerraMaster NAS
    • Thecus
    • Western Digital
    • DLNA
    • Live TV
  • Emby Apps
    • Amazon Alexa
    • Android
    • Android TV / Fire TV
    • Windows & Xbox
    • Apple iOS / macOS
    • Apple TV
    • Kodi
    • LG Smart TV
    • Linux & Raspberry Pi
    • Roku
    • Samsung Smart TV
    • Sony PlayStation
    • Web App
    • Windows Media Center
    • Plugins
  • Language-specific support
    • Arabic
    • Dutch
    • French
    • German
    • Italian
    • Portuguese
    • Russian
    • Spanish
    • Swedish
  • Community Contributions
    • Ember for Emby
    • Fan Art & Videos
    • Tools and Utilities
    • Web App CSS
  • Testing Area
    • WMC UI (Beta)
  • Other
    • Non-Emby General Discussion
    • Developer API
    • Hardware
    • Media Clubs

Blogs

  • Emby Blog

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Found 14 results

  1. Hi My file/Emby server only wakes up on access from Emby or me start it. Via WOL locally. But will it be possible to use my PI as an man in the middle, so if I try to Emby from outside my Lan, my PI can send an WOL packet to my server? My PI act as Noip updater, torrent and some other stuff.
  2. After Recreating my (32bit) Pi4B / OMV / Docker / Portainer image to upgrade to Emby 4.6, the /app/emby/EmbyServer process was constantly restarting, with no access to the Emby Web interface. After a lot of web searching and several blind alleys the solution is here: https://docs.linuxserver.io/faq#my-host-is-incompatible-with-images-based-on-ubuntu-focal Manually installing libseccomp2_2.4.4-1~bpo10+1_armhf.deb (Option 2) worked for me, although I've subsequently added the Buster backports repo (Option 3) Hope this saves time and anxiety for someone....
  3. Migrating from RasPlex and like what I have experienced so far with Emby but have one problem that I cannot resolve. using emby-theater-rpi_3.0.4.zip I cannot get audio other than Stereo from any source , the Pi is connected to my a/v amp over hdmi and with Rasplex I can get audio to work as expected by choosing my speaker setup (5.1) and ticking all the passthru selections for ac3, dts etc. Making the same selections within emby-theater does not yield the same results. is there something perhaps in config.txt that I need to enable ? I see there are differences in config.txt from the rasplex install to the emby install but am ignorant as to what changes (if any) should or could be made. given that the hardware setup is identical in either case and the only change is the media player software it has to be a configuration issue. after each change I have restarted the Pi and re-checked to make sure the settings have 'stuck' and they have so no matter what I have changed so far has not made any difference to the result. any clues as to where I may have missed something ?
  4. wickedlemon

    Slow - almost non-existent - scan

    Hi New user and first post so hopefully I'm posting in the right place and it's not full of (too) stupid questions! I recently installed Emby Server on Windows 10, just to see what it actually did and get a feel of how it actually worked. I've now decided to set up Emby on a Raspberry Pi 2. I don't need it for streaming/transcoding, purely for pulling metadata, so I'm not concerned about any of the Pi's power limitations. I installed 4.0.0.2 on a fresh install of Raspbian and started to set it up, adding libraries, plugins as I had done under Windows. Then I noticed that the scanning wasn't going as fast. Nowhere near as fast. Back to a fresh Raspbian/Emby install and this time no plugins and a minimal library - just 12 TV episodes to test. First run and I gave up before it had even completed. The episodes already had all the nfo and thumb images before the scan started but it was still taking ages. Log entries showed ffprobe entries for each file spaced anywhere between 5 and 20 minutes apart. Removed the library, nfos and images and tried again and it's still not working. Dashboard still says its scanning, but there doesn't appear to have been a log entry related to scanning for over half an hour. in both instances there just seems to be huge time periods of Emby not doing anything, or at least not logging anything. Any suggestions? There doesn't seem to be an errors in the log and I had no issues scanning under Windows. Two logs attached. 1 when folder had nfo/thumbs already and 2 with no existing local metadata. embyserver1.txt embyserver2.txt
  5. JaScoMa

    SBC Testings

    Hello.. I'm currently running Emby on a Pi3b+ with the latest version of DietPi. Was just curious what others may be using as their Emby servers? Anyone running a NanoPi M4? Its stats looking pretty impressive for a SBC. Thank you..
  6. I've been having a problem lately with emby crashing on a Raspberry Pi on DietPi. It ran almost without fault for the last year or so. After an upgrade from 3.3x to 3.5.2, it began crashing within minutes of starting it. So, I wiped the system and started over completely with a new install of DietPi and Emby as well. I'm not totally sure what's causing it, but I've been trying to run the Roku "create thumbnails" scheduled task, and it invariably crashes, even if I don't access the system in any other way. I've attached a copy of the log file, and the linux error status is also posted below. Any help would be greatly appreciated. ● emby-server.service - Emby Server is a personal media server with apps on just about every device. Loaded: loaded (/usr/lib/systemd/system/emby-server.service; disabled; vendor preset: enabled) Active: failed (Result: signal) since Tue 2018-12-18 20:07:35 EST; 1h 47min ago Process: 6526 ExecStart=/opt/emby-server/bin/emby-server (code=killed, signal=ABRT) Main PID: 6526 (code=killed, signal=ABRT) Dec 18 19:14:28 DietPi emby-server[6526]: Info App: Sqlite compiler options: COMPILER=gcc-6.4.1 20170707,ENABLE_COLUMN_METADATA,ENABLE_DBSTAT_VTAB,ENA BLE_FTS3,ENABLE_FTS3_PARENTHESIS,ENABLE_FTS3_TOKENIZER,ENABLE_FTS5,ENABLE_JSON1,ENABLE_PREUPDATE_HOOK,ENABLE_RTREE,ENABLE_SESSION,ENABLE_UNLOCK_NOTIFY ,ENABLE_UPDATE_DELETE_LIMIT,LIKE_DOESNT_MATCH_BLOBS,MAX_SCHEMA_RETRY=25,MAX_VARIABLE_NUMBER=250000,OMIT_LOOKASIDE,SECURE_DELETE,THREADSAFE=1 Dec 18 19:14:28 DietPi emby-server[6526]: Info App: Default journal_mode for /var/lib/emby/data/sync14.db is wal Dec 18 19:14:28 DietPi emby-server[6526]: Info App: PRAGMA synchronous=1 Dec 18 19:14:28 DietPi emby-server[6526]: Info App: Entry point completed: Emby.Server.Sync.SyncManagerEntryPoint. Duration: 0.082916 seconds Dec 18 19:14:28 DietPi emby-server[6526]: Info App: Starting entry point Emby.Server.Sync.SyncNotificationEntryPoint Dec 18 19:14:28 DietPi emby-server[6526]: Info App: Entry point completed: Emby.Server.Sync.SyncNotificationEntryPoint. Duration: 0.0145443 seconds Dec 18 19:14:28 DietPi emby-server[6526]: Info App: All entry points have started Dec 18 20:07:34 DietPi systemd[1]: emby-server.service: Main process exited, code=killed, status=6/ABRT Dec 18 20:07:35 DietPi systemd[1]: emby-server.service: Unit entered failed state. Dec 18 20:07:35 DietPi systemd[1]: emby-server.service: Failed with result 'signal'. log.zip
  7. I would like to request a new client that will work on the Raspberry Pi box. Myself and a large group of my mates have started using these lately. And instead of setting up XBMB3C it would be great to have MB3 create a standalone client for Pi! A link to Luke's post on Pi's website: http://www.raspberrypi.org/forum/viewtopic.php?f=35&t=36788&sid=243284e5019e0f0373dd3210919a84f6&start=25
  8. Hello Experts :-) I'm a beginner trying to install Emby server on my Raspberry PI 3 (OSMC 18b based on Debian). I followed the official method that use Docker : (Recommend install method for armhf/armv7 (Tested rpi2/3 running rasbian)) https://emby.media/community/index.php?/topic/43166-arm-devices-official-instructions/ I don't know Docker very well. It seems correctly installed and started : Ports 1900/udp, 8096/tcp, 7359/udp, 8920/tcp and opened in router for the IP address of the Raspberry PI 3 (192.168.0.20). I use other web interfaces / tools like Transmission, PhotoShow Albums, or Pyload (no Docker), that work perfectly fine. Since Docker installation, I have now 2 new network interfaces docker0 + veth***** : Plus, 2 new FS linked to docker (overlay + shm) : >> In the end : If i try to open Emby server URL on port 8096, it's not OK (i already tried to docker restart emby-server, or RPi reboot). Do i have to do something to link real RPi IP to docker0 or veth***** interface ? Did i miss something ? I'm lost :-\ Other details that may help (?) : . ps -ef . iptables -L . netstat -plnt (no Emby port displayed !) . find "emby" files : root@osmcpi:~# find / -name emby* /var/lib/docker/overlay2/fe66be4f15b80ea1068493a56e64dad2b81c58dee2811f3324d56c88286d4735/diff/etc/emby-server.conf /var/lib/docker/overlay2/fe66be4f15b80ea1068493a56e64dad2b81c58dee2811f3324d56c88286d4735/diff/etc/services.d/emby-server /var/lib/docker/overlay2/fe66be4f15b80ea1068493a56e64dad2b81c58dee2811f3324d56c88286d4735/diff/run/emby-server.pid /var/lib/docker/overlay2/fe66be4f15b80ea1068493a56e64dad2b81c58dee2811f3324d56c88286d4735/diff/run/s6/services/emby-server /var/lib/docker/overlay2/fe66be4f15b80ea1068493a56e64dad2b81c58dee2811f3324d56c88286d4735/diff/usr/lib/emby-server /var/lib/docker/overlay2/fe66be4f15b80ea1068493a56e64dad2b81c58dee2811f3324d56c88286d4735/merged/etc/emby-server.conf /var/lib/docker/overlay2/fe66be4f15b80ea1068493a56e64dad2b81c58dee2811f3324d56c88286d4735/merged/etc/sudoers.d/emby /var/lib/docker/overlay2/fe66be4f15b80ea1068493a56e64dad2b81c58dee2811f3324d56c88286d4735/merged/etc/zypp/repos.d/emby.repo /var/lib/docker/overlay2/fe66be4f15b80ea1068493a56e64dad2b81c58dee2811f3324d56c88286d4735/merged/etc/default/emby-server /var/lib/docker/overlay2/fe66be4f15b80ea1068493a56e64dad2b81c58dee2811f3324d56c88286d4735/merged/etc/services.d/emby-server /var/lib/docker/overlay2/fe66be4f15b80ea1068493a56e64dad2b81c58dee2811f3324d56c88286d4735/merged/var/lib/emby-server /var/lib/docker/overlay2/fe66be4f15b80ea1068493a56e64dad2b81c58dee2811f3324d56c88286d4735/merged/var/lib/systemd/migrated/emby-server /var/lib/docker/overlay2/fe66be4f15b80ea1068493a56e64dad2b81c58dee2811f3324d56c88286d4735/merged/run/emby-server.pid /var/lib/docker/overlay2/fe66be4f15b80ea1068493a56e64dad2b81c58dee2811f3324d56c88286d4735/merged/run/s6/services/emby-server /var/lib/docker/overlay2/fe66be4f15b80ea1068493a56e64dad2b81c58dee2811f3324d56c88286d4735/merged/usr/bin/emby-server /var/lib/docker/overlay2/fe66be4f15b80ea1068493a56e64dad2b81c58dee2811f3324d56c88286d4735/merged/usr/lib/emby-server /var/lib/docker/overlay2/fe66be4f15b80ea1068493a56e64dad2b81c58dee2811f3324d56c88286d4735/merged/usr/lib/emby-server/emby-server.sh /var/lib/docker/overlay2/fe66be4f15b80ea1068493a56e64dad2b81c58dee2811f3324d56c88286d4735/merged/usr/lib/emby-server/bin/dashboard-ui/bower_components/emby-apiclient /var/lib/docker/overlay2/fe66be4f15b80ea1068493a56e64dad2b81c58dee2811f3324d56c88286d4735/merged/usr/lib/emby-server/bin/dashboard-ui/bower_components/emby-webcomponents /var/lib/docker/overlay2/fe66be4f15b80ea1068493a56e64dad2b81c58dee2811f3324d56c88286d4735/merged/usr/lib/emby-server/bin/dashboard-ui/bower_components/emby-webcomponents/emby-textarea /var/lib/docker/overlay2/fe66be4f15b80ea1068493a56e64dad2b81c58dee2811f3324d56c88286d4735/merged/usr/lib/emby-server/bin/dashboard-ui/bower_components/emby-webcomponents/emby-textarea/emby-textarea.css /var/lib/docker/overlay2/fe66be4f15b80ea1068493a56e64dad2b81c58dee2811f3324d56c88286d4735/merged/usr/lib/emby-server/bin/dashboard-ui/bower_components/emby-webcomponents/emby-textarea/emby-textarea.js /var/lib/docker/overlay2/fe66be4f15b80ea1068493a56e64dad2b81c58dee2811f3324d56c88286d4735/merged/usr/lib/emby-server/bin/dashboard-ui/bower_components/emby-webcomponents/emby-slider /var/lib/docker/overlay2/fe66be4f15b80ea1068493a56e64dad2b81c58dee2811f3324d56c88286d4735/merged/usr/lib/emby-server/bin/dashboard-ui/bower_components/emby-webcomponents/emby-slider/emby-slider.css /var/lib/docker/overlay2/fe66be4f15b80ea1068493a56e64dad2b81c58dee2811f3324d56c88286d4735/merged/usr/lib/emby-server/bin/dashboard-ui/bower_components/emby-webcomponents/emby-slider/emby-slider.js /var/lib/docker/overlay2/fe66be4f15b80ea1068493a56e64dad2b81c58dee2811f3324d56c88286d4735/merged/usr/lib/emby-server/bin/dashboard-ui/bower_components/emby-webcomponents/emby-collapse /var/lib/docker/overlay2/fe66be4f15b80ea1068493a56e64dad2b81c58dee2811f3324d56c88286d4735/merged/usr/lib/emby-server/bin/dashboard-ui/bower_components/emby-webcomponents/emby-collapse/emby-collapse.js /var/lib/docker/overlay2/fe66be4f15b80ea1068493a56e64dad2b81c58dee2811f3324d56c88286d4735/merged/usr/lib/emby-server/bin/dashboard-ui/bower_components/emby-webcomponents/emby-collapse/emby-collapse.css /var/lib/docker/overlay2/fe66be4f15b80ea1068493a56e64dad2b81c58dee2811f3324d56c88286d4735/merged/usr/lib/emby-server/bin/dashboard-ui/bower_components/emby-webcomponents/emby-input /var/lib/docker/overlay2/fe66be4f15b80ea1068493a56e64dad2b81c58dee2811f3324d56c88286d4735/merged/usr/lib/emby-server/bin/dashboard-ui/bower_components/emby-webcomponents/emby-input/emby-input.css /var/lib/docker/overlay2/fe66be4f15b80ea1068493a56e64dad2b81c58dee2811f3324d56c88286d4735/merged/usr/lib/emby-server/bin/dashboard-ui/bower_components/emby-webcomponents/emby-input/emby-input.js /var/lib/docker/overlay2/fe66be4f15b80ea1068493a56e64dad2b81c58dee2811f3324d56c88286d4735/merged/usr/lib/emby-server/bin/dashboard-ui/bower_components/emby-webcomponents/emby-tabs /var/lib/docker/overlay2/fe66be4f15b80ea1068493a56e64dad2b81c58dee2811f3324d56c88286d4735/merged/usr/lib/emby-server/bin/dashboard-ui/bower_components/emby-webcomponents/emby-tabs/emby-tabs.js /var/lib/docker/overlay2/fe66be4f15b80ea1068493a56e64dad2b81c58dee2811f3324d56c88286d4735/merged/usr/lib/emby-server/bin/dashboard-ui/bower_components/emby-webcomponents/emby-tabs/emby-tabs.css /var/lib/docker/overlay2/fe66be4f15b80ea1068493a56e64dad2b81c58dee2811f3324d56c88286d4735/merged/usr/lib/emby-server/bin/dashboard-ui/bower_components/emby-webcomponents/emby-radio /var/lib/docker/overlay2/fe66be4f15b80ea1068493a56e64dad2b81c58dee2811f3324d56c88286d4735/merged/usr/lib/emby-server/bin/dashboard-ui/bower_components/emby-webcomponents/emby-radio/emby-radio.css /var/lib/docker/overlay2/fe66be4f15b80ea1068493a56e64dad2b81c58dee2811f3324d56c88286d4735/merged/usr/lib/emby-server/bin/dashboard-ui/bower_components/emby-webcomponents/emby-radio/emby-radio.js /var/lib/docker/overlay2/fe66be4f15b80ea1068493a56e64dad2b81c58dee2811f3324d56c88286d4735/merged/usr/lib/emby-server/bin/dashboard-ui/bower_components/emby-webcomponents/emby-toggle /var/lib/docker/overlay2/fe66be4f15b80ea1068493a56e64dad2b81c58dee2811f3324d56c88286d4735/merged/usr/lib/emby-server/bin/dashboard-ui/bower_components/emby-webcomponents/emby-toggle/emby-toggle.css /var/lib/docker/overlay2/fe66be4f15b80ea1068493a56e64dad2b81c58dee2811f3324d56c88286d4735/merged/usr/lib/emby-server/bin/dashboard-ui/bower_components/emby-webcomponents/emby-toggle/emby-toggle.js /var/lib/docker/overlay2/fe66be4f15b80ea1068493a56e64dad2b81c58dee2811f3324d56c88286d4735/merged/usr/lib/emby-server/bin/dashboard-ui/bower_components/emby-webcomponents/emby-select /var/lib/docker/overlay2/fe66be4f15b80ea1068493a56e64dad2b81c58dee2811f3324d56c88286d4735/merged/usr/lib/emby-server/bin/dashboard-ui/bower_components/emby-webcomponents/emby-select/emby-select.css /var/lib/docker/overlay2/fe66be4f15b80ea1068493a56e64dad2b81c58dee2811f3324d56c88286d4735/merged/usr/lib/emby-server/bin/dashboard-ui/bower_components/emby-webcomponents/emby-select/emby-select.js /var/lib/docker/overlay2/fe66be4f15b80ea1068493a56e64dad2b81c58dee2811f3324d56c88286d4735/merged/usr/lib/emby-server/bin/dashboard-ui/bower_components/emby-webcomponents/emby-itemscontainer /var/lib/docker/overlay2/fe66be4f15b80ea1068493a56e64dad2b81c58dee2811f3324d56c88286d4735/merged/usr/lib/emby-server/bin/dashboard-ui/bower_components/emby-webcomponents/emby-itemscontainer/emby-itemscontainer.js /var/lib/docker/overlay2/fe66be4f15b80ea1068493a56e64dad2b81c58dee2811f3324d56c88286d4735/merged/usr/lib/emby-server/bin/dashboard-ui/bower_components/emby-webcomponents/emby-button /var/lib/docker/overlay2/fe66be4f15b80ea1068493a56e64dad2b81c58dee2811f3324d56c88286d4735/merged/usr/lib/emby-server/bin/dashboard-ui/bower_components/emby-webcomponents/emby-button/emby-button.js /var/lib/docker/overlay2/fe66be4f15b80ea1068493a56e64dad2b81c58dee2811f3324d56c88286d4735/merged/usr/lib/emby-server/bin/dashboard-ui/bower_components/emby-webcomponents/emby-button/emby-button.css /var/lib/docker/overlay2/fe66be4f15b80ea1068493a56e64dad2b81c58dee2811f3324d56c88286d4735/merged/usr/lib/emby-server/bin/dashboard-ui/bower_components/emby-webcomponents/emby-checkbox /var/lib/docker/overlay2/fe66be4f15b80ea1068493a56e64dad2b81c58dee2811f3324d56c88286d4735/merged/usr/lib/emby-server/bin/dashboard-ui/bower_components/emby-webcomponents/emby-checkbox/emby-checkbox.css /var/lib/docker/overlay2/fe66be4f15b80ea1068493a56e64dad2b81c58dee2811f3324d56c88286d4735/merged/usr/lib/emby-server/bin/dashboard-ui/bower_components/emby-webcomponents/emby-checkbox/emby-checkbox.js /var/lib/docker/overlay2/fe66be4f15b80ea1068493a56e64dad2b81c58dee2811f3324d56c88286d4735/merged/usr/lib/systemd/system/emby-server.service /var/lib/docker/overlay2/8f5d19908fd23f906dc6ab375a6be6716ccd089c51cc98c293b9aca2e70a8bd5/diff/etc/emby-server.conf /var/lib/docker/overlay2/8f5d19908fd23f906dc6ab375a6be6716ccd089c51cc98c293b9aca2e70a8bd5/diff/etc/sudoers.d/emby /var/lib/docker/overlay2/8f5d19908fd23f906dc6ab375a6be6716ccd089c51cc98c293b9aca2e70a8bd5/diff/etc/zypp/repos.d/emby.repo /var/lib/docker/overlay2/8f5d19908fd23f906dc6ab375a6be6716ccd089c51cc98c293b9aca2e70a8bd5/diff/etc/default/emby-server /var/lib/docker/overlay2/8f5d19908fd23f906dc6ab375a6be6716ccd089c51cc98c293b9aca2e70a8bd5/diff/etc/services.d/emby-server /var/lib/docker/overlay2/8f5d19908fd23f906dc6ab375a6be6716ccd089c51cc98c293b9aca2e70a8bd5/diff/var/lib/emby-server /var/lib/docker/overlay2/8f5d19908fd23f906dc6ab375a6be6716ccd089c51cc98c293b9aca2e70a8bd5/diff/var/lib/systemd/migrated/emby-server /var/lib/docker/overlay2/8f5d19908fd23f906dc6ab375a6be6716ccd089c51cc98c293b9aca2e70a8bd5/diff/usr/bin/emby-server /var/lib/docker/overlay2/8f5d19908fd23f906dc6ab375a6be6716ccd089c51cc98c293b9aca2e70a8bd5/diff/usr/lib/emby-server /var/lib/docker/overlay2/8f5d19908fd23f906dc6ab375a6be6716ccd089c51cc98c293b9aca2e70a8bd5/diff/usr/lib/emby-server/emby-server.sh /var/lib/docker/overlay2/8f5d19908fd23f906dc6ab375a6be6716ccd089c51cc98c293b9aca2e70a8bd5/diff/usr/lib/emby-server/bin/dashboard-ui/bower_components/emby-apiclient /var/lib/docker/overlay2/8f5d19908fd23f906dc6ab375a6be6716ccd089c51cc98c293b9aca2e70a8bd5/diff/usr/lib/emby-server/bin/dashboard-ui/bower_components/emby-webcomponents /var/lib/docker/overlay2/8f5d19908fd23f906dc6ab375a6be6716ccd089c51cc98c293b9aca2e70a8bd5/diff/usr/lib/emby-server/bin/dashboard-ui/bower_components/emby-webcomponents/emby-textarea /var/lib/docker/overlay2/8f5d19908fd23f906dc6ab375a6be6716ccd089c51cc98c293b9aca2e70a8bd5/diff/usr/lib/emby-server/bin/dashboard-ui/bower_components/emby-webcomponents/emby-textarea/emby-textarea.css /var/lib/docker/overlay2/8f5d19908fd23f906dc6ab375a6be6716ccd089c51cc98c293b9aca2e70a8bd5/diff/usr/lib/emby-server/bin/dashboard-ui/bower_components/emby-webcomponents/emby-textarea/emby-textarea.js /var/lib/docker/overlay2/8f5d19908fd23f906dc6ab375a6be6716ccd089c51cc98c293b9aca2e70a8bd5/diff/usr/lib/emby-server/bin/dashboard-ui/bower_components/emby-webcomponents/emby-slider /var/lib/docker/overlay2/8f5d19908fd23f906dc6ab375a6be6716ccd089c51cc98c293b9aca2e70a8bd5/diff/usr/lib/emby-server/bin/dashboard-ui/bower_components/emby-webcomponents/emby-slider/emby-slider.css /var/lib/docker/overlay2/8f5d19908fd23f906dc6ab375a6be6716ccd089c51cc98c293b9aca2e70a8bd5/diff/usr/lib/emby-server/bin/dashboard-ui/bower_components/emby-webcomponents/emby-slider/emby-slider.js /var/lib/docker/overlay2/8f5d19908fd23f906dc6ab375a6be6716ccd089c51cc98c293b9aca2e70a8bd5/diff/usr/lib/emby-server/bin/dashboard-ui/bower_components/emby-webcomponents/emby-collapse /var/lib/docker/overlay2/8f5d19908fd23f906dc6ab375a6be6716ccd089c51cc98c293b9aca2e70a8bd5/diff/usr/lib/emby-server/bin/dashboard-ui/bower_components/emby-webcomponents/emby-collapse/emby-collapse.js /var/lib/docker/overlay2/8f5d19908fd23f906dc6ab375a6be6716ccd089c51cc98c293b9aca2e70a8bd5/diff/usr/lib/emby-server/bin/dashboard-ui/bower_components/emby-webcomponents/emby-collapse/emby-collapse.css /var/lib/docker/overlay2/8f5d19908fd23f906dc6ab375a6be6716ccd089c51cc98c293b9aca2e70a8bd5/diff/usr/lib/emby-server/bin/dashboard-ui/bower_components/emby-webcomponents/emby-input /var/lib/docker/overlay2/8f5d19908fd23f906dc6ab375a6be6716ccd089c51cc98c293b9aca2e70a8bd5/diff/usr/lib/emby-server/bin/dashboard-ui/bower_components/emby-webcomponents/emby-input/emby-input.css /var/lib/docker/overlay2/8f5d19908fd23f906dc6ab375a6be6716ccd089c51cc98c293b9aca2e70a8bd5/diff/usr/lib/emby-server/bin/dashboard-ui/bower_components/emby-webcomponents/emby-input/emby-input.js /var/lib/docker/overlay2/8f5d19908fd23f906dc6ab375a6be6716ccd089c51cc98c293b9aca2e70a8bd5/diff/usr/lib/emby-server/bin/dashboard-ui/bower_components/emby-webcomponents/emby-tabs /var/lib/docker/overlay2/8f5d19908fd23f906dc6ab375a6be6716ccd089c51cc98c293b9aca2e70a8bd5/diff/usr/lib/emby-server/bin/dashboard-ui/bower_components/emby-webcomponents/emby-tabs/emby-tabs.js /var/lib/docker/overlay2/8f5d19908fd23f906dc6ab375a6be6716ccd089c51cc98c293b9aca2e70a8bd5/diff/usr/lib/emby-server/bin/dashboard-ui/bower_components/emby-webcomponents/emby-tabs/emby-tabs.css /var/lib/docker/overlay2/8f5d19908fd23f906dc6ab375a6be6716ccd089c51cc98c293b9aca2e70a8bd5/diff/usr/lib/emby-server/bin/dashboard-ui/bower_components/emby-webcomponents/emby-radio /var/lib/docker/overlay2/8f5d19908fd23f906dc6ab375a6be6716ccd089c51cc98c293b9aca2e70a8bd5/diff/usr/lib/emby-server/bin/dashboard-ui/bower_components/emby-webcomponents/emby-radio/emby-radio.css /var/lib/docker/overlay2/8f5d19908fd23f906dc6ab375a6be6716ccd089c51cc98c293b9aca2e70a8bd5/diff/usr/lib/emby-server/bin/dashboard-ui/bower_components/emby-webcomponents/emby-radio/emby-radio.js /var/lib/docker/overlay2/8f5d19908fd23f906dc6ab375a6be6716ccd089c51cc98c293b9aca2e70a8bd5/diff/usr/lib/emby-server/bin/dashboard-ui/bower_components/emby-webcomponents/emby-toggle /var/lib/docker/overlay2/8f5d19908fd23f906dc6ab375a6be6716ccd089c51cc98c293b9aca2e70a8bd5/diff/usr/lib/emby-server/bin/dashboard-ui/bower_components/emby-webcomponents/emby-toggle/emby-toggle.css /var/lib/docker/overlay2/8f5d19908fd23f906dc6ab375a6be6716ccd089c51cc98c293b9aca2e70a8bd5/diff/usr/lib/emby-server/bin/dashboard-ui/bower_components/emby-webcomponents/emby-toggle/emby-toggle.js /var/lib/docker/overlay2/8f5d19908fd23f906dc6ab375a6be6716ccd089c51cc98c293b9aca2e70a8bd5/diff/usr/lib/emby-server/bin/dashboard-ui/bower_components/emby-webcomponents/emby-select /var/lib/docker/overlay2/8f5d19908fd23f906dc6ab375a6be6716ccd089c51cc98c293b9aca2e70a8bd5/diff/usr/lib/emby-server/bin/dashboard-ui/bower_components/emby-webcomponents/emby-select/emby-select.css /var/lib/docker/overlay2/8f5d19908fd23f906dc6ab375a6be6716ccd089c51cc98c293b9aca2e70a8bd5/diff/usr/lib/emby-server/bin/dashboard-ui/bower_components/emby-webcomponents/emby-select/emby-select.js /var/lib/docker/overlay2/8f5d19908fd23f906dc6ab375a6be6716ccd089c51cc98c293b9aca2e70a8bd5/diff/usr/lib/emby-server/bin/dashboard-ui/bower_components/emby-webcomponents/emby-itemscontainer /var/lib/docker/overlay2/8f5d19908fd23f906dc6ab375a6be6716ccd089c51cc98c293b9aca2e70a8bd5/diff/usr/lib/emby-server/bin/dashboard-ui/bower_components/emby-webcomponents/emby-itemscontainer/emby-itemscontainer.js /var/lib/docker/overlay2/8f5d19908fd23f906dc6ab375a6be6716ccd089c51cc98c293b9aca2e70a8bd5/diff/usr/lib/emby-server/bin/dashboard-ui/bower_components/emby-webcomponents/emby-button /var/lib/docker/overlay2/8f5d19908fd23f906dc6ab375a6be6716ccd089c51cc98c293b9aca2e70a8bd5/diff/usr/lib/emby-server/bin/dashboard-ui/bower_components/emby-webcomponents/emby-button/emby-button.js /var/lib/docker/overlay2/8f5d19908fd23f906dc6ab375a6be6716ccd089c51cc98c293b9aca2e70a8bd5/diff/usr/lib/emby-server/bin/dashboard-ui/bower_components/emby-webcomponents/emby-button/emby-button.css /var/lib/docker/overlay2/8f5d19908fd23f906dc6ab375a6be6716ccd089c51cc98c293b9aca2e70a8bd5/diff/usr/lib/emby-server/bin/dashboard-ui/bower_components/emby-webcomponents/emby-checkbox /var/lib/docker/overlay2/8f5d19908fd23f906dc6ab375a6be6716ccd089c51cc98c293b9aca2e70a8bd5/diff/usr/lib/emby-server/bin/dashboard-ui/bower_components/emby-webcomponents/emby-checkbox/emby-checkbox.css /var/lib/docker/overlay2/8f5d19908fd23f906dc6ab375a6be6716ccd089c51cc98c293b9aca2e70a8bd5/diff/usr/lib/emby-server/bin/dashboard-ui/bower_components/emby-webcomponents/emby-checkbox/emby-checkbox.js /var/lib/docker/overlay2/8f5d19908fd23f906dc6ab375a6be6716ccd089c51cc98c293b9aca2e70a8bd5/diff/usr/lib/systemd/system/emby-server.service /var/lib/docker/overlay2/0747faf49edaaddb71ec938def66162a75c301c09b661328edf0a16346506797/diff/etc/services.d/emby-server /var/lib/docker/overlay2/a06d947e1331a237faf3db00dd0401457e0526c26172494507d46df61735ed0b/diff/etc/emby-server.conf /var/lib/docker/overlay2/a06d947e1331a237faf3db00dd0401457e0526c26172494507d46df61735ed0b/diff/etc/sudoers.d/emby /var/lib/docker/overlay2/a06d947e1331a237faf3db00dd0401457e0526c26172494507d46df61735ed0b/diff/etc/default/emby-server /var/lib/docker/overlay2/a06d947e1331a237faf3db00dd0401457e0526c26172494507d46df61735ed0b/diff/var/lib/emby-server /var/lib/docker/overlay2/a06d947e1331a237faf3db00dd0401457e0526c26172494507d46df61735ed0b/diff/var/lib/systemd/migrated/emby-server /var/lib/docker/overlay2/a06d947e1331a237faf3db00dd0401457e0526c26172494507d46df61735ed0b/diff/usr/bin/emby-server /var/lib/docker/overlay2/a06d947e1331a237faf3db00dd0401457e0526c26172494507d46df61735ed0b/diff/usr/lib/emby-server /var/lib/docker/overlay2/a06d947e1331a237faf3db00dd0401457e0526c26172494507d46df61735ed0b/diff/usr/lib/emby-server/emby-server.sh /var/lib/docker/overlay2/a06d947e1331a237faf3db00dd0401457e0526c26172494507d46df61735ed0b/diff/usr/lib/emby-server/bin/dashboard-ui/bower_components/emby-apiclient /var/lib/docker/overlay2/a06d947e1331a237faf3db00dd0401457e0526c26172494507d46df61735ed0b/diff/usr/lib/emby-server/bin/dashboard-ui/bower_components/emby-webcomponents /var/lib/docker/overlay2/a06d947e1331a237faf3db00dd0401457e0526c26172494507d46df61735ed0b/diff/usr/lib/emby-server/bin/dashboard-ui/bower_components/emby-webcomponents/emby-textarea /var/lib/docker/overlay2/a06d947e1331a237faf3db00dd0401457e0526c26172494507d46df61735ed0b/diff/usr/lib/emby-server/bin/dashboard-ui/bower_components/emby-webcomponents/emby-textarea/emby-textarea.css /var/lib/docker/overlay2/a06d947e1331a237faf3db00dd0401457e0526c26172494507d46df61735ed0b/diff/usr/lib/emby-server/bin/dashboard-ui/bower_components/emby-webcomponents/emby-textarea/emby-textarea.js /var/lib/docker/overlay2/a06d947e1331a237faf3db00dd0401457e0526c26172494507d46df61735ed0b/diff/usr/lib/emby-server/bin/dashboard-ui/bower_components/emby-webcomponents/emby-slider /var/lib/docker/overlay2/a06d947e1331a237faf3db00dd0401457e0526c26172494507d46df61735ed0b/diff/usr/lib/emby-server/bin/dashboard-ui/bower_components/emby-webcomponents/emby-slider/emby-slider.css /var/lib/docker/overlay2/a06d947e1331a237faf3db00dd0401457e0526c26172494507d46df61735ed0b/diff/usr/lib/emby-server/bin/dashboard-ui/bower_components/emby-webcomponents/emby-slider/emby-slider.js /var/lib/docker/overlay2/a06d947e1331a237faf3db00dd0401457e0526c26172494507d46df61735ed0b/diff/usr/lib/emby-server/bin/dashboard-ui/bower_components/emby-webcomponents/emby-connect /var/lib/docker/overlay2/a06d947e1331a237faf3db00dd0401457e0526c26172494507d46df61735ed0b/diff/usr/lib/emby-server/bin/dashboard-ui/bower_components/emby-webcomponents/emby-collapse /var/lib/docker/overlay2/a06d947e1331a237faf3db00dd0401457e0526c26172494507d46df61735ed0b/diff/usr/lib/emby-server/bin/dashboard-ui/bower_components/emby-webcomponents/emby-collapse/emby-collapse.js /var/lib/docker/overlay2/a06d947e1331a237faf3db00dd0401457e0526c26172494507d46df61735ed0b/diff/usr/lib/emby-server/bin/dashboard-ui/bower_components/emby-webcomponents/emby-collapse/emby-collapse.css /var/lib/docker/overlay2/a06d947e1331a237faf3db00dd0401457e0526c26172494507d46df61735ed0b/diff/usr/lib/emby-server/bin/dashboard-ui/bower_components/emby-webcomponents/emby-scroller /var/lib/docker/overlay2/a06d947e1331a237faf3db00dd0401457e0526c26172494507d46df61735ed0b/diff/usr/lib/emby-server/bin/dashboard-ui/bower_components/emby-webcomponents/emby-scroller/emby-scroller.js /var/lib/docker/overlay2/a06d947e1331a237faf3db00dd0401457e0526c26172494507d46df61735ed0b/diff/usr/lib/emby-server/bin/dashboard-ui/bower_components/emby-webcomponents/emby-input /var/lib/docker/overlay2/a06d947e1331a237faf3db00dd0401457e0526c26172494507d46df61735ed0b/diff/usr/lib/emby-server/bin/dashboard-ui/bower_components/emby-webcomponents/emby-input/emby-input.css /var/lib/docker/overlay2/a06d947e1331a237faf3db00dd0401457e0526c26172494507d46df61735ed0b/diff/usr/lib/emby-server/bin/dashboard-ui/bower_components/emby-webcomponents/emby-input/emby-input.js /var/lib/docker/overlay2/a06d947e1331a237faf3db00dd0401457e0526c26172494507d46df61735ed0b/diff/usr/lib/emby-server/bin/dashboard-ui/bower_components/emby-webcomponents/emby-tabs /var/lib/docker/overlay2/a06d947e1331a237faf3db00dd0401457e0526c26172494507d46df61735ed0b/diff/usr/lib/emby-server/bin/dashboard-ui/bower_components/emby-webcomponents/emby-tabs/emby-tabs.js /var/lib/docker/overlay2/a06d947e1331a237faf3db00dd0401457e0526c26172494507d46df61735ed0b/diff/usr/lib/emby-server/bin/dashboard-ui/bower_components/emby-webcomponents/emby-tabs/emby-tabs.css /var/lib/docker/overlay2/a06d947e1331a237faf3db00dd0401457e0526c26172494507d46df61735ed0b/diff/usr/lib/emby-server/bin/dashboard-ui/bower_components/emby-webcomponents/emby-radio /var/lib/docker/overlay2/a06d947e1331a237faf3db00dd0401457e0526c26172494507d46df61735ed0b/diff/usr/lib/emby-server/bin/dashboard-ui/bower_components/emby-webcomponents/emby-radio/emby-radio.css /var/lib/docker/overlay2/a06d947e1331a237faf3db00dd0401457e0526c26172494507d46df61735ed0b/diff/usr/lib/emby-server/bin/dashboard-ui/bower_components/emby-webcomponents/emby-radio/emby-radio.js /var/lib/docker/overlay2/a06d947e1331a237faf3db00dd0401457e0526c26172494507d46df61735ed0b/diff/usr/lib/emby-server/bin/dashboard-ui/bower_components/emby-webcomponents/emby-select /var/lib/docker/overlay2/a06d947e1331a237faf3db00dd0401457e0526c26172494507d46df61735ed0b/diff/usr/lib/emby-server/bin/dashboard-ui/bower_components/emby-webcomponents/emby-select/emby-select.css /var/lib/docker/overlay2/a06d947e1331a237faf3db00dd0401457e0526c26172494507d46df61735ed0b/diff/usr/lib/emby-server/bin/dashboard-ui/bower_components/emby-webcomponents/emby-select/emby-select.js /var/lib/docker/overlay2/a06d947e1331a237faf3db00dd0401457e0526c26172494507d46df61735ed0b/diff/usr/lib/emby-server/bin/dashboard-ui/bower_components/emby-webcomponents/emby-itemscontainer /var/lib/docker/overlay2/a06d947e1331a237faf3db00dd0401457e0526c26172494507d46df61735ed0b/diff/usr/lib/emby-server/bin/dashboard-ui/bower_components/emby-webcomponents/emby-itemscontainer/emby-itemscontainer.js /var/lib/docker/overlay2/a06d947e1331a237faf3db00dd0401457e0526c26172494507d46df61735ed0b/diff/usr/lib/emby-server/bin/dashboard-ui/bower_components/emby-webcomponents/emby-button /var/lib/docker/overlay2/a06d947e1331a237faf3db00dd0401457e0526c26172494507d46df61735ed0b/diff/usr/lib/emby-server/bin/dashboard-ui/bower_components/emby-webcomponents/emby-button/emby-button.js /var/lib/docker/overlay2/a06d947e1331a237faf3db00dd0401457e0526c26172494507d46df61735ed0b/diff/usr/lib/emby-server/bin/dashboard-ui/bower_components/emby-webcomponents/emby-button/emby-button.css /var/lib/docker/overlay2/a06d947e1331a237faf3db00dd0401457e0526c26172494507d46df61735ed0b/diff/usr/lib/emby-server/bin/dashboard-ui/bower_components/emby-webcomponents/emby-checkbox /var/lib/docker/overlay2/a06d947e1331a237faf3db00dd0401457e0526c26172494507d46df61735ed0b/diff/usr/lib/emby-server/bin/dashboard-ui/bower_components/emby-webcomponents/emby-checkbox/emby-checkbox.css /var/lib/docker/overlay2/a06d947e1331a237faf3db00dd0401457e0526c26172494507d46df61735ed0b/diff/usr/lib/emby-server/bin/dashboard-ui/bower_components/emby-webcomponents/emby-checkbox/emby-checkbox.js /var/lib/docker/overlay2/a06d947e1331a237faf3db00dd0401457e0526c26172494507d46df61735ed0b/diff/usr/lib/systemd/system/emby-server.service /var/lib/docker/overlay2/089b42346baa4131c4073b6abcb30bfd1f434e7420964d84b2a013ff67b8ca12/diff/usr/lib/emby-server /usr/local/bin/emby-server . ps -ef | grep docker . ps -ef | grep emby Thanks a lot for your assistance. Best regards,
  9. Hi there Every night my emby-server service on my Pi 3 stops running and needs to be restarted. It seems to be during the library scan. Can anyone provide some insight as to what's happening here. I haven't enabled the debug logging option. I have also disabled real time monitoring, as I saw that mentioned in a similar older thread. I am also running openvpn on the device. Could that be causing some form of conflict, or maybe overloading the capabilities of the Pi 3? When it's running, it has no issues at all. Only that I need to restart it ever day as at some point it just disappears. These are all the logs I have since I started running the server on the Pi a few days ago. Happy to provide any other information, or do whatever troubleshooting to help. server-63627284127.txt server-63627292800.txt server-63627360805.txt server-63627379200.txt server-63627443467.txt server-63627465600.txt server-63627497816.txt server-63627546658.txt server-63627552000.txt server-63627592630.txt
  10. silver12

    unmet dependencies - raspberry pi

    Hello, I'm trying to install emby on Raspberry Pi 3. Both Ubuntu-mate and Rasbian give me the exact unmet dependencies error: root@raspberrypi:# apt-get update && apt-get install emby-server The following packages have unmet dependencies: emby-server : Depends: mono-runtime (>= 3.0~) but it is not going to be installed Depends: libmono-microsoft-csharp4.0-cil (>= 1.0) but it is not going to be installed Depends: libmono-posix4.0-cil (>= 4.0.0~alpha1) but it is not going to be installed Depends: libmono-system-configuration4.0-cil (>= 4.0.0~alpha1) but it is not going to be installed Depends: libmono-system-core4.0-cil (>= 4.0.0~alpha1) but it is not going to be installed Depends: libmono-system-data4.0-cil (>= 4.0.0~alpha1) but it is not going to be installed Depends: libmono-system-drawing4.0-cil (>= 3.0.6) but it is not going to be installed Depends: libmono-system-io-compression4.0-cil (>= 3.2.1) but it is not going to be installed Depends: libmono-system-net-http4.0-cil (>= 1.0) but it is not going to be installed Depends: libmono-system-runtime-serialization4.0-cil (>= 4.0.0~alpha1) but it is not going to be installed Depends: libmono-system-servicemodel4.0a-cil (>= 3.2.3) but it is not going to be installed Depends: libmono-system-transactions4.0-cil (>= 1.0) but it is not going to be installed Depends: libmono-system-web4.0-cil (>= 2.10.3) but it is not going to be installed Depends: libmono-system-xml-linq4.0-cil (>= 3.0.6) but it is not going to be installed Depends: libmono-system-xml4.0-cil (>= 3.12.0) but it is not going to be installed Depends: libmono-system4.0-cil (>= 4.0.0~alpha1) but it is not going to be installed Depends: mono-devel (>= 1.0) but it is not going to be installed Recommends: libembymagickwand-6.q8-2 but it is not installable E: Unable to correct problems, you have held broken packages. root@raspberrypi:# apt-cache policy libembymagickwand* libembymagickwand-6.q8-2: Installed: (none) Candidate: (none) Version table: Also tried the following solutions: https://emby.media/community/index.php?/topic/29622-unmet-dependencies-imagemagick-6q8/ https://emby.media/community/index.php?/topic/28188-massive-update-for-debian-and-ubuntu/ root@raspberrypi:# apt-get remove --purge libmagickwand-6.q8-2 libmagickcore-6.q8-2 Reading package lists... Done Building dependency tree Reading state information... Done E: Unable to locate package libmagickwand-6.q8-2 E: Couldn't find any package by regex 'libmagickwand-6.q8-2' E: Unable to locate package libmagickcore-6.q8-2 E: Couldn't find any package by regex 'libmagickcore-6.q8-2' Is it currently possible to install emby-server on Debian/Rpi? Cheers,
  11. Hi guys, as the tittle says, can you recommend me the best settings for the Emby addon for Kodi. I have been using it for a while now and it works great, altough a little bit slow the first time it syncs the database, however, lately I've been getting the " Library Sync Thread Has Exited! You should restart Kodi now" so I have to repair the local database to fix the error, which takes a while to complete. So after reading a few forum posts about the error, it seems that it could be related to the items requested to the server and/or artwork cache threads. I have not changed any settings before and always used the default settings. So can you tell me which settings I should change to improve the performance of the Emby addon on a Raspberry Pi 1 (Single core, 700 MHz, overclocked to 1150 MHz). Thanks.
  12. Not entirely sure where this is best placed, so I'll start here. I have Emby Server up and running on a Raspberry Pi 2 (YEAH!!!). The Raspberry Pi is reading a drive on a HOME SERVER that contains all my media. Seems to be working great. Then I have a HTPC running in my theater with Emby for WMC running and looking at the RPi. The library comes up fine, and all the artwork displays beautifully. But when I select a movie, and hit PLAY, nothing happens. It acts like it wants to start, I get a progress bar showing length of movie and the thumbnail, but nothing ever plays. I get no error or anything, just a blank dark screen. The movies play fine in straight WMC without using EMBY, so I'm not sure where it's falling apart. Any ideas welcome! And if this should be in a different area, let me know. Thank You Sean
  13. Hi! TLDR: Good news: Emby-Server on Rpi2! Bad news: Frequent crashes! Also: Me no understand because of Noob. Been reading up on Emby and thought I might try it on my Raspberry Pi 2 running debian (Well, running OSMC which is based off of Debian Jessie). Easier said than done! I couldn't really find anyone who'd been successful at it, but what the hell! Over at the OSMC forums me and one of the support guys from OSMC played around with it: https://discourse.osmc.tv/t/emby-server-osmc-on-rpi2/6274/ This morning I finally got it working by following the manual installation instructions for linux. Mediainfo was installed already (through apt-get) mono, imagemagick and sqlite3 were installed through aptitude, being careful so as to not accept any solutions that cancelled one of the others out (this was especially tricky with mono). Ffmpeg was built from source (which took ages and ages on the rpi2): sudo aptitude remove ffmpeg cd /usr/src sudo mkdir ffmpeg sudo chown `whoami`:users ffmpeg git clone git://source.ffmpeg.org/ffmpeg.git ffmpeg cd ffmpeg ./configure make sudo make install and then I changed the config files accordingly and ran with mono MediaBrowser.Server.Mono.exe -ffmpeg “/usr/src/ffmpeg/ffmpeg” -ffprobe “/usr/src/ffmpeg/ffprobe” Finally it was alive! It throws a few errors during startup: Info, ImageMagick, ImageMagick version: ImageMagick 6.8.9-9 Q16 arm 2015-01-05 http://www.imagemagick.org Error, ImageMagick, Error loading webp: *** Error Report *** Version: 3.0.5675.1 Command line: /opt/MediaBrowser/MediaBrowser.Server.Mono.exe -ffmpeg “/usr/src/ffmpeg/ffmpeg” -ffprobe “/usr/src/ffmpeg/ffprobe” Operating system: Unix 3.18.13.1 Processor count: 4 64-Bit OS: False 64-Bit Process: False Program data path: /opt/MediaBrowser/ProgramData-Server Mono: 3.2.8 (Debian 3.2.8+dfsg-10) Application Path: /opt/MediaBrowser/MediaBrowser.Server.Mono.exe delegate failed `"cwebp" -quiet -q %Q "%i" -o "%o"' @ error/delegate.c/InvokeDelegate/1310 ImageMagickSharp.WandException at ImageMagickSharp.WandCore`1[ImageMagickSharp.MagickWand].CheckError (Boolean status) [0x00000] in <filename unknown>:0 at ImageMagickSharp.MagickWand.SaveImage (System.String path) [0x00000] in <filename unknown>:0 at Emby.Drawing.ImageMagick.ImageMagickEncoder.TestWebp () [0x00000] in <filename unknown>:0 and Error, HttpServer, Exception loading certificate: /opt/MediaBrowser/ProgramData-Server/ssl/cert_9c31b7884ea5475c8687970fc5996297.pfx *** Error Report *** Version: 3.0.5675.1 Command line: /opt/MediaBrowser/MediaBrowser.Server.Mono.exe -ffmpeg “/usr/src/ffmpeg/ffmpeg” -ffprobe “/usr/src/ffmpeg/ffprobe” Operating system: Unix 3.18.13.1 Processor count: 4 64-Bit OS: False 64-Bit Process: False Program data path: /opt/MediaBrowser/ProgramData-Server Mono: 3.2.8 (Debian 3.2.8+dfsg-10) Application Path: /opt/MediaBrowser/MediaBrowser.Server.Mono.exe Input data cannot be coded as a valid certificate. System.Security.Cryptography.CryptographicException at Mono.Security.X509.X509Certificate.Parse (System.Byte[] data) [0x00000] in <filename unknown>:0 at Mono.Security.X509.X509Certificate..ctor (System.Byte[] data) [0x00000] in <filename unknown>:0 at System.Security.Cryptography.X509Certificates.X509Certificate2.Import (System.Byte[] rawData, System.String password, X509KeyStorageFlags keyStorageFlags) [0x00000] in <filename unknown>:0 at System.Security.Cryptography.X509Certificates.X509Certificate2.Import (System.String fileName, System.String password, X509KeyStorageFlags keyStorageFlags) [0x00000] in <filename unknown>:0 at System.Security.Cryptography.X509Certificates.X509Certificate2..ctor (System.String fileName) [0x00000] in <filename unknown>:0 at SocketHttpListener.Net.EndPointListener.LoadCertificateAndKey (System.Net.IPAddress addr, Int32 port, System.String certificateLocation) [0x00000] in <filename unknown>:0 InnerException: System.Security.Cryptography.CryptographicException Input data cannot be coded as a valid certificate. at Mono.Security.X509.X509Certificate.Parse (System.Byte[] data) [0x00000] in <filename unknown>:0 But starts and the web-ui seems snappy enough, I can play around with settings etc for a few minutes but then it consistently crashes. Maximum it reaches about 29% of the media library scan. The error messages vary slightly but they all look sort of like this: UnhandledExceptionThe task has already completed System.InvalidOperationException at System.Runtime.CompilerServices.AsyncTaskMethodBuilder.SetResult () [0x00000] in <filename unknown>:0 at MediaBrowser.Server.Implementations.Persistence.SqliteItemRepository+<UpdatePeople>d__3c.MoveNext () [0x00000] in <filename unknown>:0 at (wrapper unbox) MediaBrowser.Server.Implementations.Persistence.SqliteItemRepository/<UpdatePeople>d__3c:MoveNext () at System.Threading.Tasks.AwaiterActionContinuation.Execute () [0x00000] in <filename unknown>:0 at System.Threading.Tasks.Task.ProcessCompleteDelegates () [0x00000] in <filename unknown>:0 at System.Threading.Tasks.Task.Finish () [0x00000] in <filename unknown>:0 at System.Threading.Tasks.Task.ThreadStart () [0x00000] in <filename unknown>:0 at System.Threading.Tasks.Task.Execute () [0x00000] in <filename unknown>:0 at System.Threading.Tasks.TpScheduler.TaskExecuterCallback (System.Object obj) [0x00000] in <filename unknown>:0 Shutting down finalizer thread timed out. Segmentation fault oh and the media library is pointed to a mounted network share (through FStab) I literally have no idea where to go from here, I'm totally new to linux and atm I just feel I've hit a dead end. Has anyone got any suggestions where to go from here? EDIT: Changed command to sudo mono MediaBrowser.Server.Mono.exe -ffmpeg “/usr/local/share/man/man1/ffmpeg.1” -ffprobe “/usr/local/share/man/man1/ffprobe.1” To see if a) sudo would help not to run from source directory but installation directory. Checking the logs I get a whole lot of errors regarding ffprobe "error starting ffprobe" and "error in ffprobe". I enabled debug logging, dunno if that's why I got a more detailed shell output but the latest crash reads: UnhandledException The task has already completed System.InvalidOperationException at System.Runtime.CompilerServices.AsyncTaskMethodBuilder.SetResult () [0x00000] in <filename unknown>:0 at MediaBrowser.Server.Implementations.Persistence.SqliteItemRepository+<UpdatePeople>d__3c.MoveNext () [0x00000] in <filename unknown>:0 at (wrapper unbox) MediaBrowser.Server.Implementations.Persistence.SqliteItemRepository/<UpdatePeople>d__3c:MoveNext () at System.Threading.Tasks.AwaiterActionContinuation.Execute () [0x00000] in <filename unknown>:0 at System.Threading.Tasks.Task.ProcessCompleteDelegates () [0x00000] in <filename unknown>:0 at System.Threading.Tasks.Task.Finish () [0x00000] in <filename unknown>:0 at System.Threading.Tasks.Task.ThreadStart () [0x00000] in <filename unknown>:0 at System.Threading.Tasks.Task.Execute () [0x00000] in <filename unknown>:0 at System.Threading.Tasks.TpScheduler.TaskExecuterCallback (System.Object obj) [0x00000] in <filename unknown>:0 Shutting down finalizer thread timed out. Stacktrace: Native stacktrace: Debug info from gdb: ================================================================= Got a SIGSEGV while executing native code. This usually indicates a fatal error in the mono runtime or one of the native libraries used by your application. =================================================================
  14. Hello everyone, I am looking for a little guidance. I recently purchased a Raspberry Pi 2. What I want is to install MB on the Pi, and connect an external hard drive to create a media server that can be accessed by anyone on my network via the MB web interface or smartphone app. The issue that I am having trouble with is installing the server on Pi 2. I started out with Raspbian and tried to install MB using the new debian instructions, thinking that Raspbian is a fork of debian. However, this did not work. I got to thinking, Pi runs on ARM, so I'm (pretty) sure the traditional debian packages wont work? I also tried the manual install instructions, but ran into issues when trying to start the server using the mono command. I have seen people on this forum say that they have MB running on a Pi. My question is what OS and instruction set should I use to get this working? I am thinking of trying Pidora or Arch Linux next, if need be. I really have no preference as to what OS I use, this Pi's sole purpose will be to run a media server. Thanks, Tanner
×
×
  • Create New...