16 days ago
Mounting volume on: /var/lib/containers/railwayapp/bind-mounts/30321df4-8d16-4c96-9d0d-622e5fcf223f/vol_2u7mdoectceffi13
MongoDB cannot start: Linux kernel versions 6.19 and newer has a known incompatibility with this version of MongoDB. See https://jira.mongodb.org/browse/SERVER-121912 for more information.
Mounting volume on: /var/lib/containers/railwayapp/bind-mounts/30321df4-8d16-4c96-9d0d-622e5fcf223f/vol_2u7mdoectceffi13
MongoDB cannot start: Linux kernel versions 6.19 and newer has a known incompatibility with this version of MongoDB. See https://jira.mongodb.org/browse/SERVER-121912 for more information.
Mounting volume on: /var/lib/containers/railwayapp/bind-mounts/30321df4-8d16-4c96-9d0d-622e5fcf223f/vol_2u7mdoectceffi13
MongoDB cannot start: Linux kernel versions 6.19 and newer has a known incompatibility with this version of MongoDB. See https://jira.mongodb.org/browse/SERVER-121912 for more information.
Pinned Solution
16 days ago
I recently answer another thread and found temporary fix (not official fix), set env var GLIBC_TUNABLES="glibc.pthread.rseq=1" and it should deploy successfully
source: https://miliucci.org/post/mongodb-tcmalloc-rseq/
Attachments
5 Replies
Status changed to Open Railway • 16 days ago
16 days ago
Hey, just looked at your logs and this is definitely not on your end. The volume keeps mounting correctly but catatonit still can't find the entrypoint binary, which means Railway's bind-mount state is corrupted at the infrastructure level. Redeploying won't fix it because the bad state persists across deploys.
-Download a backup: go to the Volumes tab and download your data locally just to be safe
-Clone the service: click the three dots (...) on your service and hit "Clone Service". This forces Railway to deploy your app on a completely clean physical node, breaking the corrupted bind mount loop
-Switch over: attach your volume to the new cloned service verify it boots, point your domain to it, and delete the old stuck service
16 days ago
Getting same error. Broke my app.
16 days ago
I recently answer another thread and found temporary fix (not official fix), set env var GLIBC_TUNABLES="glibc.pthread.rseq=1" and it should deploy successfully
source: https://miliucci.org/post/mongodb-tcmalloc-rseq/
Attachments
mayoriii
I recently answer another thread and found temporary fix (not official fix), set env var `GLIBC_TUNABLES="glibc.pthread.rseq=1"` and it should deploy successfully source: https://miliucci.org/post/mongodb-tcmalloc-rseq/ 
16 days ago
thank you, for me this is works!
Status changed to Solved 0x5b62656e5d • 3 days ago