20 replies to this topic

[SkyBod]

Emby Premier 4.2.1.0-1

Synology 1513+ 4GB RAM - DSM 6.2.2-24922 Update 3

WIndows 10

Firefox 69.03 (x64)

 

 

Emby has suddenly become unusable. I haven't used it for some weeks and apart from a DSM update nothing has changed on my system.

 

The package center shows Emby as 'Running'. Clicking the 'Open' button produces a new Firefox tab that eventually times out with the message: "The connection has timed out The server at 192.168.0.200 is taking too long to respond.".

The Windows Emby Theatre app also fails with the message "We're unable to connect to the selected server right now. Please ensure it is running and try again."

 

I have uninstalled & reinstalled it.

 

Help!

Edited by SkyBod, 19 October 2019 - 12:40 PM.

[Luke]

Hi there, can you try rebooting your NAS?

[SkyBod]

Already done - four times - since I started trying to fix this three days ago. Windows rebooted twice and also tried Chrome and IE.

[Luke]

Are you sure Emby Server is running?

[Luke]

And is any Emby Server log created under

/var/packages/EmbyServer/target/var/logs

?

[SkyBod]

drwxr-xr-x 2 embysvr users   4096 Oct 19 14:49 .
drwxr-xr-x 8 embysvr users   4096 Oct 19 14:48 ..
-rw-r--r-- 1 embysvr users    276 Oct 19 14:48 drmsetup.log
-rw-r--r-- 1 embysvr users  24748 Oct 19 14:14 embyserver-63707091352.txt
-rw-r--r-- 1 embysvr users  27226 Oct 19 14:45 embyserver-63707093306.txt
-rw-r--r-- 1 embysvr users  36522 Oct 19 21:49 embyserver.txt
-rw-r--r-- 1 embysvr users    264 Oct 19 14:48 embysvr.stderr
-rw-r--r-- 1 embysvr users  54022 Oct 19 14:49 embysvr.stdout
 

 

@FrostByte

How do I access the contents of these files?

Edited by Luke, 20 October 2019 - 02:32 AM.

[SkyBod]

The server is running. Here are several files date-stamped around the last time I started Emby from the /var/log directory.

Attached Files

•  embyserver-63707167606.txt   12.03KB   6 downloads
•  drmsetup.log   388bytes   3 downloads
•  embysvr.stderr.txt   364bytes   2 downloads
•  ESdaemon.log   6.49KB   3 downloads
•  embysvr.stdout.txt   69.87KB   2 downloads
•  hardware_detection-63707167630.txt   105.69KB   3 downloads
•  start-stop-status_20191020.log   13.5KB   2 downloads
•  embyserver.txt   22.8KB   5 downloads

[SkyBod]

I didn't spot any clues in any of the log files - but I don't really know what I should be looking for....
I do have Plex running on the same NAS server without any problems.

Edited by SkyBod, 23 October 2019 - 01:53 AM.

[SkyBod]

Anybody able to help?

[SkyBod]

Any chance of a pointer to what I might look at next?

[SkyBod]

I take it I'm on my own then?

[GiGo]

Have you tried un-installing the emby package and re-installing?  It's a ball ache but something could of corrupted.

[SkyBod]

Yes, three times. Also, I can install it on my Windows 10 machine and access Emby on my network - no problem. I want it on my Synology box though.

Edited by SkyBod, 03 November 2019 - 03:27 AM.

[SkyBod]

I'm abandoning Emby. Doesn't  work, unable to find the cause of the failure, received no support. Waste of $119.

[chacawaca]

have you check firewall on your dsm, if you have change nothing in your emby config i dont see why it would have stop working. Something have changed on your DSM .

[SkyBod]

Seriously, don't bother any more - I'm giving up on Emby. I'll continue using Plex.

[MndWrp]

Seriously, don't bother any more - I'm giving up on Emby. I'll continue using Plex.

Too bad.... However, if you ever try again, i think you have to grant read/write access to the emby user created on synology when you install the server.

Sent from my SM-G920W8 using Tapatalk

[kadorken]

Seriously, don't bother any more - I'm giving up on Emby. I'll continue using Plex.

I am trying both Emby and Plex as well (with Alexa access). I have Emby 'working' with Alexa now (after going the SSL certificate route). I remember having to grant access for the EmbySvr user to the mediafiles on the NAS before it would work.

 

When things used to work stop working, I always think of expired SSL certificates .....

 

Only issue at present it seems songs do not terminate after playing (sometimes). The dashboard shows the playtime as x.xx / x.xx (they are equal), then you get continued repeats of the song ending.

[Luke]

@SkyBod, did you see this:

https://emby.media/c...16/#entry802859

[Interwebz]

Hey,

 

Just want to add that my Emby server also got unstable after the latest DSM 6.2.2-24922-4 (worked on 6.2.2-24922-3). My Emby server crash randomly when starting a movie.  I can no longer start Emby server from Package Center either. It throws the following errors.

[2019-11-23 21:22:18 UTC] >> PID file [/var/packages/EmbyServer/target/var/esdaemon.pid] does not exist.
[2019-11-23 21:22:18 UTC] >> Emby Server is not running.
[2019-11-23 21:22:18 UTC] >> Starting Emby Server.
[2019-11-23 21:22:18 UTC] >> Waiting for daemon status to become [0].
[2019-11-23 21:22:18 UTC] >> Checking status [1/20].
[2019-11-23 21:22:18 UTC] >> Process [29059] exists.
[2019-11-23 21:22:18 UTC] >> Emby Server is running.
[2019-11-23 21:22:18 UTC] >> Target status is now [0].
[2019-11-23 21:22:26 UTC] >> Emby Server started successfully.
[2019-11-23 21:22:26 UTC] >> Exit status is [0].
[2019-11-23 21:22:27 UTC] >> Called by [/usr/syno/sbin/synopkgctlstopEmbyServer], with action [stop].

    | init,1
    |   └─sh,29273 -e /proc/self/fd/9
    |       └─synopkgctl,29275 stop EmbyServer
    |           └─start-stop-stat,29277 /var/packages/EmbyServer/scripts/start-stop-status stop

[2019-11-23 21:22:27 UTC] >> PID file [/var/packages/EmbyServer/target/var/esdaemon.pid] does not exist.
[2019-11-23 21:22:27 UTC] >> Emby Server is not running.
[2019-11-23 21:22:27 UTC] >> Stop request ignored, package is stopped!
[2019-11-23 21:22:27 UTC] >> Exit status is [0].
[2019-11-23 21:22:27 UTC] >> Called by [synoscgi_SYNO.Core.Package_2_list], with action [status].

    | init,1
    |   └─SYNO.Core.Packa,29223
    |       └─start-stop-stat,29240 /var/packages/EmbyServer/scripts/start-stop-status status

[2019-11-23 21:22:27 UTC] >> Process [29059] does not exist.
[2019-11-23 21:22:27 UTC] >> Removed PID file [/var/packages/EmbyServer/target/var/esdaemon.pid].
[2019-11-23 21:22:27 UTC] >> Ensuring package status is correct in DSM.
[2019-11-23 21:22:27 UTC] >> Emby Server is not running.
[2019-11-23 21:22:27 UTC] >> Exit status is [1].
[2019-11-23 21:22:30 UTC] >> Called by [synoscgi_SYNO.Core.Package_2_list], with action [status].

    | init,1
    |   └─SYNO.Core.Packa,29223
    |       └─start-stop-stat,29405 /var/packages/EmbyServer/scripts/start-stop-status status

[2019-11-23 21:22:30 UTC] >> PID file [/var/packages/EmbyServer/target/var/esdaemon.pid] does not exist.
[2019-11-23 21:22:30 UTC] >> Emby Server is not running.
[2019-11-23 21:22:30 UTC] >> Exit status is [3].
[2019-11-23 21:22:31 UTC] >> Called by [synoscgi_SYNO.Core.Package_2_list], with action [status].

    | init,1
    |   └─SYNO.Core.Packa,29496
    |       └─start-stop-stat,29514 /var/packages/EmbyServer/scripts/start-stop-status status

Rebooting the NAS helps for a while.  I'll see if I can see something in the logs next time it happens.