Hi everyone, I must be overlooking something obvious... I have a simple haresources setup with
node drbddisk::sessdata Filesystem::/dev/drbd0::/raid::ext3::rw \
ip.addr httpd xinetd pure_ftpd pure_uploadscript bacula-client mon
bacula-client is in /etc/ha.d/resource.d, it's a copy of stock
/etc/init.d/bacula-fd with config, lock, and pid file changed to make it
listen on a non-standard port: this is for backing up drbd filesystem
(there's the standard bacula client running also).
bacula-client doesn't start. I added a couple of 'logger' lines and if I
manually run "/etc/ha.d/resource.d/bacula-client start ; echo $?" I get
0 and the log:
node logger: starting bacula-fd -c /etc/bacula/deposit-fd.conf
node logger: bacula-fd -c /etc/bacula/deposit-fd.conf running
Yet on failover I get this:
node ResourceManager[3734]: info: Running /etc/init.d/httpd start
node ResourceManager[3734]: info: Running /etc/init.d/xinetd start
node ResourceManager[3734]: info: Running /etc/ha.d/resource.d/pure_ftpd
start
node xinetd[4204]: xinetd Version 2.3.14 started with libwrap loadavg
labeled-networking options compiled in.
node xinetd[4204]: Started working: 1 available service
node ResourceManager[3734]: info: Running
/etc/ha.d/resource.d/pure_uploadscript start
node ResourceManager[3734]: info: Running /etc/init.d/mon start
It 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?
TIA
--
Dimitri Maziuk
Programmer/sysadmin
BioMagResBank, UW-Madison -- http://www.bmrb.wisc.edu
signature.asc
Description: OpenPGP digital signature
_______________________________________________ Linux-HA mailing list [email protected] http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems
