i just correlated our ftp server on our web machine taking a very long time to
respond and firing off our monitor warnings with a particular guest i am
working on on another machine. when it crashes on stopping, the web server
ftp goes critical. after i bring the guest back up and it works properly, the
ftp server on the other machine works fine... that particular machine is a
RH9 machine...
could something in my iproute2 config cause this? here is my host config for
the ethernet card on that particular leg of the network.
the web machine/ftp is running on 64.113.39.8 and there are approx 140 ip
addresses upward from 39.11 in its configuration.
the particular guest that appears to be the cause of it when it crashes is at
64.113.39.5.
could a crash cause some kind of screaming to happen?
should i maybe have my rules set for each individual ip rather than the entire
block? so it would be rules_eth2=( "from 64.113.39.5 table 39net" )?
this config and code is in my /etc/conf.d/net on the host machine
modules=( "iproute2" )
config_eth2=( "64.113.39.254 netmask 255.255.255.0 broadcast 64.113.39.255" )
routes_eth2=( "64.113.39.0/24 src 64.113.39.254 table 39net" )
routes_eth2=( "default via 64.113.39.1 table 39net" )
rules_eth2=( "from 64.113.39.0/24 table 39net" )
then some rules code i received from a gentoo developer that he used:
flush_route_cache() {
ebegin "Flushing route cache for ${IFACE}"
ip route flush cache dev ${IFACE}
ret=$?
eend $ret
return $ret
}
ip_rule_runner() {
cmd="$1"
case ${IFACE} in
eth2) rules=( "[EMAIL PROTECTED]" ) ;;
eth1) rules=( "[EMAIL PROTECTED]" ) ;;
eth0) rules=( "[EMAIL PROTECTED]" ) ;;
esac
max=$(([EMAIL PROTECTED] - 1))
cmd="ip rule ${cmd}"
for ln in `seq 0 $max`; do
ebegin " ${cmd} ${rules[$ln]}"
${cmd} ${rules[$ln]}
eend $?
done
}
postup() {
einfo "Adding rules"
ip_rule_runner add
flush_route_cache
}
predown() {
einfo "Removing rules"
ip_rule_runner del
flush_route_cache
}
--
Chuck
_______________________________________________
Vserver mailing list
Vserver@list.linux-vserver.org
http://list.linux-vserver.org/mailman/listinfo/vserver
