We have six VAs, and all of them are currently connected to the tenant. However, we have observed a common issue across all of them: after performing a reboot using sudo reboot, the canal process does not start automatically. We have to manually start it by running sudo systemctl start canal. any other way
You can try the following: Use the command → systemctl enable canal
If the issue still persists, then have a look to the link Virtual Appliance Tunnel Configuration - canal process not starting up after reboot of VA - #3 by gbagari
Try Step 1 first (systemctl enable canal ). If the issue persists, apply Steps 3 & 4 to handle dependencies and auto-restart failures.
This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.