Jump to content

-WARNING **: Client failed to connect to the D-BUS daemon:


mayk

Recommended Posts

Hello group,

 

i'm new, so let me say hi.. HI !! .. Everyone has got to start somewhere, so let me start here..

 

As a newbie to emby ,  i can't get it to work.. unfortunately..  I've spend the last days searching the fora, but to no avail.

 

Perhaps someone can point me in the correct direction, then i can learn for where i f*cked up..

 

I followed the instruction ( fairly easy ) for ubuntu 14.04 ..

 

When i start emby, it borked on me.  Let me first state what i have done so far, and finish with the log dump. Hope someone can point me in the right way.

 

- After broking, i reinstalled again..

- upgraded my 14.04 install to the lates packages and kernel.

- tried installing libdbus-1-dev

- changed emby user to root

 

I think it's related to the dbus error, but i'm not sure.. never used mono before..... Hope someone can help , as i'm looking for an alternative to plex.  Thanx !

 

Greets

Mayk

 

 

 

logdump :

 

Info, HttpServer, attempting to load pfx: /var/lib/emby-server/ssl/cert_9c31b7884ea5475c8687970fc5996297.pfx
Info, HttpServer, Adding HttpListener prefix http://+:8096/
Info, HttpServer, Adding HttpListener prefix https://+:8920/
Running startup tasks
Info, App, Core startup complete

(gnome-open:5190): 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
Info, SsdpHandler, MultiCast socket created
Cannot handle address family 49840
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 () <0x001fb>
  at System.Net.WebConnection.Connect (System.Net.HttpWebRequest) <0x001ab>
  at System.Net.WebConnection.InitConnection (object) <0x002fb>
  at System.Net.WebConnection.<WebConnection>m__0 (object) <0x0001f>
  at (wrapper runtime-invoke) <Module>.runtime_invoke_void__this___object (object,intptr,intptr,intptr) <0xffffffff>

Native stacktrace:

    /usr/bin/mono-sgen() [0x4b84a8]
    /lib/x86_64-linux-gnu/libpthread.so.0(+0x10340) [0x7f75d7601340]
    /lib/x86_64-linux-gnu/libc.so.6(gsignal+0x39) [0x7f75d7262cc9]
    /lib/x86_64-linux-gnu/libc.so.6(abort+0x148) [0x7f75d72660d8]
    /usr/bin/mono-sgen() [0x62d599]
    /usr/bin/mono-sgen() [0x62d79f]
    /usr/bin/mono-sgen() [0x62d842]
    /usr/bin/mono-sgen() [0x629015]
    /usr/bin/mono-sgen() [0x57ecae]
    [0x4042e277]

Debug info from gdb:
 

Link to comment
Share on other sites

thefirstofthe300

That seems to be a mono internal error.  I highly doubt that the dbus daemon error has anything to do with the error as I believe that error only happens when you don't have a monitor attached to your device.  If you are like me, you run a headless server.

 

The error seems to be related to not being able to open a url.  What mono version (mono -V) are you running?  And what kernel (uname -a)?  It could be that your kernel isn't actually new enough as there are a series of kernels that broke Mono for a while  You may or may not have one of those kernels.

Link to comment
Share on other sites

  • 4 weeks later...
jstruebel

I'm having a nearly identical error trying to open a url when starting Emby. I have it running on a debian 7 server and was trying to install it on a debian 8 server. My mono version on both servers is:

Mono JIT compiler version 4.0.3 (Stable 4.0.3.20/d6946b4 Wed Aug 19 11:56:04 UTC 2015)

The debian 7 server output of uname -a is:

Linux fs02 3.2.0-4-686-pae #1 SMP Debian 3.2.68-1+deb7u2 i686 GNU/Linux

and the debian 8 server output of uname -a is:

Linux mediaserver 3.16.0-4-amd64 #1 SMP Debian 3.16.7-ckt11-1+deb8u6 (2015-11-09) x86_64 GNU/Linux

What versions of the Linux kernel and mono were/are incompatible? It was working with an earlier version of Emby on debian 8, but unfortunately I don't remember what versions of either since I just updated both in the last couple of days.

 

For reference my log dump of the error is:

Error showing url: Operation not supported
Info, SsdpHandler, MultiCast socket created
Info, App, HttpClientManager GET: http://www.mb3admin.com/admin/service/MB3ServerNotifications.json
Cannot handle address family 17216
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 () <0x001fb>
  at System.Net.WebConnection.Connect (System.Net.HttpWebRequest) <0x001ab>
  at System.Net.WebConnection.InitConnection (object) <0x002fb>
  at System.Net.WebConnection.<WebConnection>m__0 (object) <0x0001f>
  at (wrapper runtime-invoke) <Module>.runtime_invoke_void__this___object (object,intptr,intptr,intptr) <0xffffffff>


Native stacktrace:


        /usr/bin/mono-sgen() [0x4b7d10]
        /lib/x86_64-linux-gnu/libpthread.so.0(+0xf8d0) [0x7f24dcf9c8d0]
        /lib/x86_64-linux-gnu/libc.so.6(gsignal+0x37) [0x7f24dcc19107]
        /lib/x86_64-linux-gnu/libc.so.6(abort+0x148) [0x7f24dcc1a4e8]
        /usr/bin/mono-sgen() [0x636b29]
        /usr/bin/mono-sgen() [0x636d9c]
        /usr/bin/mono-sgen() [0x636e6f]
        /usr/bin/mono-sgen() [0x6323ed]
        /usr/bin/mono-sgen() [0x582f57]
        [0x41004967]


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.
=================================================================
Link to comment
Share on other sites

Hi, what is your actual problem? I ask because the above code is non-essential and the server will recover from it's failure. Thanks.

Link to comment
Share on other sites

hurricanehrndz

 

I'm having a nearly identical error trying to open a url when starting Emby. I have it running on a debian 7 server and was trying to install it on a debian 8 server. My mono version on both servers is:

Mono JIT compiler version 4.0.3 (Stable 4.0.3.20/d6946b4 Wed Aug 19 11:56:04 UTC 2015)

The debian 7 server output of uname -a is:

Linux fs02 3.2.0-4-686-pae #1 SMP Debian 3.2.68-1+deb7u2 i686 GNU/Linux

and the debian 8 server output of uname -a is:

Linux mediaserver 3.16.0-4-amd64 #1 SMP Debian 3.16.7-ckt11-1+deb8u6 (2015-11-09) x86_64 GNU/Linux

What versions of the Linux kernel and mono were/are incompatible? It was working with an earlier version of Emby on debian 8, but unfortunately I don't remember what versions of either since I just updated both in the last couple of days.

 

For reference my log dump of the error is:

Error showing url: Operation not supported
Info, SsdpHandler, MultiCast socket created
Info, App, HttpClientManager GET: http://www.mb3admin.com/admin/service/MB3ServerNotifications.json
Cannot handle address family 17216
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 () <0x001fb>
  at System.Net.WebConnection.Connect (System.Net.HttpWebRequest) <0x001ab>
  at System.Net.WebConnection.InitConnection (object) <0x002fb>
  at System.Net.WebConnection.<WebConnection>m__0 (object) <0x0001f>
  at (wrapper runtime-invoke) <Module>.runtime_invoke_void__this___object (object,intptr,intptr,intptr) <0xffffffff>


Native stacktrace:


        /usr/bin/mono-sgen() [0x4b7d10]
        /lib/x86_64-linux-gnu/libpthread.so.0(+0xf8d0) [0x7f24dcf9c8d0]
        /lib/x86_64-linux-gnu/libc.so.6(gsignal+0x37) [0x7f24dcc19107]
        /lib/x86_64-linux-gnu/libc.so.6(abort+0x148) [0x7f24dcc1a4e8]
        /usr/bin/mono-sgen() [0x636b29]
        /usr/bin/mono-sgen() [0x636d9c]
        /usr/bin/mono-sgen() [0x636e6f]
        /usr/bin/mono-sgen() [0x6323ed]
        /usr/bin/mono-sgen() [0x582f57]
        [0x41004967]


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

 

There is definitely an error with version 3.16 if I remember correctly. I believe the issue got addressed in version 4.0.

Edited by hurricanehrndz
Link to comment
Share on other sites

jstruebel

So far whenever I try to start Emby, either via reboot or manually with the /etc/init.d/emby-server script, it runs for a couple of minutes and then exits. The error above is from the /var/log/emby-server.log. I went back and double-checked the logs in /var/lib/emby-server/logs and other than a few warnings about ffmpeg missing h254_qsv, mpeg2_qsv, and vc1_qsv decoders there aren't any errors and it looks like it started ok.

 

Any ideas or places to look to find out why it is shutting down on me?

Link to comment
Share on other sites

jstruebel

Some more info. I'm poking around in my system logs and in daemon.log I found the following messages:

 

Nov 27 03:44:31 mediaserver systemd[1]: Starting Emby Media Server...
Nov 27 03:44:31 mediaserver systemd[1]: Started Emby Media Server.
Nov 27 03:44:56 mediaserver systemd[1]: emby-server.service: main process exited, code=exited, status=134/n/a
Nov 27 03:44:56 mediaserver systemd[1]: Unit emby-server.service entered failed state.
 
And in auth.log I have the following messages:
 
Nov 27 03:44:31 mediaserver su[2412]: Successful su for emby by root
Nov 27 03:44:31 mediaserver su[2412]: + ??? root:emby
Nov 27 03:44:31 mediaserver su[2412]: pam_unix(su:session): session opened for user emby by (uid=0)
Nov 27 03:44:56 mediaserver su[2412]: pam_unix(su:session): session closed for user emby
 
--EDIT
 
Since I'm new to the SystemD process, I finally found that I should run systemctl status emby-server.service. The output of that shows:
 
* emby-server.service - Emby Media Server
   Loaded: loaded (/lib/systemd/system/emby-server.service; disabled)
   Active: failed (Result: exit-code) since Fri 2015-11-27 04:09:20 UTC; 4min 16s ago
  Process: 3040 ExecStopPost=/usr/lib/emby-server/emby-server.sh clear (code=exited, status=0/SUCCESS)
  Process: 2977 ExecStart=/usr/lib/emby-server/emby-server.sh start (code=exited, status=134)
 Main PID: 2977 (code=exited, status=134)
 
So it looks like emby is exiting with a status code of 134. What does that mean?
Edited by jstruebel
Link to comment
Share on other sites

hurricanehrndz

Hmm, seems familiar to this: https://github.com/sjdirect/abot/issues/72

 

Do me a favor and upgrade your mono version using the official repo, you can find instructions here:

http://www.mono-project.com/

 

Also, it might be worth running a dig on mb3admin.com, please let us know what you get back.

Edited by hurricanehrndz
Link to comment
Share on other sites

jstruebel

That problem does look almost the same. I upgraded to the latest mono stable release, "Mono JIT compiler version 4.2.1 (Stable 4.2.1.102/6dd2d0d Thu Nov 12 09:52:44 UTC 2015)", but I still get the same results, Emby runs for ~30sec and then exits with status 134 as reported by systemctl (at least I'm assuming that is a status code from Emby).

 

I don't have dig installed on that server at the moment, but I ran "host mb3admin.com" and got the following response. I think that means that DNS is accessible and resolving properly on the machine. If you need any output specific to dig, let me know and I can install it and report back its output.

 

mb3admin.com has address 104.28.22.116
mb3admin.com has address 104.28.23.116
mb3admin.com has IPv6 address 2600:3c02::f03c:91ff:fe6e:540
mb3admin.com mail is handled by 10 dc-65d87fa7.mb3admin.com.
 
I did notice while poking around on the mono-project website that the debian 8 Jessie version of mono is older, v3.2.8, and in the github link it was working on an older version. Should I try reverting back to the debian official version of mono or will it break other parts of Emby?
 
Thank you for you help and suggestions, I greatly appreciate your efforts.
 
One other question, has someone gotten Emby up and running on a debian 8 system? I'm trying to get this installed on a Turnkey Linux system which only installs the minimum packages necessary to run the server, in my case their filserver Samba appliance. I installed all of the dependencies required by the package when I ran apt-get, but possibly there is one that is present in a typical install that got missed in the requirements? I'm also questioning if it's something with the systemd since that is new for debian 8, but if someone else has it running then that tends to rule out systemd in a general sense at least. Just throwing that out there in case it helps us find the root cause.
Link to comment
Share on other sites

hurricanehrndz

 

That problem does look almost the same. I upgraded to the latest mono stable release, "Mono JIT compiler version 4.2.1 (Stable 4.2.1.102/6dd2d0d Thu Nov 12 09:52:44 UTC 2015)", but I still get the same results, Emby runs for ~30sec and then exits with status 134 as reported by systemctl (at least I'm assuming that is a status code from Emby).

 

I don't have dig installed on that server at the moment, but I ran "host mb3admin.com" and got the following response. I think that means that DNS is accessible and resolving properly on the machine. If you need any output specific to dig, let me know and I can install it and report back its output.

 

mb3admin.com has address 104.28.22.116
mb3admin.com has address 104.28.23.116
mb3admin.com has IPv6 address 2600:3c02::f03c:91ff:fe6e:540
mb3admin.com mail is handled by 10 dc-65d87fa7.mb3admin.com.
 
I did notice while poking around on the mono-project website that the debian 8 Jessie version of mono is older, v3.2.8, and in the github link it was working on an older version. Should I try reverting back to the debian official version of mono or will it break other parts of Emby?
 
Thank you for you help and suggestions, I greatly appreciate your efforts.
 
One other question, has someone gotten Emby up and running on a debian 8 system? I'm trying to get this installed on a Turnkey Linux system which only installs the minimum packages necessary to run the server, in my case their filserver Samba appliance. I installed all of the dependencies required by the package when I ran apt-get, but possibly there is one that is present in a typical install that got missed in the requirements? I'm also questioning if it's something with the systemd since that is new for debian 8, but if someone else has it running then that tends to rule out systemd in a general sense at least. Just throwing that out there in case it helps us find the root cause.

 

Yes, I run emby on jessie from time to time. I usually test all packages on vms. I do not think the issue has anything to do with systemd, if anything I would try turning off ipv6 resolution and report back.

Link to comment
Share on other sites

jstruebel

Ok, I finally sorted out all of my problems. Turns out I had a couple of issues.

 

The first one relates to how I was trying to setup Emby. The tools that I'm using to create a "mediaserver" appliance install all of the packages etc, into a chroot filesystem and then package it into an ISO that can be used live or installed to another machine. It appears that Emby stores something in the /var/lib/emby-server directory that remembers what machine it was installed on and will silently exit if it doesn't match. I was able to get around this by removing the /var/lib/emby-server directory from the default install, since Emby rebuilds it if it doesn't exist. Can any of the Emby developers comment on that? Does that sound right or am I completely off base?

 

The second issue that I had is that I was using nscd to allow user accounts to be defined by an ldap server. I had left the nscd settings at their default where it caches everything it knows about. I had to disable the hosts caching in order for Emby/mono to not generate the error with System.Net.Dns.GetHostByName_internal. I think it may be related to mono bug https://bugzilla.xamarin.com/show_bug.cgi?id=30018, but I haven't figured out which version will have the patch. For now it's not critical to cache hosts through nscd so I'll just live with it disabled. I did try disabling ipv6, but that didn't fix the problem.

 

Thank you for your help and suggestions.

Link to comment
Share on other sites

hurricanehrndz

Ok, I finally sorted out all of my problems. Turns out I had a couple of issues.

 

The first one relates to how I was trying to setup Emby. The tools that I'm using to create a "mediaserver" appliance install all of the packages etc, into a chroot filesystem and then package it into an ISO that can be used live or installed to another machine. It appears that Emby stores something in the /var/lib/emby-server directory that remembers what machine it was installed on and will silently exit if it doesn't match. I was able to get around this by removing the /var/lib/emby-server directory from the default install, since Emby rebuilds it if it doesn't exist. Can any of the Emby developers comment on that? Does that sound right or am I completely off base?

 

The second issue that I had is that I was using nscd to allow user accounts to be defined by an ldap server. I had left the nscd settings at their default where it caches everything it knows about. I had to disable the hosts caching in order for Emby/mono to not generate the error with System.Net.Dns.GetHostByName_internal. I think it may be related to mono bug https://bugzilla.xamarin.com/show_bug.cgi?id=30018, but I haven't figured out which version will have the patch. For now it's not critical to cache hosts through nscd so I'll just live with it disabled. I did try disabling ipv6, but that didn't fix the problem.

 

Thank you for your help and suggestions.

This sounds like an interesting project and yes your assumptions are correct. What mediaserver appliance are you using?

Edited by hurricanehrndz
Link to comment
Share on other sites

jstruebel

The mediaserver part of it is Emby.  :)  It's based on the Turnkey Linux project, specifically their fileserver appliance. They have setup tools that allow you to create and build your own appliance in the same way that they create each of their official versions. It uses their TKLDev appliance and a set of scripts that define the packages and configuration of each appliance. What I have so far for the mediaserver is on my Github at https://github.com/jstruebel/mediaserver if you want to check it out. I haven't finished testing it all out since I ran into the issue with the library paths that Luke fixed yesterday when I was working on it. Once that is fixed in the apt packages and I've had a chance to test it out, I can post an ISO if you'd like to check it out.

Link to comment
Share on other sites

Hello,

 

to update my own post.. I have not resolved it with the installation on the server in question but moved on to another. A stock ubuntu 14.04.03 , patched with the latest updates and following the steps written out on the site works and gets things up and running..   thank you for the information and feedback.. Now in need to get other things working but will post in another thread before moving on to purchase.. thanks for the information.

 

regards

 

Mayk

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