25.06.2013, 09:32, "Andrey Groshev" <gre...@yandex.ru>:
> 22.06.2013, 21:32, "Lars Marowsky-Bree" <l...@suse.com>:
>
>>  On 2013-06-21T14:30:42, Andrey Groshev <gre...@yandex.ru> wrote:
>>>   I was wrong - the resource starts in 15 minutes.
>>>   I found a matching entry in the log at the same time:
>>>    grep '11:59.*900' /var/log/cluster/corosync.log
>>>   Jun 21 11:59:50 [23616] dev-cluster2-node4 crmd:     info: 
>>> crm_timer_popped:       PEngine Recheck Timer (I_PE_CALC) just popped 
>>> (900000ms)
>>>   Jun 21 11:59:54 [23616] dev-cluster2-node4 crmd:    debug: 
>>> crm_timer_start:        Started PEngine Recheck Timer (I_PE_CALC:900000ms), 
>>> src=220
>>>
>>>   But anyway, now I'm more interested in the question "why such behavior."
>>>   Please tell me which part of the documentation I have not read?
>>  Looks like a bug. Normally, a cluster event ought to trigger the PE
>>  immediately.
>
> Maybe, even without pacemaker in log exist a errors.
> For begin, now try to understand them.
>
> # grep -i 'error\|bad' /var/log/cluster/corosync.log
> Jun 25 09:07:16 [11992] dev-cluster2-node2 corosync debug   [QB    ] 
> epoll_ctl(del): Bad file descriptor (9)
> Jun 25 09:12:57 [11992] dev-cluster2-node2 corosync debug   [VOTEQ ] getinfo 
> response error: 1
> Jun 25 09:12:57 [11992] dev-cluster2-node2 corosync debug   [VOTEQ ] getinfo 
> response error: 1
> Jun 25 09:12:57 [11992] dev-cluster2-node2 corosync debug   [QB    ] 
> epoll_ctl(del): Bad file descriptor (9)
> Jun 25 09:12:57 [11992] dev-cluster2-node2 corosync debug   [QB    ] 
> epoll_ctl(del): Bad file descriptor (9)
> Jun 25 09:12:57 [11992] dev-cluster2-node2 corosync debug   [QB    ] 
> epoll_ctl(del): Bad file descriptor (9)
> Jun 25 09:12:57 [11992] dev-cluster2-node2 corosync debug   [QB    ] 
> epoll_ctl(del): Bad file descriptor (9)
> Jun 25 09:13:01 [11992] dev-cluster2-node2 corosync debug   [VOTEQ ] getinfo 
> response error: 1
> Jun 25 09:13:01 [11992] dev-cluster2-node2 corosync debug   [VOTEQ ] getinfo 
> response error: 1
> Jun 25 09:13:01 [11992] dev-cluster2-node2 corosync debug   [VOTEQ ] getinfo 
> response error: 1
> Jun 25 09:13:01 [11992] dev-cluster2-node2 corosync debug   [QB    ] 
> epoll_ctl(del): Bad file descriptor (9)
> Jun 25 09:13:01 [11992] dev-cluster2-node2 corosync debug   [QB    ] 
> epoll_ctl(del): Bad file descriptor (9)
> Jun 25 09:13:01 [11992] dev-cluster2-node2 corosync debug   [QB    ] 
> epoll_ctl(del): Bad file descriptor (9)
> Jun 25 09:13:01 [11992] dev-cluster2-node2 corosync debug   [QB    ] 
> epoll_ctl(del): Bad file descriptor (9)
>

Damn! I do not know what to call these people ... for which the "OK" have value 
1 !!!

>>  Regards,
>>      Lars
>>
>>  --
>>  Architect Storage/HA
>>  SUSE LINUX Products GmbH, GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, 
>> HRB 21284 (AG Nürnberg)
>>  "Experience is the name everyone gives to their mistakes." -- Oscar Wilde
>>
>>  _______________________________________________
>>  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
>
> _______________________________________________
> 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

_______________________________________________
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