[ClusterLabs] [Pacemaker1.0.13] [hbagent] The hbagent does not stop.

[renayama19661014 at ybb.ne.jp]

Hi Yan,
Hi All,

The problem seems to be taking place somehow or other in the run_alarms inside carried out from hbagent.

I confirmed that hbagent received SIGTERM.

There seems to be the problem with connect() carried out from run_alarms.

We continue investigating it including a different specialized member.

Best Regars,
Hideo Yamauchi.



----- Original Message -----
> From: "renayama19661014 at ybb.ne.jp" <renayama19661014 at ybb.ne.jp>
> To: "Gao,Yan" <ygao at suse.com>; Cluster Labs - All topics related to open-source clustering welcomed <users at clusterlabs.org>
> Cc: 
> Date: 2015/9/9, Wed 05:19
> Subject: Re: [ClusterLabs] [Pacemaker1.0.13] [hbagent] The hbagent does not stop.
> 
> Hi Yan,
> 
> Thank you for comment.
> 
>>  Sounds weird. I've never encountered the issue before. Actually I
>>  haven't run it with heartbeat for years ;-)  We'd probably have to 
> find
>>  the pattern and produce it.
> 
> 
> 
> We still just began an investigation.
> 
> If there is the point that you think to be the cause of the problem, please tell 
> me.
> 
> Best Reards,
> Hideo Yamauchi.
> 
> 
> ----- Original Message -----
>>  From: "Gao,Yan" <ygao at suse.com>
>>  To: renayama19661014 at ybb.ne.jp; Cluster Labs - All topics related to 
> open-source clustering welcomed <users at clusterlabs.org>
>>  Cc: 
>>  Date: 2015/9/8, Tue 23:14
>>  Subject: Re: [ClusterLabs] [Pacemaker1.0.13] [hbagent] The hbagent does not 
> stop.
>> 
>>  Hi Hideo,
>> 
>>  On 09/08/2015 04:28 AM, renayama19661014 at ybb.ne.jp wrote:
>>>   Hi All,
>>> 
>>>   A problem produced us in Pacemaker1.0.13.
>>> 
>>>    * RHEL6.4(kernel-2.6.32-358.23.2.el6.x86_64)
>>>     * SNMP：
>>>      * net-snmp-libs-5.5-49.el6_5.1.x86_64
>>>      * hp-snmp-agents-9.50-2564.40.rhel6.x86_64
>>>      * net-snmp-utils-5.5-49.el6_5.1.x86_64
>>>      * net-snmp-5.5-49.el6_5.1.x86_64
>>>    * Pacemaker 1.0.13
>>>    * pacemaker-mgmt-2.0.1
>>> 
>>>   We started hbagnet in respawn in this environment, but hbagent did not 
> stop 
>>  when we stopped Heartbeat.
>>>   SIGTERM seemed to be transmitted by Heartbeat even if we saw log, but 
> there 
>>  was not the trace that hbagent received SIGTERM.
>>> 
>>>   We try the reproduction of the problem, but the problem never 
> reappears for 
>>  the moment.
>>> 
>>>   We suppose that pacemaker-mgmt(hbagent) or snmp has a problem.
>>> 
>>>   Know similar problem?
>>>   Know the cause of the problem?
>>  Sounds weird. I've never encountered the issue before. Actually I
>>  haven't run it with heartbeat for years ;-)  We'd probably have to 
> find
>>  the pattern and produce it.
>> 
>>  Regards,
>>    Yan
>>  -- 
>>  Gao,Yan <ygao at suse.com>
>>  Senior Software Engineer
>>  SUSE LINUX GmbH
>> 
> 
> _______________________________________________
> Users mailing list: Users at clusterlabs.org
> http://clusterlabs.org/mailman/listinfo/users
> 
> Project Home: http://www.clusterlabs.org
> Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
> Bugs: http://bugs.clusterlabs.org
>