Skip to content

K
k3s
Switch branch/tag
  1. 18 Feb, 2021 3 commits
  3. 30 Jan, 2021 1 commit
  5. 29 Jan, 2021 2 commits
  7. 23 Jan, 2021 1 commit
  9. 14 Jan, 2021 2 commits
  11. 22 Dec, 2020 2 commits
  13. 10 Dec, 2020 2 commits
  15. 08 Dec, 2020 1 commit
  17. 04 Dec, 2020 2 commits
  19. 30 Nov, 2020 1 commit
  21. 18 Nov, 2020 1 commit
  23. 13 Nov, 2020 1 commit
  25. 12 Nov, 2020 2 commits
  27. 09 Nov, 2020 1 commit
  29. 28 Oct, 2020 3 commits
  31. 15 Oct, 2020 1 commit
  33. 07 Oct, 2020 1 commit
  35. 06 Oct, 2020 1 commit
  37. 18 Sep, 2020 1 commit
  39. 17 Sep, 2020 2 commits
  41. 20 Aug, 2020 1 commit
  43. 19 Aug, 2020 1 commit
  45. 13 Aug, 2020 2 commits
  47. 21 Jul, 2020 1 commit
  49. 20 Jul, 2020 1 commit
  51. 16 Jul, 2020 2 commits
  53. 13 Jul, 2020 1 commit
    • Serge van Ginderachter's avatar
      Always keep restarting k3s process by openrc · db1c0893
      Serge van Ginderachter authored 
      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>
      db1c0893