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-api

Re: [Xen-API] Re: [Xen-users] XCP - license expiry problem - http://bugz

To: xen-api@xxxxxxxxxxxxxxxxxxx
Subject: Re: [Xen-API] Re: [Xen-users] XCP - license expiry problem - http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=1756 not fixed?
From: George Shuklin <george.shuklin@xxxxxxxxx>
Date: Tue, 19 Apr 2011 20:13:36 +0400
Delivery-date: Tue, 19 Apr 2011 09:13:56 -0700
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:subject:from:to:in-reply-to:references :content-type:date:message-id:mime-version:x-mailer :content-transfer-encoding; bh=UuszBdiXXtLP8m7aKBwCu9nviziP0yI07eqzhamWgDs=; b=GLtnPrrRw0V1BLhIGfzbEK3Qid8RIokp1v9anV/4YPRrQDH86z6TcJBVQrt1VK/kIe WrmULSK2D+nhYewr/0rTbU+ckrcZ7saSffsHEpsZcfh1vPhE+/YVmXFnCrvClOiZ+nRn WAYzEmuZvqfHX2I+PPJ98xZpbEKNPY89kz5Aw=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=subject:from:to:in-reply-to:references:content-type:date:message-id :mime-version:x-mailer:content-transfer-encoding; b=j5FrkLZ3T4QC/3OAk2aOaLPWzhcJKzpkR7pLtOmCdQMaorUaD1JxH9dZj8sbt+wL2Q H3O1ZZ6ffwUb50cxuxPnkjTQgPjCQq9lNgrVmKwq3osiJB4mDQbpO9+NMGF+pCxcEaq/ 8vrKLTHPhTpasA/TFqek+2ExJjcTCz62kScFU=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <4DADB1DA.4050609@xxxxxxxxxx>
List-help: <mailto:xen-api-request@lists.xensource.com?subject=help>
List-id: Discussion of API issues surrounding Xen <xen-api.lists.xensource.com>
List-post: <mailto:xen-api@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-api>, <mailto:xen-api-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-api>, <mailto:xen-api-request@lists.xensource.com?subject=unsubscribe>
References: <4D9C7ACF.2040507@xxxxxxxx> <20110410192340.GJ32595@xxxxxxxxxxx> <4DADB1DA.4050609@xxxxxxxxxx>
Sender: xen-api-bounces@xxxxxxxxxxxxxxxxxxx
I know one very bad reason why xcp host can disable itself. It's (xen?)
bug with unkillable domain. this domain in domain lists looks like
deadbeef-dead-beef-.... .

I'll describe this problem in next post.


В Втр, 19/04/2011 в 17:01 +0100, Mike McClurg пишет:
> >> i have 3 XCP 1.0.0 hosts in a pool, one of them is not enabled:
> >>
> >> xe host-param-list uuid=402f07f4-99c0-4501-9787-8dee8984e313
> >> uuid ( RO)                                 :
> >> 402f07f4-99c0-4501-9787-8dee8984e313
> >>                             name-label ( RW): xcp1.domain.com
> >>                       name-description ( RW): Default install of XenServer
> >>                     allowed-operations (SRO): VM.migrate; evacuate;
> >> shutdown; provision; reboot; VM.resume; VM.start
> >>                     current-operations (SRO):
> >>                                enabled ( RO): false
> >>
> >> so i tried:
> >>
> >> xe host-enable host=xcp1.domain.com
> >> Your license has expired.  Please contact your support representative.
> >>
> >> All three hosts looks like they are going to expire in 30 days. Is there
> >> a workaround for this?
> The license expiry warning should be benign...
> >> Hack with a state.db is not working either.
> >>
> >> r.
> >>
> Was the xapi process stopped when you hacked state.db? Has restarting 
> xapi caused the host to be enabled? Why was the host disabled in the 
> first place? Did you manually disable it or did it disable itself 
> because of the license expiry?
> 
> Mike
> 
> _______________________________________________
> xen-api mailing list
> xen-api@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/mailman/listinfo/xen-api



_______________________________________________
xen-api mailing list
xen-api@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/mailman/listinfo/xen-api