bryan stalcup wrote:
apologies, typo at 4 am... :(
Maybe there are another one that can explain your trouble.
file actually contains 'inet1a IPaddr::66.193.14.126::start'
Are you sure?
It is :
heartbeat daemon starts successfully with 'inet1a 66.193.14.126' :
heartbeat: 2005/07/10_14:00:46 info: **************************
heartbeat: 2005/07/10_14:00:46 info: Configuration validated. Starting
heartbeat 1.2.3
log output with 'inet1a 66.193.14.126' :
Jul 10 14:00:46 [heartbeat] info: **************************
Jul 10 14:00:46 [heartbeat] info: Configuration validated. Starting
heartbeat 1.2.3
Jul 10 14:00:46 [heartbeat] info: heartbeat: version 1.2.3
Jul 10 14:00:46 [heartbeat] info: Heartbeat generation: 22
Jul 10 14:00:46 [heartbeat] info: ucast: write socket priority set to
IPTOS_LOWDELAY on eth1
Jul 10 14:00:46 [heartbeat] info: ucast: bound send socket to device: eth1
Jul 10 14:00:46 [heartbeat] info: ucast: bound receive socket to
device: eth1
Jul 10 14:00:46 [heartbeat] info: ucast: started on port 694 interface
eth1 to 192.168.1.1
Jul 10 14:00:46 [heartbeat] info: ping heartbeat started.
Jul 10 14:00:46 [heartbeat] info: pid 1374 locked in memory.
Jul 10 14:00:46 [heartbeat] info: Local status now set to: 'up'
Jul 10 14:00:46 [heartbeat] info: pid 1408 locked in memory.
Jul 10 14:00:47 [heartbeat] info: pid 1405 locked in memory.
Jul 10 14:00:47 [heartbeat] info: pid 1406 locked in memory.
Jul 10 14:00:47 [heartbeat] info: pid 1407 locked in memory.
Jul 10 14:00:47 [heartbeat] info: pid 1409 locked in memory.
Jul 10 14:00:47 [heartbeat] info: Link 66.193.14.1:66.193.14.1 up.
Jul 10 14:00:47 [heartbeat] info: Status update for node 66.193.14.1:
status ping
heartbeat starts but throws a usage error with 'ineta IPaddr::
=====
66.193.14.126::start' :
Here I seen "ineta" instead of "inet1a". Could you go grepping a litle
your configuration files looking for "ineta" and substitue it by "inet1a"?
If it's not the case (but I think that will be), could you check again
the syntax of your cfg file. It is, b.e., that it's all on one line or
that there are apropriate "\" to continue the line before a new line and
maybe also that such files is correctly line terminated with new line
and not also carriage return (it is that maybe it has been edited under
M$ and heartbeat dislikes lines terminated also with cr).
Let me know,
Andrea
--
[email protected] mailing list
