We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Describe the bug
Investigating a large journalctl log size, I realised that casaos is flooding the logs with pings:
Mar 30 12:19:47 fragola casaos[822]: {"time":"2025-03-30T12:19:47.001257923+01:00","id":"","remote_ip":"127.0.0.1","host":"127.0.0.1:42769","method":"POST","uri":"/v1/notify/system_status","user_agent":"Go-http-client/1.1","status":200,"error":"","latency":84981,"latency_human":"84.981µs","bytes_in":85,"bytes_out":43} Mar 30 12:19:47 fragola casaos[822]: {"time":"2025-03-30T12:19:47.011317959+01:00","id":"","remote_ip":"127.0.0.1","host":"127.0.0.1:42769","method":"POST","uri":"/v1/notify/system_status","user_agent":"Go-http-client/1.1","status":200,"error":"","latency":102796,"latency_human":"102.796µs","bytes_in":118,"bytes_out":43} Mar 30 12:19:50 fragola casaos-message-bus[812]: {"time":"2025-03-30T12:19:50.0168143+01:00","id":"","remote_ip":"127.0.0.1","host":"127.0.0.1:43251","method":"POST","uri":"/v2/message_bus/event/casaos/casaos:system:utilization","user_agent":"Go-http-client/1.1","status":200,"error":"","latency":677534,"latency_human":"677.534µs","bytes_in":945,"bytes_out":1102}
that's a ping every 3s, which is obviously demented…
Aside from the log flood, this seems like way too much background activity.
Expected behavior
A much lower rate of pings and/or a way to configure.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Describe the bug
Investigating a large journalctl log size, I realised that casaos is flooding the logs with pings:
that's a ping every 3s, which is obviously demented…
Aside from the log flood, this seems like way too much background activity.
Expected behavior
A much lower rate of pings and/or a way to configure.
The text was updated successfully, but these errors were encountered: