On 02/09/11 22:44, Raoul Bhatia [IPAX] wrote:
> hi,
>
> On 09.02.2011 08:43, u.schmel...@online.de wrote:
>> I don't use ocf:heartbeat:apache because of my special configuration:
>>
>> apache is active on both nodes, the access is via haproxy, we have an
>> url http://localhost:80 which accesses th
hi,
On 09.02.2011 08:43, u.schmel...@online.de wrote:
I don't use ocf:heartbeat:apache because of my special configuration:
apache is active on both nodes, the access is via haproxy, we have an
url http://localhost:80 which accesses the local apache via ssl and
delivers a static page (returning
On 02/08/2011 02:37 PM, u.schmel...@online.de wrote:
>
> Hi list,
>
> have some problems to setup the above configuration. My environment is as
> follows:
>
> rhel6 , pacemaker-1.1.2-7.el6.x86_64, apache2, haproxy running on both nodes,
> service addresses are managed by pacemaker
> there is a
On 02/08/2011 02:37 PM, u.schmel...@online.de wrote:
>
> Hi list,
>
> have some problems to setup the above configuration. My environment is as
> follows:
>
> rhel6 , pacemaker-1.1.2-7.el6.x86_64, apache2, haproxy running on both nodes,
> service addresses are managed by pacemaker
> there is a
Hi list,
have some problems to setup the above configuration. My environment is as
follows:
rhel6 , pacemaker-1.1.2-7.el6.x86_64, apache2, haproxy running on both nodes,
service addresses are managed by pacemaker
there is an additional resource script, that takes care of reloading/restarting
