Hi Andrew, Thank you for your reply. > On 8/8/07, Takenaka Kazuhiro <[EMAIL PROTECTED]> wrote: >> > Hi All. >> > >> > I installed Heartbeat 2.1.2 into my cluster and tried >> > the new way to invoke a cluster recommended in the following URL. >> > >> > http://www.linux-ha.org/v2/faq/cib_changes_detected?highlight=%28v2/faq/%2 >> > >> > It works sanely, so I think I'd better to take it the >> > formal procedure of invoking my cluster that I am planning >> > to test for. >> > >> > On the adoption of the new way, I want to know a proper >> > timing to execute 'cibadmin -R -x cib.xml'. In other words, >> > I want to know how to detect a cluster ready to respond >> > client command's requests. >> > >> > If there is some command which enbales to detect the timing, >> > it must be best. >> > >> > I think 'crm_mon -s' might be what I want. >> > >> > If 'crm_mon -s' shows 'Ok' at 1st field of it's report, >> > I suppose that is a ready sign of a cluster for operators >> > requests. >> > >> > Am I right? > > the best way, is to run: > crmadmin -D # find out which node is the DC > crmadmin -S {uname_of_dc} # find out what status it's in > > if it says S_IDLE, then now is a good time to make changes
I tried your method on my 2 nodes cluster but found a unfavorable behavior for me. Firstly, I performed 'crmadmin -D' before the start of my cluster and the command got over immediatly with an exit code 254. # crmadmin -D # echo $? 254 It just went along the way I expected. In the next place, I invoked Heartbeats on both nodes of my cluster and performed the command before the DC node was elected. I expected the command would show some messages which ment no DC node was elected and would got over immediatly. But 'crmadmin -D' actually paused for tens of second, then the command showed a message and got over with an exit code 0. # crmadmin -D No messages received in 30 seconds.. aborting # echo $? 0 I measured the time required by the DC election and changed the timing of execution of 'crmadmin' so as to it would be permformed ten and a few seconds before the DC election run out, but I obtained a same result. Do these behaviors match your expectaion? Or do you think 'crmadmin' has some problems? The followings were shown by 'crmadmin -V -D' performed during the DC election, I wrote them for your reference. # crmadmin -V -D crmadmin[26405]: 2007/08/09_14:36:57 info: Invoked: crmadmin -V -D crmadmin[26405]: 2007/08/09_14:37:02 info: validate_crm_message: No sub-system defined. crmadmin[26405]: 2007/08/09_14:37:02 info: validate_crm_message: Expecting a (response) message but received a (request). No messages received in 30 seconds.. aborting crmadmin[26405]: 2007/08/09_14:37:32 ERROR: admin_message_timeout: No messages received in 30 seconds Sincerely. -- Takenaka Kazuhiro <[EMAIL PROTECTED]> _______________________________________________ Linux-HA mailing list [email protected] http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems
