[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-users] xen, iscsi and resilience to short network outages


  • To: xen-users@xxxxxxxxxxxxxxxxxxx, sos22@xxxxxxxxxxxxx
  • From: "Steve Feehan" <sfeehan@xxxxxxxxx>
  • Date: Fri, 10 Nov 2006 22:38:41 -0500
  • Delivery-date: Fri, 10 Nov 2006 19:38:57 -0800
  • Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=MrU0j7/7V/qy01h1J4JWdcVNV2Cfqmzk6uNB5C34oDWW7rjJij/5EhitrU5U3+aK/27JPnZC0CdxOKdRMgfb7W7e3eQY9rte/rPJ3OlbJ88B2PIIcbCUNUMUGEC7aK661XwQaXYyO/0vUvB0yYAJkTkvsdCIWAzUZ0B742hZCBY=
  • List-id: Xen user discussion <xen-users.lists.xensource.com>

On 11/10/06, Steven Smith <sos22-xen@xxxxxxxxxxxxx> wrote:
> INIT: cannot execute "/sbin/mingetty"
> INIT: cannot execute "/sbin/mingetty"
> INIT: cannot execute "/sbin/mingetty"
> INIT: Id "1" respawning too fast: disabled for 5 minutes
What happens after the five minutes is up?

Steven.

Well, I've never waited 5 minutes to find out. But it was an hour
after the original IO timeout before I tried to login at the console
and saw these messages. And during this time I was not able to ssh
into the VM (but it was still pingable).

So I will force a timeout on Monday and see what happens after 5
minutes. But my guess is that the system is not going to recover.

--
Steve Feehan

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.