Hey all,
Was hoping someone could help me out without needing to create a service request.
Due to technical issues we migrated our vCenter to a new server, which included backing up the database and restoring it.
The old vCenter Server had started a task to Upgrade vCenter Agents on cluster hosts which is now showing in the new vCenter.
All other posts about stuck tasks say to restart the service but I cannont do that as it is a new vCenter.
Is there a way to mark the task as complete?
I assume that this task is stored in the database and so should be able to be edited.
Rob
What's the vCenter version you're running?
Is it possible to restore a backup from the database prior to when the task was started? (probably not, just asking).
I never had the "pleasure" of dealing with this kind of issue, so can't really say if it is possible to "reset/stop" a task directly in the DB...
There is a possibility to reset your DB, that I know, but I'm guessing you rather not loose all data.
There is also the possibility to purge old data, but again, doubt it would help, and maybe you already tried it (http://kb.vmware.com/selfservice/microsites/search.do?cmd=displayKC&docType=kc&externalId=1025914&sl...)
vCenter server is vCenter 5.1.0 build 880146.
Need the database and cannot restore prior to task as the task was started over a week ago and we would loose to much data.
What's the Database you're using (built-in SQL express/ separate DB) ...?
In SQL you could querry the VPX_TASK
Something like this:
select task_id, parent_task_id, start_time, username, complete_time, entity_name, descriptionid, complete_state
from VPX_TASK
This used to work in vCenter 5.0 with SQL ...
Since I don't have access to my lab at the moment, I can't really test much.
Thanks for the SQL command, it is a seperate SQL database, SQL 2008 R2.
Using the commands I have found the task in the database but not sure if it is safe to edit, im guessing not?
Also rather than 1 entry there are multiple, so not sure if i just need to edit the one that is showing as running in vCenter (last one) or all of them:
402689 NULL 2012-12-01 11:39:10.037 NULL vCDCluster01 ClusterUpgrade.UpgradeAgent running
402701 NULL 2012-12-01 11:44:05.757 NULL vCDCluster01 ClusterUpgrade.UpgradeAgent running
410101 NULL 2012-12-08 12:44:42.213 NULL vCDCluster01 ClusterUpgrade.UpgradeAgent running
410121 NULL 2012-12-08 12:53:51.243 NULL vCDCluster01 ClusterUpgrade.UpgradeAgent running
410141 NULL 2012-12-08 14:28:01.020 NULL vCDCluster01 ClusterUpgrade.UpgradeAgent running
410161 NULL 2012-12-08 15:18:13.903 NULL vCDCluster01 ClusterUpgrade.UpgradeAgent running
410181 NULL 2012-12-08 16:14:00.310 NULL vCDCluster01 ClusterUpgrade.UpgradeAgent running
410261 NULL 2012-12-08 19:31:57.557 NULL vCDCluster01 ClusterUpgrade.UpgradeAgent running
410281 NULL 2012-12-08 19:51:36.447 NULL vCDCluster01 ClusterUpgrade.UpgradeAgent running
410301 NULL 2012-12-08 20:01:06.780 NULL vCDCluster01 ClusterUpgrade.UpgradeAgent running
410321 NULL 2012-12-08 20:12:07.497 NULL vCDCluster01 ClusterUpgrade.UpgradeAgent running
410341 NULL 2012-12-08 20:23:01.140 NULL vCDCluster01 ClusterUpgrade.UpgradeAgent running
410361 NULL 2012-12-08 20:30:17.883 NULL vCDCluster01 ClusterUpgrade.UpgradeAgent running
410381 NULL 2012-12-08 20:36:26.433 NULL vCDCluster01 ClusterUpgrade.UpgradeAgent running
I have no idea what the impact would be ... If it is even possible ... I think it is possible to adjust the settings in the DB though ...
Something like this (I'm not a SQL query kinda guy, so it might not work at all):
update VPX_TASK
Set status='done'
Where status='running'
Again, as I said ... Not tested and probably not supported.... I would test it, but haven't got access to my test-environment at the moment.
having the exact same issue... triggered by the same upgrade. did you ever find a resolution??
thanks
ken
actually just found one myself, here:
worked a treat. good luck!