Skip to content

Conversation

@Max-Might
Copy link
Contributor

Make the systemd service restart itself in case of a crash. A restart is attempted 5 seconds after a crash is detected. Additionally, if the service is restarted more than 5 times in a 500 second interval it is considered as failed and no more restart attempts are going to be made.

Description

Sunshine crashed when I attempted to connect to a desktop session.
Not sure what the actual crash was. Nothing suspicious in the output logs.
Maybe systemd keeps the core dumps somewhere. I will open a new ticket if I find out more about the issue.

Type of Change

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • Dependency update (updates to dependencies)
  • Documentation update (changes to documentation)
  • Repository update (changes to repository files, e.g. .github/...)

Branch Updates

LizardByte requires that branches be up-to-date before merging. This means that after any PR is merged, this branch
must be updated before it can be merged. You must also
Allow edits from maintainers.

  • I want maintainers to keep my branch updated

@CLAassistant
Copy link

CLAassistant commented Jan 24, 2023

CLA assistant check
All committers have signed the CLA.

@ReenigneArcher
Copy link
Member

@Max-Might
Copy link
Contributor Author

@ReenigneArcher I updated the documentation.

Make the systemd service restart itself in case of a crash.
A restart is attempted 5 seconds after a crash is detected.
Additionally, if the service is restarted more than 5 times
in a 500 second interval it is considered as failed and no
more restart attempts are going to be made.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants