Hi All ,
I am facing an issue while creating a virtual appliance . I have created a VA cluster and the VA in it successfully active . But , while creating a source , I’m not able to see my cluster in the VA cluster dropdown
Looking at the ‘CCG version’ and it saying ‘not available’ means that the VA hasn’t completed the setup yet. Have you checked the charon.log file on the VA to ensure it has been properly initiated?
- To see in the logs which services have completed initial update/install, check charon.log.
- grep SUCCESS charon.log | grep SERVICE_SETUP
- Successful update/setup will look like this:
{“@timestamp”:“2017-12-05 11:20:32 +0000”,“level”:“INFO”,“type”:“processor”,“message”:“Job SERVICE_SETUP ccg has FINISHED - result: SUCCESS”}
Hi @sisvanthkumar ,
Restart the cluster from IDN.
I guess the VA is in update state. Once it’s healthy, you can add it to your source.
Also check the service_status.json status - check ccg is runnning.
Thanks!!
I agree with @sauvee that it looks like your VA is still updating and configuring. If it was set up with an older image, it might need to pull more updates. I would give it time to fully update and use the suggested method to check if it is completed.
Run below two commands and check
Hi @sauvee , I’m not able to run that command it shows that " charon.log : No such file or directory "
im not able to see anything tagged as current
charon.log is found in the log directory under your home (/home/sailpoint/log).
Seeing this behaviour / message clearly means that the VA is not healthy and hasn’t correctly configured itself.
Can you run through the troubleshooting guide; specifically
tail -f /home/sailpoint/log/charon.log
sudo docker ps -a
sudo docker images
sudo systemctl status ccg
Please post the results of those here.
Perform a reboot:
sudo reboot
After that check the following log files:
va-start.log
charon.log
Are you behind a proxy or tunnel?
Hi @sisvanthkumar , the command should be :
sudo systemctl status ccg
Sorry @shaileeM , my mistake , It showing “Unit ccg.service could not be found”
Did you try a reboot and checking the files shared above?
If that doesn’t do anything, can you create a new VA cluster and put the config.yaml on the VA, replacing the current version and then do a reboot?
Tried that multiple time @sauvee , But. still the issue persists
Have you tried this suggestion as well?
Yes @sauvee tried that too…
Hi @sisvanthkumar ,
I have the same behavior as @gmilunich described, was using some old VA image and it took a long time do Download and Update all docker images.
I think you might let the VA running for some time to see if it works.
Regards
Hey @fmunerato , may i know approximate time for it , because i have already waited too long for that , also did you follow any other steps in order to resolve ?
I’ve just deploy a new VA, create a new cluster and put the config.yaml on the VA.
After that I’ve not take any actions for around 8/10 hours, once I’ve came back, the CCG was working as expected and the VA start to shown in cluster dropdown.
