I've since relocated the ocf script to: /usr/lib/ocf/resource.d/heartbeat/pgpool-II
as per http://www.linux-ha.org/OCFResourceAgent Looking at the script I see some weirdness: ## # pgpool is already running. exit 0 else su -c "$PGPOOL $PGPOOL_START_ARG" postgres exit $? fi ;; stop) if check_pid then RET=`su -c "$PGPOOL $PGPOOL_STOP_ARG | grep ERROR" postgres` if [ -z "$RET" ] ; then exit 0 else # try immediate stop. RET=`su -c "$PGPOOL $PGPOOL_FORCE_STOP_ARG | grep ERROR " postgres` ### why is the script trying to start the pgpool service as the postgres user? If I take that out, I can at least start the pgpool daemon by hand. James James Martin wrote: > I know the pgpool-ha stuff doesn't appear to have been maintained for > awhile, but I'm running into all sorts of problems. > > > Firstly, the cib.xml file referenced in the documentation doesn't work > with current versions of heartbeat. It spits out all sorts of xml errors. > > Also, in trying to use the hb_gui to create my own cluster and > referencing the pgpool ocf in /etc/ha.d/resource.d/pgpool_2, the service > never starts correctly. > > The only way I'm able to use it with heartbeat is to configure heartbeat > to use the standard lsb pgpool script. Everything fails over fine with > that, but I don't get the health checking that the pgpool-ha is supposed > to provide. > > I'm using heartbeat-2.1.3. I wouldn't mind looking at the ocf provided > in the pgpool-ha and attempt to fix it, I'm just wondering if there's > anything else I can do. > > > Thanks, > > > James > _______________________________________________ > Pgpool-general mailing list > [email protected] > http://pgfoundry.org/mailman/listinfo/pgpool-general > _______________________________________________ Pgpool-general mailing list [email protected] http://pgfoundry.org/mailman/listinfo/pgpool-general
