ipvsman-users Mailing List for ipvsman - more than a GUI for ipvs
Status: Alpha
Brought to you by:
volkerjaenisch
Menu
▾
▴
ipvsman-users — Discussion on the ipvsman GUI
You can subscribe to this list here.
| 2007 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(9) |
Jun
|
Jul
(28) |
Aug
(1) |
Sep
|
Oct
|
Nov
|
Dec
|
|---|
|
From: Dr. V. J. <vol...@in...> - 2007-08-09 09:54:20
|
Hi Gerry! Gerry Reno schrieb: > > ipvsman: > 2007-07-29 23:17:31,328 INFO : Daemon created > 2007-07-29 23:17:31,330 INFO : IPVSadm constructed > 2007-07-29 23:17:31,330 INFO : Config constructed > 2007-07-29 23:17:31,331 INFO : build gui instance > 2007-07-29 23:17:31,332 INFO : starting reinit > 2007-07-29 23:17:31,332 INFO : reading topology of cluster > 2007-07-29 23:17:31,335 WARNING : Keepalived.conf parameter > 'vrrp_instance' not implemented yet > 2007-07-29 23:17:31,336 WARNING : Keepalived.conf parameter 'vipn' not > implemented yet > As you may see here there is a parsing problem with your keepalived.conf file. The VRRP-Stuff is not included in the parser yet. I will look at this issue as soon as possible. Best Regards, Volker -- ==================================================== inqbus it-consulting +49 ( 341 ) 5643800 Dr. Volker Jaenisch http://www.inqbus.de Herloßsohnstr. 12 0 4 1 5 5 Leipzig N O T - F Ä L L E +49 ( 170 ) 3113748 ==================================================== |
|
From: Gerry R. <gr...@ve...> - 2007-07-30 03:51:45
|
Dr. Volker Jaenisch wrote:
> Hi Gerry!
>
> Gerry Reno schrieb:
>
>> The problem is actually somewhat different. When I have keepalived
>> running on both directors everything is fine and 'ipvsadm -l' shows
>> correctly. Now I start ipvsmand on one of the directors and launch
>> ipvsman and there are no servers. Now when I check 'ipvsadm -l' there
>> are also no servers. So ipvsmand is doing something to LVS and it is not
>> happy. Have you seen this behavior? Is there a workaround?
>>
>>
> This is to less information even to get an idea of whats goin on.
> Also I noticed the ongoing discussions on the LVS-List concerning your setup.
>
> Ipvsman/d is a highlevel tool. It relies on the IPVS-Layer. If this layer is not consistent ipvsmam/d will fail.
>
> * Please post your keepalived.conf
> * Your ipvsadm dump
> * your log of ipvsman/d
>
> If there is no significant hint in the log etc. then please start ipvsmand on console with the -D switch and post the stacktrace if there is any.
>
>
Here is what I see:
[root@grp-01-00-50 ~]# ipvsadm -l <------ all entries
except 10.3.0.3 are in /etc/keepalived/keepalived.conf (notice path)
IP Virtual Server version 1.2.1 (size=4096)
Prot LocalAddress:Port Scheduler Flags
-> RemoteAddress:Port Forward Weight ActiveConn InActConn
TCP 192.168.1.240:https rr persistent 600
-> 192.168.1.201:https Route 1 0 0
-> 192.168.1.200:https Route 1 0 0
TCP 10.3.0.3:http wlc persistent 600
TCP 192.168.1.240:http rr persistent 600
-> 192.168.1.201:http Route 1 0 0
-> 192.168.1.200:http Route 1 0 0
TCP 192.168.1.240:ssh rr persistent 600
-> 192.168.1.201:ssh Route 1 0 0
-> 192.168.1.200:ssh Route 1 0 0
[root@grp-01-00-50 ~]# service ipvsmand start
Starting ipvs monitoring daemon: ipvsmand.
[root@grp-01-00-50 ~]# ipvsadm -l
<------ notice all entries from /etc/keepalived/keepalived.conf are gone
IP Virtual Server version 1.2.1 (size=4096)
Prot LocalAddress:Port Scheduler Flags
-> RemoteAddress:Port Forward Weight ActiveConn InActConn
TCP 10.3.0.3:http wlc persistent 600
[root@grp-01-00-50 ~]#
[root@grp-01-00-50 ~]#
[root@grp-01-00-50 ~]# ipvsman <--- nothing in here
[root@grp-01-00-50 ~]# service ipvsmand stop
Stopping ipvs monitoring daemon: ipvsmand.
[root@grp-01-00-50 ~]# ipvsadm -l
IP Virtual Server version 1.2.1 (size=4096)
Prot LocalAddress:Port Scheduler Flags
-> RemoteAddress:Port Forward Weight ActiveConn InActConn
TCP 10.3.0.3:http wlc persistent 600
[root@grp-01-00-50 ~]# ipvsadm -l <--------- in another window
I restart keepalived just before this command
IP Virtual Server version 1.2.1 (size=4096) <------- and now all
entries are back.
Prot LocalAddress:Port Scheduler Flags
-> RemoteAddress:Port Forward Weight ActiveConn InActConn
TCP 192.168.1.240:https rr persistent 600
-> 192.168.1.201:https Route 1 0 0
-> 192.168.1.200:https Route 1 0 0
TCP 10.3.0.3:http wlc persistent 600
TCP 192.168.1.240:http rr persistent 600
-> 192.168.1.201:http Route 1 0 0
-> 192.168.1.200:http Route 1 0 0
TCP 192.168.1.240:ssh rr persistent 600
-> 192.168.1.201:ssh Route 1 0 0
-> 192.168.1.200:ssh Route 1 0 0
# end
LOGS:
ipvsmand:
2007-07-29 23:17:22,528 INFO : Daemon created
2007-07-29 23:17:22,555 INFO : IPVSadm constructed
2007-07-29 23:17:22,556 INFO : Config constructed
2007-07-29 23:17:22,556 INFO : reinit master daemon
2007-07-29 23:17:22,557 INFO : starting reinit
2007-07-29 23:17:22,591 DEBUG : ipvsadm -C ; cat
/var/lib/ipvsman/ipvscfg-2007-07-04_13:17 | ipvsadm -R
2007-07-29 23:17:22,595 INFO : IPVS initialized with desired config
2007-07-29 23:17:22,595 INFO : reading topology of cluster
2007-07-29 23:17:22,641 DEBUG : Service created: tcp:10.3.0.3:80
2007-07-29 23:17:22,642 DEBUG : Real created: tcp:172.18.1.13:80
2007-07-29 23:17:22,643 DEBUG : Real created: tcp:172.18.1.12:80
2007-07-29 23:17:22,644 DEBUG : Real created: tcp:172.18.1.11:80
2007-07-29 23:17:22,644 WARNING : No tester defined for real
tcp:172.18.1.9:80
2007-07-29 23:17:22,645 DEBUG : Real created: tcp:172.18.1.9:80
2007-07-29 23:17:22,645 INFO : reading desired IPVS config
2007-07-29 23:17:22,646 INFO : actual config
/var/lib/ipvsman/ipvscfg-2007-07-04_13:17
2007-07-29 23:17:22,648 INFO : desired IPVS config read
2007-07-29 23:17:22,664 DEBUG : found knowm running service :
tcp:10.3.0.3:80
2007-07-29 23:17:22,695 INFO : status parsed
2007-07-29 23:17:22,696 INFO : option Daemon
2007-07-29 23:17:22,698 INFO : sleeping 30 secs : 2
2007-07-29 23:17:52,699 INFO : sleeping 30 secs : 2
2007-07-29 23:18:22,700 INFO : sleeping 30 secs : 2
2007-07-29 23:18:52,701 INFO : sleeping 30 secs : 2
2007-07-29 23:19:22,703 INFO : sleeping 30 secs : 2
2007-07-29 23:19:52,705 INFO : sleeping 30 secs : 2
2007-07-29 23:20:01,635 INFO : Daemon created
2007-07-29 23:20:01,637 INFO : IPVSadm constructed
2007-07-29 23:20:01,638 INFO : Config constructed
2007-07-29 23:20:01,638 INFO : reinit master daemon
2007-07-29 23:20:01,639 INFO : starting reinit
2007-07-29 23:20:01,676 DEBUG : ipvsadm -C ; cat
/var/lib/ipvsman/ipvscfg-2007-07-04_13:17 | ipvsadm -R
2007-07-29 23:20:01,677 INFO : IPVS initialized with desired config
2007-07-29 23:20:01,678 INFO : reading topology of cluster
2007-07-29 23:20:01,683 DEBUG : Service created: tcp:10.3.0.3:80
2007-07-29 23:20:01,684 DEBUG : Real created: tcp:172.18.1.13:80
2007-07-29 23:20:01,685 DEBUG : Real created: tcp:172.18.1.12:80
2007-07-29 23:20:01,686 DEBUG : Real created: tcp:172.18.1.11:80
2007-07-29 23:20:01,687 WARNING : No tester defined for real
tcp:172.18.1.9:80
2007-07-29 23:20:01,687 DEBUG : Real created: tcp:172.18.1.9:80
2007-07-29 23:20:01,688 INFO : reading desired IPVS config
2007-07-29 23:20:01,689 INFO : actual config
/var/lib/ipvsman/ipvscfg-2007-07-04_13:17
2007-07-29 23:20:01,691 INFO : desired IPVS config read
2007-07-29 23:20:01,707 DEBUG : found knowm running service :
tcp:10.3.0.3:80
2007-07-29 23:20:01,731 INFO : status parsed
2007-07-29 23:20:01,732 INFO : option Daemon
2007-07-29 23:20:01,734 INFO : sleeping 30 secs : 2
2007-07-29 23:20:31,735 INFO : sleeping 30 secs : 2
2007-07-29 23:21:01,736 INFO : sleeping 30 secs : 2
2007-07-29 23:21:31,738 INFO : sleeping 30 secs : 2
ipvsman:
2007-07-29 23:17:31,328 INFO : Daemon created
2007-07-29 23:17:31,330 INFO : IPVSadm constructed
2007-07-29 23:17:31,330 INFO : Config constructed
2007-07-29 23:17:31,331 INFO : build gui instance
2007-07-29 23:17:31,332 INFO : starting reinit
2007-07-29 23:17:31,332 INFO : reading topology of cluster
2007-07-29 23:17:31,335 WARNING : Keepalived.conf parameter
'vrrp_instance' not implemented yet
2007-07-29 23:17:31,336 WARNING : Keepalived.conf parameter 'vipn' not
implemented yet
2007-07-29 23:17:31,337 WARNING : Keepalived.conf parameter 'state' not
implemented yet
2007-07-29 23:17:31,337 WARNING : Keepalived.conf parameter 'interface'
not implemented yet
2007-07-29 23:17:31,338 WARNING : Keepalived.conf parameter
'track_interface' not implemented yet
2007-07-29 23:17:31,338 WARNING : Keepalived.conf parameter 'eth0' not
implemented yet
2007-07-29 23:17:31,339 WARNING : Keepalived.conf parameter
'lvs_sync_daemon_interface' not implemented yet
2007-07-29 23:17:31,339 WARNING : Keepalived.conf parameter
'virtual_router_id' not implemented yet
2007-07-29 23:17:31,340 WARNING : Keepalived.conf parameter 'priority'
not implemented yet
2007-07-29 23:17:31,340 WARNING : Keepalived.conf parameter 'advert_int'
not implemented yet
2007-07-29 23:17:31,341 WARNING : Keepalived.conf parameter
'authentication' not implemented yet
2007-07-29 23:17:31,342 WARNING : Keepalived.conf parameter 'auth_type'
not implemented yet
2007-07-29 23:17:31,342 WARNING : Keepalived.conf parameter 'auth_pass'
not implemented yet
2007-07-29 23:17:31,342 WARNING : Keepalived.conf parameter
'virtual_ipaddress' not implemented yet
2007-07-29 23:17:31,343 WARNING : Keepalived.conf parameter
'notify_master' not implemented yet
2007-07-29 23:17:31,344 WARNING : Keepalived.conf parameter 'del' not
implemented yet
2007-07-29 23:17:31,344 WARNING : Keepalived.conf parameter
'192.168.1.1' not implemented yet
2007-07-29 23:17:31,344 WARNING : Keepalived.conf parameter
'notify_backup' not implemented yet
2007-07-29 23:17:31,345 WARNING : Keepalived.conf parameter 'add' not
implemented yet
2007-07-29 23:17:31,345 WARNING : Keepalived.conf parameter
'192.168.1.1' not implemented yet
2007-07-29 23:17:31,345 WARNING : Keepalived.conf parameter
'notify_fault' not implemented yet
2007-07-29 23:17:31,346 WARNING : Keepalived.conf parameter 'add' not
implemented yet
2007-07-29 23:17:31,346 WARNING : Keepalived.conf parameter
'192.168.1.1' not implemented yet
2007-07-29 23:17:31,347 WARNING : Keepalived.conf parameter 'lb_algo'
not implemented yet
2007-07-29 23:17:31,347 WARNING : Keepalived.conf parameter 'lb_kind'
not implemented yet
2007-07-29 23:17:31,348 WARNING : Keepalived.conf parameter
'persistence_timeout' not implemented yet
2007-07-29 23:17:31,349 WARNING : Keepalived.conf parameter
'inhibit_on_failure' not implemented yet
2007-07-29 23:17:31,349 WARNING : Keepalived.conf parameter '{' not
implemented yet
2007-07-29 23:17:31,350 WARNING : Keepalived.conf parameter '22' not
implemented yet
2007-07-29 23:17:31,350 WARNING : Keepalived.conf parameter '3' not
implemented yet
2007-07-29 23:17:31,351 WARNING : Keepalived.conf parameter '3' not
implemented yet
2007-07-29 23:17:31,351 WARNING : Keepalived.conf parameter '1' not
implemented yet
2007-07-29 23:17:31,352 WARNING : Keepalived.conf parameter
'inhibit_on_failure' not implemented yet
2007-07-29 23:17:31,352 WARNING : Keepalived.conf parameter '{' not
implemented yet
2007-07-29 23:17:31,353 WARNING : Keepalived.conf parameter '22' not
implemented yet
2007-07-29 23:17:31,353 WARNING : Keepalived.conf parameter '3' not
implemented yet
2007-07-29 23:17:31,353 WARNING : Keepalived.conf parameter '3' not
implemented yet
2007-07-29 23:17:31,354 WARNING : Keepalived.conf parameter '1' not
implemented yet
2007-07-29 23:17:31,355 WARNING : Keepalived.conf parameter 'lb_algo'
not implemented yet
2007-07-29 23:17:31,355 WARNING : Keepalived.conf parameter 'lb_kind'
not implemented yet
2007-07-29 23:17:31,356 WARNING : Keepalived.conf parameter
'persistence_timeout' not implemented yet
2007-07-29 23:17:31,357 WARNING : Keepalived.conf parameter
'inhibit_on_failure' not implemented yet
2007-07-29 23:17:31,358 WARNING : Keepalived.conf parameter '{' not
implemented yet
2007-07-29 23:17:31,359 WARNING : Keepalived.conf parameter '80' not
implemented yet
2007-07-29 23:17:31,359 WARNING : Keepalived.conf parameter '3' not
implemented yet
2007-07-29 23:17:31,359 WARNING : Keepalived.conf parameter '3' not
implemented yet
2007-07-29 23:17:31,360 WARNING : Keepalived.conf parameter '1' not
implemented yet
2007-07-29 23:17:31,360 WARNING : Keepalived.conf parameter
'inhibit_on_failure' not implemented yet
2007-07-29 23:17:31,361 WARNING : Keepalived.conf parameter '{' not
implemented yet
2007-07-29 23:17:31,361 WARNING : Keepalived.conf parameter '80' not
implemented yet
2007-07-29 23:17:31,362 WARNING : Keepalived.conf parameter '3' not
implemented yet
2007-07-29 23:17:31,362 WARNING : Keepalived.conf parameter '3' not
implemented yet
2007-07-29 23:17:31,362 WARNING : Keepalived.conf parameter '1' not
implemented yet
2007-07-29 23:17:31,363 WARNING : Keepalived.conf parameter 'lb_algo'
not implemented yet
2007-07-29 23:17:31,363 WARNING : Keepalived.conf parameter 'lb_kind'
not implemented yet
2007-07-29 23:17:31,364 WARNING : Keepalived.conf parameter
'persistence_timeout' not implemented yet
2007-07-29 23:17:31,364 WARNING : Keepalived.conf parameter
'inhibit_on_failure' not implemented yet
2007-07-29 23:17:31,365 WARNING : Keepalived.conf parameter '{' not
implemented yet
2007-07-29 23:17:31,365 WARNING : Keepalived.conf parameter '443' not
implemented yet
2007-07-29 23:17:31,366 WARNING : Keepalived.conf parameter '3' not
implemented yet
2007-07-29 23:17:31,366 WARNING : Keepalived.conf parameter '3' not
implemented yet
2007-07-29 23:17:31,366 WARNING : Keepalived.conf parameter '1' not
implemented yet
2007-07-29 23:17:31,367 WARNING : Keepalived.conf parameter
'inhibit_on_failure' not implemented yet
2007-07-29 23:17:31,368 WARNING : Keepalived.conf parameter '{' not
implemented yet
2007-07-29 23:17:31,368 WARNING : Keepalived.conf parameter '443' not
implemented yet
2007-07-29 23:17:31,369 WARNING : Keepalived.conf parameter '3' not
implemented yet
2007-07-29 23:17:31,369 WARNING : Keepalived.conf parameter '3' not
implemented yet
2007-07-29 23:17:31,370 WARNING : Keepalived.conf parameter '1' not
implemented yet
2007-07-29 23:17:31,370 INFO : reading desired IPVS config
2007-07-29 23:17:31,371 INFO : actual config
/var/lib/ipvsman/ipvscfg-2007-07-04_13:17
2007-07-29 23:17:31,372 DEBUG : Service created: tcp:10.3.0.3:80
2007-07-29 23:17:31,373 INFO : desired IPVS config read
2007-07-29 23:17:31,391 DEBUG : found knowm running service :
tcp:10.3.0.3:80
2007-07-29 23:17:31,406 INFO : status parsed
2007-07-29 23:17:31,408 DEBUG : serviceList :{'tcp:10.3.0.3:80':
tcp:10.3.0.3:80 s:tcp p:'600'}
2007-07-29 23:17:31,409 DEBUG : row :['tcp:10.3.0.3:80', 'nat', 'wlc',
'tcp', '600', ' run noTopo']
2007-07-29 23:17:31,411 INFO : run gui
2007-07-29 23:17:31,956 DEBUG : found knowm running service :
tcp:10.3.0.3:80
2007-07-29 23:17:40,882 INFO : reintialize gui
2007-07-29 23:17:40,884 DEBUG : serviceList :{'tcp:10.3.0.3:80':
tcp:10.3.0.3:80 s:tcp p:'600'}
2007-07-29 23:17:40,885 DEBUG : row :['tcp:10.3.0.3:80', 'nat', 'wlc',
'tcp', '600', ' run noTopo']
2007-07-29 23:19:46,577 INFO : Daemon created
2007-07-29 23:19:46,579 INFO : IPVSadm constructed
2007-07-29 23:19:46,579 INFO : Config constructed
2007-07-29 23:19:46,581 INFO : build gui instance
2007-07-29 23:19:46,582 INFO : starting reinit
2007-07-29 23:19:46,583 INFO : reading topology of cluster
2007-07-29 23:19:46,587 DEBUG : Service created: tcp:10.3.0.3:80
2007-07-29 23:19:46,588 DEBUG : Real created: tcp:172.18.1.13:80
2007-07-29 23:19:46,588 DEBUG : Real created: tcp:172.18.1.12:80
2007-07-29 23:19:46,589 DEBUG : Real created: tcp:172.18.1.11:80
2007-07-29 23:19:46,590 WARNING : No tester defined for real
tcp:172.18.1.9:80
2007-07-29 23:19:46,591 DEBUG : Real created: tcp:172.18.1.9:80
2007-07-29 23:19:46,591 INFO : reading desired IPVS config
2007-07-29 23:19:46,592 INFO : actual config
/var/lib/ipvsman/ipvscfg-2007-07-04_13:17
2007-07-29 23:19:46,594 INFO : desired IPVS config read
2007-07-29 23:19:46,611 DEBUG : found knowm running service :
tcp:192.168.1.240:443 <---------------- only finds 1 of 3 services
2007-07-29 23:19:46,612 DEBUG : Service created: tcp:192.168.1.240:443
2007-07-29 23:19:46,614 DEBUG : found unknown running real :
tcp:192.168.1.201:443 <---------------- incorrectly finds only 1 real
server
keepalived.conf:
vrrp_instance VI_1 {
state MASTER
# state BACKUP
interface eth0
track_interface {
eth0
}
lvs_sync_daemon_interface eth0
virtual_router_id 25
priority 150 # MASTER
# priority 100 # BACKUP
advert_int 2
authentication {
auth_type PASS
auth_pass tps
}
virtual_ipaddress {
192.168.1.240/24
}
notify_master "/etc/keepalived/manage_ip_lvs_dr del
192.168.1.240 192.168.1.1 192.168.1.200-201"
notify_backup "/etc/keepalived/manage_ip_lvs_dr add
192.168.1.240 192.168.1.1 192.168.1.200-201"
notify_fault "/etc/keepalived/manage_ip_lvs_dr add
192.168.1.240 192.168.1.1 192.168.1.200-201"
}
#========== SSH ==============
virtual_server 192.168.1.240 22 {
delay_loop 5
lb_algo rr
lb_kind DR
persistence_timeout 600
protocol TCP
real_server 192.168.1.200 22 {
weight 1
inhibit_on_failure
TCP_CHECK {
connect_port 22
connect_timeout 3
nb_get_retry 3
delay_before_retry 1
}
}
real_server 192.168.1.201 22 {
weight 1
inhibit_on_failure
TCP_CHECK {
connect_port 22
connect_timeout 3
nb_get_retry 3
delay_before_retry 1
}
}
}
#========== HTTP =============
virtual_server 192.168.1.240 80 {
delay_loop 5
lb_algo rr
lb_kind DR
persistence_timeout 600
protocol TCP
# sorry_server 192.168.1.15 80
real_server 192.168.1.200 80 {
weight 1
inhibit_on_failure
TCP_CHECK {
connect_port 80
connect_timeout 3
nb_get_retry 3
delay_before_retry 1
}
# HTTP_GET {
# url { # You can add multiple url block
# path alphanum
# digest alphanum
# }
# connect_port num
# connect_timeout num
# nb_get_retry num
# delay_before_retry num
# }
}
real_server 192.168.1.201 80 {
weight 1
inhibit_on_failure
TCP_CHECK {
connect_port 80
connect_timeout 3
nb_get_retry 3
delay_before_retry 1
}
# HTTP_GET {
# url { # You can add multiple url block
# path alphanum
# digest alphanum
# }
# connect_port num
# connect_timeout num
# nb_get_retry num
# delay_before_retry num
# }
}
}
#========== SSL ==============
virtual_server 192.168.1.240 443 {
delay_loop 5
lb_algo rr
lb_kind DR
persistence_timeout 600
protocol TCP
# sorry_server 192.168.1.15 443
real_server 192.168.1.200 443 {
weight 1
inhibit_on_failure
TCP_CHECK {
connect_port 443
connect_timeout 3
nb_get_retry 3
delay_before_retry 1
}
# SSL_GET {
# url { # You can add multiple url block
# path alphanum
# digest alphanum
# }
# connect_port num
# connect_timeout num
# nb_get_retry num
# delay_before_retry num
# }
}
real_server 192.168.1.201 443 {
weight 1
inhibit_on_failure
TCP_CHECK {
connect_port 443
connect_timeout 3
nb_get_retry 3
delay_before_retry 1
}
# SSL_GET {
# url { # You can add multiple url block
# path alphanum
# digest alphanum
# }
# connect_port num
# connect_timeout num
# nb_get_retry num
# delay_before_retry num
# }
}
}
|
|
From: Dr. V. J. <vol...@in...> - 2007-07-28 17:19:33
|
Gerry Reno schrieb:
> If I have 20 real servers is there a way to simplify declaring these in
> keepalived.conf. In other words how can I get the same block of
> information to apply to multiple real servers:
>
> Currently:
>
> real_server 192.168.1.200 80 {
> ...
> }
> real_server 192.168.1.201 80 {
> ... same stuff
> }
>
> Is there some way to do something like:
>
> real_server 192.168.1.200 80,
> real_server 192.168.1.201 80,
> real_server 192.168.1.202 80,
> real_server 192.168.1.203 80,
> real_server 192.168.1.204 80,
> real_server 192.168.1.205 80,
> real_server 192.168.1.206 80,
> real_server 192.168.1.207 80 {
> ... same stuff
> }
>
This is on the ToDo already.
http://sourceforge.net/tracker/index.php?func=detail&aid=1715506&group_id=171517&atid=858242
Best regards,
Volker
--
====================================================
inqbus it-consulting +49 ( 341 ) 5643800
Dr. Volker Jaenisch http://www.inqbus.de
Herloßsohnstr. 12 0 4 1 5 5 Leipzig
N O T - F Ä L L E +49 ( 170 ) 3113748
====================================================
|
|
From: Gerry R. <gr...@ve...> - 2007-07-28 17:17:58
|
Gerry Reno wrote:
> If I have 20 real servers is there a way to simplify declaring these in
> keepalived.conf. In other words how can I get the same block of
> information to apply to multiple real servers:
>
> Currently:
>
> real_server 192.168.1.200 80 {
> ...
> }
> real_server 192.168.1.201 80 {
> ... same stuff
> }
>
> Is there some way to do something like:
>
> real_server 192.168.1.200 80,
> real_server 192.168.1.201 80,
> real_server 192.168.1.202 80,
> real_server 192.168.1.203 80,
> real_server 192.168.1.204 80,
> real_server 192.168.1.205 80,
> real_server 192.168.1.206 80,
> real_server 192.168.1.207 80 {
> ... same stuff
> }
>
>
Sorry Volker,
This went to the wrong list. It's over on LVS list.
Regards,
Gerry
|
|
From: Gerry R. <gr...@ve...> - 2007-07-28 17:15:12
|
If I have 20 real servers is there a way to simplify declaring these in
keepalived.conf. In other words how can I get the same block of
information to apply to multiple real servers:
Currently:
real_server 192.168.1.200 80 {
...
}
real_server 192.168.1.201 80 {
... same stuff
}
Is there some way to do something like:
real_server 192.168.1.200 80,
real_server 192.168.1.201 80,
real_server 192.168.1.202 80,
real_server 192.168.1.203 80,
real_server 192.168.1.204 80,
real_server 192.168.1.205 80,
real_server 192.168.1.206 80,
real_server 192.168.1.207 80 {
... same stuff
}
|
|
From: Dr. V. J. <vol...@in...> - 2007-07-25 01:04:20
|
Hi Gerry! Gerry Reno schrieb: > The problem is actually somewhat different. When I have keepalived > running on both directors everything is fine and 'ipvsadm -l' shows > correctly. Now I start ipvsmand on one of the directors and launch > ipvsman and there are no servers. Now when I check 'ipvsadm -l' there > are also no servers. So ipvsmand is doing something to LVS and it is not > happy. Have you seen this behavior? Is there a workaround? > This is to less information even to get an idea of whats goin on. Also I noticed the ongoing discussions on the LVS-List concerning your setup. Ipvsman/d is a highlevel tool. It relies on the IPVS-Layer. If this layer is not consistent ipvsmam/d will fail. * Please post your keepalived.conf * Your ipvsadm dump * your log of ipvsman/d If there is no significant hint in the log etc. then please start ipvsmand on console with the -D switch and post the stacktrace if there is any. best regards, Volker -- ==================================================== inqbus it-consulting +49 ( 341 ) 5643800 Dr. Volker Jaenisch http://www.inqbus.de Herloßsohnstr. 12 0 4 1 5 5 Leipzig N O T - F Ä L L E +49 ( 170 ) 3113748 ==================================================== |
|
From: Gerry R. <gr...@ve...> - 2007-07-24 03:33:26
|
Gerry Reno wrote: > Hi Volker, > I've been working with keepalived for a bit and now I want to control > things with ipvsman. But I am finding that even when I give ipvsman the > '-k' switch it still does not find the servers defined in > keepalived.conf. I think this might be a problem of location path. > Fedora 7 puts the config as /etc/keepalived/keepalived.conf and maybe > ipvsman does not look here. Is there a switch to set the path to the > config file? > > Regards, > Gerry > The problem is actually somewhat different. When I have keepalived running on both directors everything is fine and 'ipvsadm -l' shows correctly. Now I start ipvsmand on one of the directors and launch ipvsman and there are no servers. Now when I check 'ipvsadm -l' there are also no servers. So ipvsmand is doing something to LVS and it is not happy. Have you seen this behavior? Is there a workaround? Regards, Gerry |
|
From: Gerry R. <gr...@ve...> - 2007-07-24 03:22:31
|
Hi Volker, I've been working with keepalived for a bit and now I want to control things with ipvsman. But I am finding that even when I give ipvsman the '-k' switch it still does not find the servers defined in keepalived.conf. I think this might be a problem of location path. Fedora 7 puts the config as /etc/keepalived/keepalived.conf and maybe ipvsman does not look here. Is there a switch to set the path to the config file? Regards, Gerry |
|
From: Dr. V. J. <vol...@in...> - 2007-07-05 17:19:35
|
Hi UK! ipvsman user schrieb: >> Please have a look at the documentation in the wiki. There are lots of >> pictures that say more than 1000 words. >> >> http://wiki.inqbus.de/twiki/bin/view/Ipvsman/Dokumentation >> > > It might be good to put that URL in the README file, because then people like > me who go directly to the download page will remember to look there. > Sorry for that. I will correct this. > # ls ipvsm* > ipvsman_0.9.2-10.tar.gz > > Can you add the version number to the help output? > > # mv /etc/ipvsman/topology.cfg /etc/ipvsman/topology.x > # ipvsman > Traceback (most recent call last): > File "/usr/bin/ipvsman", line 149, in ? > gui = Gui( masterDaemon ) > File "/usr/lib/python2.4/site-packages/ipvsman/gui.py", line 150, in __init__ > self.buildTop( master ) > File "/usr/lib/python2.4/site-packages/ipvsman/gui.py", line 183, in buildTop > self.master.reinit() > File "/usr/bin/ipvsman", line 69, in reinit > self.cfg.readTopology() > File "/usr/lib/python2.4/site-packages/ipvsman/config.py", line 24, in > readTopology > self.readNewServiceCfg() > File "/usr/lib/python2.4/site-packages/ipvsman/config.py", line 54, in > readNewServiceCfg > inFile = utils.findActualTopologyCfg() > File "/usr/lib/python2.4/site-packages/ipvsman/utils.py", line 54, in > findActualTopologyCfg > raise( 'No new style config file topology.cfg found!' ) > No new style config file topology.cfg found! > > > Same thing after clearing the ipvsadm config: > # ipvsadm -C > # ipvsman > Traceback (most recent call last): > OK. Without a topology ipvsman will not start. You must ipvsman teach in what world it lives. E.g. wich servervices, timeouts, checks etc are needed. You can use the topology.cfg.sample file included in the package to have a working system. Then ajust the topology.cfg to your needs. If you have further questions do not hesitate to ask. Best Regards, Volker -- ==================================================== inqbus it-consulting +49 ( 341 ) 5643800 Dr. Volker Jaenisch http://www.inqbus.de Herloßsohnstr. 12 0 4 1 5 5 Leipzig N O T - F Ä L L E +49 ( 170 ) 3113748 ==================================================== |
|
From: ipvsman u. <ip...@it...> - 2007-07-05 16:04:30
|
Dr. Volker Jaenisch wrote: > Dear Unknown! > > ipvsman user schrieb: >> I was wondering how to set the log level, I tried: > ipvsman runs in debug-level as default. Never changed that. I put it on > the Todo. > Please have a look at the documentation in the wiki. There are lots of > pictures that say more than 1000 words. > > http://wiki.inqbus.de/twiki/bin/view/Ipvsman/Dokumentation It might be good to put that URL in the README file, because then people like me who go directly to the download page will remember to look there. I'll go through that again, I kept thinking it was mostly about using ipvsman with keepalived but it covers more. >> ipvsman wouldn't start when there was no service.cfg available and gave a not >> clear error msg about why it wouldn't start. >> > Which Version do you run? ipvsman should be run with NO config file at all. > Is there a stacktrace? If so please post it - I will have a look. # ls ipvsm* ipvsman_0.9.2-10.tar.gz Can you add the version number to the help output? # mv /etc/ipvsman/topology.cfg /etc/ipvsman/topology.x # ipvsman Traceback (most recent call last): File "/usr/bin/ipvsman", line 149, in ? gui = Gui( masterDaemon ) File "/usr/lib/python2.4/site-packages/ipvsman/gui.py", line 150, in __init__ self.buildTop( master ) File "/usr/lib/python2.4/site-packages/ipvsman/gui.py", line 183, in buildTop self.master.reinit() File "/usr/bin/ipvsman", line 69, in reinit self.cfg.readTopology() File "/usr/lib/python2.4/site-packages/ipvsman/config.py", line 24, in readTopology self.readNewServiceCfg() File "/usr/lib/python2.4/site-packages/ipvsman/config.py", line 54, in readNewServiceCfg inFile = utils.findActualTopologyCfg() File "/usr/lib/python2.4/site-packages/ipvsman/utils.py", line 54, in findActualTopologyCfg raise( 'No new style config file topology.cfg found!' ) No new style config file topology.cfg found! Same thing after clearing the ipvsadm config: # ipvsadm -C # ipvsman Traceback (most recent call last): > The topology information, tests, timeouts e.g. can ipvsman not guess so > easily. But writing a topology.cfg file > is easy and needed only once (or if you have major changes in your cluster). Right it is not a big deal, esp. because it is much more simple than some of the other config files for monitoring tools. Thanks. UK |
|
From: Dr. V. J. <vol...@in...> - 2007-07-05 15:24:17
|
Dear Unknown! ipvsman user schrieb: > I was wondering how to set the log level, I tried: > > -d > -d debug > -d "debug" > -d 1 > -d 9999 > -d 'debug' > -d=debug > ipvsman runs in debug-level as default. Never changed that. I put it on the Todo. > etc, but had to finally go set it in the .py file. > > Also, what is the correct file to use now, service or topology? > Topology is the new style config. service.cfg is for legacy purposes only and will die or is dead already.. > When I tried service.cfg with the following I got an parse error: > > #ServiceName:Transport:IP:Port Realserver-Mapping (params) > ipvsm-test:t:10.1.1.100:80 ["x:10.1.1.1:","y:10.1.1.2:","z:10.1.1.3:"] (-g -swrr) > > I was able to compile everything on FC6 from the source packages, I just had to do > yum install python-devel > first > Ok. Will put this in the Installation part in the HOWTO. > And the README is not clear on what is the desired config, is it the actual or > is it what is in topology/service cfg file? Is there a way to save actual to > service/topology cfg? > Please have a look at the documentation in the wiki. There are lots of pictures that say more than 1000 words. http://wiki.inqbus.de/twiki/bin/view/Ipvsman/Dokumentation It's the other way around. In topology.cfg you define your topology means all the realservers, virtual services. This definition is static. In ipvsman you activate certain realservers from the topology. ipvsman then * saves the new desired state in the desired-condig file. * informs the livekeeping daemon ipvsmand that the desired config has changed. This approach is truely more complicated than that of keepalived or ldirectord. But it has some advantages. E.G. you can do most of the usual changes (taking servers out of the loadbalancing, changing weight) interactivly with the GUI without fiddling around in a config file. > ipvsman wouldn't start when there was no service.cfg available and gave a not > clear error msg about why it wouldn't start. > Which Version do you run? ipvsman should be run with NO config file at all. Is there a stacktrace? If so please post it - I will have a look. > If it could start with no cfg and save the actual running config to a cfg file > then people could load on a running director machine, open it up save their > running config to a service/topology cfg file and add/edit it. > This is a good idea but not so easy. The topology is more than what ipvs gives as information. E.g. the tests ipvsmand should do to check for availability. ipvsman run without desired config-file takes the information from ipvs and creates a desired-config file. So if you switch from say ldirectord or keepalived you will have a seemless migration in terms of desired state. The topology information, tests, timeouts e.g. can ipvsman not guess so easily. But writing a topology.cfg file is easy and needed only once (or if you have major changes in your cluster). Best Regards, Volker -- ==================================================== inqbus it-consulting +49 ( 341 ) 5643800 Dr. Volker Jaenisch http://www.inqbus.de Herloßsohnstr. 12 0 4 1 5 5 Leipzig N O T - F Ä L L E +49 ( 170 ) 3113748 ==================================================== |
|
From: ipvsman u. <ip...@it...> - 2007-07-05 13:48:46
|
I was wondering how to set the log level, I tried: -d -d debug -d "debug" -d 1 -d 9999 -d 'debug' -d=debug etc, but had to finally go set it in the .py file. Also, what is the correct file to use now, service or topology? When I tried service.cfg with the following I got an parse error: #ServiceName:Transport:IP:Port Realserver-Mapping (params) ipvsm-test:t:10.1.1.100:80 ["x:10.1.1.1:","y:10.1.1.2:","z:10.1.1.3:"] (-g -swrr) I was able to compile everything on FC6 from the source packages, I just had to do yum install python-devel first And the README is not clear on what is the desired config, is it the actual or is it what is in topology/service cfg file? Is there a way to save actual to service/topology cfg? ipvsman wouldn't start when there was no service.cfg available and gave a not clear error msg about why it wouldn't start. If it could start with no cfg and save the actual running config to a cfg file then people could load on a running director machine, open it up save their running config to a service/topology cfg file and add/edit it. Thanks. |
|
From: Dr. V. J. <vol...@in...> - 2007-07-05 10:25:43
|
Hi Gerry! Gerry Reno schrieb: > Volker, > In the ipvsman display there is not any status of the daemon. The > screen is identical whether the daemon is running or not. I think this > should be monitored and the daemon status displayed on the screen somewhere. > Very good Idea. Please transform it into a feature-requests at the sourceforge-site. Best Regards, Volker -- ==================================================== inqbus it-consulting +49 ( 341 ) 5643800 Dr. Volker Jaenisch http://www.inqbus.de Herloßsohnstr. 12 0 4 1 5 5 Leipzig N O T - F Ä L L E +49 ( 170 ) 3113748 ==================================================== |
|
From: Gerry R. <gr...@ve...> - 2007-07-04 18:27:30
|
Volker, In the ipvsman display there is not any status of the daemon. The screen is identical whether the daemon is running or not. I think this should be monitored and the daemon status displayed on the screen somewhere. Regards, Gerry |
|
From: Gerry R. <gr...@ve...> - 2007-07-04 18:14:39
|
Volker, The following command should be implemented: # /etc/init.d/ipvsmand status running ... pid(4321) pid(9876) pid(7654) # /etc/init.d/ipvsmand status stopped # Regards, Gerry |
|
From: Gerry R. <gr...@ve...> - 2007-07-02 16:40:15
|
Dr. Volker Jaenisch wrote: > Hi Gerry! > > Gerry Reno schrieb: > >> Volker, >> Ok, dependencies such as python-egenix-mxdatetime, python-urwid are not >> easy on Redhat/Fedora. The python-dns rpm is available but I cannot find >> any packages for these other dependencies. I don't do tarballs. And that >> is why I am able to do a 'yum update' and update to the next OS release >> without any major issue. If you know of a repository that may have these >> packages in RPM let me know. >> > Check this out > > http://dag.wieers.com/rpm/packages/python-mx-base/ > http://dag.wieers.com/rpm/packages/python-urwid/ > > Best Regards, > > Volker > > Volker, Thanks. I checked those packages in DAG and unfortunately they are really old. The only thing there that might be of use is the spec files. These are the type of problems that anyone on a distro other than probably Debian is going to come up against. And if the barrier is too high (which I already think that it is) then adoption of ipvsman will suffer greatly. Regards, Gerry |
|
From: Dr. V. J. <vol...@in...> - 2007-07-02 16:23:56
|
Hi Gerry! Gerry Reno schrieb: > Volker, > Ok, dependencies such as python-egenix-mxdatetime, python-urwid are not > easy on Redhat/Fedora. The python-dns rpm is available but I cannot find > any packages for these other dependencies. I don't do tarballs. And that > is why I am able to do a 'yum update' and update to the next OS release > without any major issue. If you know of a repository that may have these > packages in RPM let me know. Check this out http://dag.wieers.com/rpm/packages/python-mx-base/ http://dag.wieers.com/rpm/packages/python-urwid/ Best Regards, Volker -- ==================================================== inqbus it-consulting +49 ( 341 ) 5643800 Dr. Volker Jaenisch http://www.inqbus.de Herloßsohnstr. 12 0 4 1 5 5 Leipzig N O T - F Ä L L E +49 ( 170 ) 3113748 ==================================================== |
|
From: Gerry R. <gr...@ve...> - 2007-07-02 04:00:35
|
Volker, Ok, dependencies such as python-egenix-mxdatetime, python-urwid are not easy on Redhat/Fedora. The python-dns rpm is available but I cannot find any packages for these other dependencies. I don't do tarballs. And that is why I am able to do a 'yum update' and update to the next OS release without any major issue. If you know of a repository that may have these packages in RPM let me know. I have searched a little but did not find anything. eGenix says that they are included in RH but when you do a 'yum list python-*' they are not there. Regards, Gerry |
|
From: Gerry R. <gr...@ve...> - 2007-07-02 03:06:48
|
Gerry Reno wrote: > Dr. Volker Jaenisch wrote: > >> Does it work? >> >> >> > I'm still looking for the syntax error. > > G. (Copied from LVS-Users list) Volker, Ok, the problem in building RPM's using the bdist_rpm target is that there is a version mangling problem in bdist_rpm.py in python itself. The bug is # 1360200, http://sourceforge.net/tracker/index.php?func=detail&aid=1360200&group_id=5470&atid=305470 . I'm running the latest Fedora (F7) and the python rpm version is 2.5-12.fc7. The fix is supposed to be coming in python 2.6. Now if you go look at the bug you will see the patch that fixes the problem. So anyone that wants to compile python from source should be able to patch it. Regards, Gerry |
|
From: Gerry R. <gr...@ve...> - 2007-07-02 02:09:32
|
Dr. Volker Jaenisch wrote: > Gerry Reno schrieb: > >> Dr. Volker Jaenisch wrote: >> >> >>> Does it work? >>> >>> >>> >>> >> I'm still looking for the syntax error. >> >> > It's 4:00 local time. Time for a rest. > Be online 12:00 again to solve the rpm problem. > > Regards, > > Volker > Volker, I thought you were burning some late oil. See you tomorrow. Gerry |
|
From: Dr. V. J. <vol...@in...> - 2007-07-02 02:00:59
|
Gerry Reno schrieb: > Dr. Volker Jaenisch wrote: > >> Does it work? >> >> >> > I'm still looking for the syntax error. > It's 4:00 local time. Time for a rest. Be online 12:00 again to solve the rpm problem. Regards, Volker -- ==================================================== inqbus it-consulting +49 ( 341 ) 5643800 Dr. Volker Jaenisch http://www.inqbus.de Herloßsohnstr. 12 0 4 1 5 5 Leipzig N O T - F Ä L L E +49 ( 170 ) 3113748 ==================================================== |
|
From: Dr. V. J. <vol...@in...> - 2007-07-02 01:55:33
|
Gerry Reno schrieb: > Dr. Volker Jaenisch wrote: > >> Does it work? >> >> >> > I'm still looking for the syntax error. > Sorry could not confirm the error on debian platform. But this is python code. Just do a # python setup.py install and it is installed. I do not like this. I like packages - as you do. I will look into this at once to make rpms. Best regards, Volker -- ==================================================== inqbus it-consulting +49 ( 341 ) 5643800 Dr. Volker Jaenisch http://www.inqbus.de Herloßsohnstr. 12 0 4 1 5 5 Leipzig N O T - F Ä L L E +49 ( 170 ) 3113748 ==================================================== |
|
From: Gerry R. <gr...@ve...> - 2007-07-02 01:45:58
|
Dr. Volker Jaenisch wrote: > Does it work? > > I'm still looking for the syntax error. G. |
|
From: Dr. V. J. <vol...@in...> - 2007-07-02 01:42:43
|
Does it work? -- ==================================================== inqbus it-consulting +49 ( 341 ) 5643800 Dr. Volker Jaenisch http://www.inqbus.de Herloßsohnstr. 12 0 4 1 5 5 Leipzig N O T - F Ä L L E +49 ( 170 ) 3113748 ==================================================== |
|
From: Dr. V. J. <vol...@in...> - 2007-07-02 01:34:43
|
Hi Gerry! I will have a look immediatly! Never tried this - sorry! Gerry Reno schrieb: > Hi again, > I found a target: bdist_rpm that is trying to create an RPM but it errors: > > # python setup.py bdist_rpm > running bdist_rpm > creating build/bdist.linux-i686 > creating build/bdist.linux-i686/rpm > creating build/bdist.linux-i686/rpm/SOURCES > creating build/bdist.linux-i686/rpm/SPECS > creating build/bdist.linux-i686/rpm/BUILD > creating build/bdist.linux-i686/rpm/RPMS > creating build/bdist.linux-i686/rpm/SRPMS > writing 'build/bdist.linux-i686/rpm/SPECS/ipvsman.spec' > running sdist > reading manifest file 'MANIFEST' > creating ipvsman-0.9.2-9 > making hard links in ipvsman-0.9.2-9... > hard linking ipvsman -> ipvsman-0.9.2-9 > 'ipvsman.py' not a regular file -- skipping > hard linking ipvsmand -> ipvsman-0.9.2-9 > hard linking setup.py -> ipvsman-0.9.2-9 > creating dist > tar -cf dist/ipvsman-0.9.2-9.tar ipvsman-0.9.2-9 > gzip -f9 dist/ipvsman-0.9.2-9.tar > removing 'ipvsman-0.9.2-9' (and everything under it) > copying dist/ipvsman-0.9.2-9.tar.gz -> build/bdist.linux-i686/rpm/SOURCES > building RPMs > rpmbuild -ba --define _topdir > /root/build/ipvsman/trunk/build/bdist.linux-i686/rpm --clean > build/bdist.linux-i686/rpm/SPECS/ipvsman.spec > error: File > /root/build/ipvsman/trunk/build/bdist.linux-i686/rpm/SOURCES/ipvsman-0.9.2_9.tar.gz: > No such file or directory > error: command 'rpmbuild' failed with exit status 1 > # ls > build debian ipvsman ipvsmand_rh lib README.txt > svn-commit.tmp > config dist ipvsmand keepalived.conf MANIFEST setup.py test.shtml > > > Does it need for me to manually copy the tgz into SOURCES? > > Thanks, > Gerry > -- ==================================================== inqbus it-consulting +49 ( 341 ) 5643800 Dr. Volker Jaenisch http://www.inqbus.de Herloßsohnstr. 12 0 4 1 5 5 Leipzig N O T - F Ä L L E +49 ( 170 ) 3113748 ==================================================== |