CCG .service not found

Hi,
I have a situation, We have a cluster and two VA’s configured and connected. For some reason, there were some issues with the VA’s. So, wanted to reconnect the VA. So, deleted the VA from ISC tenant and generated a new pairing code from the VA and connected the VA in ISC. Now the issue is I don’t see the CCG on the VA. I see a error message when I tried restarting CCG. Any ideas on troubleshooting or next steps??. Thank you in Advance!

Failed to restart ccg.service: Unit ccg.service not found.

Hello,

I’m facing the same issue in a demo VA and still not able to figure out why!

But you can run this command sudo docker images and see if has any ccg listed(in my case only ccg is not listed)!


Check if ccg container exists:

sudo docker ps -a

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”}

If you find any solution let me know!

You need to reconnect the VA to the ISC tenant and since you generated a new pairing code, it cannot connect anymore.

Can you elaborate which commands / steps you performed on the VA itself?

I have reconnected the VA. But the CCG is not available. I have reset the VA using below. I have generated a new pairing code.

 va-bootstrap reset
 va-bootstrap pair

I believe you will have to do the following in order:

va-bootstrap reset

Create a new VA in the UI (delete the old one)

va-bootstrap set-passphrase
va-bootstrap pair

Fill in the pairing code in the UI

Let us know how it goes.

1 Like

@sauvee I have already implemented the above the steps you mentioned. But I guess the VA updates took a bit longer, Now the VA’s are connected and the CCG version is updated as well!
Thank you for all your assistance!

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.