Hi,
I've been searching the forums trying to find an answer to this issue, but to no avail. Apologies if it's already here and I'm too stupid to see it.
We currently have four ESX 3.5 hosts managed via virtualcenter 2.5. The hosts are running the update 1 revision of ESX with patches up to and including 30/04/2008 applied. We have successful managed to remediate one of the hosts up to the lastest build yesterday (All ESX patches baseline attached). However, trying to get any of the other 3 to remediate is proving frustrating. Even though we take care to power off any VMs on each host before remediating the same behaviour always occurs. Once the first install event is listed in the VC recent tasks pane the progress status eventually times out with error "operation timed out".
I've checked the vmware-vci-log4cpp.log and the common theme seems to be:
2008-06-18 14:55:29:702 'InternalScheduledTasksMgr' 4380 INFO internalScheduledTasksMgr, 131 Internal Scheduled Tasks Manager Timer callback...
2008-06-18 14:55:29:702 'InternalScheduledTasksMgr' 4380 INFO internalScheduledTasksMgr, 613 InvokeCallbacks. Total number of callbacks: 3
2008-06-18 14:55:29:702 'InternalScheduledTasksMgr' 4380 INFO internalScheduledTasksMgr, 240 Internal Scheduled Tasks Manager Timer callback end of this timer slice.....Rescheduling after 300000000 microseconds
2008-06-18 14:55:29:702 'InternalScheduledTasksMgr' 4416 INFO internalScheduledTasksMgr, 680 Patch store disk free space is: 7045317632
2008-06-18 14:55:29:702 'InternalScheduledTasksMgr' 4416 INFO internalScheduledTasksMgr, 715 Temp directory disk free space is: 7045317632
This appears to continue until the operation timeout event occurs in the VC recent tasks pane. Rebooting the hosts and/or the VC server have no positive effect. Has anyone else had such issues?
Any help would be appreciated.
Thanks,
Andrew
