Jump to content

Emby 4.0.3.0-1 Randomly Stops Responding, Must Restart Package

tiorsus

By tiorsus
in Synology

 Share

Recommended Posts

tiorsus

tiorsus   4

Posted
Posted

I've got Emby 4.0.3.0-1 setup on a Synology NAS (DS918+, running DSM 6.2.1-23824 update 6).  I access Emby over SSL via a domain name.

 

Everything is setup & working - however, on multiple occasions now, Emby was randomly unreachable - accessing its URL appears as though it simply isn't running.  I checked in DSM and the package was still running.  Stopping and starting it brought it back up (after a long - i.e. 10min+ - show of "Emby Server is upgrading your database. Please try again in a minute or two").

 

What would cause Emby to randomly stop working and need to be restarted?  While I (the admin of the NAS) am able to login to stop and restart it, the other users are not.

Link to comment
Share on other sites
tiorsus

tiorsus   4

Posted
  • Author
Posted

Alright, it happened - albeit in a slightly different way than before:

 

14:14: I restarted the NAS (for reasons unrelated to Emby).  Very shortly after it came back up, I tried to use Emby but it was unreachable (i.e. as if the package wasn't running).  I verified in the Synology package manager that it was indeed running.  I waited >15 minutes but it never became reachable.

 

14:40 or so: I stopped & restarted the Emby package.  Soon after I restarted it the Emby URL was again reachable, with the familiar "Emby Server is upgrading your database. Please try again in a minute or two."  I kept refreshing the page every minute or two for over twenty minutes, during which the message remained the same, until finally:

 

15:03: Emby came back up & was at last working normally.

 

I'll PM you two logs: from the system reboot to the package stop/restart (14:14-14:40), & from the package restart until when it began working normally again (14:41-15:03).

Link to comment
Share on other sites
Luke Emby Team

Luke   37178

Posted
Posted

Can you try turning off the realtime monitor for each of your emby libraries and see if that helps? thanks.

Link to comment
Share on other sites
tiorsus

tiorsus   4

Posted
  • Author
Posted

It actually appears as though Emby is unworking *every* time I reboot the NAS, & I think I might have just had a guess as to why.  My libraries point to files that are on encrypted folders, which aren't unlocked when the NAS first boots up (until I login to enter the encryption keys).  Is it possible this causes the Emby server to die, rather than i.e. start but the 'encrypted' libraries simply remain unavailable until unlocked?

Link to comment
Share on other sites
Luke Emby Team

Luke   37178

Posted
Posted

I wouldn't think so, but I would imagine you could test that theory by leaving them unlocked. Have you updated to the new 4.1 release?

Link to comment
Share on other sites
Luke Emby Team

Luke   37178

Posted
Posted

Ok, if you can find a way to try those things, that would be helpful information. Thanks.

Link to comment
Share on other sites
tiorsus

tiorsus   4

Posted
  • Author
Posted

If by "try those things" you mean update: done and tested.  Same issue.

 

If you mean "leaving them unlocked," they are always locked at startup.  Having them be unlocked on boot is not possible (that's the point of the encryption - data is protected until you enter the encryption key, and you can't enter the key until it's booted).

Link to comment
Share on other sites
tiorsus

tiorsus   4

Posted
  • Author
Posted

I am now completely unable to start Emby.

 

To workaround the previously-mentioned bug, after each reboot of the NAS & after mounting the encrypted folders, I would manually go into Package Manager and stop/start the package, which would get Emby going again.  However, after rebooting this morning, suddenly Emby will not start.  It had been working prior to the reboot, & no configuration has been changed.  Whenever I click "Run" in the Package Center, it briefly shows "Starting..." then just returns to "Stopped."  I tried updating again to the latest 4.1.1.0-1, but behavior is the same.  I tried rebooting an additional time, but behavior is the same.  I found Emby's logs in /volume1/@appstore/EmbyServer/var/logs/embyserver.txt; it doesn't show anything that looks like a crash:

2019-05-03 11:23:07.926 Info App: Loading Emby.Notifications, Version=4.1.1.0, Culture=neutral, PublicKeyToken=null
2019-05-03 11:23:07.926 Info App: Loading Emby.Codecs.Dxva, Version=4.1.1.0, Culture=neutral, PublicKeyToken=null
2019-05-03 11:23:07.926 Info App: Loading Emby.Codecs, Version=4.1.1.0, Culture=neutral, PublicKeyToken=null
2019-05-03 11:23:07.926 Info App: Loading Emby.Server.Connect, Version=4.1.1.0, Culture=neutral, PublicKeyToken=null
2019-05-03 11:23:07.926 Info App: Loading Emby.Server.Sync, Version=4.1.1.0, Culture=neutral, PublicKeyToken=null
2019-05-03 11:23:07.926 Info App: Loading EmbyServer, Version=4.1.1.0, Culture=neutral, PublicKeyToken=null
2019-05-03 11:23:08.807 Info SqliteUserRepository: Sqlite version: 3.28.0
2019-05-03 11:23:08.812 Info SqliteUserRepository: Sqlite compiler options: COMPILER=gcc-7.3.0,ENABLE_FTS4,ENABLE_FTS5,ENABLE_JSON1,ENABLE_RTREE,THREADSAFE=1
2019-05-03 11:23:10.349 Info SqliteUserRepository: Default journal_mode for /var/packages/EmbyServer/target/var/data/users.db is wal
2019-05-03 11:23:10.360 Info SqliteUserRepository: PRAGMA synchronous=1
2019-05-03 11:23:11.902 Info AuthenticationRepository: Default journal_mode for /var/packages/EmbyServer/target/var/data/authentication.db is wal
2019-05-03 11:23:11.902 Info AuthenticationRepository: PRAGMA synchronous=1
2019-05-03 11:23:12.231 Info ActivityRepository: Default journal_mode for /var/packages/EmbyServer/target/var/data/activitylog.db is wal
2019-05-03 11:23:12.231 Info ActivityRepository: PRAGMA synchronous=1
2019-05-03 11:23:12.300 Info SqliteDisplayPreferencesRepository: Default journal_mode for /var/packages/EmbyServer/target/var/data/displaypreferences.db is wal
2019-05-03 11:23:12.300 Info SqliteDisplayPreferencesRepository: PRAGMA synchronous=1
2019-05-03 11:23:12.375 Info HttpServer: Adding HttpListener prefix http://+:8096/
2019-05-03 11:23:12.377 Info HttpServer: Adding HttpListener prefix https://+:8920/
2019-05-03 11:23:14.704 Info SqliteItemRepository: Default journal_mode for /var/packages/EmbyServer/target/var/data/library.db is wal
2019-05-03 11:23:14.705 Info SqliteItemRepository: PRAGMA synchronous=1

That's where it ends.  Why would Emby now be failing to start at all?

Link to comment
Share on other sites
Luke Emby Team

Luke   37178

Posted
Posted

Is it possibly having difficulty with the encrypted folders?

Link to comment
Share on other sites
tiorsus

tiorsus   4

Posted
  • Author
Posted (edited)

Not sure how to answer that - how would I know? It's been working with them until this last reboot, per above.

Edited by metal450
Link to comment
Share on other sites
tiorsus

tiorsus   4

Posted
  • Author
Posted

Yep - I tried rebooting an extra time & the package wouldn't start.  Left it stopped all night, woke up this morning (again not having changed anything) & tried to start the package - now it mysteriously starts again.

 

For what it's worth, I'd been using Emby on a previous QNap NAS for over a year with virtually no issues.  Since setting it up on this new Synology though (same library content & same settings), it's been extremely buggy/problematic.  I'm not sure if it's an issue with the platform itself, the fact that it's a newer build of Emby, or something else - but I do have a bunch of other packages running on this NAS & only Emby seems to be having such endless problems :/

Link to comment
Share on other sites

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 account

Sign in

Already have an account? Sign in here.

Sign In Now
 Share
Go to topic listing
×
×
  • Create New...