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

[Xen-API] License Expired

To: xen-api@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-API] License Expired
From: "Andres E. Moya" <amoya@xxxxxxxxxxxxxxxxx>
Date: Tue, 06 Sep 2011 14:45:29 -0400 (EDT)
Delivery-date: Tue, 06 Sep 2011 11:45:47 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <b9bf0e6e-d117-44ac-a626-744538bf21d1@mbs01>
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>
Sender: xen-api-bounces@xxxxxxxxxxxxxxxxxxx
After upgrading to xcp 1.1 beta the master started complaining that the license 
had expired. We en into /var/xapi/state.db as stated in  
http://ronnybull.com/2011/07/15/xen-cloud-platform-xcp-license-expired-after-30-days/#comment-98
 and changed the date.

This worked but on the slaves it has not, currently all our slaves are down.

Does anyone know how to fix this?



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

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