After a power cut i have had a long drama with my XenServer box.
Hindsight being what it is i probably need not have incurred such a long downtime.
The short story is my Log files had filled up, and the method to clean these up at the bottom of this post The Long story is :
After the powercut my XenServer failed to boot with the message XAPI service will not start. Press F8 to retry.
The retry fails to restart the XAPI.
I assumed the powercut had meant a bad write to my harddrive and so re-installed XenServer onto the
same harddisk. My box had 2 hard disks with the 2nd disk being the storage repository for the VM's.
After the re-install i manually had to add the 2nd hard disk as a storage repository using the 2nd part of this citrix article http://support.citrix.com/article/CTX120962
This added the 2nd hard disk as additional storage repository, so i could see all my VM disks but had no VM's attatched to them.
as per the document i created new VM's with no disk attatched. Then after it booted, i edited its config and atttched the VMs from my 2nd hard disk. Its pure guess work as to which disk is which machine but after a while had most of my machines up and running.
BUT
the server then died. I rebooted and XAPI SERVICE ERROR AGAIN
I thought now that my XenServer primary hard disk must be damaged from the power failure.
I install a new hard disk and re-install XenServer 5.6 Sp1 again.
I again manually attach my 2nd disk as storage repository. Manually create VMs and attach to the disk images.
the server then died. I rebooted and XAPI SERVICE ERROR AGAIN
I now think , hmmmm
I now go back to google and find http://support.citrix.com/article/CTX128316
Error Log Full up - Method to delete
Basically my error logs have filled up and killed the XAPI service. I just connected to my xenserver with WINSCP and deleted the 1.2GB logfile in \VAR\LOG. Restart the server and im back up and running.
I will now keep an eye on the log file to see if it grows , and work out what the errors are i guess,
No comments:
Post a Comment