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/
Home Products Support Community News


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: riki <phobie@xxxxxxxx>
Date: Tue, 26 Apr 2011 15:48:07 +0200
Delivery-date: Tue, 26 Apr 2011 06:48:17 -0700
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
User-agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv: Gecko/20110303 Thunderbird/3.1.9

On 19. 4. 2011 18:01, Mike McClurg wrote:

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) :
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.


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?


Hello Mike,

sure xapi was stopped when messing with state.db. Host was disabled because of license expiry.

I reinstalled the node and it is working fine at the moment.


xen-api mailing list