[Openais] How to config the Openais? help me please
Mark Haverkamp
markh at osdl.org
Thu Sep 7 08:47:44 PDT 2006
I don't see anything obviously wrong with your configuration. I am
copying this to the openais mailing list so that others can comment on
your configuration.
Mark.
On Thu, 2006-09-07 at 20:36 +0800, Tiantian Liu wrote:
> Hi Mark:
> I am a fresh man to use openais. now I use 2 computers and a swither
> to build a openais cluster.
> I have download openais-0.80.tar.gz.I copy the openais software on the
> 2 machines (I call them nodes later),
> after I compile (use make command) and install (use make install
> command), I do not very clear to config the
> cluster by openais.conf. cause the QUICKSTART is not very clear:(
>
> (1) I give 2 nodes IP:
> node1 static IP address:192.168.5.100
> node2 staric IP address:192.168.5.200
> (2) I install openais on node1, and generate authkey:
> use command: ./keygen
> after do this, a authkey file is created under /etc/ais
> (3) I copy openais.conf and amf.conf from /conf to /etc/ais. and I
> change the bindnetaddr to 192.168.5.0
> the openais.conf I changed looks like:
>
> # Please read the openais.conf.5 manual page
> totem {
> version: 2
> secauth: off
> threads: 0
> interface {
> ringnumber: 0
> bindnetaddr: 192.168.5.0
> mcastaddr: 226.94.1.1
> mcastport: 5405
> }
> }
>
> logging {
> to_stderr: yes
> to_file: yes
> logfile: /tmp/ais
> debug: off
> timestamp: on
> }
>
> amf {
> mode: disabled
> }
> (4) I copy the authkey to node2, and install the key use command:
> install -D --group=0 --owner=0 --mode=0400
> "/path_to_copy" /etc/ais/authkey
> there is not any prompt.
> (5) I compile and install the openais software on node2, and copy
> the openais.conf and amf.conf to /etc/ais
> (6) I change the openais.conf on node2 just like what I did on
> node1, so after that, the node1 and node2 have
> the same openais.conf file!! is right?? I think there may be
> mistake!!
>
> (7) after that I run the "aisexec" on node1, the message was showed
> below:
>
> [MAIN ] AIS Executive Service RELEASE 'subrev 1152 version 0.80'
> [MAIN ] Copyright (C) 2002-2006 MontaVista Software, Inc and
> contributors.
> [MAIN ] Copyright (C) 2006 Red Hat, Inc.
> [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'
> ..................................................
> ..................................................
> [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'
> [SYNC ] Not using a virtual synchrony filter.
> [MAIN ] AIS Executive Service: started and ready to provide service.
> [TOTEM] The token was lost in state 2 from timer 8b90b60
> [TOTEM] entering GATHER state.
> [TOTEM] The token was lost in state 2 from timer 8b90b60
> [TOTEM] entering GATHER state.
> ..............................
> ..............................
>
> then the process enter infinite loop to show the message " The token
> was lost in state 2 from timer 8b90b60"
> what is wrong???
>
> (8) I run "testclm", the message was showed below:
>
> Result of saClmClusterNodeGet 1
> Node Information for saClmClusterNodeGet SA_CLM_LOCAL_NODE_ID result
> %d
> node id is c805a8c0
> node address is family=1 - address=192.168.5.200
> Node name is 192.168.5.200
> Member is 1
> Timestamp is 10109d0f3c8a8a00 nanoseconds
> result is 1
> result is 1
> result is 1
> result is 1
> result is 1
> track result is 1
> Node Information for Results from SA_TRACK_CURRENT:
> node id is c805a8c0
> node address is family=1 - address=192.168.5.200
> Node name is 192.168.5.200
> Member is 1
> Timestamp is 10109d0f3c8a8a00 nanoseconds
> select fd is 4
> press the enter key to exit with track stop and finalize.
> done with select
> Node Information for NODEGETCALLBACK 55
>
> node id is c805a8c0
> node address is family=1 - address=192.168.5.200
> Node name is 192.168.5.200
> Member is 1
> Timestamp is 10109d0f3c8a8a00 nanoseconds
> Node for invocation 60 not found (7)
> Node for invocation 61 not found (7)
> Node Information for NODEGETCALLBACK 59
>
> node id is c805a8c0
> node address is family=1 - address=192.168.5.200
> Node name is 192.168.5.200
> Member is 1
> Timestamp is 10109d0f3c8a8a00 nanoseconds
> Node Information for NODEGETCALLBACK 57
>
> node id is c805a8c0
> node address is family=1 - address=192.168.5.200
> Node name is 192.168.5.200
> Member is 1
> Timestamp is 10109d0f3c8a8a00 nanoseconds
> TrackStop result is 1 (should be 1)
> Finalize result is 1 (should be 1)
>
> the testclm process seem to wait something.....
>
> (9) I run "aisexec" on node2(since run aisexec, the node2 will join
> the cluster), the process
> just stop seem to wait for something too:
>
> ..................................................
> ..................................................
> [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'
> [SYNC ] Not using a virtual synchrony filter.
> [MAIN ] AIS Executive Service: started and ready to provide service.
> [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 5512
> [TOTEM] entering COMMIT state.
> [TOTEM] entering RECOVERY state.
> [TOTEM] position [0] member 192.168.5.100:
> [TOTEM] previous ring seq 5508 rep 192.168.5.100
> [TOTEM] aru 0 high delivered 0 received flag 0
> [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:
> [SYNC ] This node is within the primary component and will provide
> service.
> [CLM ] CLM CONFIGURATION CHANGE
> [CLM ] New Configuration:
> [CLM ] r(0) ip( 192.168.5.100)
> [CLM ] Members Left:
> [CLM ] Members Joined:
> [CLM ] r(0) ip(192.168.5.100)
> [SYNC ] This node is within the primary component and will provide
> service.
> [TOTEM] entering OPERATIONAL state.
> [SYNC ] Synchronization barrier completed
> [SYNC ] Synchronization actions starting for (openais cluster
> membership service B.01.01)
> [CLM ] got nodejoin message 192.168.5.100
> [SYNC ] Synchronization barrier completed
> [SYNC ] Committing synchronization for (openais cluster membership
> service B.01.01)
> [SYNC ] Synchronization actions starting for (openais availability
> management framework B.01.01)
> [SYNC ] Synchronization barrier completed
> [SYNC ] Committing synchronization for (openais availability
> management framework B.01.01)
> [SYNC ] Synchronization actions starting for (openais checkpoint
> service B.01.01)
> [SYNC ] Synchronization barrier completed
> [SYNC ] Committing synchronization for (openais checkpoint service
> B.01.01)
> [SYNC ] Synchronization actions starting for (openais event service
> B.01.01)
> [SYNC ] Synchronization barrier completed
> [SYNC ] Committing synchronization for (openais event service
> B.01.01)
> [SYNC ] Synchronization actions starting for (openais cluster closed
> process group service v1.01 )
> [SYNC ] Synchronization barrier completed
> [SYNC ] Committing synchronization for (openais cluster closed
> process group service v1.01)
>
> the procee seem to stop here to wait for something, at the same
> time, on the node1, there is not any
> change about the "testclm" process message!!
>
> what mistake I did?? I want to know:
> 1 is there a master node(or init node) in openais cluster?
> 2 how to build the openais.conf file on each node?
> 3 is there any other require to let several computers connect to a
> openais cluster?
>
> I wait for your help! think you very much!!
>
> yours tyler
> 2006-9-7
>
>
--
Mark Haverkamp <markh at osdl.org>
More information about the Openais
mailing list