No route to host means your lb can't reach the backends, check gateway
configuration and confirm backend is reachable with ping, telnet, etc from
lb to backends and viceversa.
Regards
Sent from mobile
El 8 ago. 2016 10:28 p. m., "Scott Berry" <sc...@boompayments.com> escribió:
> Thanks :)
>
> Show that in the admin at the top ;)
>
> Yes, 3.10.1. Grep does not find anything in any log file about “too many”
> anything.
>
> I am seeing a lot of these lines:
> Aug 4 06:24:49 ZenLB pound: (b72f6b40) connect_nb: error after
> getsockopt: No route to host
>
> And occasional bunch of these:
> Aug 4 13:39:46 ZenLB pound: NULL get_thr_arg
>
> If that doesn’t help I can see about running some more tests. We are out
> of credits for the month but I’m going to see about purchasing more.
>
> *- - - - -*
> *Scott Berry*
> Lead Developer | Boom! Payments
> m: 1.661.478.7144
>
> From: Emilio Campos
> Reply-To: <zenloadbalancer-support@lists.sourceforge.net>
> Date: Monday, August 8, 2016 at 1:02 PM
> To: <zenloadbalancer-support@lists.sourceforge.net>
> Subject: Re: [Zenloadbalancer-support] Max connections in HTTP profile
>
> Execute
>
> dpkg -l | grep zen
>
> Also check your syslog file maybe you could see "Too many open files"?
>
> Sent from mobile
>
> El 8 ago. 2016 9:58 p. m., "Scott Berry" <sc...@boompayments.com>
> escribió:
>
>> Hi,
>>
>> I’ve removed the HTTP based farms since they were extremely limited in
>> connections. When using a tool like loadimpact.com we would see the LB
>> start slowing down and preventing connections from hitting the back-end
>> servers around 100-200 connections on the farm. Meanwhile the 4 back-end
>> servers had zero load and if I hit one directly it was instant response.
>> The L4XNAT profile had no limitation on the smaller tests, we haven’t hit a
>> larger test yet.
>>
>> My config was the most basic. Simple HTTP Farm with 4 back-end servers.
>> No real changes from default config that I can recall.
>>
>> I can run the similar test again watching syslog and see if there are
>> issues. I can also fail over to the backup and see if that has an issue.
>>
>> I don’t know where or how to tell what version of Zen is installed. It
>> isn’t in the GUI I can see and I can’t find that info online. How to?
>>
>> *- - - - -*
>> *Scott Berry*
>> Lead Developer | Boom! Payments
>> m: 1.661.478.7144
>>
>> From: Laura Garcia
>> Reply-To: <zenloadbalancer-support@lists.sourceforge.net>
>> Date: Sunday, August 7, 2016 at 11:55 PM
>> To: "zenloadbalancer-support@lists.sourceforge.net"
>> Subject: Re: [Zenloadbalancer-support] Max connections in HTTP profile
>>
>> Hi Scott, please share your HTTP configuration. Are you working with
>> 3.10.1?
>>
>> Also, you can inspect the /var/log/messages searching for some system
>> errors when the connections reach the limits.
>>
>> Kind Regards.
>>
>>
>> Laura Garcia
>> Zen Load Balancer Team
>> www.zenloadbalancer.com
>>
>> On Fri, Aug 5, 2016 at 3:59 AM, Scott Berry <sc...@boompayments.com>
>> wrote:
>>
>>> I assume we are running in to some limitation on max connections
>>> although I can’t find any documentation on Zen or on Pound that discusses
>>> this.
>>>
>>> We are load balancing a Magento store. Originally I had two farms, one
>>> for HTTP and one for HTTPS. Offloading SSL was one of the major goals.
>>>
>>> We did a soft launch and found that at around 200-400 connections on the
>>> HTTP farm the response time slowed to a crawl. None of the servers (Zen,
>>> App or DB) had much load at all. After banging my head around for a while I
>>> switched to a L4XNAT profile (after reading a post somewhere about a
>>> clustered Zen setup - front–end L4XNAT and then back-end HTTP Zen farms)
>>> and that seemed to solve the problem.
>>>
>>> So question being firstly, why the limitation and what is causing it?
>>> Resources were never an issue at all.
>>>
>>> I am ok with keeping the L4XNAT profile for the HTTP side of things but
>>> then what happens when the HTTPS farm starts needing that kind of
>>> connection size? I would rather not deal with SSL on each server, but if
>>> that is the end result I will. I just can’t see how 400 connections should
>>> be a limitation?
>>>
>>> Secondly, how now would I handle a redirect in Zen? I would like to get
>>> people off the root and on to WWW and would rather not have to let the
>>> traffic pass all the way back to the app servers before we do that. Almost
>>> every first time connection will be this way. Since I can’t use HTTP farms
>>> I can use the virtual host and redirect options. I suppose the only way is
>>> to have a dedicated IP for www and for root and use another farm just for
>>> redirection. But again I worry about connections… will that then end up
>>> with connection limitations? Or not because it is just redirect and done?
>>>
>>> Any input?
>>>
>>> *- - - - -*
>>> *Scott Berry*
>>> Lead Developer | Boom! Payments
>>> m: 1.661.478.7144
>>>
>>> ------------------------------------------------------------
>>> ------------------
>>>
>>> _______________________________________________
>>> Zenloadbalancer-support mailing list
>>> Zenloadbalancer-support@lists.sourceforge.net
>>> https://lists.sourceforge.net/lists/listinfo/zenloadbalancer-support
>>>
>>>
>> ------------------------------------------------------------------------------
>> _______________________________________________ Zenloadbalancer-support
>> mailing list Zenloadbalancer-support@lists.sourceforge.nethttps://lists.
>> sourceforge.net/lists/listinfo/zenloadbalancer-support
>>
>> ------------------------------------------------------------
>> ------------------
>> What NetFlow Analyzer can do for you? Monitors network bandwidth and
>> traffic
>> patterns at an interface-level. Reveals which users, apps, and protocols
>> are
>> consuming the most bandwidth. Provides multi-vendor support for NetFlow,
>> J-Flow, sFlow and other flows. Make informed decisions using capacity
>> planning reports. http://sdm.link/zohodev2dev
>> _______________________________________________
>> Zenloadbalancer-support mailing list
>> Zenloadbalancer-support@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/zenloadbalancer-support
>>
>> ------------------------------------------------------------------------------
> What NetFlow Analyzer can do for you? Monitors network bandwidth and
> traffic patterns at an interface-level. Reveals which users, apps, and
> protocols are consuming the most bandwidth. Provides multi-vendor support
> for NetFlow, J-Flow, sFlow and other flows. Make informed decisions using
> capacity planning reports. http://sdm.link/zohodev2dev___
> ____________________________________________ Zenloadbalancer-support
> mailing list Zenloadbalancer-support@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/zenloadbalancer-support
>
> ------------------------------------------------------------
> ------------------
> What NetFlow Analyzer can do for you? Monitors network bandwidth and
> traffic
> patterns at an interface-level. Reveals which users, apps, and protocols
> are
> consuming the most bandwidth. Provides multi-vendor support for NetFlow,
> J-Flow, sFlow and other flows. Make informed decisions using capacity
> planning reports. http://sdm.link/zohodev2dev
> _______________________________________________
> Zenloadbalancer-support mailing list
> Zenloadbalancer-support@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/zenloadbalancer-support
>
>
------------------------------------------------------------------------------
What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
patterns at an interface-level. Reveals which users, apps, and protocols are
consuming the most bandwidth. Provides multi-vendor support for NetFlow,
J-Flow, sFlow and other flows. Make informed decisions using capacity
planning reports. http://sdm.link/zohodev2dev
_______________________________________________
Zenloadbalancer-support mailing list
Zenloadbalancer-support@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/zenloadbalancer-support
