"Current node is not active " while login in VRO

[tcpwave123]

I am new to VRO 7 , last two days i have been trying to resolve this but i could not  " Current node is not active " error while login
to VRO please suggest me any solution.

Thanks,
Shaikh

[chris122686]

If the 'Default tenant' of the Authentication Provider configuration does not match the name of a valid tenant in the PSC, attempts to establish a connection for authentication will fail.

In the vSphere PSC, by default, there is a single tenant which contains all of the identity stores that are seen from the vSphere Web Client, which will be named the same as the default domain created during the installation. By default, this domain will be vsphere.local, but may be altered during the installation of the PSC.

To resolve the issue:

- Open the VMware vRealize Orchestrator control center interface https://<vro_FQDN>:8283/vco-controlcenter .

- Under Manage section, click Configure Authentication Provider.

- Select Unregister.

- Enter the password.

- Click the second Unregister.

- Enter the URL for the PSC and select Connect.

- Enter an appropriate username and password.

- Configure the Default tenant to match the default directory in your PSC (i.e., vsphere.local unless it was explicitly changed during installation).

- Click Register and specify an Admin group.

- Click Save Changes.

- Under Startup Options in the Manage section, select Restart.

[tcpwave123]

Could not resolve the problem same "Current node is not active"

[GayathriS]

What version of VRO ?

Is this embeded VRO with VRA or stand alone ?

Could you provide server.log here ?

After following the steps provided in this article , try to restart your VRO service and check :https://kb.vmware.com/s/article/2144621

VMware Knowledge Base

Also check this :

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

Please mark this as correct if this answers and helps you .

regards

Gayathri

[rajen450m]

Hi Shaikh,

Try to reset authentication and restart the vco-configurator service.

SSH into the vRealize Orchestrator server.

• Run the command:
  /var/lib/vco/tools/configuration-cli/bin/vro-configure.sh reset-authentication
• Restart the control center by running the command:

service vco-configurator restart

• Log in to vRealize Orchestrator control center using the root account.
• Reconfigure authentication to repair it.

Regards,

[tcpwave123]

VRO 7.4.0 version  i am using earlier it was working but what happent to it don't know
This is stand alone VRO
from where will i get server.log file , So i can provide the logs.

Thanks ,

Shaikh

[daphnissov]

tcpwave123​ also in the wrong sub-forum. If you're new to vRA, don't use an external vRO node. Use the built-in vRO to the vRA appliance and you won't have to worry about the auth provider issue. Unless you have a very, very specific use case (if you do, what is it?) don't use an external vRO with 7.4 and forward.

[GayathriS]

If this is new set up , as daphnissov​ said , you can stop using external VRO and work on embedded VRO

[GayathriS]

Here is the location of log files:

server.log : app-server\server\vmo\log

regards

Gayathri