We are using tunnel configuration for Virtual Appliance. We have 4 VAs. All of them are connected to the tenant now. However we observed one behavior in all those VAs. When we reboot (sudo reboot) , the canal process is not starting up. We have to manually start it by running sudo systemctl start canal.
Is there a way to make sure the canal process is started up after VA reboot just like other processes.?
Try Step 1 first (systemctl enable canal). If the issue persists, apply Steps 3 & 4 to handle dependencies and auto-restart failures.
You may want to add canal service in startup services to run on every reboot just like ccg or va_agent, this is a configuration on the VA generic to all flatcar OS’s.
Thanks Gautham for the details. Yes this is what the system expects. A startup script to start the service on reboot. As @Chaithu9110 explained running this command will create startup script : sudo systemctl enable canal
Thank you. That fixed the issue
