Ubuntu 12.04, a DHCP configured local network, and the same problem.
Putting lines to rc.local was not clean enough solution for me, so I
investigated this a little bit further. I had following symptoms:
/var/log/boot.log:
* Starting mDNS/DNS-SD daemon [OK]
* Stopping mDNS/DNS-SD daemon [OK]
Hi. I might be way off here, but I had the same problem with Fedora 17
(most recent at time of comment posting), RHEL 6.2, and CentOS 6.2.
I have to restart avahi-daemon.service and or avahi-daemon.socket
with systemctl or service every couple of minutes in order for iMac
machines on the network
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: avahi (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/624043
Title:
Avahi
Hi Guys,
I run Arch Linux on a Thinkpad and two different desktops. I mention
this because I only have this problem on one desktop so it is logical to
assume the problem may be hardware / driver related. At any rate I found
a workaround similar to the one mentioned in post #17.
just adding
This may or may not relate to this bug, and may or may not be the
workaround, but recently [and only recently] became a recurring issue
after accepting some updates on 9.10 machines.
Musing on the source for that mysterious SIGTERM revealed duplicate
up/down scripts for dhclient:
in
[To clarify *my* issue and discovery: random loss of avahi / mDNS *after
boot* was determined to be due to the duplicate scripts competing in
absurd ways. This may not have anything to do with a separate race with
netatalk, but I found this bug based on the SIGTERM logged in
#17 Workaround solved it for me too, and I agree with Malthe that this way it
is like restarting the daemon after login. hope the bug gets fixed.
Cheers,
Rex
Lucid 10.04 64bit server,
Avahi and netatalk from apt-get install
OS X snow leopard
--
You received this bug notification because you
Adding the line:
service avahi-daemon start
to the file /etc/rc.local
seems to have worked for me - this should start avahi-daemon at the end
of bootup (just before login) - though I'm not an expert so I might be
wrong.
Malthe
--
You received this bug notification because you are a member of
This problem seems to have disappeared for me. I'm still running 10.04
(Lucid). I'm not sure exactly when it changed, but it might have been
one or two months ago.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
My file server has been rebooted several times and is still displaying
the problem. Avahi-daemon need to be restarted manually after boot to
get it to advertise any services except the workstation one. Could
someone post a any sort of fix? Maybe just a way to automate the restart
once boot is
I too have been affected by this bug. No issues with .local multicasting
for me either. Running 10.4.1, intel E3300, 2gb ram, g43 chipset, sata
hdd's, realtek onbord eth.
mich...@server:~$ host -t SOA local
Host local not found: 3(NXDOMAIN)
after reboot:
mich...@server:~$ ps -A |grep avahi
Hi All, Trent Lloyd here - one of the authors of the Avahi project
The cause of this situation is relatively simple, in all cases I have
seen it is caused by a faulty network driver. You will find after you
restart Avahi - services work for a few minutes and then they fail again
- here is the
Hi all, hi Trent
thanks for your quick response, but I have to disagree with you. If I
restart avahi, everything works until the next reboot, which takes a
month sometimes... And the workaround with the pre-start script implies
that it is really a matter of which service is started first.
Lorenz,
Thank-you for the extra information and apologies for misunderstanding
the bug and not reading it fully.
I guess that nils my theory.. I am curious .. I guess I will have to try
this out it doesn't make much sense.
Thanks,
Trent
--
Avahi needs to be restarted after boot to broadcast
Lorenz and I are experiencing the same problem - the problem is not a
network driver. Once avahi is restarted (after netatalk starts),
everything works fine, until a reboot. I have used it for weeks at a
time without any problems.
--
Avahi needs to be restarted after boot to broadcast netatalk
wow, so much activity here, nice!
@trent: I totally know nothing about upstart and how the sequence is
controlled there, but if you do: try loading avahi before/after netatalk
and look what happens. If loading avahi after netatalk fixes the
problem, which will happen I think, then changing the
Avahi seems to work for ever until a reboot for me as well but here is
the lspci info requested:
00:00.0 Host bridge: Intel Corporation 4 Series Chipset DRAM Controller (rev 03)
00:02.0 VGA compatible controller: Intel Corporation 4 Series Chipset
Integrated Graphics Controller (rev 03)
00:1b.0
Hi there!
I definitetly think this is not a duplicate of bug #327362, because this
one is only a matter of which daemon is started when, i.e. avahi has to
be started/restarted *after* netatalk in order to advertise these
services properly. There is a thread in a german forum which describes
the
*** This bug is a duplicate of bug 327362 ***
https://bugs.launchpad.net/bugs/327362
I suggest this to be marked as duplicate of bug # 327362
/Mikael
** This bug has been marked a duplicate of bug 327362
Some ISPs have .local domain which disables avahi-daemon
* You can subscribe to bug
*** This bug is a duplicate of bug 327362 ***
https://bugs.launchpad.net/bugs/327362
This should not be marked as a duplicate. Bug 327362 involves a .local
domain, but the problem here does not. There is no mention of a .local
domain in the logs or when I restart avahi from the command line.
*** This bug is a duplicate of bug 327362 ***
https://bugs.launchpad.net/bugs/327362
I suspect that it really is the the same mechanism. If you start avahi
from the command line you will not use the script in /etc/init.d that
contains the check if there is a local. domain.
If you do as
*** This bug is a duplicate of bug 327362 ***
https://bugs.launchpad.net/bugs/327362
Here's the output of the command:
$ host -t SOA local.
Host local. not found: 3(NXDOMAIN)
So it looks like it doesn't have to do with a local. domain.
FWIW, I always use the script in /etc/init.d to
*** This bug is a duplicate of bug 327362 ***
https://bugs.launchpad.net/bugs/327362
Do you have other avahi services enabled?
If not, try to enable other services, like ssh-login or sftp
Then, when you have rebooted the system that acts as the netatalk server and
logged in, what do you see
*** This bug is a duplicate of bug 327362 ***
https://bugs.launchpad.net/bugs/327362
I do have other services enabled. Here is the output of avahi-browse
immediately after a reboot, and then after restarting avahi-daemon. (I
removed some extraneous information from the output.)
It looks like
** Attachment added: Dependencies.txt
https://bugs.launchpad.net/bugs/624043/+attachment/1518074/+files/Dependencies.txt
--
Avahi needs to be restarted after boot to broadcast netatalk services
https://bugs.launchpad.net/bugs/624043
You received this bug notification because you are a
25 matches
Mail list logo
