dmaziuk at bmrb
May 18, 2012, 11:59 AM
Post #3 of 3
On 05/09/2012 07:07 AM, Dejan Muhamedagic wrote:
> On Wed, May 02, 2012 at 06:25:55PM -0500, Dimitri Maziuk wrote:
[heartbeat] doesn't seem to run that particular script: it starts
>> pure_uploadscript from resource.d and mon from init.d, but not the one
>> in between. What's weird is I now have it happening on 2 clusters:
>> centos 5 w/ heartbeat 2.1.4, and centos 6 w/ heartbeat 3.0.4. The only
>> common thing is bacula version: 5.
>> Any ideas?
> No, but you can add set -x in some places in ResourceManager and
> see what gives.
Not very useful on 2.1: it prints out the very 1st resource (drbd fs)
and stops there. And all that goes to the console, not to the log --
it's a good thing I have these boxes hooked up to a terminal server.
However, it did (eventually) lead me to "status)" case in my
bacula-client startup script: I forgot to change "status $prog" to
"status -p $pidfile $prog". So it was reporting bacula-fd as already
running -- correctly, since there's already an instance listening on the
standard port. It just wasn't the right instance.
Thanks Dejan for pointing me in the right direction.
BioMagResBank, UW-Madison -- http://www.bmrb.wisc.edu