vCenter

When using update manager and running a scan this error is thrown. I'm not sure which log file to look at or where it is located at. Is this a common error? I also cannot stage any baselines. I can however scan my vms and templates. Are the baselines screwed up?

Message was edited by: Raymo

Message was edited by: Raymo

What error? :smileyhappy:

Uhh." Update Manager had an unknown error. Check the Tasks and Events tab and log files for details" was the error. As I mentioned I'm trying to find where in the logs to look but I had issues with the hosts previusly so I will be resintalling update manager and see how that goes.

Thanks for you insight. :smileyhappy:

Check the logs under C:\Documents and Settings\All Users\Application Data\VMware\VMware Update Manager\Logs

Yes I'm looking at the following logs

vmware-vum-server-log4cpp.log
vmware-vum-server-7.log

But I'm not really seeing anything. I also ran the generate update manager log bundle to make sure I'm looking at the correct logs.

Hi,

please check if this KB article applies to you:

Update Manager fails to scan a host with an unknown error

Also, check the log file /var/log/esxupdate.log on the host that you scanned.

- Andreas

Thanks Andreas

No that KB doesn't apply to me. I'll have a look at the esxupdate.log

I exported all the log files (could not choose individual) but I can' find the esxupdate.log.

It looks like this log file is not included when you export a log bundle via the vSphere client.

However, you can look at it via a web browser. Open the URL

  https://[host-ip]/host

and log in as root user when prompted.

- Andreas

Yes I was looking there too. I see configuration files but no esxupdate log

Okay, so this is not an ESXi 5.0 host, but 4.x ?!

With 4.1 you need to look at /var/log/vmware/hostd.log (search for "haTask-ha-host-vim.host.PatchManager").

No it's ESXi 5 host. Attached are the screen shots. I just didn't have a hand in the original setup so I'm trying to work this issue and verify the setup.

OK it's working a little. I can scan but it will throw the error when it tries to stage the patch.

Message was edited by: Raymo

OK had to contact VMware on this one. It turns out there was a syslog setting that was pointing to a non existent directory. Created the directory and changed the settigns and after a reboot everything is fine. Again Andreas I appreciate all your help

Could you give more information on the solution?

It appears during the initial setup syslog info was pointed to another directory but the directory did not actually exist. The error was not obvious to me in the logs but the VMware engineer was quick to find it. Once we created this directory for each host I was able to stage the updates and apply them.

Hope that helps