From: Nathan March <nathan@gt.net>
To: "Fajar A. Nugraha" <list@fajar.net>
Cc: Konrad Rzeszutek Wilk <konrad@darnok.org>,
"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: Crashing / unable to start domUs due to high number of luns?
Date: Fri, 17 Feb 2012 01:21:22 -0800 [thread overview]
Message-ID: <4F3E1C12.6010005@gt.net> (raw)
In-Reply-To: <CAG1y0scV6c=oRM3P8sMD8+u9Uu8Awzc0MFpjvzRgng=VYV8DgA@mail.gmail.com>
On 2/17/2012 1:15 AM, Fajar A. Nugraha wrote:
> On Fri, Feb 17, 2012 at 2:15 PM, Nathan March<nathan@gt.net> wrote:
>> I have this happening again on a server and running udev monitor (udevadm
>> monitor --kernel --udev --property) prints absolutely *nothing*. I've
>> confirmed on a working xen host that it does actually print a ton of
>> debugging when i restart a VM. This machine however prints nothing when
>> trying to spawn.
> This might sound silly, but is udevd running? I've had cases where it
> suddenly died.
>
Sometimes it takes someone to point out the obvious =)
It's running, but whether it's actually working or not may be another
question:
root 2476 0.0 0.0 6184 488 ? S<s Feb14 0:00
/sbin/udevd --daemon
root 16274 0.0 0.0 6180 284 ? S< Feb15 0:00 \_
/sbin/udevd --daemon
root 16285 0.0 0.0 6180 164 ? S< Feb15 0:00 \_
/sbin/udevd --daemon
*Although* we're currently on udev 141 which appears to be ancient, so
that may be the source of the problem. Will try an upgrade.
- Nathan
next prev parent reply other threads:[~2012-02-17 9:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-31 21:42 Crashing / unable to start domUs due to high number of luns? Nathan March
2012-02-01 1:30 ` Konrad Rzeszutek Wilk
2012-02-01 19:48 ` Nathan March
2012-02-17 7:15 ` Nathan March
2012-02-17 9:15 ` Fajar A. Nugraha
2012-02-17 9:21 ` Nathan March [this message]
2012-04-16 14:18 ` Konrad Rzeszutek Wilk
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=4F3E1C12.6010005@gt.net \
--to=nathan@gt.net \
--cc=konrad@darnok.org \
--cc=list@fajar.net \
--cc=xen-devel@lists.xensource.com \
/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.