Heartbeat_crm check

Troubleshooting
,
1

CMK version: Checkmk Raw Edition 2.2.0p7
OS version: Alma 8.9

Error message:check failed - please submit a crash report! (Crash-ID: eee20dcc-8eb7-11ee-a00b-3ea2e4426dd4)

Output of “cmk --debug -vvn hostname”: (If it is a problem with checks or plugins)

I am encountering an issue with the CRM check on our cluster environment. The system has reported a check failure, and I have included relevant information below for your analysis. For privacy reasons, sensitive information such as server names and IP addresses has been replaced with placeholders.

Check failed - please submit a crash report! (Crash-ID: a1b2db16-8eb8-11ee-bf00-3ea2e4426dd4)

Current Output (Downlaod Agent Data):

<<<heartbeat_crm>>>
Cluster Summary:
_* Stack: corosync (Pacemaker is running)
_* Current DC: logstash-02.example.com (version 2.1.5-9.3.el8_8.alma.1-a3f44794f94) - MIXED-VERSION partition with quorum
_* Last updated: Tue Nov 28 20:38:04 2023 on logstash-01.example.com
_* Last change:  Wed Nov 15 02:22:45 2023 by root via cibadmin on logstash-01.example.com
_* 2 nodes configured
_* 3 resource instances configured
Node List:
_* Online: [logstash-01.example.com logstash-02.example.com]
Full List of Resources:
_* Resource Group: logstash_group:
_  * virtual_ipv4	(ocf::heartbeat:IPaddr2):	 Started logstash-02.example.com
_  * virtual_ipv6	(ocf::heartbeat:IPaddr2):	 Started logstash-02.example.com
_  * logstash	(systemd:logstash):	 Started logstash-02.example.com

Previous Output (Downlaod Agent Data):

<<<heartbeat_crm>>>
Status of pacemakerd: 'Pacemaker is running' (last updated 2023-11-28 20:36:23Z)
Cluster Summary:
_* Stack: corosync
_* Current DC: logstash-02.example.com (version 2.1.5-9.3.el8_8.alma.1-a3f44794f94) - MIXED-VERSION partition with quorum
_* Last updated: Tue Nov 28 20:36:23 2023
_* Last change:  Wed Nov 15 02:22:45 2023 by root via cibadmin on logstash-01.example.com
_* 2 nodes configured
_* 3 resource instances configured
Node List:
_* Online: [logstash-01.example.com logstash-02.example.com]
Full List of Resources:
_* Resource Group: logstash_group:
_  * virtual_ipv4	(ocf::heartbeat:IPaddr2):	 Started logstash-02.example.com
_  * virtual_ipv6	(ocf::heartbeat:IPaddr2):	 Started logstash-02.example.com
_  * logstash	(systemd:logstash):	 Started logstash-02.example.com

Exception: ValueError (unconverted data remains: on logstash-01.example.com)
Traceback:

 File "/omd/sites/cdc/lib/python3/cmk/base/agent_based/checking/_checking.py", line 413, in get_aggregated_result
    consume_check_results(
  File "/omd/sites/cdc/lib/python3/cmk/base/api/agent_based/checking_classes.py", line 494, in consume_check_results
    for subr in subresults:
  File "/omd/sites/cdc/lib/python3/cmk/base/api/agent_based/register/check_plugins.py", line 93, in filtered_generator
    for element in generator(*args, **kwargs):
  File "/omd/sites/cdc/lib/python3/cmk/base/plugins/agent_based/heartbeat_crm.py", line 333, in check_heartbeat_crm
    dt = calendar.timegm((time.strptime(last_updated, "%a %b %d %H:%M:%S %Y")))
  File "/omd/sites/cdc/lib/python3.11/_strptime.py", line 562, in _strptime_time
    tt = _strptime(data_string, format)[0]
  File "/omd/sites/cdc/lib/python3.11/_strptime.py", line 352, in _strptime
    raise ValueError("unconverted data remains: %s" %
2

Have you uploaded the crash? That would help our developers to look at the issue in-depth.
Also, did you have a working state before changing anything? If so, what was the last known working state?

3

oh sure i will publish the crash report.
how do you mean state before?
before the update to alma 8.9 the check was working fine

4

Thanks!
Yes, that was what I meant, since when there is a problem.
So with the OS upgrade probably came a Pacemaker update, which changed the output format.
Maybe someone can provide a quick fix, but with the crash report uploaded, we might be able to fix it. If this is very important to you, I recommend opening a support ticket and referring to this forum post.

5

Hello Robin
i sended the crash report. in this moment we disabled this check and are fine. sure we would be happy to get the check back.
kind regards

1 Like
6

This topic was automatically closed 365 days after the last reply. New replies are no longer allowed. Contact an admin if you think this should be re-opened.