Yotengrit 1 Posted January 18, 2016 Posted January 18, 2016 Hello everyone! I have a problem with starting up Emby after a failed(?) update. Today I had a notification on the admin page that there is a new update for the server. So I shut it down inside the admin menu and proceeded to OpenMediaVault's admin site and started force update. This is the way I always updated and Emby and always worked flawlessly... But today as I started force update I got the following massage: MediaBrowser already installed and running, updating... mediabrowser is not running Downloading... --2016-01-18 15:27:58-- https://github.com/MediaBrowser/MediaBrowser.Releases/raw/master/Server/MediaBrowser.Mono.zip Resolving github.com (github.com)... 192.30.252.131 Connecting to github.com (github.com)|192.30.252.131|:443... connected. HTTP request sent, awaiting response... 301 Moved Permanently Location: https://github.com/MediaBrowser/Emby.Releases/raw/master/Server/MediaBrowser.Mono.zip[following] --2016-01-18 15:28:04-- https://github.com/MediaBrowser/Emby.Releases/raw/master/Server/MediaBrowser.Mono.zip Reusing existing connection to github.com:443. HTTP request sent, awaiting response... 404 Not Found 2016-01-18 15:28:05 ERROR 404: Not Found. So I tried to restart it from OMV's plugin, and I get: mediabrowser is not running Starting mediabrowser Done... But if I try to access MB, I get no website error, so I logged in to my server to check if mediabrowser proccess running but its not and if I try to start/restart it I get starting/restarting answers but the status still says its not running. I looked up my logs folder in mb and I checked the huge most recent log file. I just post the last error message first, but If you guys needs more I can upload the whole log file too. The last error in the log file: 2016-01-18 13:48:15.1027 Info MediaEncoder: Killing ffmpeg process 2016-01-18 13:48:15.1027 Error MediaEncoder: Error sending q command to process 2016-01-18 13:48:15.1027 Error MediaEncoder: Error in WaitForExit 2016-01-18 13:48:15.1027 Error MediaEncoder: Error killing process *** Error Report *** Version: 3.0.5781.5 Command line: /opt/mediabrowser/MediaBrowser.Server.Mono.exe -programdata /var/lib/mediabrowser Operating system: Unix 3.2.0.4 Processor count: 4 64-Bit OS: True 64-Bit Process: True Program data path: /var/lib/mediabrowser Mono: 4.2.1 (Stable 4.2.1.102/6dd2d0d Thu Nov 12 09:52:44 UTC 2015) Application Path: /opt/mediabrowser/MediaBrowser.Server.Mono.exe No process to kill. System.SystemException at System.Diagnostics.Process.Close (Int32 signo) <0x416e6380 + 0x000af> in <filename unknown>:0 at System.Diagnostics.Process.Kill () <0x416e6350 + 0x00013> in <filename unknown>:0 at (wrapper remoting-invoke-with-check) System.Diagnostics.Process:Kill () at MediaBrowser.MediaEncoding.Encoder.MediaEncoder.StopProcess (MediaBrowser.MediaEncoding.Encoder.ProcessWrapper Thanks for future answers!
thefirstofthe300 292 Posted January 19, 2016 Posted January 19, 2016 This would be an issue with the rename to Emby coming back to bite us. The plugin appears to be pulling the latest release from an incorrect GitHub url. @@tekkb
Luke 42077 Posted January 19, 2016 Posted January 19, 2016 i've added back a zip with that old name. Please try again and let us know if it's still an issue. Thanks.
tekkb 13 Posted January 20, 2016 Posted January 20, 2016 (edited) He is not using the correct plugin. The latest openmediavault-emby plugin does not pull from the Emby.Releases/Server zips on github.... Just upgraded mine and it worked perfect. You need to use openmediavault-emby version 2.6 Edited January 20, 2016 by tekkb 1
tekkb 13 Posted January 20, 2016 Posted January 20, 2016 (edited) Here is the code I added to grab the latest mono version: curl -s -L https://github.com//MediaBrowser/Emby/releases/latest | grep 'Emby.Mono.zip' | head -n 1 | sed -r 's/.{21}//' | sed -r 's/.{17}$//' | wget --base=http://github.com/ -i - -O Emby.Mono.zip Which no longer is dependent on the Emby.Releases/Server, as those zips will not be used as of Feb. 1, 2016. Edited January 20, 2016 by tekkb
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now