We could use varnishlog
too, a better remembered name compared with varnishncsa
.
We need run it with root privilege - sudo varnishlog
, otherwise somethime it will said VSM: Could not get hold of varnishd, is it running?
.
For writing log to file, we could run sudo varnishlog -w <filename>
.
-w <filename>
Redirect output to file.
The file will be overwritten unless the -a
option was specified.
If the application receives a SIGHUP
in daemon mode the file will be reopened allowing the old one to be rotated away.
The file can then be read by varnishlog and other tools with the -r
option, unless the -A
option was specified. This option is required when running in daemon mode.
For reading the log file, we could run sudo varnishlog -r <filename>
.
-r <filename>
Read log in binary file format from this file. The file can be created with varnishlog -w filename
.