j0nezy 0 Posted January 13, 2016 Posted January 13, 2016 Hi, Been having issues with emby these past couple of days. It was working fine under the old mediabrowser version, but something's gone wrong recently. I've uninstalled, upgraded, reinstalled, purged and done all that I can think of, but nothing is sorting it. Running Ubuntu 14.04, Emby installs fine, and the service runs fine. However, trying to access the panel via http://{IP}:8096, I just get "This web page is not available" or "Connection refused". I can continually hit refresh and it *may* load something, but I don't get much further. I have got as far as going part way through the wizard before it dies again. Checking /var/log/emby-server.log I've found this : Running startup tasks Info, App, Core startup complete Info, SsdpHandler, MultiCast socket created (gnome-open:2581): GConf-WARNING **: Client failed to connect to the D-BUS daemon: Unable to autolaunch a dbus-daemon without a $DISPLAY for X11 GConf Error: No D-BUS daemon running Error showing url: Operation not supported Cannot handle address family 49920 Stacktrace: at <unknown> <0xffffffff> at (wrapper managed-to-native) System.Net.Dns.GetHostByName_internal (string,string&,string[]&,string[]&) <0xffffffff> at System.Net.Dns.GetHostByName (string) <0x00047> at System.Net.ServicePoint.get_HostEntry () <0x00203> at System.Net.WebConnection.Connect (System.Net.HttpWebRequest) <0x001ab> at System.Net.WebConnection.InitConnection (object) <0x00293> at System.Net.WebConnection.<WebConnection>m__0 (object) <0x0001f> at System.Threading.QueueUserWorkItemCallback.WaitCallback_Context (object) <0x00048> at System.Threading.ExecutionContext.RunInternal (System.Threading.ExecutionContext,System.Threading.ContextCallback,object,bool) <0x0016e> at System.Threading.ExecutionContext.Run (System.Threading.ExecutionContext,System.Threading.ContextCallback,object,bool) <0x00020> at System.Threading.QueueUserWorkItemCallback.System.Threading.IThreadPoolWorkItem.ExecuteWorkItem () <0x00053> at System.Threading.ThreadPoolWorkQueue.Dispatch () <0x001d6> at System.Threading._ThreadPoolWaitCallback.PerformWaitCallback () <0x00008> at (wrapper runtime-invoke) <Module>.runtime_invoke_bool (object,intptr,intptr,intptr) <0xffffffff> Native stacktrace: /usr/bin/mono-sgen() [0x4a1df8] /lib/x86_64-linux-gnu/libpthread.so.0(+0x10340) [0x7fe4dbe49340] /lib/x86_64-linux-gnu/libc.so.6(gsignal+0x39) [0x7fe4dbaaacc9] /lib/x86_64-linux-gnu/libc.so.6(abort+0x148) [0x7fe4dbaae0d8] /usr/bin/mono-sgen() [0x62bdc9] /usr/bin/mono-sgen() [0x62bfcf] /usr/bin/mono-sgen() [0x62c072] /usr/bin/mono-sgen() [0x626f15] /usr/bin/mono-sgen() [0x57a916] [0x4136b097] Debug info from gdb: ================================================================= Got a SIGABRT while executing native code. This usually indicates a fatal error in the mono runtime or one of the native libraries used by your application. ================================================================= tail: /var/log/emby-server.log: file truncated Info, Main, EmbyThis repeats ad-infinitum so it seems emby is starting then crashing out at the above point, then restarting. In the main Ubuntu thread there was a suggestion that it could be related to mono, and I think this confirms it. I've purged all packages prefixed with mono- (using apt-get), then added the official mono repository and installed mono-complete, then installed emby-server. It still keeps quitting and restarting, and I cannot access via http://{IP}:8096 Anyone have any ideas? I've exhausted everything I can think of. Wiping the server and starting again is becoming a possibility (A long one, there are some other things running on there which are going to be a pain to reinstall and get up and running again so I'd like to avoid that avenue if possible). Thanks,
hurricanehrndz 149 Posted January 13, 2016 Posted January 13, 2016 Please run the following commands: uname -a netstat -an | grep 8920
Luke 42077 Posted January 13, 2016 Posted January 13, 2016 can you also please provide the complete log file? thanks.
j0nezy 0 Posted January 14, 2016 Author Posted January 14, 2016 (edited) uname -a produces Linux Ubuntu-1404-trusty-64-minimal 3.13.0-46-generic #79-Ubuntu SMP Tue Mar 10 20:06:50 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux and netstat -an | grep 8920 at first produced no output, then I re-ran it and it produced this tcp 0 0 0.0.0.0:8920 0.0.0.0:* LISTEN Attached is a copy of /var/log/emby-server.logemby-server.log.txt Thanks Edited January 14, 2016 by j0nezy
j0nezy 0 Posted January 14, 2016 Author Posted January 14, 2016 Nvermind. Crisis averted. I completely wiped the server. Fresh install of Ubuntu 15.10 and fresh download of Emby and it's working.
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