varnish reports [CLI telnet 127.0.0.1 42212 127.0.0.1 6082 Wr 101 Unknown request]

Joydeep Bakshi joydeep.bakshi at netzrezepte.de
Tue Apr 22 12:16:41 CEST 2014


and even with 6081 the log reports followings

[error] 17648#0: *8 connect() failed (111: Connection refused) while
connecting to upstream, client: 88.198.185.226, server:
www.dustri.bookopt.de, request: "GET / HTTP/1.1", upstream: "
http://127.0.0.1:6081/"


On Tue, Apr 22, 2014 at 3:42 PM, Joydeep Bakshi <
joydeep.bakshi at netzrezepte.de> wrote:

> Thanks for the info, but after starting varnish only the following ports
> are open
>
> # netstat  -nat | grep 60
> tcp        0      0 0.0.0.0:6082            0.0.0.0:*               LISTEN
> tcp        0      0 :::6082                 :::*                    LISTEN
>
>
> On Tue, Apr 22, 2014 at 3:33 PM, Dridi Boukelmoune <
> dridi.boukelmoune at zenika.com> wrote:
>
>> On Tue, Apr 22, 2014 at 10:04 AM, Joydeep Bakshi
>> <joydeep.bakshi at netzrezepte.de> wrote:
>> > Hello all,
>> >
>> > My setting works well  through nginx->apache but not through
>> > nginx->varnish->apache
>> >
>> > apache is configured to listen to port 8080 . when nginx uses
>> >
>> > proxy_pass http://127.0.0.1:8080
>> >
>> > the sites are running fine.
>> >
>> > If I introduce varnish after nginx  by  [proxy_pass
>> http://127.0.0.1:6082]
>> > the nginx starts throwing following error and browser also shows "Zero
>> Sized
>> > Reply"
>>
>> Hi,
>>
>> Varnish listens to the port 6081 by default for HTTP. The port 6082 is
>> the default port for the process administration (eg. varnishadm).
>>
>> Cheers,
>> Dridi
>>
>> > [error] 17147#0: *207 upstream sent no valid HTTP/1.0 header while
>> reading
>> > response header from upstream
>> >
>> > and /var/log/messages shows
>> >
>> > varnishd[16984]: CLI telnet 127.0.0.1 42212 127.0.0.1 6082 Wr 101
>> Unknown
>> > request.#012Type 'help' for more info.#012all commands are in
>> lower-case.
>> >
>> > varnishd[16984]: CLI telnet 127.0.0.1 42212 127.0.0.1 6082 Rd
>> Cache-Control:
>> > max-age=0
>> >
>> > obviously varnish is configured to listen to apache
>> >
>> > backend default {
>> >         .host = "127.0.0.1";
>> >         .port = "8080";
>> > }
>> >
>> > Can anyone please suggest the possible reason which is causing the
>> problem ?
>> >
>> > _______________________________________________
>> > varnish-misc mailing list
>> > varnish-misc at varnish-cache.org
>> > https://www.varnish-cache.org/lists/mailman/listinfo/varnish-misc
>>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://www.varnish-cache.org/lists/pipermail/varnish-misc/attachments/20140422/b4279b72/attachment.html>


More information about the varnish-misc mailing list