zeldor.biz

Linux, programming and more

Copyright © 2023
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

Categories

Archives

Tags

apache2 Apple arduino ARM Automation backup bash Cisco Cluster Corosync Database Debian Debian squeeze DIY DNS Fedora FTP Fun Icinga Ipv6 KVM Linux LVM MAC OS X Monitoring MySQL Nagios Nginx openSUSE OpenVPN PHP Proxy Python python3 qemu RAID rsync Samba security ssh Ubuntu virtualization Windows Windows 7 Wordpress

Comments

  1. hahegi says

    January 21, 2020 at 10:52

    Hello. I have a question. I wrote down the text.
    First, I would like to know about the configurable scope of ha cluster (pacemaker, corosync, pcs).
    Can you adjust the time when the primary is down and moving on to the secondary?
    Can monitoring tools such as nagios and zabbix be implanted into the ha cluster?

  2. Igor Drobot says

    November 27, 2017 at 20:58

    No problem, bee free to provide the information with a follow back link to my page :)

  3. mlb jerseys size chart juniors says

    November 21, 2017 at 05:47

    Do you mind if I quote a few of your posts as long as I provide credit and sources back to your webpage? My blog is in the exact same area of interest as yours and my users would genuinely benefit from a lot of the information you provide here. Please let me know if this ok with you. Regards!

Leave a Reply

Your email address will not be published. Required fields are marked *