WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-users

[Xen-users] Re: XCP VM restart strangeness

To: Dave Scott <Dave.Scott@xxxxxxxxxxxxx>
Subject: [Xen-users] Re: XCP VM restart strangeness
From: SwiftWater Telecom Customer Service <service@xxxxxxxxxxxxxxxxx>
Date: Tue, 09 Mar 2010 16:25:05 -0500
Cc: "xen-users@xxxxxxxxxxxxxxxxxxx" <xen-users@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Fri, 26 Mar 2010 09:12:49 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <81A73678E76EA642801C8F2E4823AD21565E554188@xxxxxxxxxxxxxxxxxxxxxxxxx>
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
References: <4B96AD3B.1060005@xxxxxxxxxxxxxxxxx> <81A73678E76EA642801C8F2E4823AD21565E554188@xxxxxxxxxxxxxxxxxxxxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1.8) Gecko/20100227 Thunderbird/3.0.3
This is certainly odd. I was just testing my watchdog (it automatically restarts halted VMs that are marked to be restarted if they're found halted using xe), ran it from the Linux command line on my command and control server with a halted VM for it to restart and got:

[root@xc1-me1-vps007 cgi-bin]# sh ./watchdog.cgi
You gave an invalid session reference. It may have been invalidated by a server restart, or timed out. You should get a new session handle, using one of the session.login_ calls. This error does not invalidate the current connection. The handle parameter echoes the bad value given.
handle: OpaqueRef:90c823fb-548e-93f9-b2d2-34809fe74e87

I hopped on the same server with a new SSH connection, reran the watchdog and it went fine and restarted the down VM perfectly. I killed the VM, went back to the original term window, reran the watchdog, and it ran perfectly.

I swear this place is built over an ancient Indian burial ground.


Vern Burke

SwiftWater Telecom
http://www.swiftwatertel.com
ISP/CLEC Engineering Services
Data Center Services
Remote Backup Services

On 3/9/2010 3:41 PM, Dave Scott wrote:
Hi Vern,

Those are very odd symptoms! It's good that you've got a workaround.

If this happens again, grab a 'bugtool' on the master host when it's in this 
state:
   xen-bugtool --silent --yestoall
If you send me the output then I'll do some digging to see if I can figure out 
what happened.

Cheers,
Dave

-----Original Message-----
From: SwiftWater Telecom Customer Service
[mailto:service@xxxxxxxxxxxxxxxxx]
Sent: 09 March 2010 20:19
To: Dave Scott; xen-users@xxxxxxxxxxxxxxxxxxx
Subject: XCP VM restart strangeness

Just when I think I've got XCP beat into submission, it sneaks up and
whacks me again :).

I rebooted a CentOS VM from it's command line and it failed to restart.
A check of vm-list showed that the VM was showing halted on the pool
master and the slaves, but trying to vm-start resulted in an error that
the session reference was invalid.

After a great deal of fooling with it, I managed to clear the problem
by
doing a vm-reset-powerstate, which I wouldn't have expected to make any
difference, since the VM was already showing halted.

I toss this out for informational purposes, in case someone else runs
into this :).

--
Vern Burke

SwiftWater Telecom
http://www.swiftwatertel.com
ISP/CLEC Engineering Services
Data Center Services
Remote Backup Services


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

<Prev in Thread] Current Thread [Next in Thread>