Hi Michael

Sorry, but was is machine63? You have custdevc03, 04 and 05. Did you mean: "The machine that run resource res.ip.m63"?

---> YES


my purpose is to have 3 apaches on 3 machines

and I'd like to start/stop manually one of them.


have I to assign a Vritual IP? (I've seen that IPaddr2/IPaddr work
on the virtual IP)?

can I use the real IP with a different resource agent (e.g. IPsrcaddr)?


thanks

gilberto




Michael Schwartzkopff wrote:
Am Dienstag, 27. Oktober 2009 14:55:42 schrieb gilberto migliavacca:
Hi

I have 2 nodes and 1 node that I'm using just
to manage the cluster.

I started up the nodes and created the following
configuration :

node custdevc03.funambol.com
node custdevc04.funambol.com
node custdevc05.funambol.com
primitive res.ip.m63 ocf:heartbeat:IPaddr2 \
         params ip="172.16.20.63" \
         op monitor interval="2s" timeout="1s"
primitive res.ocf.apache63 ocf:heartbeat:apache \
         params configfile="/etc/httpd/conf/httpd.conf" \
         op monitor interval="30s" timeout="10s" \
         meta target-role="Started"
location lo.m63 res.ip.m63 -inf: custdevc04.funambol.com
colocation co.apache63_on_m63 -inf: res.ocf.apache63 res.ip.m63
order o.m63_before_apache63 inf: res.ip.m63 res.ocf.apache63:start
property $id="cib-bootstrap-options" \
         dc-version="1.0.5-462f1569a43740667daf7b0f6b521742e9eb8fa7" \
         cluster-infrastructure="openais" \
         expected-quorum-votes="3" \
         stonith-enabled="false"



the problem is that I cannot manage the apache instance
on the machine 63.

Sorry, but was is machine63? You have custdevc03, 04 and 05. Did you mean: "The machine that run resource res.ip.m63"?

Then why did yor *forbid* to run both resources on the same machine with
*-inf* points in the colocation?

When I run
- crm(live)resource# start res.ocf.apache63
Nothing happen on the 63 machine, the apache service is down

these are my questions
- did I take all the steps correctly?
Depends on what you want to do.

- is my confoguration correct?
Depends on what you want to do.

- Have I to remove the start up script in the /etc/init.d?
No. Just be sure that it is NOT called during the system start.

- How can I check the log of the pacemaker in order to understand the
issue?
Read the logs /var/log/syslog or /var/log/messages. grep for "res.ocf.apache63" and search for "ERROR".



_______________________________________________
Pacemaker mailing list
Pacemaker@oss.clusterlabs.org
http://oss.clusterlabs.org/mailman/listinfo/pacemaker

Reply via email to