-
-
Notifications
You must be signed in to change notification settings - Fork 38
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
Add crash and server restart alert #2849
Comments
|
I don't think we want |
|
https://github.com/apple/swift/blob/main/docs/Backtracing.rst
|
|
We had another instance this morning where a node was completely locked up for hours, running swift-backtrace at 100% CPU: What's also concerning is that we're not seeing any traces anymore in our logs even when backtrace doesn't lock up. We used to get unsymbolicated ones at least but now they're gone. |
|
Also look for |
i have seen something sporadically similar to this ever since upgrading to swift 5.9. did you see |
|
Yes, exactly - like in the screenshot at the very top. My understanding is that the hang was perhaps due a misconfiguration. We're statically linking but hadn't bundled up and reference the backtrace binary. But it's possible that this happens regardless, it's hard to tell at this point. |

We should add an alert for server restarts
We've seen crashes today that led to
swift-backtracelocking up the nodes for a while:We don't have good visibility when restarts happen - it's a testament really to how stable the processes have been, we've never really had issues with crashes in the server process.
The text was updated successfully, but these errors were encountered: