[Pacemaker] Resources are not started

Andreas Kurz andreas at hastexo.com
Tue Nov 8 06:17:19 EST 2011

On 11/08/2011 09:29 AM, Matti Linnanvuori wrote:
> Andreas Kurz:
>> Beside an update to 1.1.5 or later ... does restarting DB-daemon
>> resource trigger the wanted starts?
> No, restarting DB-daemon resource does not trigger the wanted starts. I tried "crm resource restart DB-daemon" and direct init script restart. Pacemaker seems stuck. I got the following type of recurring printouts in file /var/log/corosync.log:
> Nov 08 10:27:06 iac-pgis lrmd: [2561]: info: perform_op:2884: operation monitor[4675] on ocf::db::DB-daemon for client 2564, its parameters: CRM_meta_name=[monitor] crm_feature_set=[3.0.2] db_binary=[/etc/init.d/iac-db] CRM_meta_timeout=[20000] CRM_meta_interval=[5000]  for rsc is already running.
> Nov 08 10:27:06 iac-pgis lrmd: [2561]: info: perform_op:2894: postponing all ops on resource DB-daemon by 1000 ms

full logs around this restart would be interesting ... you tested all
your own OCF scripts with ocf-tester and they are sane?


Need help with Pacemaker?

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 286 bytes
Desc: OpenPGP digital signature
URL: <https://lists.clusterlabs.org/pipermail/pacemaker/attachments/20111108/709343bc/attachment-0003.sig>

More information about the Pacemaker mailing list