Mailing List Archive: Errors when starting heartbeat on CentOS

Hi All,

I was trying to configure heart beat on 2 AWS EC2 instances (CentOS) and
currently facing following error [1].

Also the kernel version;

*[root@node01 stratos]# rpm -qa |egrep 'heartbeat|kernel-2.6'*
kernel-2.6.32-431.5.1.el6.x86_64
kernel-2.6.32-279.1.1.el6.x86_64
heartbeat-3.0.4-2.el6.x86_64
kernel-2.6.32-431.11.2.el6.x86_64
heartbeat-libs-3.0.4-2.el6.x86_64
kernel-2.6.32-431.17.1.el6.x86_64
kernel-2.6.32-431.20.3.el6.x86_64

Any help is appreciated.

[1]
Jul 21 10:22:25 node01 heartbeat: [3083]: info: **************************
Jul 21 10:22:25 node01 heartbeat: [3083]: info: Configuration validated.
Starting heartbeat 3.0.4
Jul 21 10:22:25 node01 heartbeat: [3084]: info: heartbeat: version 3.0.4
Jul 21 10:22:25 node01 heartbeat: [3084]: info: Heartbeat generation:
1405925294
Jul 21 10:22:25 node01 heartbeat: [3084]: info: glib: ucast: write socket
priority set to IPTOS_LOWDELAY on eth0
Jul 21 10:22:25 node01 heartbeat: [3084]: info: glib: ucast: bound send
socket to device: eth0

*Jul 21 10:22:25 node01 heartbeat: [3084]: ERROR: glib: ucast: error
setting option SO_REUSEPORT(w): Protocol not available Jul 21 10:22:25
node01 heartbeat: [3084]: ERROR: make_io_childpair: cannot open ucast eth0*
Jul 21 10:22:26 node01 heartbeat: [3086]: CRIT: Emergency Shutdown: Master
Control process died.
Jul 21 10:22:26 node01 heartbeat: [3086]: CRIT: Killing pid 3084 with
SIGTERM
Jul 21 10:22:26 node01 heartbeat: [3086]: CRIT: Emergency Shutdown(MCP
dead): Killing ourselves.

--

Thanks & regards,
Nirmal

Senior Software Engineer- Platform Technologies Team, WSO2 Inc.
Mobile: +94715779733
Blog: http://nirmalfdo.blogspot.com/
_______________________________________________
Linux-HA mailing list
Linux-HA@lists.linux-ha.org
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems

On 21/07/14 07:48 AM, Nirmal Fernando wrote:
> Hi All,
>
> I was trying to configure heart beat on 2 AWS EC2 instances (CentOS) and
> currently facing following error [1].
>
> Also the kernel version;
>
> *[root@node01 stratos]# rpm -qa |egrep 'heartbeat|kernel-2.6'*
> kernel-2.6.32-431.5.1.el6.x86_64
> kernel-2.6.32-279.1.1.el6.x86_64
> heartbeat-3.0.4-2.el6.x86_64
> kernel-2.6.32-431.11.2.el6.x86_64
> heartbeat-libs-3.0.4-2.el6.x86_64
> kernel-2.6.32-431.17.1.el6.x86_64
> kernel-2.6.32-431.20.3.el6.x86_64
>
> Any help is appreciated.
>
> [1]
> Jul 21 10:22:25 node01 heartbeat: [3083]: info: **************************
> Jul 21 10:22:25 node01 heartbeat: [3083]: info: Configuration validated.
> Starting heartbeat 3.0.4
> Jul 21 10:22:25 node01 heartbeat: [3084]: info: heartbeat: version 3.0.4
> Jul 21 10:22:25 node01 heartbeat: [3084]: info: Heartbeat generation:
> 1405925294
> Jul 21 10:22:25 node01 heartbeat: [3084]: info: glib: ucast: write socket
> priority set to IPTOS_LOWDELAY on eth0
> Jul 21 10:22:25 node01 heartbeat: [3084]: info: glib: ucast: bound send
> socket to device: eth0
>
> *Jul 21 10:22:25 node01 heartbeat: [3084]: ERROR: glib: ucast: error
> setting option SO_REUSEPORT(w): Protocol not available Jul 21 10:22:25
> node01 heartbeat: [3084]: ERROR: make_io_childpair: cannot open ucast eth0*
> Jul 21 10:22:26 node01 heartbeat: [3086]: CRIT: Emergency Shutdown: Master
> Control process died.
> Jul 21 10:22:26 node01 heartbeat: [3086]: CRIT: Killing pid 3084 with
> SIGTERM
> Jul 21 10:22:26 node01 heartbeat: [3086]: CRIT: Emergency Shutdown(MCP
> dead): Killing ourselves.

Heartbeat is long deprecated, and there are no plans to restart
development. You are much better off starting a new project based on
corosync + pacemaker. In RHEL/CentOS 6, this requires a minimal cman
config, but that's not at all daunting. The future HA stack is corosync
+ pacemaker, with both heartbeat and RHCS being now deprecated (though
both are still commercially supported for the time being).

--
Digimer
Papers and Projects: https://alteeve.ca/w/
What if the cure for cancer is trapped in the mind of a person without
access to education?
_______________________________________________
Linux-HA mailing list
Linux-HA@lists.linux-ha.org
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems