Distributed Replicated Block Device (DRBD) development
 help / color / mirror / Atom feed
From: Florian Haas <florian@hastexo.com>
To: drbd-dev@lists.linbit.com,
	The Pacemaker cluster resource manager
	<pacemaker@oss.clusterlabs.org>
Cc: "Robinson, Eric" <eric.robinson@psmnv.com>
Subject: [Drbd-dev] crm_attribute --quiet (was Fwd: [Linux-HA] Should This Worry Me?)
Date: Sun, 13 Nov 2011 09:30:26 +0100	[thread overview]
Message-ID: <4EBF8022.6020202@hastexo.com> (raw)

Lars/Andrew,

While Eric is evidently on a DRBD version whose ocf:linbit:drbd does not
invoke crm_attribute with the flag to suppress logging, I'm mildly
confused as to what the correct flag actually is. ocf:linbit:drbd (in
both 8.3 and 8.4) uses "-Q" whereas Pacemaker expects "-q" as of this
commit:

commit c11ce5e9b0b13ead02b5fc4add928d7e7f95092e
Author: Andrew Beekhof <andrew@beekhof.net>
Date:   Tue Sep 22 17:29:38 2009 +0200

    Medium: Tools: Use -q as the short form for --quiet (for consistency)

    Mercurial revision: 7289e661e4923beee4b7b45bc85592564ccdc438

Should ocf:linbit:drbd be using "-q"?

Cheers,
Florian

-------- Original Message --------
Subject: [Linux-HA] Should This Worry  Me?
Date: Sat, 12 Nov 2011 18:02:51 -0800
From: Robinson, Eric <eric.robinson@psmnv.com>
Reply-To: General Linux-HA mailing list <linux-ha@lists.linux-ha.org>
To: <linux-ha@lists.linux-ha.org>

Should I be concerned that the standby node of a 2-node cluster is
logging these messages about every 15 seconds? This cluster has been up
and running apparently fine for a year.

Nov 12 17:53:59 ha05 crm_attribute: [2420]: info: Invoked: crm_attribute
-N ha05.mycharts.md -n master-p_DRBD:1 -l reboot -v 100
Nov 12 17:54:14 ha05 crm_attribute: [2455]: info: Invoked: crm_attribute
-N ha05.mycharts.md -n master-p_DRBD:1 -l reboot -v 100
Nov 12 17:54:29 ha05 crm_attribute: [2482]: info: Invoked: crm_attribute
-N ha05.mycharts.md -n master-p_DRBD:1 -l reboot -v 100
Nov 12 17:54:44 ha05 crm_attribute: [2510]: info: Invoked: crm_attribute
-N ha05.mycharts.md -n master-p_DRBD:1 -l reboot -v 100
Nov 12 17:54:59 ha05 crm_attribute: [2537]: info: Invoked: crm_attribute
-N ha05.mycharts.md -n master-p_DRBD:1 -l reboot -v 100
Nov 12 17:55:14 ha05 crm_attribute: [2574]: info: Invoked: crm_attribute
-N ha05.mycharts.md -n master-p_DRBD:1 -l reboot -v 100
Nov 12 17:55:29 ha05 crm_attribute: [2603]: info: Invoked: crm_attribute
-N ha05.mycharts.md -n master-p_DRBD:1 -l reboot -v 100
Nov 12 17:55:44 ha05 crm_attribute: [2633]: info: Invoked: crm_attribute
-N ha05.mycharts.md -n master-p_DRBD:1 -l reboot -v 100

--
Eric Robinson

             reply	other threads:[~2011-11-13  8:30 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-13  8:30 Florian Haas [this message]
2011-11-13 11:34 ` [Drbd-dev] crm_attribute --quiet (was Fwd: [Linux-HA] Should This Worry Me?) Robinson, Eric
2011-11-13 16:01   ` Florian Haas
2011-11-13 16:27     ` Robinson, Eric
2011-11-13 16:54       ` Florian Haas
2011-11-14 10:43         ` Robinson, Eric
2011-11-13 22:51 ` [Drbd-dev] [Pacemaker] " Andrew Beekhof
2011-11-14 10:56   ` Lars Ellenberg

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4EBF8022.6020202@hastexo.com \
    --to=florian@hastexo.com \
    --cc=drbd-dev@lists.linbit.com \
    --cc=eric.robinson@psmnv.com \
    --cc=pacemaker@oss.clusterlabs.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox