Hello Dejan,
I have solved the problem described below by
adding the parameter
statusurl="http://127.0.0.1/server-status";
to the apache resource and by replacing this line
Listen 10.5.75.83:80
by the line
Listen 80
in the file /etc/apache2/ports.conf. So we enabled
the Apache to list
On Wed, Jan 25, 2012 at 04:35:39PM +0100, Michal Vyoral wrote:
> Hi Dejan,
>
> On Tue, Jan 24, 2012 at 11:52:20PM +0100, Dejan Muhamedagic wrote:
> > Hi,
> >
> > On Tue, Jan 24, 2012 at 06:31:54PM +0100, Michal Vyoral wrote:
> > > Hello,
> > > we had a cluster of two nodes both running Debian 5.0
Hi Dejan,
On Tue, Jan 24, 2012 at 11:52:20PM +0100, Dejan Muhamedagic wrote:
> Hi,
>
> On Tue, Jan 24, 2012 at 06:31:54PM +0100, Michal Vyoral wrote:
> > Hello,
> > we had a cluster of two nodes both running Debian 5.0, each with two
> > resources
> > IPaddr2 and apache managed by pacemaker 1.0.
Hi,
On Tue, Jan 24, 2012 at 06:31:54PM +0100, Michal Vyoral wrote:
> Hello,
> we had a cluster of two nodes both running Debian 5.0, each with two resources
> IPaddr2 and apache managed by pacemaker 1.0.9.1. After an upgrading of
> one node from Debian 5.0 to 6.0 we have a problem to start the
> a
Hello,
we had a cluster of two nodes both running Debian 5.0, each with two resources
IPaddr2 and apache managed by pacemaker 1.0.9.1. After an upgrading of
one node from Debian 5.0 to 6.0 we have a problem to start the
apache resource on the upgraded node. Here are the details:
Versions of heartb
