Jump to content

Recommended Posts

Posted

I was running version 3.5.3.0 on my headless Ubuntu server. Uninstalled it, and installed version 4.3.1.0, and I get no web GUI, htop shows no emby running.

'service emby-server status' gives me this:

 

   Loaded: loaded (/usr/lib/systemd/system/emby-server.service; enabled; vendor preset: enabled)
   Active: failed (Result: core-dump) since Mon 2020-02-24 22:11:50 PST; 5min ago
  Process: 18191 ExecStart=/opt/emby-server/bin/emby-server (code=dumped, signal=ABRT)
 Main PID: 18191 (code=dumped, signal=ABRT)
 
Feb 24 22:11:50 server emby-server[18191]:    at Microsoft.Win32.SafeHandles.SafeFileHandle.Open(String path, OpenFlags flags, Int32 mode)
Feb 24 22:11:50 server emby-server[18191]:    at System.IO.FileStream..ctor(String path, FileMode mode, FileAccess access, FileShare share, Int32 bufferSize, FileOpt
Feb 24 22:11:50 server emby-server[18191]:    at System.IO.FileStream..ctor(String path, FileMode mode, FileAccess access, FileShare share, Int32 bufferSize)
Feb 24 22:11:50 server emby-server[18191]:    at Emby.Server.Implementations.Logging.FileLogger..ctor(String path)
Feb 24 22:11:50 server emby-server[18191]:    at Emby.Server.Implementations.Logging.SimpleLogManager.ReloadLogger(LogSeverity severity, CancellationToken cancellati
Feb 24 22:11:50 server emby-server[18191]:    --- End of inner exception stack trace ---
Feb 24 22:11:50 server emby-server[18191]:    at System.Threading.Tasks.Task.WaitAllCore(Task[] tasks, Int32 millisecondsTimeout, CancellationToken cancellationToken
Feb 24 22:11:50 server emby-server[18191]:    at EmbyServer.Program.Main(String[] args)
Feb 24 22:11:50 server systemd[1]: emby-server.service: Main process exited, code=dumped, status=6/ABRT
Feb 24 22:11:50 server systemd[1]: emby-server.service: Failed with result 'core-dump'.
 
There are no log files in /var/lib/emby-server/logs
If I reinstall the older version, it runs fine again, (but my TV doesn't like the old version.) Where do I go from here?
Posted

Hi, that looks like the server doesn't have write access to it's own data folder. Was there already a system user in your OS called emby?

Posted

I believe so, from the older version.

Just uninstalled, deleted the user 'emby', and reinstalled the latest version. Still the same status output.

Posted

As a test can you try once running as root? I just want to know if that allows it to start. thanks.

Posted

Thanks for the feedback.

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...