VAMI no longer up after update to 6.5.0.22000 Build Number 9451637

[bateau59]

Maybe I am using the wrong terminology, but to me VAMI is the service that runs on port 5480, and allows me to update VCSA. It calls/called itself "VMWare Appliance Management". So that looks like VAMI to me.

The update via the app on port 5480 initially failed. I rebooted, and then did the update again.

Now VCSA is up, on version 6.5.0.22000 Build Number 9451637, but port 5480 is not open. Tried rebooting again, still no port 5480.

All services are up according to VCSA. No stopped nor failed services.

When I look in /var/log/vmware/applmgmt:

• vami.log states "twisted: Site starting on 8201", plus some logs about vAPI http client running. No failures. Nothing on 5480.
• firewall-reload.log states that 5480 is opened ACCEPT
• old vami and vapi logs show that I did get in on port 5480 for the update I did.

but "netstat -an | grep 5480" comes up empty. A lot of ports open, tested some, none look like VAMI.

What could cause this?

How to repair this?

Other question, (and I must admit I did not read through the entire forum, but sorry, searching for "6.7" and "6.5" returns a huge amount of false positives, so please point to a good thread on this and I'll be on my way)

am I really on a dead end with 6.5? I would like to move to 6.7 one of these days, and the latest release note states "Important: Upgrade and migration paths from vCenter Server 6.5 Update 2 and above to vCenter Server 6.7 and later are not supported.". Am I really in for a clean install of everything?

[bateau59]

(cannot edit my posts) .. ignore that secondary question at the end about 6.5 and 6.7. I'll wait for 6.7U1 if that arrives.

Also, I'm somewhat confused now, the Flash UI shows "Version 6.5.0.20000 Build 9451637", the console shows "Version 6.5.0.21000".

But it is supposed to be "6.5.0.22000", which is what I installed and matches the build number. I'll ignore all of that.

[a_p_]

I don't have access to a vCSA at the moment.

Please run service vami-lighttp start (or restart) from the vCSA's command line to see whether this command throws an error.

André

[bateau59]

That works. No error. Port 5480 opens up. But there it says the present install is on 6.5.0.21000 Build Number 8815520. Looks like the update got botched. Will try updating via the iso file.

Thanks

[bateau59 · Accepted solution]

Follow up:

the patch update failed because the root password (or the admin password) needed to be updated.

You can see this in /storage/log/vmware/applmgmt/software-packages.log

So I updated the root and the admin passwords, installed the update via ISO, and now I am on version 6.5.0.22000 Build Number 9451637.

BUT:

VAMI was still not up after a reboot. All services looked OK in the VCSA console, but vami-lighttp was disabled in the OS. To start it, 2 options:

1) go to the console/shell and run "service vami-lighttp start", every time you restart VCSA

2) go to the console/shell and run "chkconfig vami-lighttp on", and reboot. (once)

I marked this as the correct answer as it is more complete, but I would have been unable to get here without the help from a.p.

[a_p_]

The main goal for a community is to get help, and to help others.

It is absolutely ok to mark your own reply with the solution as the correct answer.

The solution you've posted will definitely help others. Thanks for sharing it!

André