[Question] About a combination of Pacemaker1.1.14 and crmsh2.1.5. about crmsh HOT 16 CLOSED

Hello,

Thank you for this report! The problem is a log format I have not previously encountered. I will create a fix for this.

from crmsh.

Hi Kristoffer,

Thank you for comment.

All right!
I wait for your correction.

Best Regards,
Hideo Yamauchi.

from crmsh.

Hello Hideo-san,

I apologize, but it will take a little time for me to publish an updated version of crmsh 2.1.5 with a fix for this problem, as I am currently travelling.

If it is any help, the master branch currently does not suffer this issue, I seem to have repaired the problem since releasing 2.1.5. I will take care of this as soon as I am able.

Thank you,
Kristoffer

from crmsh.

Hi Kristoffer,

Thank you for comment.

Okay!
Because I have the work of other investigations, I decide to wait a little more.

Best Regards,
Hideo Yamauchi.

from crmsh.

Hello, and apologies again for taking so long to respond. I have now released 2.1.6 which should fix this issue (and others).

https://github.com/ClusterLabs/crmsh/releases/tag/2.1.6

from crmsh.

Hi Kristoffer,

Great!
I confirm your correction.

Many thanks!
Hideo Yamauchi.

from crmsh.

Hi Kristoffer,

There seems to be still a problem with the matching of the event somehow or other.

Because contents of the log of Pacemaker are changed somehow or other, a change is necessary for the contents of EVENT_PATTERNS.

EVENT_PATTERNS="
membership crmd.*(NEW|LOST)|pcmk.*(lost|memb|LOST|MEMB):
quorum crmd.*Updating.quorum.status|crmd.*quorum.(lost|ac?quir)
pause Process.pause.detected
resources lrmd.*(start|stop)
stonith crmd.*Exec|stonith-ng.*log_oper.*reboot|stonithd.*(requests|(Succeeded|Failed).to.STONITH|result=)
start_stop Configuration.validated..Starting.heartbeat|Corosync.Cluster.Engine|Executive.Service.RELEASE|Requesting.shutdown|Shutdown.complete
"

As a result of having performed matching of EVENT_PATTERNS in Pacemaker1.1.14
(I composed a cluster of two nodes and carried it out after having carried out stonith.)

[root@rh72-01 ~]# grep -E "crmd.*(NEW|LOST)|pcmk.*(lost|memb|LOST|MEMB):" /var/log/messages
[root@rh72-01 ~]# grep -E "crmd.*Updating.quorum.status|crmd.*quorum.(lost|ac?quir)" /var/log/messages
Apr 28 11:10:42 rh72-01 <local1.notice> crmd[1252]:  notice: Membership 632: quorum acquired (2)
Apr 28 11:11:14 rh72-01 <local1.notice> crmd[1252]:  notice: Membership 644: quorum lost (1)
[root@rh72-01 ~]# grep -E "Process.pause.detected" /var/log/messages
[root@rh72-01 ~]# grep -E "lrmd.*(start|stop)" /var/log/messages
Apr 28 11:10:54 rh72-01 <local1.info> lrmd[1249]:    info: executing - rsc:prmDummy action:start call_id:14
Apr 28 11:10:54 rh72-01 <local1.info> lrmd[1249]:    info: finished - rsc:prmDummy action:start call_id:14 pid:1326 exit-code:0 exec-time:12ms queue-time:0ms
Apr 28 11:10:54 rh72-01 <local1.info> lrmd[1249]:    info: executing - rsc:prmStonith2-1 action:start call_id:15
Apr 28 11:10:56 rh72-01 <local1.info> lrmd[1249]:    info: finished - rsc:prmStonith2-1 action:start call_id:15  exit-code:0 exec-time:1108ms queue-time:0ms
[root@rh72-01 ~]# grep -E "crmd.*Exec|stonith-ng.*log_oper.*reboot|stonithd.*(requests|(Succeeded|Failed).to.STONITH|result=)" /var/log/messages
Apr 28 11:11:09 rh72-01 <local1.notice> crmd[1252]:  notice: Executing reboot fencing operation (9) on rh72-02 (timeout=60000)
[root@rh72-01 ~]# grep -E "Configuration.validated..Starting.heartbeat|Corosync.Cluster.Engine|Executive.Service.RELEASE|Requesting.shutdown|Shutdown.complete" /var/log/messages
Apr 28 11:10:06 rh72-01 <daemon.info> systemd:Starting Corosync Cluster Engine...
Apr 28 11:10:06 rh72-01 <local1.notice> corosync[1239]: [MAIN  ] Corosync Cluster Engine ('2.3.5'): started and ready to provide service.
Apr 28 11:10:07 rh72-01 <daemon.info> corosync:Starting Corosync Cluster Engine (corosync): [  OK  ]
Apr 28 11:10:07 rh72-01 <daemon.info> systemd:Started Corosync Cluster Engine.

I think that the correction of EVENT_PATTERNS is necessary.

What do you think?

Best Regards,
Hideo Yamauchi.

from crmsh.

Hi,

Yes, that is probably true. We already have different patterns for 1.1.8
and earlier in crmsh itself.

Can you create a report that shows the problem and email me? I will update
the event patterns.

On Thu, Apr 28, 2016, 03:02 Hideo Yamauchi [email protected] wrote:

Hi Kristoffer,

There seems to be still a problem with the matching of the event somehow
or other.

Because contents of the log of Pacemaker are changed somehow or other, a
change is necessary for the contents of EVENT_PATTERNS.

EVENT_PATTERNS="
membership crmd.(NEW|LOST)|pcmk.(lost|memb|LOST|MEMB):
quorum crmd._Updating.quorum.status|crmd.quorum.(lost|ac?quir)
pause Process.pause.detected
resources lrmd.(start|stop)
stonith crmd._Exec|stonith-ng._log_oper._reboot|stonithd.*(requests|(Succeeded|Failed).to.STONITH|result=)
start_stop Configuration.validated..Starting.heartbeat|Corosync.Cluster.Engine|Executive.Service.RELEASE|Requesting.shutdown|Shutdown.complete
"

Different EVENT_PATTERNS seems to be necessary every version to handle
Pacemaker of the old version.

What do you think?

Best Regards,
Hideo Yamauchi.

—
You are receiving this because you modified the open/close state.
Reply to this email directly or view it on GitHub
#129 (comment)

from crmsh.

For the next major release, I am considering removing events.txt from the report, since we now have crm history events which is a more sophisticated analysis.

from crmsh.

Hi Kristoffer,

Please give me time a little.
Japan becomes the vacation for approximately one week from tomorrow.
Because I go for work on Monday, I send a report to you.

Best Regards,
Hideo Yamauchi.

from crmsh.

No problem, enjoy your vacation :)

from crmsh.

Hi Kristoffer,

I will send hb_report which I acquired in Pacemaker1.1.14 tomorrow evening.
Is the address good in [email protected]?

Best Regards,
Hideo Yamauchi.

from crmsh.

Hi,

Yes, that is OK :)

Cheers,
Kristoffer

On Sun, May 1, 2016, 06:29 Hideo Yamauchi [email protected] wrote:

Hi Kristoffer,

I will send hb_report which I acquired in Pacemaker1.1.14 tomorrow evening.
Is the address good in [email protected]?

Best Regards,
Hideo Yamauchi.

—
You are receiving this because you modified the open/close state.
Reply to this email directly or view it on GitHub
#129 (comment)

from crmsh.

Hi Kristoffer,

I sent an email in the evening.
Did the email arrive?

Best Regards,
Hideo Yamauchi.

from crmsh.

Hello Hideo-san,

I checked my spam folder and found the message. I suppose it was flagged
due to the attachment, but it has arrived now.

I will get back to you when I have looked at the log data.

Thank you!
Kristoffer

On Mon, May 2, 2016 at 4:01 PM, Hideo Yamauchi [email protected]
wrote:

Hi Kristoffer,

I sent an email in the evening.
Did the email arrive?

Best Regards,
Hideo Yamauchi.

—
You are receiving this because you modified the open/close state.
Reply to this email directly or view it on GitHub
#129 (comment)

from crmsh.

Hi Kristoffer,

Okay!
Sorry....The address of ybb.ne.jp may not be so good.

Many Thanks!
Hideo Yamauchi.

from crmsh.