Help! I can't login to vco at all. I need to recover my workflows.

[anoopvb]

Very odd thing this morning.

I tried to login to vRO and that failed. I tried to pull up the control center and that failed. Even https://IP fails.

I logged in via SSH and netstat -ntlp showed that port 443 wasn't open at all.

I can't figure out what's broken here but a reboot didn't fix it either.

what can i do to troubleshoot this?

I see a lot of references to lighthttpd but there's nothing on the system named "lighthttpd"

find / -name "lighthttpd"

has 0 results.

Very weird stuff that I can't figure out.

Any ideas on how to proceed? And more importantly, any ideas on how I can pull my workflows out?

[iiliev]

The find has 0 results because the name you search for has too many h's and t's

If I recall correctly, the service name is vami-lighttp. Try restarting it with service vami-lighttp restart. If it fails, please collect the logs (especially the files in /opt/vmware/var/log/lighttpd/) and attach them there to check what is the exact error.

[anoopvb]

damnit.

Ok i found the files but none of the lighttpd configs have 443 mentioned in them.

vami-lighttpd is running and i restarted it.

I got some more information too.

I don't think VRO listens on port 443 at all. I compared it to a freshly installed VRO

port 80 redirects to :8281/vco

I get an error 503 on that page. I restarted vco-server and hoping that will fix it.

Type Status Report

Message Current node is not ACTIVE! Server is initializing...

Description The server is currently unable to handle the request due to a temporary overload or scheduled maintenance, which will likely be alleviated after some delay.

[anoopvb]

Also, vco-controlcenter is not responding.

i have a feeling that this may be tied to a authentication provider change i was trying to make. Any way to undo that?

When i use the vco client, i get an error of "current node is not active"

so i'm troubleshooting that by looking at DNS, etc.

/etc/hosts looks ok too.

unfortunately, i have no way of getting back in. I'd love to be able to get my workflows out though. Any ideas?

[iiliev]

There are configuration backup files stored in /var/lib/vco/backup/ folder (as zip files).

Error 503 / current node is not active - this error means the vRO server has not started properly. It is hard to say why without looking at log files (under /var/log/vco/) and configuration files (under /etc/vco/).

[anoopvb]

Does this help? I'm also downloading all the logs to upload.

edit: removed the log.

[anoopvb]

Attached is the contents of /var/log/vco as requested. Thank you again for all your help.

edit: removed.

[iiliev]

There are a lot of errors in server.log file, eg. Property 'ch.dunes.ldap.vso-admin-group' not set, which means your authentication provider is not configured properly.

Also, in controlcenter.log file there are multiple exception related to certificates and java.net.UnknownHostException: vcenter.train.actifio.com: Name or service not known

So it seems your configuration is not correct, and that's why the server is not working.

[anoopvb]

any way for me to recover from a backup?

i see the backups dir that has one zip file in it.

ideally, i'd just like to get my workflows out and just build a new server.

[iiliev · Accepted solution]

Connect via SSH to the appliance, and then execute the following commands in a terminal:

cd /usr/lib/vco/tools/configuration-cli/bin

./vro-configure.sh reset-authentication

service vco-configurator restart

Wait a minute or two, then open vRO Control Center in a browser, and you should be able to reconfigure the authentication.

[anoopvb]

Thanks so much. I will give this a shot

[anoopvb]

did as you suggested.

it's back now.

Since i was messing with it in other ways to fix it, my vmo.properties file had the wrong permissions

thank you for that CLI tip.

I used it to check the status etc.

I exported my workflows and saved them off. Now i can look to fix the authentication again.