Endless Avahi system.log errors
Adam Dershowitz
dersh at alum.mit.edu
Sat Feb 2 14:19:42 PST 2008
I have Avahi port installed due to a dependency. I recently noticed
that my system.log contains this repeated every 10 seconds:
Feb 2 14:16:35 Macintosh org.freedesktop.avahi-dnsconfd[808]:
connect(): No such file or directory
Feb 2 14:16:35 Macintosh org.freedesktop.avahi-dnsconfd[808]: Failed
to connect to the daemon. This probably means that you
Feb 2 14:16:35 Macintosh org.freedesktop.avahi-dnsconfd[808]: didn't
start avahi-daemon before avahi-dnsconfd.
Feb 2 14:16:35 Macintosh com.apple.launchd[1] (org.freedesktop.avahi-
dnsconfd[808]): Exited with exit code: 1
Feb 2 14:16:35 Macintosh com.apple.launchd[1] (org.freedesktop.avahi-
dnsconfd): Throttling respawn: Will start in 10 seconds
Feb 2 14:16:36 Macintosh org.freedesktop.avahi-daemon[809]: Found
user 'avahi' (UID 502) and group 'avahi' (GID 502).
Feb 2 14:16:36 Macintosh org.freedesktop.avahi-daemon[809]:
Successfully dropped root privileges.
Feb 2 14:16:36 Macintosh org.freedesktop.avahi-daemon[809]: avahi-
daemon 0.6.22 starting up.
Feb 2 14:16:36 Macintosh org.freedesktop.avahi-daemon[809]: WARNING:
No NSS support for mDNS detected, consider installing nss-mdns!
Feb 2 14:16:36 Macintosh org.freedesktop.avahi-daemon[809]:
dbus_bus_get_private(): Failed to connect to socket /opt/local/var/run/
dbus/system_bus_socket: No such file or directory
Feb 2 14:16:36 Macintosh org.freedesktop.avahi-daemon[809]: WARNING:
Failed to contact D-Bus daemon.
Feb 2 14:16:36 Macintosh com.apple.launchd[1] (org.freedesktop.avahi-
daemon[809]): Exited with exit code: 255
Feb 2 14:16:36 Macintosh com.apple.launchd[1] (org.freedesktop.avahi-
daemon): Throttling respawn: Will start in 10 seconds
I found this: http://lists.macosforge.org/pipermail/macports-users/2007-October/006496.html
that seems to relate, but I am not sure why the stream of errors.
Any suggestions about why and what to do about it?
I am not even sure if this is really a macports issue or an avahi
issue, but I figured that this is the right place to start. It looks
like something is perhaps not installed or configured correctly?
Thanks,
--Adam
More information about the macports-users
mailing list