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
Startup fails with "Timeout waiting for ping event" #699
Comments
I'm seeing this now too. I'm not certain, but this seems to happen after startup for me – where it throws an error that triggers a full exit. i.e. an uncaught promise rejection? Here's the similar error I'm seeing:
I'm not a Node.js expert so please take this with a grain of salt, but I think the Node.js version change may have had something to do with it. Uncaught promise rejections used to be warnings only, and changed to throws in Node.js 15:
I haven't looked, but I wonder if we're missing the |
Aha, that was it! I added
I imagine a more proper fix would involve resolving the uncaught rejection at the source, but maybe adding an unhandled rejection hook would be prudent as well. |
I'm having the same issue and adding this extra argument stops the container from restarting but I'm wondering why it's happening in the first place. |
I've noticed that after the warning happens, though, the bridge stops responding. I've reverted the change but the bridge crashes regularly, after the ping timeout. The container restarts, some messages flow and then it crashes again, etc. This has been happening since December 1, for me. |
I'm experiencing the same with |
Same problem here with latest. Curious it was working until a node crash, after the restart there's no way to make it work again. Did you find any workaround? |
is there a stable version of this bridge? |
I continue to experience this with docker. Container runs for 60 seconds then crashes.
logs look like this:
|
Describe the bug
Slack bridge throws this at startup:
And shortly after times out and exits with:
All of this would point at a server issue (Synapse runs on localhost) except the bridge is actively logging successful calls from it:
I'm honestly at a loss for options. Debugging log mode doesn't log anything more. I'm conscious this is not good enough as a bug report but does anyone have any idea, or knows where I can pull more details? The error and subsequent behaviour don't really make sense to me.
Thanks!
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Matrix Slack bridge should start no issues. If there is a server side issue, I should not be able to see successful calls to it.
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):
Smartphone (please complete the following information):
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: