Re: connection to backend smtp server is being reset

I guest that was the answer.  I found out that  there was no listener
on .249 on the local server.

Now, works like a charm.

On Fri, Nov 22, 2013 at 9:06 AM, Roman Gelfand <[email protected]> wrote:
>>Does it work if you 'telnet 192.168.0.249 25' on the real servers themselves?
>
> nop.  I am getting
>
> root@pmx11:~# telnet 192.168.0.249 25
> Trying 192.168.0.249...
> telnet: Unable to connect to remote host: Connection refused
>
>>It looks like one of your real servers failed it's TCP_CHECK and was removed. As long as the other real server shows up in 'ipvsadm -L -n' it should be able to service requests for the VIP.
>
> Yes, this is not a problem as I didn't start the other real server.
>
> On Fri, Nov 22, 2013 at 12:45 AM, Todd Fleisher <[email protected]> wrote:
>> And you are testing the VIP from somewhere on the same subnet (not the keepalived nodes themselves) since you are using LVS-DR?
>>
>> Does it work if you 'telnet 192.168.0.249 25' on the real servers themselves?
>>
>> It looks like one of your real servers failed it's TCP_CHECK and was removed. As long as the other real server shows up in 'ipvsadm -L -n' it should be able to service requests for the VIP.
>>
>> Now that you have IPVS support, you should try and tcpdump all along the path and figure out where things are getting hung up.
>>
>> -T
>>
>> On Nov 21, 2013, at 7:36 PM, Roman Gelfand wrote:
>>
>>> I fixed can't initalize ipvs.  Still no go.
>>>
>>> Nov 21 22:21:37 lb1 Keepalived[2608]: Starting Keepalived v1.2.9 (11/20,2013)
>>> Nov 21 22:21:37 lb1 Keepalived[2609]: Starting Healthcheck child
>>> process, pid=2610
>>> Nov 21 22:21:37 lb1 Keepalived[2609]: Starting VRRP child process, pid=2611
>>> Nov 21 22:21:37 lb1 Keepalived_vrrp[2611]: Registering Kernel netlink reflector
>>> Nov 21 22:21:37 lb1 Keepalived_vrrp[2611]: Registering Kernel netlink
>>> command channel
>>> Nov 21 22:21:37 lb1 Keepalived_vrrp[2611]: Registering gratuitous ARP
>>> shared channel
>>> Nov 21 22:21:37 lb1 Keepalived_vrrp[2611]: Initializing ipvs 2.6
>>> Nov 21 22:21:37 lb1 Keepalived_vrrp[2611]: Opening file
>>> '/etc/keepalived/keepalived.conf'.
>>> Nov 21 22:21:37 lb1 Keepalived_healthcheckers[2610]: Initializing ipvs 2.6
>>> Nov 21 22:21:37 lb1 Keepalived_healthcheckers[2610]: Registering
>>> Kernel netlink reflector
>>> Nov 21 22:21:37 lb1 Keepalived_healthcheckers[2610]: Registering
>>> Kernel netlink command channel
>>> Nov 21 22:21:37 lb1 Keepalived_healthcheckers[2610]: Opening file
>>> '/etc/keepalived/keepalived.conf'.
>>> Nov 21 22:21:37 lb1 Keepalived_vrrp[2611]: Configuration is using : 61690 Bytes
>>> Nov 21 22:21:37 lb1 Keepalived_vrrp[2611]: Using LinkWatch kernel
>>> netlink reflector...
>>> Nov 21 22:21:37 lb1 Keepalived_healthcheckers[2610]: Configuration is
>>> using : 12661 Bytes
>>> Nov 21 22:21:37 lb1 Keepalived_healthcheckers[2610]: Using LinkWatch
>>> kernel netlink reflector...
>>> Nov 21 22:21:37 lb1 Keepalived_healthcheckers[2610]: Activating
>>> healthchecker for service [192.168.0.245]:25
>>> Nov 21 22:21:37 lb1 Keepalived_healthcheckers[2610]: Activating
>>> healthchecker for service [192.168.0.244]:25
>>> Nov 21 22:21:37 lb1 kernel: [    5.661834] IPVS: [rr] scheduler registered.
>>> Nov 21 22:21:37 lb1 mpt-statusd: detected non-optimal RAID status
>>> Nov 21 22:21:38 lb1 Keepalived_vrrp[2611]: VRRP_Instance(VI_1)
>>> Transition to MASTER STATE
>>> Nov 21 22:21:38 lb1 Keepalived_healthcheckers[2610]: TCP connection to
>>> [192.168.0.245]:25 failed !!!
>>> Nov 21 22:21:38 lb1 Keepalived_healthcheckers[2610]: Removing service
>>> [192.168.0.245]:25 from VS [192.168.0.249]:25
>>> Nov 21 22:21:39 lb1 Keepalived_vrrp[2611]: VRRP_Instance(VI_1)
>>> Entering MASTER STATE
>>>
>>> On Thu, Nov 21, 2013 at 8:46 PM, Todd Fleisher <[email protected]> wrote:
>>>> On Nov 21, 2013, at 4:22 PM, Roman Gelfand wrote:
>>>>
>>>>> There is, also, this in the log IPVS: Can't initialize ipvs: Protocol
>>>>> not available
>>>>
>>>> This is your problem. You don't have IPVS support in your kernel. Fix that and it should work.
>>>>
>>>>> From the google:
>>>> https://www.linuxquestions.org/questions/red-hat-31/can't-initialize-ipvs-protocol-not-available-351241/
>>>>
>>>> -T
>>>>
>>>>
>>>> ------------------------------------------------------------------------------
>>>> Shape the Mobile Experience: Free Subscription
>>>> Software experts and developers: Be at the forefront of tech innovation.
>>>> Intel(R) Software Adrenaline delivers strategic insight and game-changing
>>>> conversations that shape the rapidly evolving mobile landscape. Sign up now.
>>>> http://pubads.g.doubleclick.net/gampad/clk?id=63431311&iu=/4140/ostg.clktrk
>>>> _______________________________________________
>>>> Keepalived-devel mailing list
>>>> [email protected]
>>>> https://lists.sourceforge.net/lists/listinfo/keepalived-devel
>>
>>
>> ------------------------------------------------------------------------------
>> Shape the Mobile Experience: Free Subscription
>> Software experts and developers: Be at the forefront of tech innovation.
>> Intel(R) Software Adrenaline delivers strategic insight and game-changing
>> conversations that shape the rapidly evolving mobile landscape. Sign up now.
>> http://pubads.g.doubleclick.net/gampad/clk?id=63431311&iu=/4140/ostg.clktrk
>> _______________________________________________
>> Keepalived-devel mailing list
>> [email protected]
>> https://lists.sourceforge.net/lists/listinfo/keepalived-devel

------------------------------------------------------------------------------
Shape the Mobile Experience: Free Subscription
Software experts and developers: Be at the forefront of tech innovation.
Intel(R) Software Adrenaline delivers strategic insight and game-changing 
conversations that shape the rapidly evolving mobile landscape. Sign up now. 
http://pubads.g.doubleclick.net/gampad/clk?id=63431311&iu=/4140/ostg.clktrk