Skip to content

V
varnish-cache
Commit b3e08acc authored by Dag Haavi Finstad's avatar Dag Haavi Finstad
Browse files
Options

Update forgotten varnishlog example to 4.0 syntax. 

Fixes: #1610
parent 4e5828d8
Hide whitespace changes
Inline Side-by-side
Showing with 5 additions and 4 deletions
doc/sphinx/users-guide/troubleshooting.rst
View file @ b3e08acc
...@@ -106,16 +106,17 @@ give you a clue. Since `varnishlog` logs a lot of data it might be hard ...@@ -106,16 +106,17 @@ give you a clue. Since `varnishlog` logs a lot of data it might be hard
to track the entries down. You can set `varnishlog` to log all your 503 to track the entries down. You can set `varnishlog` to log all your 503
errors by issuing the following command:: errors by issuing the following command::
$ varnishlog -c -m TxStatus:503 $ varnishlog -q 'RespStatus == 503' -g request
If the error happened just a short time ago the transaction might still If the error happened just a short time ago the transaction might still
be in the shared memory log segment. To get `varnishlog` to process the be in the shared memory log segment. To get `varnishlog` to process the
whole shared memory log just add the '-d' parameter:: whole shared memory log just add the '-d' parameter::
$ varnishlog -d -c -m TxStatus:503 $ varnishlog -d -q 'RespStatus == 503' -g request
Please see the `varnishlog` man page for elaborations on further Please see the `vsl-query` and `varnishlog` man pages for elaborations
filtering capabilities and explanation of the various options. on further filtering capabilities and explanation of the various
options.
Varnish doesn't cache Varnish doesn't cache
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment