Errors when starting heartbeat on CentOS

Nirmal Fernando <[email protected]>
Newsgroups gmane.linux.highavailability.user
Message-ID <CAJ+w7FnYKdmqbwSe4y3DD+jOdW_n=a9r29-ro84wcCncU-T6DQ@mail.gmail.com>
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
[email protected]
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.