Hello Railway Support,

I’m currently experiencing an issue with my MongoDB plugin on Railway. The logs show the following error indicating an unclean shutdown:

Detected unclean shutdown - Lock file is not empty

I’ve attempted to restart the MongoDB plugin through the Railway dashboard, but the error persists. Since the plugin is fully managed, I don’t have file-system access to remove the lock file or run a mongod --repair. Here are the relevant log excerpts:

Detected unclean shutdown - Lock file is not empty
Storage engine to use detected by data files
Recovering data from the last clean checkpoint.
…
vm.maxmapcount is too low
…

I have data in this database that I need to preserve, so removing and recreating the plugin isn’t a viable option. Can you please help remove the lock file and/or perform any necessary repair steps so my MongoDB instance can start cleanly again?

If you need additional information or logs, please let me know. Thank you for your assistance!

Best regards,

Kennard Daniel
blkQ
kenndaniel@blkqapp.com

View Deploy details

ⓘ Deployment information is only viewable by project members and Railway employees.