Replies: 3 comments 3 replies
-
|
This is a wild one, especially that it seems to be exactly 30 seconds. Have you tried running with something like In the image, we don't do much more than install upstream's pre-built binaries and run them, so I don't think this failure is specific to the image, but it's possible! |
Beta Was this translation helpful? Give feedback.
-
|
I encountered the same issue and did some research:
While reviewing the changes from 8.0.4 to 8.0.5, I noticed that RSEQ was disabled for glibc / enabled for Google TCMalloc in 7bf2228. It was also disabled from the beginning in 8.2 versions, starting with 9306458. It would be helpful if someone could try to reproduce this issue with MongoDB running outside of a Docker container. For now, a temporary fix is to run the mongo Docker container with: |
Beta Was this translation helpful? Give feedback.
-
|
Hi everyone, I started an issue on the mongod tracker: https://jira.mongodb.org/browse/SERVER-120238 Another workaround: |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Genuinely lost for debug steps and couldn't find another place to post. Been having connection issues with mongodb and it turned out to be because the whole damn thing is crashing horribly without logging anything. I'm not sure where I could find debug symbols, so I can't find anything further. The crash happens after exactly 30 seconds of uptime, then the container is restarted due to my docker settings.
Happens on 8.0 and 8.2
I have read #485 and it doesn't appear to be related.
Hardware info if relevant:
Versions used:
Beta Was this translation helpful? Give feedback.
All reactions