-
Notifications
You must be signed in to change notification settings - Fork 35
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
corosync parser error: could not parse node id in corosync-quorumtool output: could not find Node ID line #188
Comments
I'm not able to reproduce this issue: your example matches the regex we're using to parse quorumtool output. |
Here it is: cd /var/lib/pacemaker_exporter/ls -ltotal 18436 ./ha_cluster_exporter-amd64 --versionversion 1.2.1+git.1606912430.4fceb77 |
IF you have a debug module, I should be able to install it and see exactly what happened to this parser error. Please let me know if more information you need from me.. Really appreciate your help!!! |
in my environment, I have pacemaker installed as well, together with this prometheus exporter installed for Grafana... |
Nope, we don't have a debug module. ha_cluster_exporter/collector/corosync/parser.go Lines 85 to 93 in 4fceb77
Btw, what corosync version you're using? |
hold on let me check |
corosync -vCorosync Cluster Engine, version '2.4.3' |
How exactly to debug this on RHEL7? Do you have a specific steps to set it up? |
Or modify the source code to print out the variable "quorumToolOutput" from "parseNodeId" when it gets called? |
You could clone the project and then use https://github.com/go-delve/delve to debug it, but that assumes some familiarity with the Go language and toolkit! |
Thanks...I can figure this out. I let you know soon what value of "quorumToolOutput" is passed over to this function....Thank you again. |
yes, you could also do that by adding log.Debug(string(quorumToolOutput)) after line 85 |
even better...thx |
Will get back to you tomorrow morning this time.... |
We modified that function like this: Then in the log, we see this: Notice that we changed "not" to "NOT" in purpose and see if the code can take out changes.... Looks like the x variable is an empty space.... Any more ideas? |
Hello, is there any update about this issue? |
I need an example output from Until I get an actual example, there is not much I can do. |
Hello @stefanotorresi i've the same issue, here is the output :
Issue on Debian 11 |
hmm, ok, that does match the regex, so it's not helping me either: https://regex101.com/r/JuhDCK/1 |
oh, by the way, please always report the versions of the exporter and corosync you're using. |
Here it is : corosync 3.1.2-2 I've just updated to 1.3.2, it seems fixed 🤔 |
tl;dr: if that can help anyone, make sure you test running
In this case (unprivileged user) and I guess in other cases, I guess a possible improvement would be ignoring the return code as is currently done but also failing when |
That's a good suggestion! We'll see to implement this tweak in the next iteration. |
Hi Support,
The following corosync parser error on the "Node ID" exists on the v1.2.0. So I upgraded the ha_cluster_exporter from v1.2.0 to the latest version v.1.2.1 on my RHEL7 VM. But unfortunately, this error still exists on v1.2.1.
The error message is and noticed that the field name complained by corosync is "Node ID":
msg="'corosync' collector scrape failed: corosync parser error: could not parse node id in corosync-quorumtool output: could not find Node ID line"
See below:
The text was updated successfully, but these errors were encountered: