All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nivedita Singhvi <niv@us.ibm.com>
To: Andrew Athan <aathan-xen-1542@cloakmail.com>
Cc: xen-devel@lists.sourceforge.net
Subject: Re: Problem with apache proxying between domains
Date: Mon, 14 Feb 2005 16:41:01 -0800	[thread overview]
Message-ID: <4211451D.1000808@us.ibm.com> (raw)
In-Reply-To: <42113431.6010901@cloakmail.com>

Andrew Athan wrote:

> What's the equivalent of strace on Windows XP?

Ah, right, you did say 240 was a windows box.

I don't know that your browser read any data at all.
It starts off with a 64K window - and if you notice
in the log, it just ramps down till it goes to zero.
Doesn't look like any data got pushed to the application.
205 (dom0) sure pushed a bunch of data out, so not sure
that the problem is between dom0 <-> dom1. At least,
no evidence yet of that.

If it's not too much trouble, could you also grab
a trace of a successful transfer?

> I can strace the two apache processes on the Linux hosts, but not sure I 
> can get useful information about the quicktime plugin in the browser.

Might help to collect stats off dom1, though.

> By the way, dom1 is using swap which is an LVM volume in dom0.  Could 
> there be some kind of deadlock in which dom0's apache is blocking on a 
> network read which dom1 cannot service because it needs swap, which dom0 
> cannot supply via LVM because the dom0 inter-domain stuff is "stuck" 
> trying to service the apache inter-domain network request ??

See above - your trace is showing the exchange between dom0 and
the browser box, correct? It has a problem on the receiver end
(windows browser not reading) - double check that..

> I needed to make progress, so I have punted on inter-domain apache 
> proxying for now.  However, I can set up a test config easily enough if 
> that is of interest to the group.  The missing packets are somewhat 
> worrisome to me, since I would have thought that inter-domain 
> communication was lossless.

Could be ethereal that's missing the packets, not
necessarily the interfaces that dropped them, stats would tell..

thanks,
Nivedita



-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click

      reply	other threads:[~2005-02-15  0:41 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-14 21:15 Problem with apache proxying between domains Andrew Athan
2005-02-14 22:39 ` Nivedita Singhvi
2005-02-14 23:28   ` Andrew Athan
2005-02-15  0:41     ` Nivedita Singhvi [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4211451D.1000808@us.ibm.com \
    --to=niv@us.ibm.com \
    --cc=aathan-xen-1542@cloakmail.com \
    --cc=xen-devel@lists.sourceforge.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.