All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Пётр Волков" <pva-IzMiZDvh46SHXe+LvDLADg@public.gmane.org>
To: containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org
Subject: Need help to debug container's freeze
Date: Fri, 29 Oct 2010 16:27:40 +0400	[thread overview]
Message-ID: <1288355260.4451.121.camel@tablet> (raw)

Hi. We are using lxc to separate different services into containers: for
this discussions we have apache+php, mysql, nginx containers to serve
our web application. After upgrade (I think from kernel 2.6.32 into
something newer, now we are using 2.6.35, but tried 34 too) we've
experience following issue: at some point nginx starts to show us "504
Gateway Time-out" error and while it is possible to ssh on server `ps
aux` hangs (with no ability to stop it), it is impossible to restart
apache container (hangs on stop) and the only way to fix this is to
restart server using sysrq or power button. At the same time there is
nothing in the logs. I suspect apache starts to eat lots of memory but
oom killer somehow freezes container but I don't have any proves. What
could you suggest to debug this issue? What sysrq information could be
useful here?

-- 
Peter.

             reply	other threads:[~2010-10-29 12:27 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-29 12:27 Пётр Волков [this message]
2010-10-31  0:36 ` Need help to debug container's freeze Matt Helsley
     [not found] ` <20101031003652.GD3566@count0.beaverton.ibm.com>
     [not found]   ` <20101031003652.GD3566-52DBMbEzqgQ/wnmkkaCWp/UQ3DHhIser@public.gmane.org>
2010-11-05 12:41     ` Need help to debug freeze on kernel side (somehow related to lxc) Пётр Волков

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=1288355260.4451.121.camel@tablet \
    --to=pva-izmizdvh46shxe+lvdladg@public.gmane.org \
    --cc=containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org \
    /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.