Hi All!
When I start heartbeat manually all works fine, but when I try to start it 
automatically when the system boots up I get the following error:

Apr  1 14:51:57 k1286mcs-n1 heartbeat: [8520]: ERROR: Duplicate apiauth 
directive for API client pingd: [pingd        uid=root]
Apr  1 14:51:57 k1286mcs-n1 heartbeat: [8520]: ERROR: Invalid apiauth 
directive [pingd          uid=root]
Apr  1 14:51:57 k1286mcs-n1 heartbeat: [8520]: info: Syntax: apiauth 
client [uid=uidlist] [gid=gidlist]
Apr  1 14:51:57 k1286mcs-n1 heartbeat: [8520]: info: Where uidlist is a 
comma-separated list of uids,
Apr  1 14:51:57 k1286mcs-n1 heartbeat: [8520]: info: and gidlist is a 
comma-separated list of gids
Apr  1 14:51:57 k1286mcs-n1 heartbeat: [8520]: info: One or the other must 
be specified.
Apr  1 14:51:57 k1286mcs-n1 heartbeat: [8520]: ERROR: Directive apiauth 
pingd           uid=root failed
Apr  1 14:51:57 k1286mcs-n1 heartbeat: [8520]: ERROR: Heartbeat not 
started: configuration error.
Apr  1 14:51:57 k1286mcs-n1 heartbeat: [8520]: ERROR: Configuration error, 
heartbeat not started.

But when I grep the /etc/ha.d/ha.cf i find only one entry, that seems ok:
k1286mcs-n1:~ # cat /etc/ha.d/ha.cf|grep root
#apiauth ping gid=haclient uid=alanr,root
apiauth pingd  gid=haclient uid=root
k1286mcs-n1:~ # cat /etc/ha.d/ha.cf|grep pingd
apiauth pingd  gid=haclient uid=root
k1286mcs-n1:~ # 

Could It be, that an old version of ha.cf sneaks around in some cache or 
so? I hat the error described in the error message, but corrected it a 
while ago. since then i did not restart the whole machine, but only the 
heartbeat service, which always worked and is still working when start it 
manually. before i corrected the error it did also occurr, when starting 
manually.
Thanks for yout help in advance.
heartbeat is 2.1.3, OS is SLES 10 SP1 x86_64

Robert Köppl
_______________________________________________
Linux-HA mailing list
[email protected]
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems

Reply via email to