![]() ![]() ![]() If this is invalid, please remove /opt/xensource/patch-backup/f735af04-069f-4cf0-b80a-795c178c94a8/ and retry.īasically there were files from my first patch-pool-apply run, so I simply removed the noted directory in the error from all 8 XenServer hosts in the pool with ‘rm -rf /opt/xensource/patch-backup/f735af04-069f-4cf0-b80a-795c178c94a8/’. Output: Backup files already present - aborting. This has happened to me before, as currently the root file system is only 4gb (which is very small by today’s standards) so it fills up quite easily when uploading updates.Īfter checking and confirming that all XenServer hosts had adequate space, I proceeded to run the patch-pool-apply command again, this time it failed with a different error. My first thought on this failing was that perhaps one of the XenServer hosts did not have enough disk space. The problems began when trying to apply the patches with ‘xe patch-pool-apply uuid=UUID’ The pool had 8 hosts and from the pool master I ran the usual ‘xe patch-upload file-name=update.xsupdate’ to upload the updates to all hosts, which succeeded. It all started when I attempted the simple task of applying some newly released patches to a XenServer 6.2 cluster. Sometimes the migration would fail and the virtual machine would stop or pause resulting in down time, here is how the problem was investigated and fixed. ![]() Recently I had a whole lot of problems migrating virtual machines running on XenServer 6.2 and 6.0.2. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |