#vROPS stuck in Waiting for Analytics state: check your hostname

During a Partner enablement session we figured out that a new deployed vRealize Operations Manager (vROPS) instance was not able to be started correctly. Login into https://vrops.fqdn/admin the following was shown under system status.

Screen Shot 2016-06-29 at 13.36.29

Even after deleting and redeploying vROPS it was not working that the vROPS service comes up.

The collector.log file was showing some strange heartbeat messages:

Screen Shot 2016-06-17 at 12.53.56

Not really helpful, but luckily the gemfire logfiles were giving us further information and were pointing us to an interesting finding:

Screen Shot 2016-06-29 at 13.50.06

 

Screen Shot 2016-06-17 at 12.39.47

Exception “Caused by: hava.net.MalformedUrlException: Bad URL path: _vcops.testlab.intern”

the hostname for the vROPS instance was pbu_vcops.testlab.intern. Somehow the internal mechanism screwed it up to work with the _ within the name.

–> Redeploying vROPS with a NETBIOS compatible hostname was totally working fine.

My recommendation: Keep your hostnames short and clean ;-)

 

Leave a Reply

Your email address will not be published. Required fields are marked *

Time limit is exhausted. Please reload CAPTCHA.