Your message dated Mon, 25 Jul 2011 23:26:02 +0200
with message-id
<cafx5sby2fwduso1hcx85pfmbahfc+f5v9pkxwf0+bbfty8v...@mail.gmail.com>
and subject line Solved since 1.10-1
has caused the Debian Bug report #635135,
regarding ethtool has wrong path in /etc/ctdb/events.d/10.interface
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.)
--
635135: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=635135
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: ctdb
Version: 1.0.112-12-1
Severity: important
Tags: squeeze patch
The script 10.interface incorrectly uses /usr/sbin/ethtool instead of
/sbin/ethtool. This makes ctdb goes in an unhealthy state.
The fix is easy (see attached patch).
This is a stability patch and I plan to upload it to squeeze-proposed-updates.
Index: ctdb-1.0.112-12/config/events.d/10.interface
===================================================================
--- ctdb-1.0.112-12.orig/config/events.d/10.interface 2011-07-22 23:58:09.000000000 +0200
+++ ctdb-1.0.112-12/config/events.d/10.interface 2011-07-22 23:58:34.000000000 +0200
@@ -164,13 +164,13 @@
;;
*)
[ -z "$IFACE" ] || {
- /usr/sbin/ethtool $IFACE | grep -q 'Link detected: yes' || {
+ ethtool $IFACE | grep -q 'Link detected: yes' || {
# On some systems, this is not successful when a
# cable is plugged but the interface has not been
# brought up previously. Bring the interface up and
# try again...
/sbin/ip link set $IFACE up
- /usr/sbin/ethtool $IFACE | grep -q 'Link detected: yes' || {
+ ethtool $IFACE | grep -q 'Link detected: yes' || {
echo "ERROR: No link on the public network interface $IFACE"
exit 1
}
--- End Message ---
--- Begin Message ---
Version: 1.10-1
This bug was solved post 1.0.113. The fix is in 1.10.
This is still to be fixed in squeeze.
--
Mathieu
--- End Message ---
