Take the 2-minute tour ×
Server Fault is a question and answer site for professional system and network administrators. It's 100% free, no registration required.

I tried everything:

service varnishlog start - logs everything

varnishlog -D -c -m TxStatus:503 > /var/log/varnish/varnish.log - doesn't seem to be doing anything

varnishlog -c -m TxStatus:503 > /var/log/varnish/varnish.log - only logs until I close my SSH connection

I'm out of options, any help?

Note: varnishncsa is not an option, since it doesn't tell me which error causes the 503. I'm running Varnish 3.x (latest) and CentOS 5.8 with Apache 2 as backend.

share|improve this question
add comment

1 Answer 1

up vote 2 down vote accepted

If I understand correctly varnishlog -c -m TxStatus:503 > /var/log/varnish/varnish.log does meet your needs but has the downside to stop once you close ssh.

If you need to temporary log 503 error, like for a few months, time to debug a problem, then you can look at nohup or screen.

If you need to permanently log 503 error, have a look at varnishlog init script (/etc/init.d/varnishlog ).

share|improve this answer
Editing /etc/init.d/varnishlog had no effect (still logged all hits). Tried nohup, logged in again and it's still in the process list, so I'm guessing it worked. Thanks! –  Eduard Luca Aug 3 '12 at 11:01
add comment

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.