Re: piranha stop balancing
Cyrille Mertes <[email protected]>
| Newsgroups | gmane.linux.redhat.piranha |
|---|---|
| Message-ID | <[email protected]> |
I didn't find any links on the redhat advanced server website to
download the src rpm of pirnaha ? I try google.com, the download site of
redhat but I found only the rmps...
Any links to help me ?
Thanks,
Cyrille.
Jeff Bearer wrote:
>I don't know if it will help, but as a suggestion I offer, upgrade
>piranha, download the src rpm from the Red Hat Advanced Server website
>and compile it, it will run fine on both 7.2 and 7.3 that I've tried it
>on.
>
>On Thu, 2002-11-14 at 17:00, Cyrille Mertes wrote:
>
>
>>Hi,
>>
>>My configuration :
>>
>>One NFS : Linux 2.4.7-10, Red Hat Linux release 7.2
>>
>>Three Web Servers : Linux 2.4.7-10, Red Hat Linux release 7.2
>>
>>Two LB (one primary and one secondary) : Linux 2.4.18, Red Hat Linux
>>release 7.2
>>
>>ipvsadm version 1.20
>>
>>piranha 0.6.1
>>
>>So, I have three virtual servers (public) with three real servers
>>(locals). See lvs.conf at the end of this email. I use direct routing.
>>
>>I think I have an nfs configuration problem because, when the load is
>>approximately at 2 on the nfs, all my httpd process on my web server are
>>in state D (waiting for device) and they can't access the data on the
>>nfs and the load increase on the web server (10 and more). I have a
>>script on the web serveur which stop apache when the load is more than
>>10 . So when the script stop apache on the three web server piranah stop
>>working and I have to restart piranha on the load balancer.
>>
>>Sometimes I think piranha stop load balancing only on one virtual server
>>???? And again, I have to restart pulse...
>>
>>Someone can help me to solve these problems ?
>>
>>Thanks,
>>
>>Cyrille.
>>
>>
>>
>>
>>
>>Nov 14 10:50:35 poof nanny[25084]: CONNECT to 192.168.6.13:8008 timed out
>> > Nov 14 10:50:35 poof nanny[25084]: shutting down 192.168.6.13:8008 due
>> > to connection failure
>> > Nov 14 10:50:35 poof nanny[25114]: CONNECT to 192.168.6.13:80 timed out
>> > Nov 14 10:50:35 poof nanny[25114]: shutting down 192.168.6.13:80 due to
>> > connection failure
>> > Nov 14 10:50:47 poof nanny[25114]: CONNECT to 192.168.6.13:80 timed out
>> > Nov 14 10:50:52 poof nanny[25084]: making 192.168.6.13:8008 available
>> > Nov 14 10:50:59 poof nanny[25114]: making 192.168.6.13:80 available
>> > Nov 14 10:55:16 poof ucd-snmp[27282]: Connection from 216.187.127.21
>> > Nov 14 10:55:17 poof last message repeated 3 times
>> > Nov 14 10:55:30 poof nanny[25077]: READ to 192.168.6.14:80 timed out
>> > Nov 14 10:55:30 poof nanny[25077]: shutting down 192.168.6.14:80 due to
>> > connection failure
>> > Nov 14 10:55:30 poof nanny[25115]: READ to 192.168.6.14:80 timed out
>> > Nov 14 10:55:30 poof nanny[25115]: shutting down 192.168.6.14:80 due to
>> > connection failure
>> > Nov 14 10:55:30 poof nanny[25101]: READ to 192.168.6.14:80 timed out
>> > Nov 14 10:55:30 poof nanny[25101]: shutting down 192.168.6.14:80 due to
>> > connection failure
>> > Nov 14 10:55:31 poof nanny[25100]: READ to 192.168.6.13:80 timed out
>> > Nov 14 10:55:31 poof nanny[25100]: shutting down 192.168.6.13:80 due to
>> > connection failure
>> > Nov 14 10:55:37 poof sshd(pam_unix)[25349]: session opened for user leia
>> > by (uid=0)
>> > Nov 14 10:55:37 poof sshd(pam_unix)[25349]: session closed for user leia
>> > Nov 14 10:55:40 poof nanny[25077]: READ returned error 104:Connection
>> > reset by peer
>> > Nov 14 10:55:40 poof nanny[25115]: READ returned error 104:Connection
>> > reset by peer
>> > Nov 14 10:55:40 poof nanny[25101]: READ returned error 104:Connection
>> > reset by peer
>> > Nov 14 10:55:43 poof nanny[25100]: READ returned error 104:Connection
>> > reset by peer
>> > Nov 14 10:55:43 poof nanny[25114]: READ returned error 104:Connection
>> > reset by peer
>> > Nov 14 10:55:43 poof nanny[25114]: shutting down 192.168.6.13:80 due to
>> > connection failure
>> > Nov 14 10:55:43 poof nanny[25073]: READ returned error 104:Connection
>> > reset by peer
>> > Nov 14 10:55:43 poof nanny[25073]: shutting down 192.168.6.13:80 due to
>> > connection failure
>> > Nov 14 10:55:46 poof nanny[25113]: READ to 192.168.6.12:80 timed out
>> > Nov 14 10:55:46 poof nanny[25113]: shutting down 192.168.6.12:80 due to
>> > connection failure
>> > Nov 14 10:55:47 poof nanny[25099]: READ to 192.168.6.12:80 timed out
>> > Nov 14 10:55:47 poof nanny[25099]: shutting down 192.168.6.12:80 due to
>> > connection failure
>> > Nov 14 10:55:47 poof nanny[25072]: READ to 192.168.6.12:80 timed out
>> > Nov 14 10:55:47 poof nanny[25072]: shutting down 192.168.6.12:80 due to
>> > connection failure
>> > Nov 14 10:55:58 poof nanny[25113]: READ to 192.168.6.12:80 timed out
>> > Nov 14 10:55:59 poof nanny[25072]: READ to 192.168.6.12:80 timed out
>> > Nov 14 10:56:02 poof nanny[25099]: READ to 192.168.6.12:80 timed out
>> > Nov 14 10:56:07 poof nanny[25113]: READ returned error 104:Connection
>> > reset by peer
>> > Nov 14 10:56:08 poof nanny[25072]: READ returned error 104:Connection
>> > reset by peer
>> > Nov 14 10:56:08 poof pulse[25064]: Terminating due to signal 15
>> > Nov 14 10:56:08 poof lvs[25068]: shutting down due to signal 15
>> > Nov 14 10:56:08 poof lvs[25068]: shutting down virtual service
>> > sebulba_http_122
>> > Nov 14 10:56:08 poof nanny[25072]: Terminating due to signal 15
>> > Nov 14 10:56:08 poof nanny[25073]: Terminating due to signal 15
>> > Nov 14 10:56:08 poof nanny[25077]: Terminating due to signal 15
>> > Nov 14 10:56:08 poof lvs[25068]: shutting down virtual service
>> > sebulba_vadmin_122
>> > Nov 14 10:56:08 poof nanny[25083]: Terminating due to signal 15
>> > Nov 14 10:56:08 poof nanny[25084]: Terminating due to signal 15
>> > Nov 14 10:56:08 poof nanny[25089]: Terminating due to signal 15
>> > Nov 14 10:56:08 poof lvs[25068]: shutting down virtual service
>> > sebulba_http_123
>> > Nov 14 10:56:08 poof nanny[25099]: Terminating due to signal 15
>> > Nov 14 10:56:08 poof nanny[25100]: Terminating due to signal 15
>> > Nov 14 10:56:08 poof nanny[25101]: Terminating due to signal 15
>> > Nov 14 10:56:08 poof lvs[25068]: shutting down virtual service
>> > sebulba_vadmin_123
>> > Nov 14 10:56:08 poof nanny[25103]: Terminating due to signal 15
>> > Nov 14 10:56:08 poof nanny[25106]: Terminating due to signal 15
>> > Nov 14 10:56:08 poof nanny[25107]: Terminating due to signal 15
>> > Nov 14 10:56:08 poof lvs[25068]: shutting down virtual service
>> > sebulba_http_124
>> > Nov 14 10:56:08 poof nanny[25113]: Terminating due to signal 15
>> > Nov 14 10:56:08 poof nanny[25114]: Terminating due to signal 15
>> > Nov 14 10:56:08 poof nanny[25115]: Terminating due to signal 15
>> > Nov 14 10:56:09 poof lvs[25068]: shutting down virtual service
>> > sebulba_vadmin_124
>> > Nov 14 10:56:09 poof nanny[25117]: Terminating due to signal 15
>> > Nov 14 10:56:09 poof nanny[25118]: Terminating due to signal 15Nov 14
>> > 10:56:09 poof lvs[25068]: shutting down virtual service lumiva_pop_130
>> > Nov 14 10:56:09 poof nanny[25126]: Terminating due to signal 15
>> > Nov 14 10:56:09 poof nanny[25127]: Terminating due to signal 15
>> > Nov 14 10:56:09 poof lvs[25068]: shutting down virtual service
>> > lumiva_smtp_25
>> > Nov 14 10:56:09 poof nanny[25130]: Terminating due to signal 15
>> > Nov 14 10:56:09 poof nanny[25131]: Terminating due to signal 15
>> > Nov 14 10:56:09 poof pulse: pulse shutdown succeeded
>> > Nov 14 10:56:09 poof pulse[25434]: STARTING PULSE AS MASTER
>> > Nov 14 10:56:09 poof pulse: pulse startup succeeded
>>
>>
>>serial_no = 293
>>primary = 216.187.127.118
>>primary_private = 192.168.6.11
>>service = lvs
>>backup_active = 1
>>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 = NONE
>>
>>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 = wlc
>> 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 = wlc
>> 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 = wlc
>> 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
>> }
>>}
>>
>>
>>
>>
>>
>>
>>
>>
>>_______________________________________________
>>Piranha-list mailing list
>>[email protected]
>>https://listman.redhat.com/mailman/listinfo/piranha-list
>>
>>