Re: [gentoo-cluster] heartbeat won't pass arguments

[bryan stalcup]

apologies, typo at 4 am... :(

file actually contains 'inet1a  IPaddr::66.193.14.126::start'

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' :

heartbeat: 2005/07/10_14:03:30 info: **************************
heartbeat: 2005/07/10_14:03:30 info: Configuration validated.  
Starting heartbeat 1.2.3
usage: /etc/ha.d/resource.d/IPaddr ip-address {start|stop|status| 
monitor  [ ok ]

log output with ineta IPaddr::66.193.14.126::start' :

Jul 10 14:03:30 [heartbeat] info: **************************
Jul 10 14:03:30 [heartbeat] info: Configuration validated. Starting  
heartbeat 1.2.3
Jul 10 14:03:30 [heartbeat] info: heartbeat: version 1.2.3
Jul 10 14:03:30 [heartbeat] info: Heartbeat generation: 23
Jul 10 14:03:30 [heartbeat] info: ucast: write socket priority set to  
IPTOS_LOWDELAY on eth1
Jul 10 14:03:30 [heartbeat] info: ucast: bound send socket to device:  
eth1
Jul 10 14:03:30 [heartbeat] info: ucast: bound receive socket to  
device: eth1
Jul 10 14:03:30 [heartbeat] info: ucast: started on port 694  
interface eth1 to 192.168.1.1
Jul 10 14:03:30 [heartbeat] info: ping heartbeat started.
Jul 10 14:03:30 [heartbeat] info: pid 1747 locked in memory.
Jul 10 14:03:30 [heartbeat] info: Local status now set to: 'up'
Jul 10 14:03:31 [heartbeat] info: pid 1771 locked in memory.
Jul 10 14:03:31 [heartbeat] info: pid 1772 locked in memory.
Jul 10 14:03:31 [heartbeat] info: pid 1773 locked in memory.
Jul 10 14:03:31 [heartbeat] info: pid 1774 locked in memory.
Jul 10 14:03:31 [heartbeat] info: pid 1775 locked in memory.
Jul 10 14:03:31 [heartbeat] info: Link 66.193.14.1:66.193.14.1 up.
Jul 10 14:03:31 [heartbeat] info: Status update for node 66.193.14.1:  
status ping

no arguments are passed, in testing i've edited the /etc/ha.d/ 
resource.d/IPaddr file to echo $1 and $2 instead of usage and no  
arguments are being received.

my ha.cf file:

logfacility     local0
keepalive 1
deadtime 10
warntime 2
initdead 120
udpport 694
ucast eth1 192.168.1.1 192.168.1.2
auto_failback on
node    inet1a
node    inet1b
ping 66.193.14.1
respawn cluster /usr/lib/heartbeat/ipfail

uname -a output, if relevant:

Linux inet1a 2.6.11-hardened-r1-bbix-20050430 #3 SMP Fri Jun 24  
05:27:37 GMT 2005 x86_64 AMD Opteron(tm) Processor 146 AuthenticAMD  
GNU/Linux

thanks for any help again,

bryan

On Jul 10, 2005, at 7:11 AM, andrea ferraris wrote:

> bryan stalcup wrote:
>
>> running version 1.2.3 on amd64.
>> anyone have any idea why a haresources file with 'inet1a
>> 66.193.14.126' won't start the ip address? i can run '/etc/ha.d/
>> resource.d/IPaddr 66.193.14.126 start' in a console and it works
>> just  fine, but it seems the arguments don't get passed, even with
>> 'inet1a  IPaddr::66.193.14.126:start'
>>
>
> I reply only because the ml is not very crowded (about a message
> for month), but I don't have my clusters under the fingers, so I
> can't check better than you and I dont remember with precision.
>
> I can only give generic advices, it is:
>
> - check the syntax of your configuration file
>
> - check that the daemon is running
>
> - check the logs
>
> and follow the good examples in docs.
>
> Regards,
>         Andrea
>
> P.S.: I don't remember the ":start" at the end of the cfg file
> line, are you sure that's right and with only a ":" before the
> "start"?
> --
> gentoo-cluster@g.o mailing list
>
>

-- 
gentoo-cluster@g.o mailing list