3 answers
- 321
This means that the docker container for hbase didn't startup properly.
Can I see what output you get when you run docker logs container_name?
- Rizwan Qamar
Venkata Harish Kajur I am using Vanilla Openstack
Docker logs:
Logs for hbase:
hbase--zookeeper-localhost.log
hbase--1-regionserver-localhost.log
Logs for aai-service "/opt/app/aai/logs/rest/*"
So far I am unable to run robot. Should I see something in "Subscriber Name"?
Add your comment... - 10-1
Hi Rizwan,
From the logs, it looks like you were able to create both aai-service and hbase correctly and were able to connect to it successfully.
The error that you are looking at is unrelated. It doesn't affect the aai application.
If you look at the audit log that you provided me, you can see there are ResponseCode=201 which means that it was able to create the necessary resources from the robot. That seems not to be the problem.
Everything from aai looks like its perfectly working from the logs that you provided me.
Thanks,
Harish
Add your comment... - 10-1
Venkata Harish Kajur does this mean the db scripts havent run?
Add your comment...
I am trying to run aai project. I followed "robot_vm demo.sh failing with ssl error" and added the localhost entry to run zookeeper. Now at this path "tailf /opt/hbase-1.2.3/log/hbase--1-regionserver-localhost.log" I can see this exception.
Moreover, I cannot see any Service Instances: