Arch Linux

nibblebot

Member

Registered: 2013-02-08

Posts: 5

[SOLVED] Avahi will not start

I had avahi + cups working for a while back, but going to use it today and avahi-daemon will not start:

%  ~  sudo systemctl status avahi-daemon
avahi-daemon.service - Avahi mDNS/DNS-SD Stack
   Loaded: loaded (/usr/lib/systemd/system/avahi-daemon.service; enabled)
   Active: failed (Result: timeout) since Mon 2013-07-15 12:03:33 EDT; 5min ago
 Main PID: 2234
   Status: "Server startup complete. Host name is air-laptop.local. Local service cookie is 81586563."
   CGroup: name=systemd:/system/avahi-daemon.service

Jul 15 12:02:05 air-laptop avahi-daemon[2234]: Service "air-laptop" (/services/ssh.service) successfully established.
Jul 15 12:02:05 air-laptop avahi-daemon[2234]: Service "air-laptop" (/services/sftp-ssh.service) successfully established.
Jul 15 12:03:33 air-laptop systemd[1]: avahi-daemon.service operation timed out. Terminating.
Jul 15 12:03:33 air-laptop avahi-daemon[2234]: Got SIGTERM, quitting.
Jul 15 12:03:33 air-laptop avahi-daemon[2234]: Leaving mDNS multicast group on interface virbr0.IPv4 with address 192.168.122.1.
Jul 15 12:03:33 air-laptop avahi-daemon[2234]: Leaving mDNS multicast group on interface wlan0.IPv4 with address 10.0.1.128.
Jul 15 12:03:33 air-laptop avahi-daemon[2234]: avahi-daemon 0.6.31 exiting.
Jul 15 12:03:33 air-laptop systemd[1]: avahi-daemon.service: Got notification message from PID 2234, but reception only permitted for PID 0
Jul 15 12:03:33 air-laptop systemd[1]: Failed to start Avahi mDNS/DNS-SD Stack.
Jul 15 12:03:33 air-laptop systemd[1]: Unit avahi-daemon.service entered failed state.

All files in /etc/avahi/* appear to be defaults.

/etc/dhcpcd.conf:

# A sample configuration for dhcpcd.
# See dhcpcd.conf(5) for details.

# Inform the DHCP server of our hostname for DDNS.
hostname
# To share the DHCP lease across OSX and Windows a ClientID is needed.
# Enabling this may get a different lease than the kernel DHCP client.
# Some upstream DHCP servers may also require a ClientID, such as FRITZ!Box.
#clientid

# A list of options to request from the DHCP server.
option domain_name_servers, domain_name, domain_search, host_name
option classless_static_routes
# Most distributions have NTP support.
option ntp_servers
# Respect the network MTU.
option interface_mtu
# A ServerID is required by RFC2131.
#require dhcp_server_identifier

# A hook script is provided to lookup the hostname if not set by the DHCP
# server, but it should not be run by default.
nohook lookup-hostname
noipv4ll
noipv6rs

Any ideas for investigation?

Last edited by nibblebot (2013-07-15 17:55:35)

WonderWoofy

Member

From: Los Gatos, CA

Registered: 2012-05-19

Posts: 8,414

Re: [SOLVED] Avahi will not start

You should probably look in the journal itself.  Sometimes I have noticed that the "systemctl status <unit>" will only give the more significant messages when there are a bunch that are logged at once.  So there might be more information there.

nibblebot

Member

Registered: 2013-02-08

Posts: 5

Re: [SOLVED] Avahi will not start

Ok, should have researched this more. This post https://bbs.archlinux.org/viewtopic.php?id=165913 led me to https://www.archlinux.org/news/filesyst … equired-1/
Basically, somehow, my /var/run was no longer symlinked to /run.
I ran the commands here after stopping all the services whose pids were in /var/run.
Then restarted and now avahi works again.