VA Connectivity - ---------- Daemon Stopped Normally ----------

[mbrahmer (Matthew Brahmer)]

Hello All,
I am attempting to spin up a second VA for our cluster and noticed an issue when adding the config.yaml. After multiple attempts of creating the cluster in IDN, downloading the config file and uploading it with the key passphrase we noticed an issue on the firewall that was causing some traffic to be referred to our default firewall rule that has deep packet inspection. We resolved this issue, but noticed on the VA when attempting to connect again that the daemon had stopped and now the service doesnt seem to be running. When checking charon.log for details this following came up:

{“@timestamp”:“2023-11-13 15:42:02 +0000”,“level”:“INFO”,“type”:“charon”,“message”:“---------- Daemon Stopped Normally ----------”}

The documentation doesnt seem to address this issue. A reboot doesnt correct the issue either. Has anyone experienced this before and is it fixable without just reinstalling the image again? Any help you can provide is appreciated.

[edmarks]

If it’s a new VA that you’re spinning up, I’d just re-install from the latest image and see if you get the same error. I’ve seen people spend WAY too many hours debugging a VA issue when it’s really easier to just recreate it (unless there’s something very specific about the VA that prohibits it from just being replaced).