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

[Jacques]

Yes, wget works fine.  As does lynx, etc.  :D

I checked ulimit per Jorge's response as well.  No impact.

I ran make test, (which I should have done before).  123 of 174 tests
failed.  All the same 503 issue.

I'm going to recompile with debugging enabled and see what I can see.

FYI, the log of tests is attached if you have any insights.

Thanks,
Jacques


On Sun, Jul 11, 2010 at 8:48 PM, Kacper Wysocki <kacperw at gmail.com> wrote:

> 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
> http://varnish-cache.org/wiki/DebuggingVarnish
> 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).
>
>
>
> 0K
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.varnish-cache.org/pipermail/varnish-misc/attachments/20100712/7bf2f0e5/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: check.log.gz
Type: application/x-gzip
Size: 43530 bytes
Desc: not available
URL: <http://lists.varnish-cache.org/pipermail/varnish-misc/attachments/20100712/7bf2f0e5/attachment-0001.bin>