Status console IU vROPS - Data Retriever is not initialized yet. Please wait...

[vinicius_silva_]

Hi, guys,

My name Vinicius Silva, I'm from Brazil I have problema with VROPS with a mensagem the in console UI.

Data Retriever is not initialized yet. Please wait...

Why ?

[sxnxr]

Check your admin UI to make sure the cluster is online. You normal get this when the cluster is "Waiting for Analytics" Depending on the version of vrops this is a know problem.

[vinicius_silva_]

Hi sxnxr,

Yes is a cluster, but stop runnig without explication.

In KBs below have not solved my problem.

2106950,2114663,2078313,2013358 e 2034781

Do I have to redeploy my environment?

[vinicius_silva_ · Accepted solution]

Hi, guys.

After various day without success in solution, I start re-deploy OVA.

Problem resolved.

[StephenRahul]

Hi,

Please share the output of the following command;

- service vmware-vcops status

A working vROps server will show the following:

Slice Online-true

admin Role Enabled-true

        vRealize Operations vPostgres Replication Database is running (5860).

        vRealize Operations Gemfire Locator is running (5928).

data Role Enabled-true

        vRealize Operations vPostgres Database is running (6032).

        vRealize Operations Cassandra Distributed Database is running (6096).

        vRealize Operations Analytics is running (6171).

        vRealize Operations Collector is running (6241).

        vRealize Operations API is running (6311).

ui Role Enabled-true

remote collector Role Enabled-false

Above is from version 6.1

Re-deploying isn't an option for production deployments

Regards

Rahul

[sxnxr]

I just fixed a problem giving the same issue.

I had a GSS case to change the root logger the analytic logs on all nodes to debug which all worked fine

Once i was done i dinnt change it back. A week ot two later i rebooted the nodes and got the waiting on error and the cluster world not come back on line. It turns out there was a bug present when the 'rootLogger' setting was set to DEBUG, which was preventing the analytics service from staying online consistently. after changing the logger config file back to warn it started working.