n00b42 41 Posted November 17, 2018 Posted November 17, 2018 Emby Server does not start after update to 3.5.3.0-18 on my XPenology Setup (DSM 6.1.4) ESdaemon.log [2018-11-17 11:21:27 UTC] >> ESdaemon called by [/sbin/init]. | init,1 | └─ESdaemon,31709 /var/packages/EmbyServer/scripts/ESdaemon start [2018-11-17 11:21:27 UTC] >> Setting up signal handlers... [2018-11-17 11:21:27 UTC] >> DONE [0]. [2018-11-17 11:21:27 UTC] >> Syncing certifictes... [2018-11-17 11:21:27 UTC] << DONE [0]. [2018-11-17 11:21:27 UTC] >> Setting up DRM devices... [2018-11-17 11:21:27 UTC] - DRM devices: NONE [2018-11-17 11:21:27 UTC] << DONE [0]. [2018-11-17 11:21:27 UTC] >> Starting server... [2018-11-17 11:21:27 UTC] - Setting up stdout and stderr for server process. [2018-11-17 11:21:27 UTC] - Launch command [env PATH=/var/packages/EmbyServer/scripts/utilities/sbin:/var/packages/EmbyServer/target/mono/bin:/var/packages/EmbyServer/target/ffmpeg/bin:/var/packages/EmbyServer/target/imagemagick/bin:/var/packages/EmbyServer/target/sqlite/bin:/sbin:/bin:/usr/sbin:/usr/bin:/usr/syno/sbin:/usr/syno/bin:/usr/local/sbin:/usr/local/bin:/var/packages/Java8/target/j2sdk-image/bin:/var/packages/Java8/target/j2sdk-image/jre/bin MONO_TLS_PROVIDER=btls /var/packages/EmbyServer/target/mono/bin/mono /var/packages/EmbyServer/target/server/EmbyServer.exe -package synology -programdata /var/packages/EmbyServer/target/var -ffmpeg /var/packages/EmbyServer/target/ffmpeg/bin/ffmpeg -ffprobe /var/packages/EmbyServer/target/ffmpeg/bin/ffprobe -restartexitcode 121 1>> /var/packages/EmbyServer/target/var/logs/embysvr.stdout 2>> /var/packages/EmbyServer/target/var/logs/embysvr.stderr & embysvr_pid=$!;]. [2018-11-17 11:21:27 UTC] - Waiting on process with PID [31787]. [2018-11-17 11:21:27 UTC] - Process has exited with code [132]. [2018-11-17 11:21:27 UTC] - Abnormal shutdown detected, cannot recover automatically. [2018-11-17 11:21:27 UTC] << DONE [1]. [2018-11-17 11:21:27 UTC] >> Exit status is [1]. start-stop-status_20181117.log [2018-11-17 11:21:27 UTC] >> Called by [/usr/syno/sbin/synopkgctlstartEmbyServer], with action [start]. | init,1 | └─sh,31663 -e /proc/self/fd/9 | └─synopkgctl,31664 start EmbyServer | └─start-stop-stat,31675 /var/packages/EmbyServer/scripts/start-stop-status start [2018-11-17 11:21:27 UTC] >> PID file [/var/packages/EmbyServer/target/var/esdaemon.pid] does not exist. [2018-11-17 11:21:27 UTC] >> Emby Server is not running. [2018-11-17 11:21:27 UTC] >> Starting Emby Server. [2018-11-17 11:21:27 UTC] >> Waiting for daemon status to become [0]. [2018-11-17 11:21:27 UTC] >> Checking status [1/20]. [2018-11-17 11:21:27 UTC] >> Process [31709] exists. [2018-11-17 11:21:27 UTC] >> Emby Server is running. [2018-11-17 11:21:27 UTC] >> Target status is now [0]. [2018-11-17 11:21:35 UTC] >> Emby Server started successfully. [2018-11-17 11:21:35 UTC] >> Exit status is [0]. [2018-11-17 11:21:35 UTC] >> Called by [/usr/syno/sbin/synopkgctlstopEmbyServer], with action [stop]. | init,1 | └─sh,32042 -e /proc/self/fd/9 | └─synopkgctl,32044 stop EmbyServer | └─start-stop-stat,32051 /var/packages/EmbyServer/scripts/start-stop-status stop [2018-11-17 11:21:36 UTC] >> PID file [/var/packages/EmbyServer/target/var/esdaemon.pid] does not exist. [2018-11-17 11:21:36 UTC] >> Emby Server is not running. [2018-11-17 11:21:36 UTC] >> Stop request ignored, package is stopped! [2018-11-17 11:21:36 UTC] >> Exit status is [0]. [2018-11-17 11:21:35 UTC] >> Called by [synoscgi_SYNO.Core.Package_1_list], with action [status]. | init,1 | └─synoscgi_______,10332 | └─SYNO.Core.Packa,31899 | └─start-stop-stat,32010 /var/packages/EmbyServer/scripts/start-stop-status status [2018-11-17 11:21:35 UTC] >> Process [31709] does not exist. [2018-11-17 11:21:35 UTC] >> Removed PID file [/var/packages/EmbyServer/target/var/esdaemon.pid]. [2018-11-17 11:21:36 UTC] >> Ensuring package status is correct in DSM. [2018-11-17 11:21:36 UTC] >> Emby Server is not running. [2018-11-17 11:21:36 UTC] >> Exit status is [1]. [2018-11-17 11:21:36 UTC] >> Called by [synoscgi_SYNO.Core.Package_1_list], with action [log]. | init,1 | └─synoscgi_______,10332 | └─SYNO.Core.Packa,31899 | └─start-stop-stat,32103 /var/packages/EmbyServer/scripts/start-stop-status log [2018-11-17 11:21:36 UTC] >> Returning log file location [/var/packages/EmbyServer/target/var/logs/start-stop-status_20181117.log]. [2018-11-17 11:21:36 UTC] >> Exit status is [0]. [2018-11-17 11:21:36 UTC] >> Called by [synoscgi_SYNO.Core.Package.Server_1_list], with action [status]. | init,1 | └─synoscgi_______,10332 | └─SYNO.Core.Packa,32049 | └─start-stop-stat,32136 /var/packages/EmbyServer/scripts/start-stop-status status [2018-11-17 11:21:36 UTC] >> PID file [/var/packages/EmbyServer/target/var/esdaemon.pid] does not exist. [2018-11-17 11:21:36 UTC] >> Emby Server is not running. [2018-11-17 11:21:36 UTC] >> Exit status is [3].
solabc16 379 Posted November 17, 2018 Posted November 17, 2018 Hello @@n00b42 Please can you run the send logs utility: https://github.com/MediaBrowser/Wiki/wiki/Synology-:-How-to-Send-us-Support-Logs Best -James
n00b42 41 Posted November 17, 2018 Author Posted November 17, 2018 done. sendlogs_BigAssStorage_synology_bromolow_3615xs_20181117T225210UTC.tgz
solabc16 379 Posted November 17, 2018 Posted November 17, 2018 Hello @@n00b42 Thanks for the logs, can you run the diagnostics as well and then the send logs again. Diags : https://github.com/MediaBrowser/Wiki/wiki/Synology-:-How-to-Run-Diagnostics Thanks - James
BobXU 0 Posted November 18, 2018 Posted November 18, 2018 sendlogs_BobXU_NAS_synology_bromolow_3615xs_20181118T005352UTC.tgz
solabc16 379 Posted November 18, 2018 Posted November 18, 2018 Thanks @@BobXU, also an XPEnology system? Best - James
BobXU 0 Posted November 18, 2018 Posted November 18, 2018 Thanks @@BobXU, also an XPEnology system? Best - James yes ，DSM 6.1.4
BobXU 0 Posted November 18, 2018 Posted November 18, 2018 (edited) Thanks @@BobXU, also an XPEnology system? Best - James * I've got all the data in the logs, thanks - so will remove it from cluttering up the thread. Edited November 18, 2018 by solabc16
solabc16 379 Posted November 18, 2018 Posted November 18, 2018 @@BobXU - can you run the 'send logs' after running the 'diags'. Thanks -James
BobXU 0 Posted November 18, 2018 Posted November 18, 2018 @@BobXU - can you run the 'send logs' after running the 'diags'. Thanks -James done，sendlogs_BobXU_NAS_synology_bromolow_3615xs_20181118T011313UTC.tgz
BobXU 0 Posted November 18, 2018 Posted November 18, 2018 @@BobXU - can you run the 'send logs' after running the 'diags'. Thanks -James Again，sendlogs_BobXU_NAS_synology_bromolow_3615xs_20181118T011545UTC.tgz
n00b42 41 Posted November 18, 2018 Author Posted November 18, 2018 rundiags, then sendlogs sendlogs_BigAssStorage_synology_bromolow_3615xs_20181118T014549UTC.tgz
l0fL 0 Posted November 18, 2018 Posted November 18, 2018 (edited) @@solabc16 I've the same issue. I also use xpenology on 6.1.7 with Jun's mod 1.02. sendlogs before rundiags: sendlogs_NAS_synology_bromolow_3615xs_20181118T103930UTC.tgz sendlogs after rundiags: sendlogs_NAS_synology_bromolow_3615xs_20181118T104502UTC.tgz Thank you! Edited November 19, 2018 by l0fL
solabc16 379 Posted November 19, 2018 Posted November 19, 2018 Hello All I believe we've got to the bottom of the issue, I've just published an update for the default XPEnology package (3.5.3.0-19), others will follow shortly. Once you've updated, let us know how you get on and either way, appreciate if you can run the 'send logs' utility again. Best - James
l0fL 0 Posted November 19, 2018 Posted November 19, 2018 (edited) Hello solabcd16,the update doesn‘t work for me. I will submit the logs later.Thank you! Edit: @@solabc16 here are the logs after rundiags. sendlogs_NAS_synology_bromolow_3615xs_20181119T150803UTC.tgz Edited November 19, 2018 by l0fL
n00b42 41 Posted November 19, 2018 Author Posted November 19, 2018 I am currently on the default XPEnology package, version "3.5.3.0-18", but the package manager shows "3.5.2.0-1" as newest version and so I cant update to the new one.
solabc16 379 Posted November 19, 2018 Posted November 19, 2018 Thanks for the logs @@l0fL, is your XPEnology system a bare metal installation or are you running it as a virtual machine? @@n00b42, I pulled the 3.5.3.0-19 update as it appears there are still problems with some CPUs. Best - James
l0fL 0 Posted November 19, 2018 Posted November 19, 2018 @@solabc16 It‘s a baremetal on a Intel G5600.
solabc16 379 Posted November 19, 2018 Posted November 19, 2018 Hello OK, thanks for the info - the system is being identified as an Intel G4620, but that's more than close enough to a G5600. The default XPEnology package targets the 'nehalem' architecture. The failures on your system are unexpected, as the G5600 has a superset of the features supported by 'nehalem' based CPUs. Will update again later... Best - James 1
mr_curator 0 Posted November 19, 2018 Posted November 19, 2018 Hello On my processo Intel Xeon CPU X3430 2.4 ghzr, the system also does not start after update 3.5.3.0-18-19 Thanks.
solabc16 379 Posted November 19, 2018 Posted November 19, 2018 Hello All An updated default package for XPEnology (3.5.3.0-20) is now available, please let me know how you get on. https://github.com/MediaBrowser/Wiki/wiki/Synology-:-How-to-Run-Diagnostics https://github.com/MediaBrowser/Wiki/wiki/Synology-:-How-to-Send-us-Support-Logs Either way, diagnostics followed by send logs appreciated. Best - James
l0fL 0 Posted November 19, 2018 Posted November 19, 2018 @@solabc16 Now it works for me! But yes you are right it‘s a G4620 not a G5600. When I am at my pc i will do a sendlog, but not today. Thank you for your effort! Best wishes
mr_curator 0 Posted November 19, 2018 Posted November 19, 2018 my system started, but then it stopped.
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