Thanks a lot, Willy!
Seems the issue was with preference of resolvers itself.
After configuring it to prefer IPv4 as stated by you; it starting working
like a charm.
Ref:
https://cbonte.github.io/haproxy-dconv/1.8/configuration.html#5.2-resolve-prefer
Thanks again for your help.
On Thu, Nov 8,
Hello Vijay,
I'm having several comments below :
On Thu, Nov 08, 2018 at 08:21:37AM +0530, Vijay Bais wrote:
> Hello Aleksandar,
>
> I tried running haproxy as root, but it still failed with same logs.
>
> Btw, here's the global section used,
>
>
> global
> log 127.0.0.1 local2
>
Hello Aleksandar,
I tried running haproxy as root, but it still failed with same logs.
Btw, here's the global section used,
global
log 127.0.0.1 local2
chroot /var/lib/haproxy
pidfile /var/run/haproxy.pid
maxconn 4000
userroot
group roo
Thanks for the reply!
Here, the haproxy process runs as a *haproxy* user itself.
Let me try it as root and revert back.
On Tue 6 Nov, 2018, 9:19 PM Aleksandar Lazic, wrote:
> Hi Vijay.
>
> Am 06.11.2018 um 10:06 schrieb Vijay Bais:
> > Hello,
> >
> > I'm using HAProxy 1.8 as a forward proxy wi
Hi Vijay.
Am 06.11.2018 um 10:06 schrieb Vijay Bais:
> Hello,
>
> I'm using HAProxy 1.8 as a forward proxy with below configuration
>
>
>
> defaults
> mode tcp
> log global
> option tcplog
> option
Hello,
I'm using HAProxy 1.8 as a forward proxy with below configuration
defaults
modetcp
log global
option tcplog
option dontlognull
option http-server-close
#option forwardfor except 127.0.
6 matches
Mail list logo