Re: Strange 224.0.0.251 address being accessed on bootup
On Wednesday 29 August 2007 03:27, Douglas A. Tutty wrote:
> On Tue, Aug 28, 2007 at 11:50:14PM +0200, Nigel Henry wrote:
> > Any comments, suggestions, and including "go and get a life", welcome.
> >
> > This is no big deal, but would be nice to resolve this problem.
>
> So its a script in /etc/network/ip-up.d? That would be run by the
> networking stuff and you don't want to play with that.
>
> To disable the actual script, put an exit -1 in after the shebang before
> it actually does anything. By using -1, something that calls the script
> should log an error somewhere that you can then trace. Use exit 0 to
> just return 'success'.
>
> I wouldn't tell you to "go and get a life". You've got a properly
> installed debian package that is spitting out unwanted net traffic. To
> me that's a big deal and worth a talk with the maintainer.
>
> Doug.
A big Oops on my part.
I looked at the bootlog today, and just after "Entering runlevel 2" the script
is run, as below.
Wed Aug 29 13:47:21 2007: INIT: Entering runlevel: 2
Wed Aug 29 13:47:21 2007: Starting system log daemon: syslogd.
Wed Aug 29 13:47:21 2007: Starting kernel log daemon: klogd.
Wed Aug 29 13:47:21 2007: Starting portmap daemon...Already running..
Wed Aug 29 13:47:21 2007: Starting Common Unix Printing System: cupsd.
Wed Aug 29 15:47:22 2007: Starting system message bus: dbus.
Wed Aug 29 15:47:23 2007: Starting Hardware abstraction layer: hald.
Wed Aug 29 15:47:30 2007: Starting Avahi mDNS/DNS-SD Daemon: avahi-daemon.
Wed Aug 29 15:47:30 2007: Starting DirMngr: dirmngr.
Wed Aug 29 15:47:31 2007: Starting internet superserver: inetd.
Ho hum. I now look in /etc/rc2.d thro rc5.d, and there are no links for the
avahi-daemon. It appears that some time in the past, as a newbie to Debian,
I deleted the "S" links for the avahi-daemon, thinking that would prevent the
script being run in /etc/init.d. It obviously didn't work, and appears that
if a script is in /etc/init.d, and there are no links to it in the runlevel
directories, the script is run anyway.
Next I re-create the links (twice). Ist time I do them as:
ln -s /etc/init.d/avahi-daemon /etc/rc2.d/K16avahi-daemon
The same for the other runlevels, but a reboot still has the messages showing
the script is running. I see that the other links are ../init.d rather
than /etc/init.d, so redo the links. Another reboot, and the messages are
still there. The output of ps auxw shows as below after the reboot.
avahi 4480 0.0 0.1 2692 1380 ? Ss 17:30 0:00 avahi-daemon:
running [debian.local]
avahi 4481 0.0 0.0 2556 468 ? Ss 17:30 0:00 avahi-daemon:
chroot helper
If I stop the daemon with /etc/init.d/avahi-daemon stop, then restart it, ps
auxw shows no entries for it.
I stop the avahi-daemon again, and go into sysv-rc-conf, and enable avahi for
runlevels 2 thro 5. I check /etc/rc2.d, and now have "S84avahi-daemon". The
daemon should be started now, but an ifdown eth0, then an ifup eth0, results
in no messages pointing to IP 224.0.0.251.
It appears that the links I recreated from /etc/rcx.d pointing to ../init.d
arn't working. I'm losing the plot a bit now.
Renaming avahi-daemon in /etc/init.d has fixed it, and it's no longer started,
but isn't the answer.
Shutting down before rebooting with the renamed daemon, I saw flying by,
something that appeared to say, referring to avahi, something about bad link,
but I can't find it in dmesg. This may be referring to the recreated links
I'd made in /etc/rcx.d.
Rooting around in /var/log, I find this in daemon.log:
Aug 28 20:47:33 debian ntpd[4692]: kernel time sync enabled 0001
Aug 28 21:30:34 debian avahi-daemon[4484]: Interface eth0.IPv4 no longer
relevant for mDNS.
Aug 28 21:30:34 debian avahi-daemon[4484]: Leaving mDNS multicast group on
interface eth0.IPv4 with address 192.168.0.7.
Aug 28 21:30:34 debian avahi-daemon[4484]: Withdrawing address record for
192.168.0.7 on eth0.
Aug 28 21:31:09 debian avahi-daemon[4484]: New relevant interface eth0.IPv4
for mDNS.
Aug 28 21:31:09 debian avahi-daemon[4484]: Joining mDNS multicast group on
interface eth0.IPv4 with address 192.168.0.7.
Aug 28 21:31:09 debian avahi-daemon[4484]: Registering new address record for
192.168.0.7 on eth0.
Aug 28 21:31:11 debian ntpdate[29752]: the NTP socket is in use, exiting
Aug 28 21:40:43 debian avahi-daemon[4484]: Got SIGTERM, quitting.
Aug 28 21:40:43 debian avahi-daemon[4484]: Leaving mDNS multicast group on
interface eth0.IPv4 with address 192.168.0.7.
Aug 28 21:41:20 debian ntpd[4692]: sendto(192.168.0.230) (fd=21): Network is
unreachable
Aug 28 21:41:34 debian ntpdate[3030]: the NTP socket is in use, exiting
Aug 28 21:46:02 debian init: Switching to runlevel: 6
Aug 28 21:46:07 debian ntpd[4692]: ntpd exiting on signal 15
Aug 28 21:48:12 debian ntpdate[4012]: step time server 192.168.0.230 offset
-0.502414 sec
Aug 28 21:48:22 debian avahi-daemon[4488]: Found user 'avahi' (UID 106) and
group 'avahi' (GID 111).
Aug 28 21:48:22 debian avahi-daemon[4488]: Successfully dropped root
privileges.
Aug 28 21:48:22 debian avahi-daemon[4488]: avahi-daemon 0.6.16 starting up.
Aug 28 21:48:22 debian avahi-daemon[4488]: Successfully called chroot().
Aug 28 21:48:22 debian avahi-daemon[4488]: Successfully dropped remaining
capabilities.
Aug 28 21:48:22 debian avahi-daemon[4488]: No service found
in /etc/avahi/services.
Aug 28 21:48:22 debian avahi-daemon[4488]: New relevant interface eth0.IPv4
for mDNS.
Aug 28 21:48:22 debian avahi-daemon[4488]: Joining mDNS multicast group on
interface eth0.IPv4 with address 192.168.0.7.
Aug 28 21:48:22 debian avahi-daemon[4488]: Network interface enumeration
completed.
Aug 28 21:48:22 debian avahi-daemon[4488]: Registering new address record for
192.168.0.7 on eth0.
Aug 28 21:48:22 debian avahi-daemon[4488]: Registering HINFO record with
values 'I686'/'LINUX'.
Aug 28 21:48:23 debian avahi-daemon[4488]: Server startup complete. Host name
is debian.local. Local service cookie is 3493426229.
Aug 28 21:48:27 debian ntpd[4659]: ntpd 4.2.2p4@1.1585-o Sun Mar 4 13:21:35
UTC 2007 (1)
Is there anything in the above stuff that rings any bells as to why I'm having
such a problem in disabling avahi? 3 lines up I see a mention of
"debian.local" . I saw this also on the ps auxw output which is a few lines
further up this message.
As mentioned above, I can disable the daemon by renaming it, and it won't
start, but it would be nice to resolve the problem in the proper way, rather
than my hack of renaming avahi-daemon in /etc/init.d.
I've been on this for about 8 hrs today, on, and off. Neglected taking my
doggie for walkies in the sunshine, and playing with his stick.
Nevermind. Tomorrows another day, and if it's fine the dog (Rizla) get's the
attention, not the infernal machine.
Before closing this post, and I've still got tail -f /var/log/messages
running. I keep getting every 20 mins "debian -- MARK --" . What's that all
about?
As usual very gratefull for any help that comes from the list.
Nigel.
Reply to: