1 |
bryan stalcup wrote: |
2 |
> apologies, typo at 4 am... :( |
3 |
|
4 |
Maybe there are another one that can explain your trouble. |
5 |
|
6 |
> file actually contains 'inet1a IPaddr::66.193.14.126::start' |
7 |
|
8 |
Are you sure? |
9 |
It is : |
10 |
|
11 |
> heartbeat daemon starts successfully with 'inet1a 66.193.14.126' : |
12 |
> |
13 |
> heartbeat: 2005/07/10_14:00:46 info: ************************** |
14 |
> heartbeat: 2005/07/10_14:00:46 info: Configuration validated. Starting |
15 |
> heartbeat 1.2.3 |
16 |
> |
17 |
> log output with 'inet1a 66.193.14.126' : |
18 |
> |
19 |
> Jul 10 14:00:46 [heartbeat] info: ************************** |
20 |
> Jul 10 14:00:46 [heartbeat] info: Configuration validated. Starting |
21 |
> heartbeat 1.2.3 |
22 |
> Jul 10 14:00:46 [heartbeat] info: heartbeat: version 1.2.3 |
23 |
> Jul 10 14:00:46 [heartbeat] info: Heartbeat generation: 22 |
24 |
> Jul 10 14:00:46 [heartbeat] info: ucast: write socket priority set to |
25 |
> IPTOS_LOWDELAY on eth1 |
26 |
> Jul 10 14:00:46 [heartbeat] info: ucast: bound send socket to device: eth1 |
27 |
> Jul 10 14:00:46 [heartbeat] info: ucast: bound receive socket to |
28 |
> device: eth1 |
29 |
> Jul 10 14:00:46 [heartbeat] info: ucast: started on port 694 interface |
30 |
> eth1 to 192.168.1.1 |
31 |
> Jul 10 14:00:46 [heartbeat] info: ping heartbeat started. |
32 |
> Jul 10 14:00:46 [heartbeat] info: pid 1374 locked in memory. |
33 |
> Jul 10 14:00:46 [heartbeat] info: Local status now set to: 'up' |
34 |
> Jul 10 14:00:46 [heartbeat] info: pid 1408 locked in memory. |
35 |
> Jul 10 14:00:47 [heartbeat] info: pid 1405 locked in memory. |
36 |
> Jul 10 14:00:47 [heartbeat] info: pid 1406 locked in memory. |
37 |
> Jul 10 14:00:47 [heartbeat] info: pid 1407 locked in memory. |
38 |
> Jul 10 14:00:47 [heartbeat] info: pid 1409 locked in memory. |
39 |
> Jul 10 14:00:47 [heartbeat] info: Link 66.193.14.1:66.193.14.1 up. |
40 |
> Jul 10 14:00:47 [heartbeat] info: Status update for node 66.193.14.1: |
41 |
> status ping |
42 |
> |
43 |
> heartbeat starts but throws a usage error with 'ineta IPaddr:: |
44 |
===== |
45 |
> 66.193.14.126::start' : |
46 |
|
47 |
Here I seen "ineta" instead of "inet1a". Could you go grepping a litle |
48 |
your configuration files looking for "ineta" and substitue it by "inet1a"? |
49 |
|
50 |
If it's not the case (but I think that will be), could you check again |
51 |
the syntax of your cfg file. It is, b.e., that it's all on one line or |
52 |
that there are apropriate "\" to continue the line before a new line and |
53 |
maybe also that such files is correctly line terminated with new line |
54 |
and not also carriage return (it is that maybe it has been edited under |
55 |
M$ and heartbeat dislikes lines terminated also with cr). |
56 |
|
57 |
Let me know, |
58 |
|
59 |
Andrea |
60 |
-- |
61 |
gentoo-cluster@g.o mailing list |