[Linux-HA] Newbie heartbeat stops a few seconds after its started address already in use [with logs]

[Nick Peterson]

Hi there,

I've got heartbeat 2.0.8 on two servers connected with public IPs.
When I start Heartbeat on either of them it starts and then ends a few
seconds later.  I think the problem is where it says  "Unable to bind
socket (Address already in use). Giving up".  Anyone have any idea
what this means?

Thanks,
  Nick

************************ Start Log ************************
Jun  1 12:14:49 Fex1 heartbeat: [11057]: WARN: Logging daemon is
disabled --enabling logging daemon is recommended
Jun  1 12:14:49 Fex1 heartbeat: [11057]: info: **************************
Jun  1 12:14:49 Fex1 heartbeat: [11057]: info: Configuration
validated. Starting heartbeat 2.0.8
Jun  1 12:14:49 Fex1 heartbeat: [11058]: info: heartbeat: version 2.0.8
Jun  1 12:14:49 Fex1 heartbeat: [11058]: info: Heartbeat generation: 32
Jun  1 12:14:49 Fex1 heartbeat: [11058]: info:
G_main_add_TriggerHandler: Added signal manual handler
Jun  1 12:14:49 Fex1 heartbeat: [11058]: info:
G_main_add_TriggerHandler: Added signal manual handler
Jun  1 12:14:49 Fex1 heartbeat: [11058]: info: Removing
/var/run/heartbeat/rsctmp failed, recreating.
Jun  1 12:14:49 Fex1 heartbeat: [11058]: ERROR: glib: Error binding
socket (Address already in use). Retrying.
Jun  1 12:14:58 Fex1 last message repeated 9 times
Jun  1 12:14:59 Fex1 heartbeat: [11058]: ERROR: glib: Unable to bind
socket (Address already in use). Giving up.
Jun  1 12:14:59 Fex1 heartbeat: [11058]: info: glib: UDP Broadcast
heartbeat closed on port 694 interface eth0 - Status: 1
Jun  1 12:14:59 Fex1 heartbeat: [11058]: ERROR: cannot open bcast eth0
Jun  1 12:15:00 Fex1 heartbeat: [11061]: CRIT: Emergency Shutdown:
Master Control process died.
Jun  1 12:15:00 Fex1 heartbeat: [11061]: CRIT: Killing pid 11058 with SIGTERM
Jun  1 12:15:00 Fex1 heartbeat: [11061]: CRIT: Emergency Shutdown(MCP
dead): Killing ourselves.
************************ End Log **************************