Jump to content

Server starting then stopping on Ubuntu 16.04.5 LTS


papalozarou

Recommended Posts

papalozarou

Have clean installed 3.5.2.0 after fully removing apt-get installed 3.3.x version which worked perfectly.

 

I now start the server, but it either quits after a few seconds, or quits after a few minutes:

● 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; enabled; vendor preset: enabled)   Active: active (running) since Wed 2018-08-01 15:37:07 BST; 1s ago Main PID: 10109 (EmbyServer)   CGroup: /system.slice/emby-server.service           └─10109 /opt/emby-server/system/EmbyServer -programdata /var/lib/emby -ffmpeg /opt/emby-server/bin/ffmpeg -ffprobe /opt/emby-server/bin/ffprobe -restartexitcode 3 -updatepackage emby-server-deb_{version}_amd64.deb Aug 01 15:37:08 ns352838.ip-91-121-86.eu emby-server[10109]: Info SqliteUserRepository: PRAGMA synchronous=1Aug 01 15:37:08 ns352838.ip-91-121-86.eu emby-server[10109]: Info AuthenticationRepository: Default journal_mode for /var/lib/emby/data/authentication.db is walAug 01 15:37:08 ns352838.ip-91-121-86.eu emby-server[10109]: Info AuthenticationRepository: PRAGMA synchronous=1Aug 01 15:37:08 ns352838.ip-91-121-86.eu emby-server[10109]: Info ActivityRepository: Default journal_mode for /var/lib/emby/data/activitylog.db is walAug 01 15:37:08 ns352838.ip-91-121-86.eu emby-server[10109]: Info ActivityRepository: PRAGMA synchronous=1Aug 01 15:37:08 ns352838.ip-91-121-86.eu emby-server[10109]: Info SqliteDisplayPreferencesRepository: Default journal_mode for /var/lib/emby/data/displaypreferences.db is walAug 01 15:37:08 ns352838.ip-91-121-86.eu emby-server[10109]: Info SqliteDisplayPreferencesRepository: PRAGMA synchronous=1Aug 01 15:37:08 ns352838.ip-91-121-86.eu emby-server[10109]: Info SqliteItemRepository: Default journal_mode for /var/lib/emby/data/library.db is walAug 01 15:37:08 ns352838.ip-91-121-86.eu emby-server[10109]: Info SqliteItemRepository: PRAGMA synchronous=1Aug 01 15:37:08 ns352838.ip-91-121-86.eu emby-server[10109]: Info HttpServer: Calling ServiceStack AppHost.Init
● 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; enabled; vendor preset: enabled)   Active: failed (Result: exit-code) since Wed 2018-08-01 15:37:10 BST; 7s ago  Process: 10109 ExecStart=/opt/emby-server/bin/emby-server (code=exited, status=5) Main PID: 10109 (code=exited, status=5) Aug 01 15:37:10 ns352838.ip-91-121-86.eu emby-server[10109]:    at System.IO.FileStream..ctor(String path, FileMode mode, FileAccess access, FileShare share, Int32 bufferSize, FileOptions options)Aug 01 15:37:10 ns352838.ip-91-121-86.eu emby-server[10109]:    at System.IO.StreamReader..ctor(String path, Encoding encoding, Boolean detectEncodingFromByteOrderMarks, Int32 bufferSize)Aug 01 15:37:10 ns352838.ip-91-121-86.eu emby-server[10109]:    at System.IO.File.InternalReadAllLines(String path, Encoding encoding)Aug 01 15:37:10 ns352838.ip-91-121-86.eu emby-server[10109]:    at System.IO.File.ReadAllLines(String path)Aug 01 15:37:10 ns352838.ip-91-121-86.eu emby-server[10109]:    at System.Net.NetworkInformation.StringParsingHelpers.ParseGatewayAddressesFromRouteFile(String filePath, String interfaceName)Aug 01 15:37:10 ns352838.ip-91-121-86.eu emby-server[10109]:    at System.Net.NetworkInformation.LinuxIPInterfaceProperties.GetGatewayAddresses()Aug 01 15:37:10 ns352838.ip-91-121-86.eu emby-server[10109]:    at System.Net.NetworkInformation.LinuxIPInterfaceProperties..ctor(LinuxNetworkInterface lni)Aug 01 15:37:10 ns352838.ip-91-121-86.eu systemd[1]: emby-server.service: Main process exited, code=exited, status=5/NOTINSTALLEDAug 01 15:37:10 ns352838.ip-91-121-86.eu systemd[1]: emby-server.service: Unit entered failed state. Aug 01 15:37:10 ns352838.ip-91-121-86.eu systemd[1]: emby-server.service: Failed with result 'exit-code'.
I've attached the log file as well.

embyserver.txt

Edited by papalozarou
Link to comment
Share on other sites

Yea one other user has reported this. I haven't yet figured that out, but it would appear there is some configuration on the machine that is blocking our access to that file. 

 

Unfortunately the error is happening in such a way that it can't caught and handled, and that's why the server crashes.

Link to comment
Share on other sites

mastrmind11

It's a root:root file system file, bizarre that this access violation would appear in an update.  If I have some time today I'll dig around.

Link to comment
Share on other sites

papalozarou

It's a root:root file system file, bizarre that this access violation would appear in an update.  If I have some time today I'll dig around.

 

I did a clean install after reading a few threads that suggested that i should if moving from one method of install to another.

 

Also, oddly, subsequent attempts to start the server, whilst resulting in it dying seconds later, don't have the same output in the logs – they appear to stop abruptly with no decernable error (I can't post it right now as in work and don't have server access unfortunately)

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
×
×
  • Create New...