Mailing List Archive: Varnish 4.1.3 (RPM rhel6) not listening on all interfaces

Varnish 4.1.3 (RPM rhel6) not listening on all interfaces

Nov 17, 2016, 3:54 PM

Post #1 of 4 (517 views)

Hi all,

I've been upgrading Varnish to 4.1.3 using an RPM
varnish-4.1.3-1.el6.x86_64

All is good, except of Varnish cannot be configured to listen on all
interfaces via sysconfig file?! I read the docs and they claim that the
sysconfig works as before - EG, :80 will make Varnish listen on port 80
on all interfaces. However, I cannot achieve this! Varnish errors out
with

Starting Varnish Cache: Error: Cannot open socket: :80: Address
family not supported by protocol

Currently I *must* specify all the IPs I want Varnish to listen to on
in the sysconfig file.

This is particulary annoying when trying to automate the config with a
mix of physical and virtual IPs..

I'm assuming I'm doing smth wrong, anybody has any suggestions?

thanks

v

--
Regards

Viktor Villafuerte
Optus Internet Engineering
t: +61 2 80825265

_______________________________________________
varnish-misc mailing list
varnish-misc@varnish-cache.org
https://www.varnish-cache.org/lists/mailman/listinfo/varnish-misc

Re: Varnish 4.1.3 (RPM rhel6) not listening on all interfaces [ In reply to ]

dridi at varni

Nov 18, 2016, 1:46 AM

Post #2 of 4 (505 views)

Permalink

On Fri, Nov 18, 2016 at 12:54 AM, Viktor Villafuerte
<viktor.villafuerte@optusnet.com.au> wrote:
> Hi all,
>
> I've been upgrading Varnish to 4.1.3 using an RPM
> varnish-4.1.3-1.el6.x86_64
>
> All is good, except of Varnish cannot be configured to listen on all
> interfaces via sysconfig file?! I read the docs and they claim that the
> sysconfig works as before - EG, :80 will make Varnish listen on port 80
> on all interfaces. However, I cannot achieve this! Varnish errors out
> with
>
> Starting Varnish Cache: Error: Cannot open socket: :80: Address
> family not supported by protocol

Is your kernel started with IPv6 disabled? I think this is a known issue.

Dridi

_______________________________________________
varnish-misc mailing list
varnish-misc@varnish-cache.org
https://www.varnish-cache.org/lists/mailman/listinfo/varnish-misc

Re: Varnish 4.1.3 (RPM rhel6) not listening on all interfaces [ In reply to ]

dridi at varni

Nov 18, 2016, 6:38 AM

Post #3 of 4 (504 views)

Permalink

> Currently I *must* specify all the IPs I want Varnish to listen to on
> in the sysconfig file.

If IPv6 is disabled as I suspect, you could start with -a 0.0.0.0:80
to listen to all IPv4 interfaces. Does that work?

Dridi

_______________________________________________
varnish-misc mailing list
varnish-misc@varnish-cache.org
https://www.varnish-cache.org/lists/mailman/listinfo/varnish-misc

Re: Varnish 4.1.3 (RPM rhel6) not listening on all interfaces [ In reply to ]

viktor.villafuerte at optusnet

Nov 20, 2016, 3:05 PM

Post #4 of 4 (501 views)

Permalink

Hi Dridi,

yes, kernel is ipv6 disabled and 0.0.0.0 does seems to fix this. :)

thanks

v

On Fri 18 Nov 2016 10:46:18, Dridi Boukelmoune wrote:
> On Fri, Nov 18, 2016 at 12:54 AM, Viktor Villafuerte
> <viktor.villafuerte@optusnet.com.au> wrote:
> > Hi all,
> >
> > I've been upgrading Varnish to 4.1.3 using an RPM
> > varnish-4.1.3-1.el6.x86_64
> >
> > All is good, except of Varnish cannot be configured to listen on all
> > interfaces via sysconfig file?! I read the docs and they claim that the
> > sysconfig works as before - EG, :80 will make Varnish listen on port 80
> > on all interfaces. However, I cannot achieve this! Varnish errors out
> > with
> >
> > Starting Varnish Cache: Error: Cannot open socket: :80: Address
> > family not supported by protocol
>
> Is your kernel started with IPv6 disabled? I think this is a known issue.
>
> Dridi

--
Regards

Viktor Villafuerte
Optus Internet Engineering
t: +61 2 80825265

_______________________________________________
varnish-misc mailing list
varnish-misc@varnish-cache.org
https://www.varnish-cache.org/lists/mailman/listinfo/varnish-misc