Management Agents v8.5.1 will not install on ESX 4.0 Update 2

[Solusjen]

HI,

had the same problem on one of 4 ESX server where I had to do this update.

I was sure that there was nothing active anymore so I edited the install script. Just keep de counter to zero and the script will run succesfull.

Just change the text + 1 to + 0 in the script on some lines.

It is not the best solution, but it worked for me.


Regards,
Lucien Bosman

[Florian Schmutz]

Hi Solusjen

If got the same prob. I Removed manualy with the previus szenario the varios software packs. No is no software pack listed anymore. I try to uninstall the whole agents with the script.
./install860vibs.sh --uninstall
Got this error:
HP Insight Manager Agent 8.6.0-11 Installer for VMware ESX
Target System is VMware ESX 4.1.0 build-260247
Server: ProLiant DL380 G6


This script will now attempt to set ESX Host in Maintenance Mode
for IM agents uninstall.
Do you wish to continue? (y/n) y
System is already in Maintenace mode.

/opt/hp/hp-agents-config /vmfs/volumes/ISO/hpmgmt/860
ls: configure*: No such file or directory
/vmfs/volumes/ISO/hpmgmt/860
Uninstalling HP Insight Manager Agents bulletin [hp-classic-mgmt-solution-860.11.0508] ...
....FAILED

I will now try to reboot the exs and try to uninstall / reinstall again.

But i expect that this will not work. Can you told me wath did you exactly switch the install860vibs.sh?

Thanks for your fast answer ^^

Kind Regards

Florian

[Florian Schmutz]

Oke jkopp version of uninstalling was working. After a reboot could i inst. the SMH again

[David Niven DE]

Same problem.

I want to run 'install851vibs.sh --uninstall' and got the error message with 'Insufficient arguments.'. There were 3 power-off VMs on the ESX 4.1 host.

I replaced
--- old --- line 405 ---
if [ "$VM_ID" = "Vmid" ] ; then
continue
else
--- old ---
with
--- new ---
if [ "$VM_ID" = "Vmid" ] ; then
continue
elif [ "$VM_ID" = "" ] ; then
continue
else
--- new ---

The uninstall runs fine after the fix. The function 'vmops_list_vm' (vim-cmd vmsvc/getallvms > $HPIM_VMLIST) returns a empty add the end, which is interpreted as a VM later.

I started the installation of install860avibs.sh afterwards.

Surprise, surprise -> same bug. But the coding is now in line 414.

825 -> 851 -> 860a

There could also a problem with comments on VM, but I removed all comments on VMs in vCenter before --uninstall and --install.

Make your homework:
1. Test with registered VMs on ESX host
2. Test with registered VMs on ESX host,
which has a comment (for example: last backup date or user/passwd)

thx.