-
Notifications
You must be signed in to change notification settings - Fork 107
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
KH1 crashes #24
Comments
The refbuf_copy crashes will be down to the clearing of the queue occurring too early on a relay, should of been fixed on Jun 27. The send_iceblock_to_client crash (which is master feeding a relay), should of been fixed on Jul 6. karl. |
Great to hear. Matthias |
still waiting? kh3 has been out for a little while now. karl. |
Hi Karl, last week we switched to KH3. Thank you! Matthias |
Hi Karl,
for testing I put a KH1 in production (as a slave - without having own sources).
As it seems it's not stable.
Yesterday four crashes. Today already one.
Cause or initiator for the crashes yesterday was, that the connection to the master server was broken (or better: the master server itself was not running for some minutes) while the crashed server was under user load (around 3k connections).
Interesting is, that another KH1, which was connected to the same master server, did not crash. But this second server had no client connections on it. So it's a issue while listerners are connected and the source goes down (my guess).
The crash today was caused (AFAICS) because a single source got disconnected. So basicly it should be the same error.
Here are the 5 stack traces (the first 4 yesterday - the 5th today):
Crash number 3 looks different. So we have two issues?
Matthias
The text was updated successfully, but these errors were encountered: