| 2020-09-16 14:51:57 |
Chris Sanders |
description |
During troubleshooting of an issue I found that Canal (deployed with the Calico charm) uses a systemd that is configured to restart always with no limit.
This results in a very quick recycle of the service which never ends. In this case there was an error in the service configuration and checking the service status would typically show it as running when in fact it was starting, failing, and restarting in a loop.
Ideally, systemd should be set with a start interval and burst such that continued failures do not result in a persistent restart loop. |
During troubleshooting of an issue I found that Canal (deployed with the Calico charm) uses a systemd that is configured to restart always with no limit.
This results in a very quick recycle of the service which never ends. In this case there was an error in the service configuration and checking the service status would typically show it as running when in fact it was starting, failing, and restarting in a loop.
Ideally, systemd should be set with a start interval and burst such that continued failures do not result in a persistent restart loop.
The configuration error in this case was having rp_filter=2 and not having enabled the charm option to allow this setting. Therefore making this same configuration is a good reproducer to see the continual restarting of the service. |
|
