You are not logged in.
Greetings, I noticed this problem for the first time after pacman -Syu (idk if it is related). After starting mongosh I am getting error
Current Mongosh Log ID: 6a10f11f1cf6d7dbcfe43268
Connecting to: mongodb://127.0.0.1:27017/?directConnection=true&serverSelectionTimeoutMS=2000&appName=mongosh+2.3.9
MongoNetworkError: connect ECONNREFUSED 127.0.0.1:27017I checked if mongodb service works and it shows it failed with printed stack traces:
× mongodb.service - MongoDB Database Server
Loaded: loaded (/usr/lib/systemd/system/mongodb.service; enabled; preset: disabled)
Active: failed (Result: core-dump) since Sat 2026-05-23 02:08:13 CEST; 6min ago
Duration: 1min 4.163s
Invocation: a844d9d27e7e48c389b6d6d84af22b49
Docs: https://docs.mongodb.org/manual
Process: 803 ExecStart=/usr/bin/mongod --config /etc/mongodb.conf (code=dumped, signal=SEGV)
Main PID: 803 (code=dumped, signal=SEGV)
Mem peak: 406.1M
CPU: 1.544s
May 23 02:07:08 Archimedes systemd[1]: Started MongoDB Database Server.
May 23 02:07:09 Archimedes mongod[803]: {"t":{"$date":"2026-05-23T02:07:09.463+02:00"},"s":"I", "c":"-", "id":8991200, "ctx":"main","msg":"Shuffl>
May 23 02:07:09 Archimedes mongod[803]: {"t":{"$date":"2026-05-23T02:07:09.479+02:00"},"s":"I", "c":"CONTROL", "id":7484500, "ctx":"main","msg":"Enviro>
May 23 02:08:12 Archimedes systemd-coredump[2405]: [?] Process 803 (mongod) of user 961 dumped core.
Stack trace of thread 1027:
#0 0x000056160b3f395a _ZN5boost3log12v2s_mt_posix13attribute_setC1Ev (/usr/bin/mongod + 0xa04c95a)
#1 0x00005616057e003b _ZN5mongo5logv29LogSourceC2EPKNS0_9LogDomain8InternalEb (/usr/bin/mongod + 0x44>
#2 0x00005616057c6c7a _ZN5mongo5logv215LogDomainGlobal6sourceEv (/usr/bin/mongod + 0x441fc7a)
#3 0x0000561605801d73 _ZN5mongo5logv26detail10_doLogImplEiRKNS0_11LogSeverityERKNS0_10LogOptionsENS_1>
#4 0x000056160565776b _ZN5mongo5logv26detail9doLogImplEiRKNS0_11LogSeverityERKNS0_10LogOptionsENS_10S>
#5 0x000056160b30f1ca _ZN5mongo12_GLOBAL__N_126writeMallocFreeStreamToLogEv (/usr/bin/mongod + 0x9f68>
#6 0x000056160b30f8d0 abruptQuitWithAddrSignal (/usr/bin/mongod + 0x9f688d0)
#7 0x00007ff4a683e8f0 n/a (libc.so.6 + 0x3e8f0)
#8 0x0000561605896696 _ZN5mongo14JournalFlusher3runEv (/usr/bin/mongod + 0x44ef696)
#9 0x000056160b18026e _ZN5mongo13BackgroundJob7jobBodyEv (/usr/bin/mongod + 0x9dd926e)
#10 0x000056160b180757 _ZNSt6thread11_State_implINS_8_InvokerISt5tupleIJZN5mongo4stdx6threadC4IZNS3_13>
#11 0x000056160b6b4514 execute_native_thread_routine (/usr/bin/mongod + 0xa30d514)
#12 0x00007ff4a68981b9 n/a (libc.so.6 + 0x981b9)
#13 0x00007ff4a691d21c n/a (libc.so.6 + 0x11d21c)with much more threads' stack traces but it is too long to paste. After I restart it, it works fine but after couple of minutes it fails again. Could anyone guess what it is? I would be very grateful.
Last edited by blicko (2026-05-23 00:20:00)
Offline
with much more threads' stack traces but it is too long to paste.
1st link below, make sure to not copy&paste it out of the pager (">" indicates truncated lines) - the thread in the snippet is the SEGV handling and extremely unlikely to be the cause.
Offline
Great, that is a very useful advice. This is the full output of
sudo systemctl status mongodbOffline
No, the crash handler is the the culpable thread - fits https://www.reddit.com/r/mongodb/commen … v_on_arch/
https://www.mongodb.com/docs/manual/release-notes/8.2/
Does it work w/ the LTS kernel?
Offline