client-browse-services.c fails: "Unexpected DBUS error occured"

avahi-0.6.10, configured with all defaults except no QT
bindings, no
mono, and no python.

dbus-0.61, default configuration

libdaemon-0.10, default configuration

On debian stable, I compiled the example with the following
command:

gcc client-browse-services.c `pkg-config avahi-client
--cflags --libs`

There were no warnings and no errors. When I run the
executable, I get
the following error: "Failed to create client: An
unexpected DBUS
error occured"

Both dbus-daemon and dbus-start appear to be running,
however I don't
see the avahi-daemon. If I try to start it again with
"avahi-daemon"
it fails with:

dbus_bus_get(): Failed to connect to socket
/usr/local/var/run/dbus/system_bus_socket: No such file or
directory
WARNING: Failed to contact D-BUS daemon.

Am I missing a configuration step?

Cheers!

-Nick
_______________________________________________
avahi mailing list
avahilists.freedesktop.org
h
ttp://lists.freedesktop.org/mailman/listinfo/avahi

avahi-discover-standalone works, though.

On 6/8/06, Nicholas Andrews <tar.bz2gmail.com> wrote:
> avahi-0.6.10, configured with all defaults except no QT
bindings, no
> mono, and no python.
>
> dbus-0.61, default configuration
>
> libdaemon-0.10, default configuration
>
> On debian stable, I compiled the example with the
following command:
>
> gcc client-browse-services.c `pkg-config avahi-client
--cflags --libs`
>
> There were no warnings and no errors. When I run the
executable, I get
> the following error: "Failed to create client: An
unexpected DBUS
> error occured"
>
> Both dbus-daemon and dbus-start appear to be running,
however I don't
> see the avahi-daemon. If I try to start it again with
"avahi-daemon"
> it fails with:
>
> dbus_bus_get(): Failed to connect to socket
> /usr/local/var/run/dbus/system_bus_socket: No such file
or directory
> WARNING: Failed to contact D-BUS daemon.
>
> Am I missing a configuration step?
>
> Cheers!
>
> -Nick
>
_______________________________________________
avahi mailing list
avahilists.freedesktop.org
h
ttp://lists.freedesktop.org/mailman/listinfo/avahi

Thats because avahi-discover-standalone uses the core avahi
libraries
directly (like avahi-daemon) and not the dbus interface to
avahi-daemon.

Cheers,
Trent

On Thu, Jun 08, 2006 at 11:21:24AM -0400, Nicholas Andrews
wrote:
> avahi-discover-standalone works, though.
> 
> On 6/8/06, Nicholas Andrews <tar.bz2gmail.com> wrote:
> >avahi-0.6.10, configured with all defaults except
no QT bindings, no
> >mono, and no python.
> >
> >dbus-0.61, default configuration
> >
> >libdaemon-0.10, default configuration
> >
> >On debian stable, I compiled the example with the
following command:
> >
> >gcc client-browse-services.c `pkg-config
avahi-client --cflags --libs`
> >
> >There were no warnings and no errors. When I run
the executable, I get
> >the following error: "Failed to create
client: An unexpected DBUS
> >error occured"
> >
> >Both dbus-daemon and dbus-start appear to be
running, however I don't
> >see the avahi-daemon. If I try to start it again
with "avahi-daemon"
> >it fails with:
> >
> >dbus_bus_get(): Failed to connect to socket
> >/usr/local/var/run/dbus/system_bus_socket: No such
file or directory
> >WARNING: Failed to contact D-BUS daemon.
> >
> >Am I missing a configuration step?
> >
> >Cheers!
> >
> >-Nick
> >
> _______________________________________________
> avahi mailing list
> avahilists.freedesktop.org
> h
ttp://lists.freedesktop.org/mailman/listinfo/avahi

-- 
Trent Lloyd <lathiatbur.st>
Bur.st Networking Inc.
_______________________________________________
avahi mailing list
avahilists.freedesktop.org
h
ttp://lists.freedesktop.org/mailman/listinfo/avahi

Hi Nicholas,

On Thu, Jun 08, 2006 at 11:18:43AM -0400, Nicholas Andrews
wrote:
> avahi-0.6.10, configured with all defaults except no QT
bindings, no
> mono, and no python.
> 
> dbus-0.61, default configuration
> 
> libdaemon-0.10, default configuration
> 
> On debian stable, I compiled the example with the
following command:
> 
> gcc client-browse-services.c `pkg-config avahi-client
--cflags --libs`
> 
> There were no warnings and no errors. When I run the
executable, I get
> the following error: "Failed to create client: An
unexpected DBUS
> error occured"
> 
> Both dbus-daemon and dbus-start appear to be running,
however I don't
> see the avahi-daemon. If I try to start it again with
"avahi-daemon"
> it fails with:
> 
> dbus_bus_get(): Failed to connect to socket
> /usr/local/var/run/dbus/system_bus_socket: No such file
or directory
> WARNING: Failed to contact D-BUS daemon.

This means that we don't have your system bus socket right,
if dbus is
running do a "ps aux|grep dbus" find the dbus
with "--system" it may be
that you dont have a sytem bus running (there are two,
--system and
--session) if not you can start one with (at a guess)
/usr/local/bin/dbus-daemon --system

If it is running, check /proc/<pid>/fd and look for
the
system_bus_socket file and see if its location is different.

Let me know how that goes for you.

Cheers,
Trent

> Am I missing a configuration step?
> 
> Cheers!
> 
> -Nick
> _______________________________________________
> avahi mailing list
> avahilists.freedesktop.org
> h
ttp://lists.freedesktop.org/mailman/listinfo/avahi

-- 
Trent Lloyd <lathiatbur.st>
Bur.st Networking Inc.
_______________________________________________
avahi mailing list
avahilists.freedesktop.org
h
ttp://lists.freedesktop.org/mailman/listinfo/avahi

Trent,

The --system dbus is indeed running. Looking at
proc/<pid>/fd, I see 0
through 12 files (named 0->12) but a "ls -l"
shows that they either
point to /dev/null or to a socket:[XXXX]. How should I fix
this?

Thanks for the help! 

-Nick

On 6/8/06, Trent Lloyd <lathiatbur.st> wrote:
> Hi Nicholas,
>
> On Thu, Jun 08, 2006 at 11:18:43AM -0400, Nicholas
Andrews wrote:
> > avahi-0.6.10, configured with all defaults except
no QT bindings, no
> > mono, and no python.
> >
> > dbus-0.61, default configuration
> >
> > libdaemon-0.10, default configuration
> >
> > On debian stable, I compiled the example with the
following command:
> >
> > gcc client-browse-services.c `pkg-config
avahi-client --cflags --libs`
> >
> > There were no warnings and no errors. When I run
the executable, I get
> > the following error: "Failed to create
client: An unexpected DBUS
> > error occured"
> >
> > Both dbus-daemon and dbus-start appear to be
running, however I don't
> > see the avahi-daemon. If I try to start it again
with "avahi-daemon"
> > it fails with:
> >
> > dbus_bus_get(): Failed to connect to socket
> > /usr/local/var/run/dbus/system_bus_socket: No such
file or directory
> > WARNING: Failed to contact D-BUS daemon.
>
> This means that we don't have your system bus socket
right, if dbus is
> running do a "ps aux|grep dbus" find the
dbus with "--system" it may be
> that you dont have a sytem bus running (there are two,
--system and
> --session) if not you can start one with (at a guess)
> /usr/local/bin/dbus-daemon --system
>
> If it is running, check /proc/<pid>/fd and look
for the
> system_bus_socket file and see if its location is
different.
>
> Let me know how that goes for you.
>
> Cheers,
> Trent
>
> > Am I missing a configuration step?
> >
> > Cheers!
> >
> > -Nick
> > _______________________________________________
> > avahi mailing list
> > avahilists.freedesktop.org
> > h
ttp://lists.freedesktop.org/mailman/listinfo/avahi
>
> --
> Trent Lloyd <lathiatbur.st>
> Bur.st Networking Inc.
> _______________________________________________
> avahi mailing list
> avahilists.freedesktop.org
> h
ttp://lists.freedesktop.org/mailman/listinfo/avahi
>
_______________________________________________
avahi mailing list
avahilists.freedesktop.org
h
ttp://lists.freedesktop.org/mailman/listinfo/avahi

On Fri, 09.06.06 10:49, Nicholas Andrews (tar.bz2gmail.com) wrote:

> 
> Trent,
> 
> The --system dbus is indeed running. Looking at
proc/<pid>/fd, I see 0
> through 12 files (named 0->12) but a "ls
-l" shows that they either
> point to /dev/null or to a socket:[XXXX]. How should I
fix this?

I don't know any way to map the kernel socket inode back to
the path
it was created with.

However, you can use "strace -e connect" to
track down which UNIX
socket it is avahi wants to connect to.

Lennart

-- 
Lennart Poettering; lennart [at] poettering [dot] net
ICQ# 11060553; GPG 0x1A015CC4; http://0pointer.net/lenn
art/
_______________________________________________
avahi mailing list
avahilists.freedesktop.org
h
ttp://lists.freedesktop.org/mailman/listinfo/avahi

On Thu, Jun 15, 2006 at 09:46:31PM +0200, Lennart Poettering
wrote:
> On Fri, 09.06.06 10:49, Nicholas Andrews (tar.bz2gmail.com) wrote:
> 
> > 
> > Trent,
> > 
> > The --system dbus is indeed running. Looking at
proc/<pid>/fd, I see 0
> > through 12 files (named 0->12) but a "ls
-l" shows that they either
> > point to /dev/null or to a socket:[XXXX]. How
should I fix this?
> 
> I don't know any way to map the kernel socket inode
back to the path
> it was created with.

lsof?

Trent

> 
> However, you can use "strace -e connect" to
track down which UNIX
> socket it is avahi wants to connect to.
> 
> Lennart
> 
> -- 
> Lennart Poettering; lennart [at] poettering [dot] net
> ICQ# 11060553; GPG 0x1A015CC4; http://0pointer.net/lenn
art/
> _______________________________________________
> avahi mailing list
> avahilists.freedesktop.org
> h
ttp://lists.freedesktop.org/mailman/listinfo/avahi

-- 
Trent Lloyd <lathiatbur.st>
Bur.st Networking Inc.
_______________________________________________
avahi mailing list
avahilists.freedesktop.org
h
ttp://lists.freedesktop.org/mailman/listinfo/avahi

On Fri, 16.06.06 09:33, Trent Lloyd (lathiatbur.st)
wrote:

> 
> On Thu, Jun 15, 2006 at 09:46:31PM +0200, Lennart
Poettering wrote:
> > On Fri, 09.06.06 10:49, Nicholas Andrews
(tar.bz2gmail.com) wrote:
> > 
> > > 
> > > Trent,
> > > 
> > > The --system dbus is indeed running. Looking
at proc/<pid>/fd, I see 0
> > > through 12 files (named 0->12) but a
"ls -l" shows that they either
> > > point to /dev/null or to a socket:[XXXX]. How
should I fix this?
> > 
> > I don't know any way to map the kernel socket
inode back to the path
> > it was created with.
> 
> lsof?

lsof doesn't show the paths of unix sockets.

Lennart

-- 
Lennart Poettering; lennart [at] poettering [dot] net
ICQ# 11060553; GPG 0x1A015CC4; http://0pointer.net/lenn
art/
_______________________________________________
avahi mailing list
avahilists.freedesktop.org
h
ttp://lists.freedesktop.org/mailman/listinfo/avahi

On Fri, Jun 16, 2006 at 05:43:27PM +0200, Lennart Poettering
wrote:
> On Fri, 16.06.06 09:33, Trent Lloyd (lathiatbur.st)
wrote:
> 
> > 
> > On Thu, Jun 15, 2006 at 09:46:31PM +0200, Lennart
Poettering wrote:
> > > On Fri, 09.06.06 10:49, Nicholas Andrews
(tar.bz2gmail.com) wrote:
> > > 
> > > > 
> > > > Trent,
> > > > 
> > > > The --system dbus is indeed running.
Looking at proc/<pid>/fd, I see 0
> > > > through 12 files (named 0->12) but a
"ls -l" shows that they either
> > > > point to /dev/null or to a
socket:[XXXX]. How should I fix this?
> > > 
> > > I don't know any way to map the kernel
socket inode back to the path
> > > it was created with.
> > 
> > lsof?
> 
> lsof doesn't show the paths of unix sockets.

rootzim:~# netstat -anp|grep sock
Active UNIX domain sockets (servers and established)
unix  2      [ ACC ]     STREAM     LISTENING     628408  
6922/mysqld
/var/run/mysqld/mysqld.sock
unix  2      [ ACC ]     STREAM     LISTENING     628350  
6865/mysqld
/tmp/mysql.sock

?

Trent

> Lennart
> 
> -- 
> Lennart Poettering; lennart [at] poettering [dot] net
> ICQ# 11060553; GPG 0x1A015CC4; http://0pointer.net/lenn
art/
> _______________________________________________
> avahi mailing list
> avahilists.freedesktop.org
> h
ttp://lists.freedesktop.org/mailman/listinfo/avahi

-- 
Trent Lloyd <lathiatbur.st>
Bur.st Networking Inc.
_______________________________________________
avahi mailing list
avahilists.freedesktop.org
h
ttp://lists.freedesktop.org/mailman/listinfo/avahi