[Linux-cluster] diferent ip nodes with diferent commands
ESGLinux
esggrupos at gmail.com
Tue May 26 08:44:18 UTC 2009
Hello,
thanks for you answer,
Here is the information you have requested:
lsof -p `pidof aisexec`
COMMAND PID USER FD TYPE DEVICE SIZE NODE NAME
aisexec 3781 root cwd DIR 253,0 4096 36208670
/var/lib/openais
aisexec 3781 root rtd DIR 253,0 4096 2 /
aisexec 3781 root txt REG 253,0 181336 49495806
/usr/sbin/aisexec
aisexec 3781 root mem REG 253,0 139416 7307558 /lib64/
ld-2.5.so
aisexec 3781 root mem REG 253,0 1713088 7307559 /lib64/
libc-2.5.so
aisexec 3781 root mem REG 253,0 23360 7307561 /lib64/
libdl-2.5.so
aisexec 3781 root mem REG 253,0 145592 7307562 /lib64/
libpthread-2.5.so
aisexec 3781 root mem REG 253,0 58400 7307466
/lib64/libgcc_s-4.1.2-20080825.so.1
aisexec 3781 root mem REG 253,0 10896 50332152
/usr/libexec/lcrso/objdb.lcrso
aisexec 3781 root mem REG 253,0 57584 50332612
/usr/libexec/lcrso/service_cman.lcrso
aisexec 3781 root mem REG 253,0 53880 7307289 /lib64/
libnss_files-2.5.so
aisexec 3781 root mem REG 253,0 19592 50332157
/usr/libexec/lcrso/service_cpg.lcrso
aisexec 3781 root mem REG 253,0 8984 50332154
/usr/libexec/lcrso/service_cfg.lcrso
aisexec 3781 root mem REG 253,0 20264 50332161
/usr/libexec/lcrso/service_msg.lcrso
aisexec 3781 root mem REG 253,0 19704 50332160
/usr/libexec/lcrso/service_lck.lcrso
aisexec 3781 root mem REG 253,0 47416 50332159
/usr/libexec/lcrso/service_evt.lcrso
aisexec 3781 root mem REG 253,0 48888 50332155
/usr/libexec/lcrso/service_ckpt.lcrso
aisexec 3781 root mem REG 253,0 79520 50332153
/usr/libexec/lcrso/service_amf.lcrso
aisexec 3781 root mem REG 253,0 15400 50332156
/usr/libexec/lcrso/service_clm.lcrso
aisexec 3781 root mem REG 253,0 8872 50332158
/usr/libexec/lcrso/service_evs.lcrso
aisexec 3781 root 0u CHR 1,3 1738 /dev/null
aisexec 3781 root 1u CHR 1,3 1738 /dev/null
aisexec 3781 root 2u CHR 1,3 1738 /dev/null
aisexec 3781 root 3u CHR 1,3 1738 /dev/null
aisexec 3781 root 4u unix 0xffff8101042dd140 7966 socket
aisexec 3781 root 5u unix 0xffff8101278d08c0 7950 socket
aisexec 3781 root 6u IPv4 7959 UDP
239.192.41.253:netsupport
aisexec 3781 root 7u IPv4 7960 UDP
ciambbdd2.lab.cert.inteco.es:5149
aisexec 3781 root 8u IPv4 7961 UDP
ciambbdd2.lab.cert.inteco.es:netsupport
aisexec 3781 root 9u unix 0xffff8101278d0600 7962
/var/run/cman_client
aisexec 3781 root 10u unix 0xffff8101042dd400 7964
/var/run/cman_admin
aisexec 3781 root 11u unix 0xffff8102278220c0 7972
/var/run/cman_client
aisexec 3781 root 12u unix 0xffff810227cef9c0 8006
/var/run/cman_client
aisexec 3781 root 13u unix 0xffff810227cee100 8007
/var/run/cman_admin
aisexec 3781 root 14u unix 0xffff810227cee680 8009 socket
aisexec 3781 root 15u unix 0xffff810227ceec00 8011 socket
aisexec 3781 root 16u unix 0xffff810226a4e6c0 8033
/var/run/cman_client
aisexec 3781 root 17u unix 0xffff810227823400 8074
/var/run/cman_client
aisexec 3781 root 18u unix 0xffff810227cef440 8121
/var/run/cman_client
aisexec 3781 root 19u unix 0xffff810226a57940 8124 socket
aisexec 3781 root 20u unix 0xffff810226a4fa00 8184 socket
aisexec 3781 root 21u unix 0xffff810226a573c0 8129 socket
aisexec 3781 root 22u unix 0xffff810226a568c0 8133 socket
aisexec 3781 root 23u unix 0xffff810226a56340 8136 socket
aisexec 3781 root 24u unix 0xffff810227cef180 8186 socket
aisexec 3781 root 25u unix 0xffff8101042dc640 8477 socket
aisexec 3781 root 26u unix 0xffff8101042dcbc0 8479 socket
aisexec 3781 root 27u unix 0xffff810126c6d1c0 8503 socket
aisexec 3781 root 28u unix 0xffff810126c6d740 8506 socket
aisexec 3781 root 29u unix 0xffff81022348b100 11787
/var/run/cman_client
aisexec 3781 root 30u unix 0xffff810119f78680 11793 socket
aisexec 3781 root 31u unix 0xffff810119f78100 11796 socket
------------------------------------------------------------------------
cluster.conf
?xml version="1.0"?>
<cluster alias="myCLUSTER" config_version="28" name="myCLUSTER">
<fence_daemon clean_start="0" post_fail_delay="5" post_join_delay="3"/>
<clusternodes>
<clusternode name="NODE1" nodeid="1" votes="1">
<fence>
<method name="1">
<device name="FENCENODE1"/>
</method>
</fence>
</clusternode>
<clusternode name="NODE2" nodeid="2" votes="1">
<fence>
<method name="1">
<device name="FENCENODE2"/>
</method>
</fence>
</clusternode>
</clusternodes>
<cman expected_votes="1" two_node="1"/>
<fencedevices>
<fencedevice agent="fence_ipmilan" ipaddr="172.16.1.187" login="admin"
name="FENCENODE1" passwd=***/>
<fencedevice agent="fence_ipmilan" ipaddr="172.16.1.190" login="admin"
name="FENCENODE2" passwd=***/>
</fencedevices>
<rm>
<failoverdomains>
<failoverdomain name="FAILOVERDM" nofailback="0" ordered="0" restricted="1">
<failoverdomainnode name="NODE1" priority="1"/>
<failoverdomainnode name="NODE2" priority="1"/>
</failoverdomain>
</failoverdomains>
<resources>
<ip address="172.16.1.191" monitor_link="1"/>
</resources>
<service autostart="1" domain="FAILOVERDM" exclusive="0" name="MYSQL"
recovery="relocate">
<mysql config_file="/etc/my.cnf" listen_address="172.16.1.191" name="MYSQL"
shutdown_wait="5"/>
<ip ref="172.16.1.191"/>
</service>
</rm>
</cluster>
-----
cman_tool join -d
[MAIN ] AIS Executive Service RELEASE 'subrev 1358 version 0.80.3'
[MAIN ] Copyright (C) 2002-2006 MontaVista Software, Inc and contributors.
[MAIN ] Copyright (C) 2006 Red Hat, Inc.
[MAIN ] AIS Executive Service: started and ready to provide service.
[MAIN ] Using default multicast address of 239.192.41.253
[MAIN ] openais component openais_cpg loaded.
[MAIN ] Registering service handler 'openais cluster closed process group
service v1.01'
[MAIN ] openais component openais_cfg loaded.
[MAIN ] Registering service handler 'openais configuration service'
[MAIN ] openais component openais_msg loaded.
[MAIN ] Registering service handler 'openais message service B.01.01'
[MAIN ] openais component openais_lck loaded.
[MAIN ] Registering service handler 'openais distributed locking service
B.01.01'
[MAIN ] openais component openais_evt loaded.
[MAIN ] Registering service handler 'openais event service B.01.01'
[MAIN ] openais component openais_ckpt loaded.
[MAIN ] Registering service handler 'openais checkpoint service B.01.01'
[MAIN ] openais component openais_amf loaded.
[MAIN ] Registering service handler 'openais availability management
framework B.01.01'
[MAIN ] openais component openais_clm loaded.
[MAIN ] Registering service handler 'openais cluster membership service
B.01.01'
[MAIN ] openais component openais_evs loaded.
[MAIN ] Registering service handler 'openais extended virtual synchrony
service'
[MAIN ] openais component openais_cman loaded.
[MAIN ] Registering service handler 'openais CMAN membership service 2.01'
[TOTEM] Token Timeout (10000 ms) retransmit timeout (495 ms)
[TOTEM] token hold (386 ms) retransmits before loss (20 retrans)
[TOTEM] join (60 ms) send_join (0 ms) consensus (4800 ms) merge (200 ms)
[TOTEM] downcheck (1000 ms) fail to recv const (50 msgs)
[TOTEM] seqno unchanged const (30 rotations) Maximum network MTU 1500
[TOTEM] window size per rotation (50 messages) maximum messages per rotation
(17 messages)
[TOTEM] send threads (0 threads)
[TOTEM] RRP token expired timeout (495 ms)
[TOTEM] RRP token problem counter (2000 ms)
[TOTEM] RRP threshold (10 problem count)
[TOTEM] RRP mode set to none.
[TOTEM] heartbeat_failures_allowed (0)
[TOTEM] max_network_delay (50 ms)
[TOTEM] HeartBeat is Disabled. To enable set heartbeat_failures_allowed > 0
[TOTEM] Receive multicast socket recv buffer size (288000 bytes).
[TOTEM] Transmit multicast socket send buffer size (262142 bytes).
[TOTEM] The network interface [172.16.1.188] is now up.
[TOTEM] Created or loaded sequence id 1624.172.16.1.188 for this ring.
[TOTEM] entering GATHER state from 15.
[SERV ] Initialising service handler 'openais extended virtual synchrony
service'
[SERV ] Initialising service handler 'openais cluster membership service
B.01.01'
[SERV ] Initialising service handler 'openais availability management
framework B.01.01'
[SERV ] Initialising service handler 'openais checkpoint service B.01.01'
[SERV ] Initialising service handler 'openais event service B.01.01'
[SERV ] Initialising service handler 'openais distributed locking service
B.01.01'
[SERV ] Initialising service handler 'openais message service B.01.01'
[SERV ] Initialising service handler 'openais configuration service'
[SERV ] Initialising service handler 'openais cluster closed process group
service v1.01'
[SERV ] Initialising service handler 'openais CMAN membership service 2.01'
[CMAN ] CMAN 2.0.98 (built Dec 3 2008 16:32:34) started
[SYNC ] Not using a virtual synchrony filter.
[TOTEM] Creating commit token because I am the rep.
[TOTEM] Saving state aru 0 high seq received 0
[TOTEM] Storing new sequence id for ring 65c
[TOTEM] entering COMMIT state.
[TOTEM] entering RECOVERY state.
[TOTEM] position [0] member 172.16.1.188:
[TOTEM] previous ring seq 1624 rep 172.16.1.188
[TOTEM] aru 0 high delivered 0 received flag 1
[TOTEM] Did not need to originate any messages in recovery.
[TOTEM] Sending initial ORF token
[CLM ] CLM CONFIGURATION CHANGE
[CLM ] New Configuration:
[CLM ] Members Left:
[CLM ] Members Joined:
[CLM ] CLM CONFIGURATION CHANGE
[CLM ] New Configuration:
[CLM ] r(0) ip(172.16.1.188)
[CLM ] Members Left:
[CLM ] Members Joined:
[CLM ] r(0) ip(172.16.1.188)
[SYNC ] This node is within the primary component and will provide service.
[TOTEM] entering OPERATIONAL state.
# [CMAN ] quorum regained, resuming activity
[CLM ] got nodejoin message 172.16.1.188
[TOTEM] entering GATHER state from 11.
[TOTEM] Saving state aru a high seq received a
[TOTEM] Storing new sequence id for ring 660
[TOTEM] entering COMMIT state.
[TOTEM] entering RECOVERY state.
[TOTEM] position [0] member 172.16.1.185:
[TOTEM] previous ring seq 1624 rep 172.16.1.185
[TOTEM] aru 4f high delivered 4f received flag 1
[TOTEM] position [1] member 172.16.1.188:
[TOTEM] previous ring seq 1628 rep 172.16.1.188
[TOTEM] aru a high delivered a received flag 1
[TOTEM] Did not need to originate any messages in recovery.
[CLM ] CLM CONFIGURATION CHANGE
[CLM ] New Configuration:
[CLM ] r(0) ip(172.16.1.188)
[CLM ] Members Left:
[CLM ] Members Joined:
[CLM ] CLM CONFIGURATION CHANGE
[CLM ] New Configuration:
[CLM ] r(0) ip(172.16.1.185)
[CLM ] r(0) ip(172.16.1.188)
[CLM ] Members Left:
[CLM ] Members Joined:
[CLM ] r(0) ip(172.16.1.185)
[SYNC ] This node is within the primary component and will provide service.
[TOTEM] entering OPERATIONAL state.
[CLM ] got nodejoin message 172.16.1.185
[CLM ] got nodejoin message 172.16.1.188
[CPG ] got joinlist message from node 1
Thanks again,
ESG
2009/5/26 Chrissie Caulfield <ccaulfie at redhat.com>
> ESGLinux wrote:
> > Hello,
> >
> > Looking the configuration of my 2 nodes cluster I have seen that when I
> > run the command cman_tool with diferent commands I get diferent ips for
> > my nodes.
> >
> > here is the example:
> >
> > cman_tool -af nodes
> > Node Sts Inc Joined Name
> > 1 M 1624 2009-05-21 11:41:41 NODE1
> > Addresses: 172.16.1.185
> > 2 M 1620 2009-05-21 11:41:41 NODE2
> > Addresses: 172.16.1.188
> >
> > ---------------------------
> >
> > cman_tool status
> > Version: 6.1.0
> > Config Version: 28
> > Cluster Name: myCLUSTER
> > Cluster Id: 10708
> > Cluster Member: Yes
> > Cluster Generation: 1624
> > Membership state: Cluster-Member
> > Nodes: 2
> > Expected votes: 1
> > Total votes: 2
> > Quorum: 1
> > Active subsystems: 9
> > Flags: 2node Dirty
> > Ports Bound: 0 11 177
> > Node name: NODE1
> > Node ID: 1
> > Multicast addresses: 239.192.41.253
> > Node addresses: 172.16.1.186
> >
> >
> > As you can see node1 shows 2 diferente ips (172.16.1.185 (eth0)
> > and 172.16.1.186 (eth1))
> >
> > How can I determine which ip they are using to communicate and how can I
> > change the configuration to use always the same ip (the one asociated to
> > eth1)
>
> That's very very strange! I can't think what might be causing that. The
> correct information is that shown by 'cman_tool nodes -a' as that
> queries the totem stack to get its information. You can double-check
> this with the command
>
> # lsof -p `pidof aisexec`
>
> But I'm intrigued as to how this has happened. Is it possible you could
> post your cluster.conf and also the output of "cman_tool join -d" please?
>
>
>
> Chrissie
>
> --
> Linux-cluster mailing list
> Linux-cluster at redhat.com
> https://www.redhat.com/mailman/listinfo/linux-cluster
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/linux-cluster/attachments/20090526/e3e382ef/attachment.htm>
More information about the Linux-cluster
mailing list