Feed for content matching tag 'update_mgr'

VUM and erroneous disk space installation issue

gary1012 — Thu, 19 Nov 2009 19:57:26 GMT

Hello,

I have an interesting problem with a manual VUM installation and wanted to know if anyone has run into this problem. I'm trying to retrofit VUM into an existing vCenter on W2K8 R2 EE installation using VMware-VIMSetup-all-4.0.0-162902 and am getting a disk space issue (see attached). The error states that I need at least 20GB of free disk space to perform the VUM installation. I have two disks with 26GB and 54GB free and have tried both without success. Has anyone run into this issue before? If so, what was the workaround?

TIA,

-g

Community Supported, Community Rewarded - Please consider marking questions answered and awarding points to the correct post. It helps us all.

Can't enable Update Manager

llamaware — Tue, 17 Nov 2009 19:10:31 GMT

My problem is similar to the one found in this discussion:

http://communities.vmware.com/thread/214413?start=0&tstart=0

I have installed Vcenter on a VM, and on a seperate VM installed Update Manager. During the Installation of Update Manager I followed all the steps and pointed the Update Manager at my Vcenter server (They are both Windows Server 2008 SP2). It recognizes that the Update Manager has been installed, however when I right click enable, nothing happens. It is a clean install and there are no older Plug-Ins installed. I have rebuild the Update Manager VM a few times and still have the same problem. When I run a netstat on the VCenter server it shows the IP Connection and the correct port is established. Has anyone else had this problem/Any Suggestions

VUM Baseline Details Blank

JasonDubya — Thu, 12 Nov 2009 15:48:38 GMT

I'm running into an odd issue while attempting to apply updates for the first time in VI Client 2.5 on a ESX 3.5u3 host. When I go to the Update Manager tab, I see I have multiple updates that need to be applied (as shown in the attached picture). However, if I click on the Not Compliant link or attempt to remediate, I do not see the updates.

When I attempt to remediate the hosts, I can check the Select All box and below I will see 86 of 86 updates will be remediated, but when I click Next, I get an error stating Object reference not set to an instance of an object.

Has anyone seen this issue before? If you have or not, does anyone have any idea how to resolve this? Thank you.

Update Manager Latest Build Number ?

TonyJK — Sun, 01 Nov 2009 23:57:22 GMT

I would like to know

1) How can we find out the build number of Update Manager in VI Client ?

2) What is the latest build ?

3) Can we download Update Manager for vSphere separate from VI Client ?

Thanks

Waiting for Inventory Collector to Finish ?

TonyJK — Mon, 28 Sep 2009 03:06:38 GMT

We just update the latest patch on an ESX 4.0 Host.

When it reboots, it stops at the stage "Waiting for Inventory Collector to Finish". Is it a VC issue or an ESX host one ?

Thanks

Request Timed out Issues

kellumit — Wed, 07 Oct 2009 16:01:43 GMT

Hello Everyone.

Here is my situation. I have a poweredge 2850 and a powervault 22os attached to it as well. the server has 6 gigabit nic cards, 16 g's of memory, and is a 2 quad core processors.

Yesterday about 3:00pm all my thin clients went down. I tried to restart the virtual machines and the host and it would be to about 95% then it would say request timed out. I would have to restart the server and the storage device just to get it working about this has happened twice in the past week. It need happened before. just trying to get input if its a esx problem, server problem, storage problem, or switch/network connectivity problem.

Update manager for remote location?

chrisy — Tue, 01 Apr 2008 08:50:05 GMT

Suppose there's a local ESX farm, with VirtualCenter and around 14 ESX servers, and UpdateManager's handling patches. If a remote datacenter is added with enough bandwidth to manage a couple of ESX servers but not enough to push large files around easily, what's the best approach for Update Manager?

Assume for discussion that there's only a couple of remote ESX servers, and no budget / plan for a remote instance of VC.

Is there anyone actually in this situation? I'd rather not give up on update manager; it doesn't seem so good for virtual machines but handles ESX nicely, at least for local servers.

Chris

Problems with update manager - scan results in "download updates metadata first"

DiPersiaTech — Sat, 06 Dec 2008 14:19:22 GMT

So we have a brand new install of the Virtual Center server and client. (2.5) Also installed the update manager and client. Setup the update manager to pull the downloads last night, and I show files in the patch directory, and 18 critical host updates, 91 non-critical.

However, when we attempt to scan the hosts, they return, "Patch metadata for 10.0.0.2 missing. Please download updates metadata first."

Saw another thread re: multiple nics. (We do have multiple nics, but only one in use.) Problem is, I can't find the log file discussed under any of the infrastructure directories. I didn't want to mess with the vci-integrity.xml file if I didn't need to.

I attached the critical and non-critical baselines to the data center collection and it shows 2 unknown hosts. No go.

Any suggestions?

Installing Update 4 for ESX 3.5 using Update manager

techpaul — Thu, 06 Aug 2009 16:22:47 GMT

Hi,

I am trying to update 5 ESX 3.5 hosts from Update 2 to Update 4. I have created a baseline, choosing the fixed option and selecting only update 4. When I check the status column it shows that update 4 is not applicable to my esx host, how can this be?

I chose to remediate the baseline in any case to see if anything would happen, it starts and completes within 5 mins with no errors. I then reboot the host and can see that the build number has not change from 3.5.0 110268 (update 2), it looks like it hasnt done anything . I have checked on the VC server in the downloaded updates folder and can see that update 4 folder exists. We used update manager to update all esx hosts from update 1 to update 2 without any issues.

I have rebooted the vc server, checked eventviewer on the VC there are no errors, the update manager database is fine.

Any help is much appreciated

Metadata for patch missing

murreyaw — Tue, 05 Feb 2008 19:34:41 GMT

I am trying to run an initial scan of some new 3.5 hosts. I am getting the error "Metadata for patch Missing" when I scan against the "Critical Host Updates" Baseline.

Where can I get some more info, or has anyone else run into this?

Migrate Virtual machine: operation timed out - dest ip = <0.0.0.0>

bofh2 — Thu, 20 Aug 2009 07:05:23 GMT

yesterday, I installed the following patches on aESXhost, using update manager:

vmkctl and vmkernel RPMs (ESX350-200906401-BG)
netXen Driver (ESX350-200906402-BG)
Kernel Source and VMNIX (ESX350-200906403-BG)
bnx2x Driver for Broadcom (ESX350-200906405-BG)
VMware Tools (ESX350-200906406-BG)
krb5 and pam-krb5 (ESX350-200906407-BG)
VMX RPM (ESX350-200906408-BG)
VMware Tools (ESX350-200907403-BG)
vmx RPM (ESX350-200907404-BG)
Kernel Source and VMNIX (ESX350-200907405-BG)
vmkernel and hostd RPMs (ESX350-200907407-BG)

After the machine has been patched:

I can no longer migrate RUNNING virtual machines to this host
I can migrate some, but not all, virtual machines that are powered down, and start it
Some powered down virtual machines, that are migrated to the patched host, simple migrate automatically to another host, when they are powered on.

the vmkernel.log file contains the following:
Aug 20 08:27:20 andedce0005m vmkernel: 0:01:23:34.215 cpu1:1035)World: vm 1092: 901: Starting world vmware-vmx with flags 4
Aug 20 08:27:20 andedce0005m vmkernel: 0:01:23:34.674 cpu1:1092)World: vm 1093: 901: Starting world vmm0:andedcw0008v with flags 8
Aug 20 08:27:20 andedce0005m vmkernel: 0:01:23:34.674 cpu1:1092)Sched: vm 1093: 5333: adding 'vmm0:andedcw0008v': group 'host/user': cpu: shares=-3 min=0 minLimit=-1 max=-1
Aug 20 08:27:20 andedce0005m vmkernel: 0:01:23:34.674 cpu1:1092)Sched: vm 1093: 5352: renamed group 22 to vm.1092
Aug 20 08:27:20 andedce0005m vmkernel: 0:01:23:34.674 cpu1:1092)Sched: vm 1093: 5366: moved group 22 to be under group 4
Aug 20 08:27:20 andedce0005m vmkernel: 0:01:23:34.679 cpu1:1092)Swap: vm 1093: 2169: extending swap to 2097152 KB
Aug 20 08:27:23 andedce0005m vmkernel: 0:01:23:37.806 cpu0:1092)Migrate: vm 1093: 7383: Setting migration info ts = 1250749634579448, src ip = <10.240.230.13> dest ip = <0.0.0.0> Dest wid = -1 using SHARED swap
Aug 20 08:27:23 andedce0005m vmkernel: 0:01:23:37.807 cpu0:1092)World: vm 1094: 901: Starting world migSendHelper-1093 with flags 1
Aug 20 08:27:23 andedce0005m vmkernel: 0:01:23:37.807 cpu0:1092)World: vm 1095: 901: Starting world migRecvHelper-1093 with flags 1
Aug 20 08:28:23 andedce0005m vmkernel: 0:01:24:37.811 cpu3:1092)WARNING: Migrate: 1346: 1250749634579448: Migration considered a failure by the VMX. It is most likely a timeout, but check the VMX log for the true error.
Aug 20 08:28:23 andedce0005m vmkernel: 0:01:24:37.811 cpu3:1092)WARNING: Migrate: 1243: 1250749634579448: Failed: Migration determined a failure by the VMX (0xbad0091) @0x9eb9b5

notice the "dest ip = <0.0.0.0>", i checked log entries from other migrations to other hosts, these entries list the vmkernel destination ip address, example:
Aug 19 14:45:46 andedce0004m vmkernel: 51:04:02:01.073 cpu3:1104)Migrate: vm 1105: 7383: Setting migration info ts = 1250685934801620, src ip = <10.240.230.13> dest ip = <10.240.230.14> Dest wid = 1075 using SHARED swap
the vmkernel network configuration for the problematic host however looks ok, at least, when looking at it, using virtual center client

I assume the problem is caused by one of the patches, any solution for this problem out there?

Updates applied now no persistant storage msg

setht — Tue, 18 Aug 2009 06:56:10 GMT

I've just installed the following updates on a host in one of our ESX clusters:

ESX350-200907405-BG, ESX350-200905403-BG, ESX350-200905404-BG, ESX350-200905407-BG, ESX350-200906401-BG, ESX350-200906402-BG, ESX350-200906405-BG, ESX350-200906407-BG, ESX350-200907403-BG, ESX350-200907404-BG

It's completed (events say successful) but now I've got the following message:

"The VMware ESX Server does not have persisteent storage."

Is this a known issue with an easy fix or should I be looking to raise a support ticket to get it fixed?

Thanks.

Quick update - the iSCSI targets reads "0" from "Configuration" -> "Storage Adapters" -> "iSCSI Software Adapter". There were previously 6 available.

If I look under "Configuration" -> "Storage" it shows the 6 iSCSI datastores and using browse I can browse the first one ok.

Further update - the issue seems to be with the iSCSI initiator. It's can't log in to the target (Equallogic). The IQN is the same and the config seems correct though.

I get this message logged on the SAN - "iSCSI initiation connection failure. No response on connection for 6 seconds"

Message was edited by: setht

Difference between Patches and Upgrades in vCenter Server 4 ?

TonyJK — Tue, 18 Aug 2009 00:51:58 GMT

We just upgrade vCenter to Release 4. The ESX Hosts are still running ESX 3.5 U5.

When we run update manager, we observe that there are two checkboxes - Patches and Upgrade. We suppose that patches is for ESX Host 3.5 and upgrade for ESX 3.5 to vSphere 4. Is this correct ?

When we run update manager with both checkboxes selected, it does show up the patches we have to apply for those ESX 3.5 Hosts. However, there is no upgrade shows up for us to upgrade from ESX 3.5 U5 to vSphere. Is there any suggestion ?

Thanks

Newbie question

BigSam1 — Tue, 11 Aug 2009 17:34:23 GMT

Can I use Update Manager to update a web application on multiple instances of Windows 2k8 servers? If so, how do I do it?

How to determine what update is installed on ESX

sultanahmed — Mon, 27 Jul 2009 10:23:53 GMT

How do you know what update version is installed on an ESX host. As all I can see is 3.5.0,153875.

Also why is it update 1,2 3 etc are not viewable via the update manager...I'm I missing something?