Your message dated Sun, 8 May 2011 18:22:06 +0200
with message-id <[email protected]>
and subject line Re: [Bug 442] ripd packet debug option refuses daemon to start
has caused the Debian Bug report #469346,
regarding quagga: ripd packet debug option refuses daemon to start
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
469346: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=469346
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: quagga
Version: 0.99.5-5etch3
Severity: critical
Justification: breaks the whole system
Quagga's ripd provides the possibility to turn on debugging which will
show up and explain received and sent RIP packets. To enable this kind
of debugging, you have to enter the following two lines into ripd's
configuration:
myrouter# conf t
myrouter(config)# debug rip packet recv detail
myrouter(config)# debug rip packet send detail
myrouter(config)# exit
myrouter#
If you now show the current config with "show running-config", only one
additional line appears in the config which says:
myrouter# show running-conig
...
debug rip packet detail
...
Note that "recv" and "send" are gone (looks like some aggregation).
Anyway, if you store now running-config with "write" into the
config-file "/etc/quagga/ripd.conf" and afterwards restart ripd,
it will spit out the following error message:
myrouter:~# /etc/init.d/quagga restart ripd
Stopping Quagga daemons (prio:0): (ripd).
Removing all routes made by zebra.
Nothing to flush.
Loading capability module if not yet done.
Starting Quagga daemons (prio:10): ripdThere is no such command.
Error occured during reading below line.
debug rip packet detail
To get around this bug, you have to open ripd.conf with an editor and
manually remove the line. Afterwards ripd will start up smoothly.
A nasty bug, if you forgot to disable debugging, stored the config
and reboot your machine - if you really depend on ripd, then the machine
will not fully come back on the network, because ripd fails.
At the end of this post [1] it was noted, but not answered later.
[1]
http://lists.quagga.net/pipermail/quagga-users/2005-September/005406.html
-- System Information:
Debian Release: 4.0
APT prefers stable
APT policy: (990, 'stable')
Architecture: i386 (i686)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.18-6-686
Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1)
Versions of packages quagga depends on:
ii adduser 3.102 Add and remove users and groups
ii debconf [debconf-2.0] 1.5.11etch1 Debian configuration management sy
ii iproute 20061002-3 Professional tools to control the
ii libc6 2.3.6.ds1-13etch5 GNU C Library: Shared libraries
ii libcap1 1:1.10-14 support for getting/setting POSIX.
ii libpam0g 0.79-5 Pluggable Authentication Modules l
ii libreadline5 5.2-2 GNU readline and history libraries
ii logrotate 3.7.1-3 Log rotation utility
quagga recommends no packages.
-- debconf information:
quagga/really_stop: false
--- End Message ---
--- Begin Message ---
Hello
This is fixed in the latest 0.99.18 according to:
https://bugzilla.quagga.net/show_bug.cgi?id=442
bye,
-christian-
--- End Message ---
