Varnish install on aws
michaeljones401 at gmail.com
Sat Feb 13 19:43:07 CET 2016
Thank you, running ‘varnishd -d -a :80 -T localhost:6082 -b localhost:8080
-u varnish -g varnish -s file,/var/lib/varnish/varnish_storage.bin,1G’ works
When trying to run your original example it complained 'Only one of -b or
-f can be specified'. So I removed the the 'f'.
Changing it to ‘varnishd -a :80 -T localhost:6082 -b localhost:8080 -u
varnish -g varnish -s file,/var/lib/varnish/varnish_storage.bin,1G’
Starts Varnish and the web page now loads, thank you.
Out of interest, restarting the service fails on stopping the cache
[ec2-user at ip-xxx-xx-xx-xx varnish]$ sudo service varnish restart
Stopping Varnish Cache: [FAILED]
Starting Varnish Cache: [ OK ]
This isn't a huge issue, but any reason why the cache is failing?
Thanks again :)
On Sat, Feb 13, 2016 at 6:23 PM, Paul Armstrong <psa at otoh.org> wrote:
> > On 2016-02-13, at 05:25:41, Mike Jones <michaeljones401 at gmail.com>
> > DAEMON_OPTS="-a :80 \
> > -T localhost:6082\
> > -b localhost:8080 \
> > -u varnish -g varnish \
> > -s file,/var/lib/varnish/varnish_storage.bin,1G"
> > But when I restart both services, the webpage fails to load.
> Start varnish by hand: ‘varnishd -fd -a :80 -T localhost:6082 -b
> localhost:8080 -u varnish -g varnish -s
> This turns on foreground and debugging, which should help locate the issue.
> You can also use ‘varnishlog' to show what’s going on traffic wise after
> you’ve worked out why it’s giving you a connection refused on the front end.
> If performance is your game, ‘-s malloc' is more likely to serve you
> better than ‘-s file’, unless you’re on a t2.tiny.
> > Do I need to open port 8080 too?
> As pointed out by others, do not open port 8080 to the world.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the varnish-misc