Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#40040 - avahi-daemon cannot start after clean install

Attached to Project: Arch Linux
Opened by Christian Bürckert (Kriese) - Tuesday, 22 April 2014, 18:07 GMT
Last edited by Dave Reisner (falconindy) - Thursday, 24 April 2014, 14:03 GMT
Task Type Bug Report
Category Packages: Core
Status Closed
Assigned To No-one
Architecture All
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:

Additional info:
* package version(s)
clean install and updated pacman -Syu

* config and/or log files etc.

running avahi-daemon
Failed to find user 'avahi'.

running avahi-daemon --no-chroot prints:
Found user 'avahi' (UID 84) and group 'avahi' (GID 84).
Successfully dropped root privileges.
open(/var/run/avahi-daemon//pid): Permission denied
Failed to create PID file: Permission denied

I checked the permissions they are set to user avahi:avahi.
I also tried to su into the user avahi (/bin/false -> /bin/bash) but this did not work.

running avahi-daemon --no-chroot --no-drop-root works

I checked the passwd and group files the user exists and is linked correctly with its group.

It must have something to do with the install since my normal system is also up to date but avahi runs perfectly.
I am using the new USB stick on the same computer so it cannot be a hardware problem.

Steps to reproduce:
- Installed according to installation guide up to first boot into the new system
(No SWAP using Label ARCH to create a installation on a USB Stick)
- Boot works but avahi fails
- Network does not work as well
This task depends upon

Closed by  Dave Reisner (falconindy)
Thursday, 24 April 2014, 14:03 GMT
Reason for closing:  Not a bug

Loading...