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 > [email protected] > http://lists.xensource.com/mailman/listinfo/xen-api _______________________________________________ xen-api mailing list [email protected] http://lists.xensource.com/mailman/listinfo/xen-api
