Thank you all for tips and suggestions. I managed to configure postgres so
it actually starts.
First, I updated resource-agents (Florian thanks for the tip, still don't
know how did I manage to miss that :) )
Second, I deleted postgres primitive, cleared all failcounts and configure
it again like this:
primitive postgres_res ocf:heartbeat:pgsql \
params pgctl="/usr/lib/postgresql/8.4/bin/pg_ctl"
psql="/usr/bin/psql" start_opt="" pgdata="/var/lib/postgresql/8.4/main"
config="/etc/postgresql/8.4/main/postgresql.conf" pgdba="postgres" \
op start interval="0" timeout="120s" \
op stop interval="0" timeout="120s" \
op monitor interval="30s" timeout="30s" depth="0"
After that, it all worked like a charm.
However, I noticed some strange output in the log file, it wasn't there
before I updated the resource-agents.
Here is the extract from the syslog:
http://pastebin.com/ybPi0VMp
(postgres_res:monitor:stderr) [: 647: monitor: unexpected operator
This error is actually reported with any operator. I tried to start the
script from CLI, I got the same thing with ./pgsql start, ./pgsql status,
./pgsql stop
Here is the pgsql script I am using:
http://pastebin.com/55mKNDCM
P..S. you can ignore nginx errors in syslog, I will open a new topic about
that
_______________________________________________
Pacemaker mailing list: Pacemaker@oss.clusterlabs.org
http://oss.clusterlabs.org/mailman/listinfo/pacemaker
Project Home: http://www.clusterlabs.org
Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
Bugs: http://developerbugs.linux-foundation.org/enter_bug.cgi?product=Pacemaker
