Bug 172017 – avahi-daemon fails to start during system startup

This service will be undergoing maintenance at 00:00 UTC, 2017-10-23 It is expected to last about 30 minutes

Bug 172017 - avahi-daemon fails to start during system startup

Summary:	avahi-daemon fails to start during system startup

Status:	CLOSED RAWHIDE

Aliases:	None

Product:	Fedora
Classification:	Fedora
Component:	avahi (Show other bugs)
Sub Component:
Version:	rawhide
Hardware:	All Linux

Priority	medium Severity medium
Target Milestone:	---
Target Release:	---
Assigned To:	Alexander Larsson
QA Contact:
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2005-10-29 03:29 EDT by Frank Arnold
Modified:	2007-11-30 17:11 EST (History)
CC List:	0 users

See Also:
Fixed In Version:	0.5.2-3
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2005-10-29 14:28:47 EDT
Type:	---
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Groups: None (edit)

Description Frank Arnold 2005-10-29 03:29:45 EDT

Description of problem:
avahi-daemon fails to start during system startup

Version-Release number of selected component (if applicable):
avahi-0.5.2-2

How reproducible:
Every time at system startup

Steps to Reproduce:
1. Restart system
2. Look at system messages or use rhgb in quiet mode to get notified
  
Additional info:
I found this line in /var/log/messages...
avahi-daemon[1834]: dbus_bus_get(): Failed to connect to socket
/var/run/dbus/system_bus_socket: No such file or directory

The reason is that avahi-daemon is started before messagebus. I've changed the
chkconfig line from the avahi-daemon init script to "# chkconfig: 345 98 02" and
did --del/--add. Worked thereafter.

Comment 1 Frank Arnold 2005-10-29 14:28:47 EDT

Somebody was quicker than me. It's fixed in version 0.5.2-3.

Note You need to log in before you can comment on or make changes to this bug.