Hi Xia,

Thanks for the patch. I have a question.

Following errors always be output. Are you correct about the log level?
If this isn't a error, it would be better to output as a log info.
And, I attached the log.

ERROR: lseek set offset to 0 error: 4: Success
or
ERROR: lseek set offset to 0 error: 4: Operation now in progress

Sincerely,
Yuichi

2013/1/31 Xia Li <x...@suse.com>:
> Hi Yuichi
>
>>>> On 1/31/2013 at 02:05 PM, in message
> <510a7a350200001500006...@soto.provo.novell.com>, "Xia Li" <x...@suse.com>
> wrote:
>> Hi Yuichi
>>
>> I create two patches trying to fix this issue.
>>
>> In these patches, expand lockfile() to let it not only record the daemon
>> pid,
>> but also record daemon starting status(include "starting" and "started") .
>> At the same time, modify the logic of the controld RA, so that it can read
>
> Sorry, it's typo, it should be boothd RAs.
>
> Regards,
>  Xia Li
>



--
Yuichi SEINO
METROSYSTEMS CORPORATION
E-mail:seino.clust...@gmail.com

2013/1/31 Xia Li <x...@suse.com>:
> Hi Yuichi
>
>>>> On 1/31/2013 at 02:05 PM, in message
> <510a7a350200001500006...@soto.provo.novell.com>, "Xia Li" <x...@suse.com>
> wrote:
>> Hi Yuichi
>>
>> I create two patches trying to fix this issue.
>>
>> In these patches, expand lockfile() to let it not only record the daemon
>> pid,
>> but also record daemon starting status(include "starting" and "started") .
>> At the same time, modify the logic of the controld RA, so that it can read
>
> Sorry, it's typo, it should be boothd RAs.
>
> Regards,
>  Xia Li
>



-- 
Yuichi SEINO
METROSYSTEMS CORPORATION
E-mail:seino.clust...@gmail.com
# booth site -D
booth-site[17036]: 2013/02/01_17:01:17 ERROR: lseek set offset to 0 error: 4: 
Success
booth-site[17036]: 2013/02/01_17:01:17 info: BOOTH cluster site daemon is 
starting.
booth-site[17036]: 2013/02/01_17:01:17 info: command: 'crm_ticket -t ticketA -G 
owner --quiet' was executed
booth-site[17036]: 2013/02/01_17:01:17 info: command: 'crm_ticket -t ticketA -G 
expires --quiet' was executed
booth-site[17036]: 2013/02/01_17:01:17 info: command: 'crm_ticket -t ticketA -G 
ballot --quiet' was executed
booth-site[17036]: 2013/02/01_17:01:17 debug: attempting catchup from 
192.168.201.166
booth-site[17036]: 2013/02/01_17:01:17 debug: connected to 192.168.201.166
booth-site[17036]: 2013/02/01_17:01:17 debug: sent catchup command to 
192.168.201.166
booth-site[17036]: 2013/02/01_17:01:17 debug: attempting catchup from 
192.168.201.167
booth-site[17036]: 2013/02/01_17:01:17 debug: connected to 192.168.201.167
booth-site[17036]: 2013/02/01_17:01:17 debug: sent catchup command to 
192.168.201.167
booth-site[17036]: 2013/02/01_17:01:17 debug: attempting catchup from 
192.168.201.168
booth-site[17036]: 2013/02/01_17:01:17 debug: connected to 192.168.201.168
booth-site[17036]: 2013/02/01_17:01:17 debug: sent catchup command to 
192.168.201.168
booth-site[17036]: 2013/02/01_17:01:17 debug: attempting catchup from 
192.168.201.169
booth-site[17036]: 2013/02/01_17:01:17 debug: connected to 192.168.201.169
booth-site[17036]: 2013/02/01_17:01:17 debug: sent catchup command to 
192.168.201.169
booth-site[17036]: 2013/02/01_17:01:17 info: command: 'crm_ticket -t ticketA -S 
owner -v 2' was executed
booth-site[17036]: 2013/02/01_17:01:17 info: command: 'crm_ticket -t ticketA -S 
expires -v 1359705709' was executed
booth-site[17036]: 2013/02/01_17:01:17 info: command: 'crm_ticket -t ticketA -S 
ballot -v 2' was executed
booth-site[17036]: 2013/02/01_17:01:17 info: command: 'crm_ticket -t ticketA -r 
--force' was executed
booth-site[17036]: 2013/02/01_17:01:17 debug: catchup result: name: ticketA, 
owner: 2, ballot: 2, expires: 1359705709
booth-site[17036]: 2013/02/01_17:01:17 info: command: 'crm_ticket -t ticketA -S 
owner -v 2' was executed
booth-site[17036]: 2013/02/01_17:01:17 info: command: 'crm_ticket -t ticketA -S 
expires -v 1359705709' was executed
booth-site[17036]: 2013/02/01_17:01:17 info: command: 'crm_ticket -t ticketA -S 
ballot -v 2' was executed
booth-site[17036]: 2013/02/01_17:01:17 info: command: 'crm_ticket -t ticketB -G 
owner --quiet' was executed
booth-site[17036]: 2013/02/01_17:01:17 info: command: 'crm_ticket -t ticketB -G 
expires --quiet' was executed
booth-site[17036]: 2013/02/01_17:01:17 info: command: 'crm_ticket -t ticketB -G 
ballot --quiet' was executed
booth-site[17036]: 2013/02/01_17:01:17 debug: attempting catchup from 
192.168.201.166
booth-site[17036]: 2013/02/01_17:01:17 debug: connected to 192.168.201.166
booth-site[17036]: 2013/02/01_17:01:17 debug: sent catchup command to 
192.168.201.166
booth-site[17036]: 2013/02/01_17:01:17 debug: attempting catchup from 
192.168.201.167
booth-site[17036]: 2013/02/01_17:01:17 debug: connected to 192.168.201.167
booth-site[17036]: 2013/02/01_17:01:17 debug: sent catchup command to 
192.168.201.167
booth-site[17036]: 2013/02/01_17:01:17 debug: attempting catchup from 
192.168.201.168
booth-site[17036]: 2013/02/01_17:01:17 debug: connected to 192.168.201.168
booth-site[17036]: 2013/02/01_17:01:17 debug: sent catchup command to 
192.168.201.168
booth-site[17036]: 2013/02/01_17:01:18 debug: attempting catchup from 
192.168.201.169
booth-site[17036]: 2013/02/01_17:01:18 debug: connected to 192.168.201.169
booth-site[17036]: 2013/02/01_17:01:18 debug: sent catchup command to 
192.168.201.169
booth-site[17036]: 2013/02/01_17:01:18 info: command: 'crm_ticket -t ticketB -S 
owner -v -1' was executed
booth-site[17036]: 2013/02/01_17:01:18 info: command: 'crm_ticket -t ticketB -S 
expires -v 0' was executed
booth-site[17036]: 2013/02/01_17:01:18 info: command: 'crm_ticket -t ticketB -S 
ballot -v 0' was executed
booth-site[17036]: 2013/02/01_17:01:18 info: command: 'crm_ticket -t ticketB -r 
--force' was executed
booth-site[17036]: 2013/02/01_17:01:18 debug: catchup result: name: ticketB, 
owner: -1, ballot: 0, expires: 0
booth-site[17036]: 2013/02/01_17:01:18 ERROR: lseek set offset to 0 error: 4: 
Operation now in progress
booth-site[17036]: 2013/02/01_17:01:18 info: BOOTH cluster site daemon started
_______________________________________________
Pacemaker mailing list: Pacemaker@oss.clusterlabs.org
http://oss.clusterlabs.org/mailman/listinfo/pacemaker

Project Home: http://www.clusterlabs.org
Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
Bugs: http://bugs.clusterlabs.org

Reply via email to