Pushkar, thanks for writing. Comments below.

On Wed, Jul 28, 2010 at 5:50 PM, Pushkar Pradhan <[email protected]> wrote:
> Sorry I haven't got a chance to go through the logs. I have a few questions 
> though:
>
> 1. Have you modified the resource scripts? What does cl_status rscstatus 
> return? What about cl_status hbstatus? They should at least see the other 
> node as alive.

I do not think that I modified any resource scripts.

Here's the status things from both:

r...@pfs-srv3:~# cl_status rscstatus
local
r...@pfs-srv3:~# cl_status hbstatus
Heartbeat is running on this machine.

r...@pfs-srv4:~# cl_status rscstatus
local
r...@pfs-srv4:~# cl_status hbstatus
Heartbeat is running on this machine.

> 2. Why don't you try with just the virtual IP as your resource? Does the 
> problem still persist then?

Yes., I tried with ONLY the virtual IP. The problem still persists --
if I reboot both servers simultaneously, NONE takes over. If I then
reboot one of them, the other takes over.

> 3. Have you made some drastic changes to your ha.cf and haresources? 
> haresources is identical on both nodes right?

Both files are identical. I maintain them on my desktop and copy to
both servers via a makefile.

> 4. I noticed in your haresources you don't have the other node listed 
> (pfs-srv4), if you don't want it to run any resource in normal situations you 
> should at least list the node.

I added mention of the other node, with no resources, in haresources.

It did not help.

> 5. Is your line in haresources split across lines? In that case I think you 
> need a \ to split it across newlines.

It is not split, it is one line.

Thank you

Igor

> pushkar
>
>
> _______________________________________________
> Linux-HA mailing list
> [email protected]
> http://lists.linux-ha.org/mailman/listinfo/linux-ha
> See also: http://linux-ha.org/ReportingProblems
>
_______________________________________________
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