On Mon, Oct 3, 2011 at 7:16 AM, Gerald Vogt wrote:
> On 03.10.11 03:47, Serge Dubrouski wrote:
> > As I wrote before: you should be able to test this easily by sending
> a
> > STOP signal to the named process. At least in this situation I see
> that
> > the "rndc stop" doesn't return
On 03.10.11 03:47, Serge Dubrouski wrote:
> As I wrote before: you should be able to test this easily by sending a
> STOP signal to the named process. At least in this situation I see that
> the "rndc stop" doesn't return before those 60s.
>
>
> Indeed you are right. Thanks for catchi
On Sun, Oct 2, 2011 at 12:31 AM, Gerald Vogt wrote:
> On 02.10.11 03:18, Serge Dubrouski wrote:
> > 1. You expect rndc and host to be in $PATH. At the same time the path
> to
> > named can be configured. I think consequently, the same should apply
> to
> > rndc and host as they are bi
On 02.10.11 03:18, Serge Dubrouski wrote:
> 1. You expect rndc and host to be in $PATH. At the same time the path to
> named can be configured. I think consequently, the same should apply to
> rndc and host as they are bind utils.
>
> On our CentOS servers we run the latest version
On Sat, Oct 1, 2011 at 2:49 PM, Gerald Vogt wrote:
> On 01.10.11 04:53, Serge Dubrouski wrote:
> > Technically, I don't want the cluster to control the service in the
> > meaning of starting and stopping. The cluster controls the IP
> addresses
> > and moves them between nodes. The dn
On 01.10.11 04:53, Serge Dubrouski wrote:
> Technically, I don't want the cluster to control the service in the
> meaning of starting and stopping. The cluster controls the IP addresses
> and moves them between nodes. The dns service resource is supposed to
> provide a check that th
On Fri, Sep 30, 2011 at 9:20 AM, Gerald Vogt wrote:
> On 30.09.11 15:03, Serge Dubrouski wrote:
> > May be you didn't look carefully but that script does exactly that, it
> > monitors process and service. Also if you want cluster to control your
> > service, it has to be able to start and stop it
On 30.09.11 15:03, Serge Dubrouski wrote:
> May be you didn't look carefully but that script does exactly that, it
> monitors process and service. Also if you want cluster to control your
> service, it has to be able to start and stop it. You can configure your
> service as a clone and it'll be up
May be you didn't look carefully but that script does exactly that, it
monitors process and service. Also if you want cluster to control your
service, it has to be able to start and stop it. You can configure your
service as a clone and it'll be up on several nodes.
But if you don't want to use it
On 30.09.11 13:41, Serge Dubrouski wrote:
> OCF script for bind was recently added to cluster-resources on gorging.
> Could you please try to use that one?
Which script where?
The one you have posted here:
http://lists.linux-ha.org/pipermail/linux-ha-dev/attachments/20110712/e1a1e792/attachment.o
OCF script for bind was recently added to cluster-resources on gorging.
Could you please try to use that one?
On Sep 30, 2011 2:09 AM, "Gerald Vogt" wrote:
> Hi!
>
> I am running a cluster with 3 nodes. These nodes provide dns service.
> The purpose of the cluster is to have our two dns service ip
On Fri, Sep 30, 2011 at 10:06:51AM +0200, Gerald Vogt wrote:
> Hi!
>
> I am running a cluster with 3 nodes. These nodes provide dns service.
> The purpose of the cluster is to have our two dns service ip addresses
> online at all times. I use IPaddr2 and that part works.
>
> Now I try to extend o
Hi!
I am running a cluster with 3 nodes. These nodes provide dns service.
The purpose of the cluster is to have our two dns service ip addresses
online at all times. I use IPaddr2 and that part works.
Now I try to extend our setup to check the dns service itself. So far,
if a dns server on any no
13 matches
Mail list logo
