Re: Other strange LB balancing issue

Cyrille Mertes <[email protected]>
Newsgroups gmane.linux.redhat.piranha
Message-ID <[email protected]>
>>The logs you sent are not in sync with the configuration file you sent.
>>Port 8008 is sometimes referenced in the logs whereas it never appears
>>in the conf :(
>>Nanny is launched more than twice per RS whereas each RS it is never
>>used by more than 2 virtual servers.

Ok, I'm sorry. It's only because I didn't cut/paste all my configuration 
file :

serial_no = 344
primary = 216.187.127.77
primary_private = 192.168.6.21
service = lvs
backup_active = 0
backup = 216.187.127.117
backup_private = 192.168.6.10
heartbeat = 1
heartbeat_port = 539
keepalive = 6
deadtime = 15
network = direct
nat_nmask = 255.255.255.255
reservation_conflict_action = preempt
debug_level = MAX
virtual sebulba_http_122 {
     active = 1
     address = 216.187.127.122 eth0:1
     vip_nmask = 255.255.255.0
     port = 80
     send = "GET / HTTP/1.0\r\n\r\n"
     expect = "HTTP"
     load_monitor = none
     scheduler = wrr
     protocol = tcp
     timeout = 6
     reentry = 15
     quiesce_server = 0
     server motti {
         address = 192.168.6.12
         active = 1
         weight = 2
     }
     server gragra {
         address = 192.168.6.13
         active = 1
         weight = 1
     }
     server koon {
         address = 192.168.6.14
         active = 1
         weight = 2
     }
}
virtual sebulba_vadmin_122 {
     active = 1
     address = 216.187.127.122 eth0:1
     vip_nmask = 255.255.255.0
     port = 8008
     send = "GET / HTTP/1.0\r\n\r\n"
     expect = "HTTP"
     load_monitor = none
     scheduler = rr
     protocol = tcp
     timeout = 6
     reentry = 15
     quiesce_server = 0
     server motti {
         address = 192.168.6.12
         active = 1
         weight = 1
     }
     server gragra {
         address = 192.168.6.13
         active = 1
         weight = 1
     }
     server koon {
         address = 192.168.6.14
         active = 1
         weight = 1
     }
}
virtual sebulba_http_123 {
     active = 1
     address = 216.187.127.123 eth0:2
     vip_nmask = 255.255.255.0
     port = 80
     send = "GET / HTTP/1.0\r\n\r\n"
     expect = "HTTP"
     load_monitor = none
     scheduler = rr
     protocol = tcp
     timeout = 6
     reentry = 15
     quiesce_server = 0
     server motti {
         address = 192.168.6.12
         active = 1
         weight = 1
     }
     server gragra {
         address = 192.168.6.13
         active = 1
         weight = 1
     }
     server koon {
         address = 192.168.6.14
         active = 1
         weight = 1
     }
}

virtual sebulba_vadmin_123 {
     active = 1
     address = 216.187.127.123 eth0:2
     vip_nmask = 255.255.255.0
     port = 8008
     send = "GET / HTTP/1.0\r\n\r\n"
     expect = "HTTP"
     load_monitor = none
     scheduler = rr
     protocol = tcp
     timeout = 6
     reentry = 15
     quiesce_server = 0
     server motti {
         address = 192.168.6.12
         active = 1
         weight = 1
     }
     server gragra {
         address = 192.168.6.13
         active = 1
         weight = 1
     }
     server koon {
         address = 192.168.6.14
         active = 1
         weight = 1
     }
}
virtual sebulba_http_124 {
     active = 1
     address = 216.187.127.124 eth0:3
     vip_nmask = 255.255.255.0
     port = 80
     send = "GET / HTTP/1.0\r\n\r\n"
     expect = "HTTP"
     load_monitor = none
     scheduler = wrr
     protocol = tcp
     timeout = 6
     reentry = 15
     quiesce_server = 0
     server motti {
         address = 192.168.6.12
         active = 1
         weight = 1
     }
     server gragra {
         address = 192.168.6.13
         active = 1
         weight = 2
     }
     server koon {
         address = 192.168.6.14
         active = 1
         weight = 1
     }
}
virtual sebulba_vadmin_124 {
     active = 1
     address = 216.187.127.124 eth0:3
     vip_nmask = 255.255.255.0
     port = 8008
     send = "GET / HTTP/1.0\r\n\r\n"
     expect = "HTTP"
     load_monitor = none
     scheduler = rr
     protocol = tcp
     timeout = 6
     reentry = 15
     quiesce_server = 0
     server motti {
         address = 192.168.6.12
         active = 1
         weight = 1
     }
     server gragra {
         address = 192.168.6.13
         active = 1
         weight = 1
     }
     server koon {
         address = 192.168.6.14
         active = 1
         weight = 1
     }
}
virtual lumiva_pop_130 {
     active = 1
     address = 216.187.127.130 eth0:4
     vip_nmask = 255.255.255.0
     port = 110
     expect = "+OK"
     load_monitor = none
     scheduler = rr
     protocol = tcp
     timeout = 6
     reentry = 15
     quiesce_server = 0
     server anor {
         address = 192.168.6.19
         active = 1
         weight = 1
     }
     server hill {
         address = 192.168.6.18
         active = 1
         weight = 1
     }
}
virtual lumiva_smtp_25 {
     active = 1
     address = 216.187.127.130 eth0:4
     vip_nmask = 255.255.255.0
     port = 25
     expect = "220"
     load_monitor = none
     scheduler = rr
     protocol = tcp
     timeout = 6
     reentry = 15
     quiesce_server = 0
     server anor {
         address = 192.168.6.19
         active = 1
         weight = 1
     }
     server hill {
         address = 192.168.6.18
         active = 1
         weight = 1
     }
}


And the ipvsadm output :


IP Virtual Server version 1.0.4 (size=65536)
Prot LocalAddress:Port Scheduler Flags
  -> RemoteAddress:Port           Forward Weight ActiveConn InActConn
TCP  216.187.127.124:http wrr
  -> gragra.privatedns.com:http   Route   2      203        430
  -> koon.privatedns.com:http     Route   1      84         230
  -> motti.privatedns.com:http    Route   1      79         217
TCP  216.187.127.123:http-alt rr
  -> gragra.privatedns.com:http-alt Route   1      0          0
  -> motti.privatedns.com:http-alt Route   1      0          0
  -> koon.privatedns.com:http-alt Route   1      0          0
TCP  216.187.127.122:http-alt rr
  -> gragra.privatedns.com:http-alt Route   1      0          0
  -> motti.privatedns.com:http-alt Route   1      0          1
  -> koon.privatedns.com:http-alt Route   1      0          1
TCP  216.187.127.122:http wrr
  -> gragra.privatedns.com:http   Route   1      145        389
  -> motti.privatedns.com:http    Route   2      225        768
  -> koon.privatedns.com:http     Route   2      239        762
TCP  216.187.127.124:http-alt rr
  -> gragra.privatedns.com:http-alt Route   1      0          0
  -> koon.privatedns.com:http-alt Route   1      0          0
  -> motti.privatedns.com:http-alt Route   1      0          0
TCP  216.187.127.123:http rr
  -> gragra.privatedns.com:http   Route   1      0          2
  -> koon.privatedns.com:http     Route   1      1          4
  -> motti.privatedns.com:http    Route   1      1          3
TCP  lumiva.privatedns.com:smtp rr
  -> 192.168.6.18:smtp            Route   1      0          0
  -> 192.168.6.19:smtp            Route   1      0          0
TCP  lumiva.privatedns.com:pop3 rr
  -> 192.168.6.19:pop3            Route   1      0          0
  -> 192.168.6.18:pop3            Route   1      0          0




Cyrille.



Sébastien Bonnet wrote:

>Cross-posting to piranha mailing-list as it does sound like an LVS
>problem but more likely a piranha one.
>
>  
>
>>Actual LB : redhat 8.0, kernel 2.4.18-14, IP Virtual Server version
>>1.0.4 (source), piranha-0.7.0-3 (source)
>>    
>>
>
>I'm running quite fine with RH7.3 2.4.18-10 IPVS 1.0.6 & piranha 0.7.0-3
>with personal patches. Never got your current problem.
>
>The logs you sent are not in sync with the configuration file you sent.
>Port 8008 is sometimes referenced in the logs whereas it never appears
>in the conf :(
>Nanny is launched more than twice per RS whereas each RS it is never
>used by more than 2 virtual servers.
>
>Check your lvs.cf and iptables rules. Make sure you don't have any ARP
>issue and your routing is OK.
>Finally "killall -9 pulse lvs fos nanny" and restart pulse.
>
>  
>
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.