Skip to content

K
k3s
Commit 5f75e573 authored by Serge van Ginderachter's avatar Serge van Ginderachter Committed by Craig Jellick
Browse files
Options

Always keep restarting k3s process by openrc

When for some reason, k3s crashes, and can't startup again, e.g. when the data backend is not available (dqlite crashed, database server is offline, ...), on openrc systems, supervise-daemon will try to restart it, as per supervise-daemon(8): respawn-max: Sets the maximum number of times a daemon will be respawned during a respawn period. If a daemon dies more than this number of times during a respawn period, will give up trying to respawn it and exit. The default is 10, and 0 means unlimited. Setting respawn-max to 0, makes sure a k3s process on openrc systems will keep trying to come online, even if the database backend is offline for a longer period of time. This aligns the openrc service configuration with the systemd configuration, which has Restart=always RestartSec=5s Signed-off-by: 's avatarSerge van Ginderachter <serge@vanginderachter.be>
parent ce658156
Hide whitespace changes
Inline Side-by-side
Showing with 1 addition and 0 deletions
install.sh
View file @ 5f75e573
...@@ -653,6 +653,7 @@ error_log=${LOG_FILE} ...@@ -653,6 +653,7 @@ error_log=${LOG_FILE}
pidfile="/var/run/${SYSTEM_NAME}.pid" pidfile="/var/run/${SYSTEM_NAME}.pid"
respawn_delay=5 respawn_delay=5
respawn_max=0
set -o allexport set -o allexport
if [ -f /etc/environment ]; then source /etc/environment; fi if [ -f /etc/environment ]; then source /etc/environment; fi
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment