crm ra info ocf:heartbeat:apache | grep port
export OCF_ROOT=/usr/lib/ocf
cd /usr/lib/ocf/resource.d/heartbeat
./apache meta-data | grep port
hth
jiaju liu wrote:
apache default listen port is 80, which is used by IIC so I have
to change apache listen port to 800. when I use service ht
apache default listen port is 80, which is used by IIC so I have to change
apache listen port to 800. when I use service httpd start it is ok however when
I use pacemaker to start it it failed
it shows :apache_start_0 (node=mds1, call=57, rc=1, status=complete): unknown
error
the apache agent
Devin,
Thanks for your support.
As I have tested, its not a problem on the shutdown order. On a regular
shutdown everything is working fine until I pull the power cable. After losing
the ilo communication the status of the online node changes to "online
UNCLEAN". The other node which is turned
Johannes Freygner wrote:
> You mean with corosync will work fine, because I am using heartbeat instead.
I suspect that it's a similar situation with heartbeat. The problem is
pacemaker losing communication before the node cleanly disconnects.
The behavior I saw on my own clusters is that becau
Devin,
You mean with corosync will work fine, because I am using heartbeat instead.
Using "shutdown " and pulling the power cable or pulling the power cable
directly without shutting down gives always the same solution. The resource
wouldn't be started by the other node, because it can't fe
Johannes Freygner wrote:
> could somebody give me an idea what will be the best stonith solution on a
> drbd cluster to avoid split brain if the network between the nodes is lost.
>
> I have already tried to use stonith with ILO, but if the power cable is
> removed from the node (because we ha
Hi,
could somebody give me an idea what will be the best stonith solution on a drbd
cluster to avoid split brain if the network between the nodes is lost.
I have already tried to use stonith with ILO, but if the power cable is removed
from the node (because we have to service the hardware) the
Hi Florian,
It would help if you shared your ntp resource agent so we can understand
> how it updates its master preference.
>
> See also:
> http://www.linux-ha.org/doc/dev-guides/_specifying_a_master_preference.html
>
ok, it is attached.
--
Regards
Simon Jansen
---
On 2011-01-03 10:07, Simon Jansen wrote:
> Hi,
>
> I have got some multistate resources running. This resources should
> start after the resources resIP (IPaddr2) and resFSys (Filesystem).
> So to accomplish this requirement I defined the following constraints.
> colocation colFSysNTP inf: msNTP:M
Hi,
I have got some multistate resources running. This resources should start
after the resources resIP (IPaddr2) and resFSys (Filesystem).
So to accomplish this requirement I defined the following constraints.
colocation colFSysNTP inf: msNTP:Master resFSys
colocation colIPNTP inf: msNTP:Master r
10 matches
Mail list logo
