Just some general notes on debugging. Debug verbose levels: - 1 is least verbose - 12 is most verbose - 0 disables debugging Kernel needs to be compiled with CONFIG_IP_VS_DEBUG=y To get even more det
2013/8/26 Julian Anastasov <ja@xxxxxx>: This explains why expire time from "ipvsadm -lcn" keeps at 5.00min. Again, thanks for your explanation, now I understand all these "weird" things, it's all bec
Hello, OK, I was worried that my recent RCU changes broke something in the WRR scheduler and the configuration process. OK, I have no more doubts. To summarize, here is what I think happened: - packe
Good news, I finally found the crap source, it's keepalived. I tested several times without keepalived in runlevel 3, after kernel boots I add the ipvs service by hand: ./ipvsadm -C sleep 1 echo 20 >
2013/8/24 Julian Anastasov <ja@xxxxxx>: Sure, ops is always there. Also sure. Badly, Conns is a fixed number and Conns/s is zero. vs3 ~ # cat /proc/net/ip_vs_stats_percpu Total Incoming Outgoing Inco
Hello, In first email you said that traffic goes to single server, is it first in list or what is its position? Can you also check if sleep 1 solves the problem: ipvsadm -C && sleep 1 && ipvsadm -R <
Hello, Whatever is your preference, it does not matter for me. With traffic you risk to flood log in director, for 10ms we get ~600 packets. I think, even usleep 1000 will work. And I'm not sure what
I'll provide those test result later. So, about debug, do you mean when I find OPS is not working, then cutoff the traffic, turn on debug with "echo 20 > /proc/sys/net/ipv4/vs/debug_level", and then
Hello, There is no "./" in above ipvsadm commands, I hope you put everything in scripts to make sure the new ipvsadm binary is used. My tests are on 32-bit UP, may be that is why I can not reproduce
2013/8/23 Julian Anastasov <ja@xxxxxx>: No,ingress traffic is always on going. I'm running x86_64 kernel. I compared kernel config of my two servers, a big difference between them is CONFIG_PREEMPT.
2013/8/22 Julian Anastasov <ja@xxxxxx>: I noticed this too. While ops working, the InActConn is always changing too, if it's fixed, the ops is not working. After every restore, the stats also zeroed,
Hello, The OPS connections are accounted in InActConn for a very short period, they live up to 1 jiffie, eg. 10ms. Also, WRR should be reliable for OPS while other schedulers (eg. *LC) are not suitab
2013/8/22 Julian Anastasov <ja@xxxxxx>: Thanks, this resolved my first problem :D Still no lucky here, ops is set in running config, but it's not like that in real world. vs3 ~ # cat /proc/net/ip_vs
Hello, Can you try with recent ipvsadm from git: git clone git://git.kernel.org/pub/scm/utils/kernel/ipvsadm/ipvsadm.git I see related commit that will print -o for the OPS feature: ipvsadm: Fix wron
Need help here, thank you for replying :-) I'm setting up a syslog cluster based on IPVS, all UDP datagrams sent from firewall with fixed source IP and fixed source port, so pseudo-random balancing b