[prev in list] [next in list] [prev in thread] [next in thread] 

List:       keepalived-devel
Subject:    Re: [Keepalived-devel] WG: Problems with SMTP_CHECK
From:       David Pujadas <dpujadas () atrapalo ! com>
Date:       2006-01-25 8:03:31
Message-ID: 200601250903.31684.dpujadas () atrapalo ! com
[Download RAW message or body]

Hi Heinz,

thanks for your answer.
I've finally implemented a solution based on a MISC_CHECK (executing a perl 
script that checks if smtp server is alive) because I couldn't wait any 
longer, but I'll try your solution asap.

On Tuesday 24 January 2006 12:57, Heinz.Knutzen@dataport.de wrote:
> David Pujadas wrote:
> >I'm trying to set up a cluster of smtp servers with keepalived-1.1.11
> >and kernel 2.6.14.
> >This is my keepalived.conf:
>
> ...
>
> >virtual_server 192.168.1.175 25
> >{
>
> ...
>
> >    real_server 192.168.1.180 25
> >    {
> >        SMTP_CHECK
> >        {
> >                connect_timeout 10
> >                retry 3
> >                delay_before_retry 5
> >        }
> >    }
> >
> >    real_server 192.168.1.181 25
> >    {
> >        SMTP_CHECK
> >        {
> >                connect_timeout 10
> >                retry 3
> >                delay_before_retry 5
> >        }
> >    }
> >}
>
> ...
>
> >Why does keepalived remove [192.168.1.181:25] service from VS when the
> >problem is connecting to server [192.168.1.180:25]? What's wrong with
> >my config file?
> >Or is there a problem with keepalived?
>
> Try running
> 	keepalived --dump-conf
> This will show keepalived's interpretation of your configuration by
> syslog.
> Propably you will see something like this:
> Keepalived_healthcheckers:  192.168.1.180:25
> Keepalived_healthcheckers:    Checked ip = 192.168.1.180
> Keepalived_healthcheckers:  192.168.1.181:25
> Keepalived_healthcheckers:    Checked ip = 192.168.1.180
>
> The checked ip of the second realserver is wrong.
> This is caused by a bug/feature in
> keepalived-1.1.11/keepalived/check/check_smtp.c
> which takes the ip address of the first realserver as default for all
> subsequent SMTP_CHECK sections.
>
> A workaround would be to add an explicit 'host' section with
> 'connect_ip' attribute like this:
> SMTP_CHECK {
>   host {
>     connect_ip 192.168.1.181
>   }
> }
>
> Greetings
> ---
> Heinz Knutzen
>
>
> -------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc. Do you grep through log
> files for problems?  Stop!  Download the new AJAX search engine that makes
> searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
> http://sel.as-us.falkag.net/sel?cmd=lnk&kid3432&bid#0486&dat1642
> _______________________________________________
> Keepalived-devel mailing list
> Keepalived-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/keepalived-devel

-- 
David Pujadas
www.atrapalo.com
Tel. 902 200 808


-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642
_______________________________________________
Keepalived-devel mailing list
Keepalived-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/keepalived-devel
[prev in list] [next in list] [prev in thread] [next in thread]