zeldor.biz

Linux, programming and more

Copyright © 2025
Log in

Pacemaker: fix timeout warnings

March 15, 2011 by Igor Drobot 3 Comments

Sometimes if you add a new resource or change something in your cluster configuration you get some warnings like this one.

Or if you run a configuration syntax check:

1
root@node1:~# crm configure verify

root@node1:~# crm configure verify

1
2
3
4
5
6
7
crm(live)configure# verify 
WARNING: mount_srv: default timeout 20s for start is smaller than the advised 60
WARNING: mount_srv: default timeout 20s for stop is smaller than the advised 60
WARNING: drbd_r0: default timeout 20s for start is smaller than the advised 240
WARNING: drbd_r0: default timeout 20s for stop is smaller than the advised 100
WARNING: pingnet: default timeout 20s for start is smaller than the advised 60
WARNING: pingnet: default timeout 20s for monitor_0 is smaller than the advised 60

crm(live)configure# verify WARNING: mount_srv: default timeout 20s for start is smaller than the advised 60 WARNING: mount_srv: default timeout 20s for stop is smaller than the advised 60 WARNING: drbd_r0: default timeout 20s for start is smaller than the advised 240 WARNING: drbd_r0: default timeout 20s for stop is smaller than the advised 100 WARNING: pingnet: default timeout 20s for start is smaller than the advised 60 WARNING: pingnet: default timeout 20s for monitor_0 is smaller than the advised 60

Solution: define new operations, use the same times 240s and 100s
op start interval=”0″ timeout=”240s”
op stop interval=”0″ timeout=”100s”

Config snippet:

1
2
3
4
5
primitive drbd_r0 ocf:linbit:drbd \
        params drbd_resource="drbd0" \
        op monitor interval="120s" \
        op start interval="0" timeout="240s" \
        op stop interval="0" timeout="100s"

primitive drbd_r0 ocf:linbit:drbd \ params drbd_resource="drbd0" \ op monitor interval="120s" \ op start interval="0" timeout="240s" \ op stop interval="0" timeout="100s"

Really dirty fix (set global timeouts):

1
crm configure property default-action-timeout="240"

crm configure property default-action-timeout="240"

Filed Under: Linux Tagged With: Corosync, corosync WARNING, crm, default timeout, Pacemaker

Yeaaah Cookie! We use cookies to ensure that we give you the best experience on our website. If you continue to use this site we will assume that you are happy with it.Ok