What are the steps to problem solve when all I can get are 503s?

Kacper Wysocki kacperw at gmail.com
Mon Jul 12 05:48:24 CEST 2010

On Sun, Jul 11, 2010 at 7:54 PM, Jacques <whshub at gmail.com> wrote:
> I tried using a local server and using a vcl rather than command line
> parameters to define the backend.  I still only get 503s.  Is there a way to
> better debug Varnish so that I can determine why it can't make a backend
> connection?

Yup there is a better way to debug. You attach a debugger to the live
process and watch your own request come in
it's a little hands on but works fine if you have symbols and don't
mind getting dirty.

A dumb and simple suggestion: can you wget the backend from the
varnish host? :-)

Still, to me it looks like something quite platform-specific, not so simple.
Do the makecheck tests all run fine?
Oh, and I have a solaris box here too, my makecheck fails and it looks
like there is some IPC problem:

#### v1   CLI RX| Unknown request in manager process (child not running).\n
---- v1   CLI debug.xid command failed: 101 Unknown request in manager
process (+++ child not running).

-------------- next part --------------
A non-text attachment was scrubbed...
Name: varnish-2.1.2-opensolaris-2009.fail.log
Type: text/x-log
Size: 3848 bytes
Desc: not available
URL: <https://www.varnish-cache.org/lists/pipermail/varnish-misc/attachments/20100712/c137a3f9/attachment-0003.bin>

More information about the varnish-misc mailing list