[ClusterLabs] issue

Reid Wahl nwahl at redhat.com
Tue Nov 17 23:38:12 EST 2020

Thanks so much, Gerry. I'm glad that we know the right direction to point
toward now.

On Tuesday, November 17, 2020, Gerry R Sommerville <gerry at ca.ibm.com> wrote:
> Hey Reid, and Guy,
> I want to clarify that Guy is using the Db2 built and packaged version of
Pacemaker and Corosync released for technical preview to be used with Db2
V11.5.4.0. The db2cm utility and db2 specific resource agents (db2ethmon,
db2inst, db2hadr) were developed and packaged by Db2, not by Redhat or
Clusterlabs. Support is limited since its technical preview but he should
reach out to Db2 for questions about these scripts so we can make
improvements if necessary.
> I have reached out to Guy directly and can hopefully answer his questions.
> Gerry Sommerville
> Db2 Development, pureScale Domain
> E-mail: gerry at ca.ibm.com
> ----- Original message -----
> From: Reid Wahl <nwahl at redhat.com>
> Sent by: "Users" <users-bounces at clusterlabs.org>
> To: Cluster Labs - All topics related to open-source clustering welcomed <
users at clusterlabs.org>
> Cc:
> Subject: [EXTERNAL] [ClusterLabs] Fwd: issue
> Date: Tue, Nov 17, 2020 5:48 AM
> Forwarding Guy's response to me, onward to the list.
> I work on the cluster support team at Red Hat and I'm not aware that we
ship this db2cm script. Since you've said the script is defined by IBM and
also Red Hat, where did you obtain the script?
> The resource agent script for ocf:heartbeat:db2inst should be located at
/usr/lib/ocf/resource/heartbeat/db2inst. It should have one or more
functions that it runs when the monitor operation is executed.
> If the resource is showing "Started" state when the DB is in fact down,
then one of two explanations is likely:
> - The function that is run for a monitor operation doesn't properly check
the DB status. If this is the case, then it sounds like a bug in the
script. The logic in that function needs to be modified. I would suggest
reaching out to whoever maintains the
/usr/lib/ocf/resource.d/heartbeat/db2inst script.
> - No recurring monitor operation has been defined for the resource, so
Pacemaker is not even checking the resource's status. If this is the case,
then a monitor operation needs to be added.
> ---------- Forwarded message ---------
> From: Guy Przytula <guy.przytula at infocura.be>
> Date: Tue, Nov 17, 2020 at 2:33 AM
> Subject: Re: [ClusterLabs] issue
> To: Reid Wahl <nwahl at redhat.com>
> we are using a db2 (ibm and also redhat) defined script db2cm to create
the resources and handling these. we do not handle the scripts for
> in current version of db2 pacemaker is shipped as a tech-preview, but in
next release, pacemaker will be officially supported for db2
> if the problem persist, we can open a ticket for this at ibm
> --
> Best Regards,     Beste Groeten,      Meilleures Salutations
> Guy Przytula
> Tel. GSM : +32 (0)475-33.81.86
> Email : Guy Przytula



> Infocura - Tel : +32 (0) 478 32 83 54
> --
> Regards,
> Reid Wahl, RHCA
> Senior Software Maintenance Engineer, Red Hat
> CEE - Platform Support Delivery - ClusterHA
> _______________________________________________
> Manage your subscription:

> ClusterLabs home:



Reid Wahl, RHCA
Senior Software Maintenance Engineer, Red Hat
CEE - Platform Support Delivery - ClusterHA
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.clusterlabs.org/pipermail/users/attachments/20201117/0a3bbdbb/attachment.htm>

More information about the Users mailing list