[ClusterLabs] [Problem] An SNMP trap is not transmitted.

[renayama19661014 at ybb.ne.jp]

Hi All,

I tried a planned new SNMP function released in Pacemaker1.1.14.(pacemaker-87bc29e4b821fd2a98c978d5300e43eef41c2367)

However, in the next procedure, the SNMP trap is not transmitted.

Step 1) Start node A.
Step 2) Send CLI file.(The trap is transmitted definitely then.)

Dec  3 14:25:25 SNMP-MANAGER snmptrapd[2963]: 2015-12-03 14:25:25 rh72-01 [UDP: [192.168.40.20]:43092->[192.168.40.2]]:#012DISMAN-EVENT-MIB::sysUpTimeInstance = Timeticks: (167773) 0:27:57.73#011SNMPv2-MIB::snmpTrapOID.0 = OID: PACEMAKER-MIB::pacemakerNotificationTrap#011PACEMAKER-MIB::pacemakerNotificationTrap = STRING: "rh72-01"#011PACEMAKER-MIB::pacemakerNotificationResource = STRING: "prmDummy"#011PACEMAKER-MIB::pacemakerNotificationOperation = STRING: "start"#011PACEMAKER-MIB::pacemakerNotificationDescription = STRING: "ok"#011PACEMAKER-MIB::pacemakerNotificationStatus = INTEGER: 0#011PACEMAKER-MIB::pacemakerNotificationReturnCode = INTEGER: 0#011PACEMAKER-MIB::pacemakerNotificationTargetReturnCode = INTEGER: 0
Dec  3 14:25:25 SNMP-MANAGER snmptrapd[2963]: 2015-12-03 14:25:25 rh72-01 [UDP: [192.168.40.20]:53635->[192.168.40.2]]:#012DISMAN-EVENT-MIB::sysUpTimeInstance = Timeticks: (167773) 0:27:57.73#011SNMPv2-MIB::snmpTrapOID.0 = OID: PACEMAKER-MIB::pacemakerNotificationTrap#011PACEMAKER-MIB::pacemakerNotificationTrap = STRING: "rh72-01"#011PACEMAKER-MIB::pacemakerNotificationResource = STRING: "prmDummy"#011PACEMAKER-MIB::pacemakerNotificationOperation = STRING: "monitor"#011PACEMAKER-MIB::pacemakerNotificationDescription = STRING: "ok"#011PACEMAKER-MIB::pacemakerNotificationStatus = INTEGER: 0#011PACEMAKER-MIB::pacemakerNotificationReturnCode = INTEGER: 0#011PACEMAKER-MIB::pacemakerNotificationTargetReturnCode = INTEGER: 0
Dec  3 14:25:26 SNMP-MANAGER snmptrapd[2963]: 2015-12-03 14:25:26 rh72-01 [UDP: [192.168.40.20]:50867->[192.168.40.2]]:#012DISMAN-EVENT-MIB::sysUpTimeInstance = Timeticks: (167864) 0:27:58.64#011SNMPv2-MIB::snmpTrapOID.0 = OID: PACEMAKER-MIB::pacemakerNotificationTrap#011PACEMAKER-MIB::pacemakerNotificationTrap = STRING: "rh72-01"#011PACEMAKER-MIB::pacemakerNotificationResource = STRING: "prmStonith2-1"#011PACEMAKER-MIB::pacemakerNotificationOperation = STRING: "start"#011PACEMAKER-MIB::pacemakerNotificationDescription = STRING: "ok"#011PACEMAKER-MIB::pacemakerNotificationStatus = INTEGER: 0#011PACEMAKER-MIB::pacemakerNotificationReturnCode = INTEGER: 0#011PACEMAKER-MIB::pacemakerNotificationTargetReturnCode = INTEGER: 0

Step 3) Start node B.
* However, the trap of the start of prmStonith1-1 is not transmitted.

[root at rh72-01 ~]# crm_mon -1 -Af
Last updated: Thu Dec  3 14:25:46 2015          Last change: Thu Dec  3 14:25:24 2015 by root via cibadmin on rh72-01
Stack: corosync
Current DC: rh72-01 (version 1.1.13-a7d6e6b) - partition with quorum
2 nodes and 3 resources configured

Online: [ rh72-01 rh72-02 ]

prmDummy       (ocf::pacemaker:Dummy): Started rh72-01
prmStonith1-1  (stonith:external/ssh): Started rh72-02
prmStonith2-1  (stonith:external/ssh): Started rh72-01



Step 4) Stop node B.
* However, the trap of the stop of prmStonith1-1 is not transmitted.

[root at rh72-01 ~]# crm_mon -1 -Af
Last updated: Thu Dec  3 14:28:24 2015          Last change: Thu Dec  3 14:25:24 2015 by root via cibadmin on rh72-01
Stack: corosync
Current DC: rh72-01 (version 1.1.13-a7d6e6b) - partition with quorum
2 nodes and 3 resources configured

Node rh72-02: pending
Online: [ rh72-01 ]

prmDummy       (ocf::pacemaker:Dummy): Started rh72-01
prmStonith2-1  (stonith:external/ssh): Started rh72-01


The problem seems to depend on a practice judgment of NOTIFY not being carried out somehow or other after the node that participated later received CIB.
* After having received CIB, the node that participated does not carry out crmd_enable_notifications() processing.

I registered this problem with Bugzilla.
* http://bugs.clusterlabs.org/show_bug.cgi?id=5261

Best Regards,
Hideo Yamauchi.