You dropped “server1” from the server line. So it’s reading the server address as the server-name and “check” as the server-address: server server-name server-address [check] [resolvers resolver-name]
From: DHAVAL JAISWAL [mailto:[email protected]] Sent: July-24-17 12:56 PM To: Aleksandar Lazic <[email protected]> Cc: [email protected] Subject: Re: AWS ELB as a backend With the following change its working on Haproxy. backend mybackend server server1 internal-testinelbtomcat-1988883184.ap-southeast-1.elb.amazonaws.com:8080<http://internal-testinelbtomcat-1988883184.ap-southeast-1.elb.amazonaws.com:8080> However, when i tried following config its throwing following error on Haproxy 1.7 could not resolve address 'check' resolvers myresolver nameserver dns1 8.8.8.8:53<http://8.8.8.8:53> resolve_retries 30 timeout retry 1s hold valid 10s backend mybackend server internal-testinelbtomcat-1988883184.ap-southeast-1.elb.amazonaws.com:8080<http://internal-testinelbtomcat-1988883184.ap-southeast-1.elb.amazonaws.com:8080> check resolvers myresolver haproxy -vv HA-Proxy version 1.7.8 2017/07/07 Copyright 2000-2017 Willy Tarreau <[email protected]<mailto:[email protected]>> Build options : TARGET = linux26 CPU = generic CC = gcc CFLAGS = -m64 -march=x86-64 -O2 -g -fno-strict-aliasing -Wdeclaration-after-statement -fwrapv OPTIONS = USE_OPENSSL=1 USE_PCRE=1 Default settings : maxconn = 2000, bufsize = 16384, maxrewrite = 1024, maxpollevents = 200 Encrypted password support via crypt(3): yes Built without compression support (neither USE_ZLIB nor USE_SLZ are set) Compression algorithms supported : identity("identity") Built with OpenSSL version : OpenSSL 1.0.1k-fips 8 Jan 2015 Running on OpenSSL version : OpenSSL 1.0.1k-fips 8 Jan 2015 OpenSSL library supports TLS extensions : yes OpenSSL library supports SNI : yes OpenSSL library supports prefer-server-ciphers : yes Built with PCRE version : 8.21 2011-12-12 Running on PCRE version : 8.21 2011-12-12 PCRE library supports JIT : no (USE_PCRE_JIT not set) Built without Lua support Built with transparent proxy support using: IP_TRANSPARENT IPV6_TRANSPARENT IP_FREEBIND Available polling systems : epoll : pref=300, test result OK poll : pref=200, test result OK select : pref=150, test result OK Total: 3 (3 usable), will use epoll. Available filters : [COMP] compression [TRACE] trace [SPOE] spoe On Sun, Jul 23, 2017 at 1:01 PM, Aleksandar Lazic <[email protected]<mailto:[email protected]>> wrote: Hi DHAVAL JAISWAL, DHAVAL JAISWAL wrote on 21.07.2017: > I have used ELB (public) as a front of Haproxy and ELB (internal) as a > backend for the apps server. > > so structure is like as follows. Currently using Haproxy 1.7. > However, request is not going to the backend server. > > ELB ->> HAPROXY -> ELB -> APPS server. > > Following config in my haproxy. Let me know what i am doing wrong. > > backend mybackend > > server server1 > internal-testinelbtomcat-1988883184.ap-southeast-1.elb.amazonaws.com<http://internal-testinelbtomcat-1988883184.ap-southeast-1.elb.amazonaws.com> Do you have set a resolver? http://cbonte.github.io/haproxy-dconv/1.7/configuration.html#5.3 Please post also the following data, thanks. haproxy -vv anonymized haproxy conf some error and access logs -- Best Regards Aleks -- Thanks & Regards Dhaval Jaiswal
