|
Hi,
I have this error before. I solve it by removing the ha-debug log from
/var/log/ . This log file is configured in your ha.cf file located in
/etc/ha.d . This log file continue to grow and cause start up problem. Hope
this help.
Eric ^_^
----- Original Message -----
From: "Roberto Nibali" <ratz@xxxxxxxxxxxx>
To: "LinuxVirtualServer.org users mailing list."
<lvs-users@xxxxxxxxxxxxxxxxxxxxxx>
Sent: Thursday, December 16, 2004 7:15 AM
Subject: Re: Heartbeat start up problem
> Hello,
>
> > Any one know the reason why I have the below error when I start up the
heartbeat ?
>
> I don't and a as it seems not a lot of other people would.
>
> > Nov 12 15:18:27 eprhut1 heartbeat[4868]: info: Configuration validated.
Starting
> > heartbeat 1.0.4
> > Nov 12 15:18:27 eprhut1 heartbeat[4868]: info: nice_failback is in
effect.
> > Nov 12 15:18:27 eprhut1 heartbeat[4869]: info: heartbeat: version 1.0.4
> > Nov 12 15:18:27 eprhut1 heartbeat[4869]: info: Heartbeat generation: 44
> > Nov 12 15:18:27 eprhut1 heartbeat[4869]: info: UDP multicast heartbeat
started f
> > or group 225.0.0.7 port 694 interface eth1 (ttl=1 loop=1)
> > Nov 12 15:18:28 eprhut1 heartbeat[4872]: info: pid 4872 locked in
memory.
> > Nov 12 15:18:28 eprhut1 heartbeat[4873]: info: pid 4873 locked in
memory.
> > Nov 12 15:18:28 eprhut1 heartbeat[4874]: info: pid 4874 locked in
memory.
> > Nov 12 15:18:28 eprhut1 heartbeat[4874]: info: Local status now set to:
'up'
> > Nov 12 15:18:28 eprhut1 heartbeat[4869]: ERROR: FIFO open failed.:
Interrupted s
> > ystem call
>
> EINTR ... so fopen(FIFONAME, "r") failed --> thus open(2) syscall broke
> ;). You might want to ask on the linux-ha mailing list for additional
> help. What does your ha.cf look like? Could you tune up your debug level
> and run again?
>
> Take care,
> Roberto Nibali, ratz
> --
> echo
> '[q]sa[ln0=aln256%Pln256/snlbx]sb3135071790101768542287578439snlbxq' | dc
> _______________________________________________
> LinuxVirtualServer.org mailing list - lvs-users@xxxxxxxxxxxxxxxxxxxxxx
> Send requests to lvs-users-request@xxxxxxxxxxxxxxxxxxxxxx
> or go to http://www.in-addr.de/mailman/listinfo/lvs-users
>
|
