Adam, you're great :) it worked. I actually had 'org.macports.dbus: Already loaded' when trying to load dbus. I didn't think restart it could solve the problem. Anyway I didn't know how to, thanks for the set of instruction. Let's see if this support a reboot. Paul, I had the message: 24/03/2008 12:05:14 PM org.freedesktop.avahi-daemon[523] dbus_bus_get_private(): Failed to connect to socket /opt/local/var/run/ dbus/system_bus_socket: Connection refused 24/03/2008 12:05:14 PM org.freedesktop.avahi-daemon[523] WARNING:Failed to contact D-Bus daemon. So I figured asahi needed to connect to DBus... I don't understand what is the relation between the two. thanks Jean On 25 Mar 2008, at 2:45 PM, Adam Dershowitz wrote:
Are you sure about that? Because I had the identical set of errors a while back and I believe that relaunching dbus solved it. I think that avahi was trying to connect to dbus and failing because dbus was not running. But most of the errors that showed up were avahi errors. Do you get any errors in your system log if you do: sudo launchctl load -w /Library/LaunchDaemons/org.macports.dbus.plist
When I had the error there were some existing files that confused dbus, so it would not restart properly. What about if you do this: sudo launchctl unload /Library/LaunchDaemons/org.macports.dbus.plist sudo rm /opt/local/var/run/dbus/pid sudo rm /opt/local/var/run/dbus/system_bus_socket sudo launchctl load -w /Library/LaunchDaemons/org.macports.dbus.plist
Does that get the errors to go away?
--Adam
On Mar 24, 2008, at 6:53 PM, nodje wrote:
thanks for the tip Adam.
but the dbus is already started in my case: It's avahi-daemon that cannot start. For some obscure reason, it cannot connect to dbus...
--nodje
On 25 Mar 2008, at 1:28 AM, Adam Dershowitz wrote:
I believe that this is the problem that I saw before. It seems that by default dbus doesn't run while avahi does. Just doing: sudo launchctl load -w /Library/LaunchDaemons/ org.macports.dbus.plist starts the dbus daemon and should allow avahi to connect to it properly.
And, for anyone who might be interested, I had an additional avahi problem where my log was filling up with: Mar 23 17:41:06 Macintosh org.freedesktop.avahi-daemon[67]: Received packet from invalid interface. Mar 23 17:41:36: --- last message repeated 9 times --- Mar 23 17:41:36 Macintosh org.freedesktop.avahi-daemon[67]: Received packet from invalid interface. Mar 23 17:42:06: --- last message repeated 9 times --- Mar 23 17:42:06 Macintosh org.freedesktop.avahi-daemon[67]: Received packet from invalid interface.
I found that the solution was just to kill it: sudo avahi-daemon -k
at which point it automatically restarted and the errors went away.
--Adam
On Mar 24, 2008, at 12:33 AM, nodje wrote:
thanks for the reply Paul. gives no hope though :(
I've had this message for months. It's polluting my console log and probably consumes resources.
As you say, some other applications need it. So it's not even possible to uninstall.
...
On 24 Mar 2008, at 1:30 PM, paul beard wrote:
On Sun, Mar 23, 2008 at 8:19 PM, nodje <nodje.co@gmail.com> wrote: I had an avahi probleme due to thuis missing user. I recently updated avahi to 0.6.22_0 (from 0.6.17_0). It fixed the missing avahi user problem. But I'm still having an issue, apparently similar with Paul's one.
Console log: 24/03/2008 12:05:13 PM org.freedesktop.avahi-dnsconfd[522] Failed to connect to the daemon. This probably means that you 24/03/2008 12:05:13 PM org.freedesktop.avahi-dnsconfd[522] didn't start avahi-daemon before avahi-dnsconfd. 24/03/2008 12:05:13 PM com.apple.launchd[1] (org.freedesktop.avahi-dnsconfd[522]) Exited with exit code: 1 24/03/2008 12:05:13 PM com.apple.launchd[1] (org.freedesktop.avahi-dnsconfd) Throttling respawn: Will start in 10 seconds 24/03/2008 12:05:14 PM org.freedesktop.avahi-daemon[523] Found user 'avahi' (UID 502) and group 'avahi' (GID 502). 24/03/2008 12:05:14 PM org.freedesktop.avahi-daemon[523] Successfully dropped root privileges. 24/03/2008 12:05:14 PM org.freedesktop.avahi-daemon[523] avahi- daemon 0.6.22 starting up. 24/03/2008 12:05:14 PM org.freedesktop.avahi-daemon[523] WARNING: No NSS support for mDNS detected, consider installing nss-mdns! 24/03/2008 12:05:14 PM org.freedesktop.avahi-daemon[523] dbus_bus_get_private(): Failed to connect to socket /opt/local/var/run/dbus/system_bus_socket: Connection refused 24/03/2008 12:05:14 PM org.freedesktop.avahi-daemon[523] WARNING: Failed to contact D-Bus daemon. 24/03/2008 12:05:14 PM com.apple.launchd[1] (org.freedesktop.avahi-daemon[523]) Exited with exit code: 255 24/03/2008 12:05:14 PM com.apple.launchd[1] (org.freedesktop.avahi-daemon) Throttling respawn: Will start in 10 seconds 24/03/2008 12:05:23 PM org.freedesktop.avahi-dnsconfd[524] connect(): No such file or directory 24/03/2008 12:05:23 PM org.freedesktop.avahi-dnsconfd[524] Failed to connect to the daemon. This probably means that you 24/03/2008 12:05:23 PM org.freedesktop.avahi-dnsconfd[524] didn't start avahi-daemon before avahi-dnsconfd. 24/03/2008 12:05:23 PM com.apple.launchd[1] (org.freedesktop.avahi-dnsconfd[524]) Exited with exit code: 1
Would reinstall avahi solve the problem? I have seen very few thread about the topic. Paul, did you manage to get a working asahi?
Thanks,
--nodje
To be honest, I'm not sure. This seems to be one of those areas where MacPorts and Apple duplicate each other's efforts. I don't know if avahi is supposed to do anything other than just be installed so other applications don't grumble. An mDNS responder exists on OS X, anyway.
At the moment, my avahi isn't even running, for some reason. I don't know if it matters or not.
-- Paul Beard / www.paulbeard.org/ <paulbeard@gmail.com/paulbeard@gmail.com>
_______________________________________________ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.
_______________________________________________ macports-users mailing list macports-users@lists.macosfor