| Git Clone URL: | https://aur.archlinux.org/mongodb-bin.git (read-only, click to copy) |
|---|---|
| Package Base: | mongodb-bin |
| Description: | A high-performance, open source, schema-free document-oriented database |
| Upstream URL: | https://www.mongodb.com/ |
| Keywords: | database document-oriented mongo mongod mongodb mongos |
| Licenses: | SSPL-1.0 |
| Conflicts: | mongodb, mongodb-shell-bin |
| Provides: | mongodb |
| Submitter: | ali.molaei |
| Maintainer: | ali.molaei (rafaelff) |
| Last Packager: | ali.molaei |
| Votes: | 96 |
| Popularity: | 0.99 |
| First Submitted: | 2019-01-28 09:01 (UTC) |
| Last Updated: | 2026-04-17 13:54 (UTC) |
I had the same issue. In mongodb.service configuration I had a line: Environment=GLIBC_TUNABLES=glibc.pthread.rseq=0 which disables glibc.pthread.rseq as the official website suggests: https://www.mongodb.com/docs/manual/administration/tcmalloc-performance/
If I remove that line and enable glibc.pthread.rseq, my mongodb does not crash any more.
My docker containers which are also crashing shutting down too ..I had to temporarily switch to Linux lts kernel from the same zen kernel
pp82, thanks for the tip,
after reading your comment I thought it might be permissions related, so I chown(ed) some file in /var/lib/mongodb that belonged to root:root to mongodb:mongodb this did not help, then I modified /usr/lib/systemd/system/mongodb.service and commented "User=mongodb", this worked however this is not recommended because it means the service is running as root, but is is a clear indication that it is something to do with permissions so I will continue digging
Just to clarify, the coredump is not immediate, it appears after a few seconds I am assuming read operations are fine but writes cause a dump based on how my application is responding
Weirdly, when I start it with sudo systemctl start mongodb.service, it crashes with a coredump after about a minute. But if I just run sudo -u mongodb /usr/bin/mongod --config /etc/mongodb.conf directly, everything works fine. (mongodb-8.2.4 + linux-zen-6.19.6.zen1-1.1)
@Alien @mailme_gx @cram Same observation here, the downgrade of linux to 6.18.9-arch1-2 does the trick, trying mongodb-bin-8.2.4 and mongodb-bin-8.2.5. Since I am a brand-new MongoDB user, I tried this with a completely empty DB.
Upgrading linux to version 6.19.6.arch1-1 also causes my MongoDB instance to core-dump
Yes we are also experiencing issues, thanks for the heads up..
"Alien commented on 2026-03-06 09:12 (UTC): Upgrading linux from 6.18.13.arch1-1 to 6.19.6.arch1-1 "
For now we downgraded the kernel and are looking for a solution
Upgrading linux from 6.18.13.arch1-1 to 6.19.6.arch1-1 causes my MongoDB to core-dump whenever I start using it (it starts fine however). Anyone else hitting this?
8.2 is a major update so you either have to update your database Upgrade 8.0 to 8.2 or use mongodb80-bin
L. I think they don't even have sigs for this.
Pinned Comments
ali.molaei commented on 2025-10-24 19:22 (UTC) (edited on 2025-10-24 19:25 (UTC) by ali.molaei)
8.2 is a major update so you either have to update your database Upgrade 8.0 to 8.2 or use mongodb80-bin
ali.molaei commented on 2021-07-28 14:29 (UTC) (edited on 2024-11-02 19:21 (UTC) by ali.molaei)
If you get core dumps on version 5 or above, read this: https://jira.mongodb.org/browse/SERVER-58648