Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Klippain installer removes sonar.conf which puts the service in a restart loop #647

Open
1 task done
faelenor opened this issue Sep 8, 2024 · 1 comment
Open
1 task done
Labels
bug Something isn't working stale Issue that appear to be inactive, mark for potenial closing if stale for longer time triage This is a new issue to be sorted (automatic label)

Comments

@faelenor
Copy link

faelenor commented Sep 8, 2024

Klippain branch

  • I confirm using the main branch

Version

v4.3.1-17-gdf5ad5bf

Describe the bug and expected behavior

When there's no sonar.conf file, the sonar service restarts every 5-10 seconds, creating huge CPU spikes (100% for a fraction of a second). I reported the issue to the Mainsail team, but I thought that it was important to report it here as well because installing Klippain will trigger this unless you had previously uninstalled Sonar.

Additional information and klippy.log

No response

@faelenor faelenor added bug Something isn't working triage This is a new issue to be sorted (automatic label) labels Sep 8, 2024
Copy link

github-actions bot commented Oct 9, 2024

📌 This issue has been marked as stale because it has not had activity in the past 30 days.
To keep it open, please respond to this message or add new information. Otherwise, this will be closed in 14 days.
Thank you for your contributions!

@github-actions github-actions bot added the stale Issue that appear to be inactive, mark for potenial closing if stale for longer time label Oct 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working stale Issue that appear to be inactive, mark for potenial closing if stale for longer time triage This is a new issue to be sorted (automatic label)
Projects
None yet
Development

No branches or pull requests

1 participant