MongoDB：mongod.service：失败，结果\'exit-code\'答案

【问题标题】：MongoDB: mongodb.service: Failed with result 'exit-code'MongoDB：mongod.service：失败，结果\'exit-code\'
【发布时间】：2022-08-06 01:42:26
【问题描述】：

至少还有两个其他帖子存在这个问题（1、2）。这两个问题的答案都没有被证明是成功的，所以我决定发布更多信息。

我在 Ubuntu 18.04.6 上：

$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:    Ubuntu 18.04.6 LTS
Release:    18.04
Codename:   bionic

我按照here 的说明安装了 MongoDB，注意选择与我的操作系统对应的版本：

$ mongod --version
db version v5.0.5
Build Info: {
    \"version\": \"5.0.5\",
    \"gitVersion\": \"d65fd89df3fc039b5c55933c0f71d647a54510ae\",
    \"openSSLVersion\": \"OpenSSL 1.1.1  11 Sep 2018\",
    \"modules\": [],
    \"allocator\": \"tcmalloc\",
    \"environment\": {
        \"distmod\": \"ubuntu1804\",
        \"distarch\": \"x86_64\",
        \"target_arch\": \"x86_64\"
    }
}

当我尝试启动 MongoDB 时，我收到以下错误：

$ sudo systemctl start mongodb
Job for mongodb.service failed because the control process exited with error code.
See \"systemctl status mongodb.service\" and \"journalctl -xe\" for details.

我尝试了第一个建议，但它并没有帮助：

$ systemctl status mongodb.service
● mongodb.service - LSB: An object/document-oriented database
   Loaded: loaded (/etc/init.d/mongodb; generated)
   Active: failed (Result: exit-code) since Tue 2022-01-18 15:56:17 PST; 1h 19min ago
     Docs: man:systemd-sysv-generator(8)
  Process: 19071 ExecStart=/etc/init.d/mongodb start (code=exited, status=1/FAILURE)
 Main PID: 6332 (code=exited, status=0/SUCCESS)

Jan 18 15:56:16 rylan-ThinkPad-E590 systemd[1]: Starting LSB: An object/document-oriented database...
Jan 18 15:56:16 rylan-ThinkPad-E590 mongodb[19071]:  * Starting database mongodb
Jan 18 15:56:17 rylan-ThinkPad-E590 mongodb[19071]:    ...fail!
Jan 18 15:56:17 rylan-ThinkPad-E590 systemd[1]: mongodb.service: Control process exited, code=exited status=1
Jan 18 15:56:17 rylan-ThinkPad-E590 systemd[1]: mongodb.service: Failed with result \'exit-code\'.
Jan 18 15:56:17 rylan-ThinkPad-E590 systemd[1]: Failed to start LSB: An object/document-oriented database.

我尝试了第二个建议，这是结果输出：

$ journalctl -xe
Jan 18 17:16:06 rylan-ThinkPad-E590 slack.desktop[14549]: [01/18/22, 17:16:06:941] info: [RTM] (TT141UC80) Processed 1 file_deleted event(s) over 0.00ms
Jan 18 17:16:06 rylan-ThinkPad-E590 slack.desktop[14549]: [01/18/22, 17:16:06:941] info: [RTM] (TMTJNTNMQ) Processed 1 file_deleted event(s) over 0.00ms
Jan 18 17:16:06 rylan-ThinkPad-E590 slack.desktop[14549]: [01/18/22, 17:16:06:941] info: [RTM] (T020XA65T3P) Processed 1 file_deleted event(s) over 0.00ms
Jan 18 17:16:08 rylan-ThinkPad-E590 slack.desktop[14549]: [01/18/22, 17:16:08:457] info: [RTM] (E7SAV7LAD) Processed 1 user_invalidated event(s) over 0.00ms
Jan 18 17:16:10 rylan-ThinkPad-E590 slack.desktop[14549]: [01/18/22, 17:16:10:673] info: [API-Q] (T2BRHD5EC) noversion-1642554970.664 Flannel users/info called with reason: flannel-call:users/info
Jan 18 17:16:10 rylan-ThinkPad-E590 slack.desktop[14549]: [01/18/22, 17:16:10:673] info: [API-Q] (T2BRHD5EC) noversion-1642554970.664 Flannel users/info is ENQUEUED
Jan 18 17:16:10 rylan-ThinkPad-E590 slack.desktop[14549]: [01/18/22, 17:16:10:692] info: [API-Q] (T2BRHD5EC) noversion-1642554970.664 Flannel users/info is ACTIVE
Jan 18 17:16:10 rylan-ThinkPad-E590 slack.desktop[14549]: [01/18/22, 17:16:10:786] info: [API-Q] (T2BRHD5EC) noversion-1642554970.664 Flannel users/info is RESOLVED
Jan 18 17:16:12 rylan-ThinkPad-E590 slack.desktop[14549]: [01/18/22, 17:16:12:201] info: [RTM] (E7SAV7LAD) Processed 1 user_invalidated event(s) over 0.10ms
Jan 18 17:16:13 rylan-ThinkPad-E590 slack.desktop[14549]: [01/18/22, 17:16:13:599] info: [RTM] (E7SAV7LAD) Processed 1 user_invalidated event(s) over 0.10ms
Jan 18 17:16:16 rylan-ThinkPad-E590 slack.desktop[14549]: [01/18/22, 17:16:16:718] info: [RTM] (E01044K0LBZ) Processed 1 user_invalidated event(s) over 0.10ms
Jan 18 17:16:18 rylan-ThinkPad-E590 slack.desktop[14549]: [01/18/22, 17:16:18:673] info: [RTM] (E7SAV7LAD) Processed 1 user_invalidated event(s) over 0.00ms
Jan 18 17:16:39 rylan-ThinkPad-E590 slack.desktop[14549]: [01/18/22, 17:16:39:717] info: [RTM] (E7SAV7LAD) Processed 1 user_invalidated event(s) over 0.10ms
Jan 18 17:16:42 rylan-ThinkPad-E590 slack.desktop[14549]: [01/18/22, 17:16:42:063] info: [RTM] (E01044K0LBZ) Processed 1 user_invalidated event(s) over 0.10ms
Jan 18 17:16:43 rylan-ThinkPad-E590 slack.desktop[14549]: [01/18/22, 17:16:43:524] info: [RTM] (T2BRHD5EC) Processed 1 presence_change event(s) over 5.80ms
Jan 18 17:16:44 rylan-ThinkPad-E590 slack.desktop[14549]: [01/18/22, 17:16:44:009] info: [RTM] (E7SAV7LAD) Processed 1 user_invalidated event(s) over 0.10ms
Jan 18 17:16:44 rylan-ThinkPad-E590 slack.desktop[14549]: [01/18/22, 17:16:44:527] info: [RTM] (T2BRHD5EC) Processed 1 presence_change event(s) over 6.20ms
Jan 18 17:16:48 rylan-ThinkPad-E590 slack.desktop[14549]: [01/18/22, 17:16:48:111] info: [RTM] (E7SAV7LAD) Processed 1 user_invalidated event(s) over 0.10ms
Jan 18 17:16:50 rylan-ThinkPad-E590 slack.desktop[14549]: [01/18/22, 17:16:50:396] info: [RTM] (E7SAV7LAD) Processed 1 user_invalidated event(s) over 0.10ms
Jan 18 17:16:51 rylan-ThinkPad-E590 slack.desktop[14549]: [01/18/22, 17:16:51:324] info: [RTM] (E7SAV7LAD) Processed 1 user_invalidated event(s) over 0.10ms
Jan 18 17:16:51 rylan-ThinkPad-E590 slack.desktop[14549]: [01/18/22, 17:16:51:695] info: [RTM] (E7SAV7LAD) Processed 1 user_invalidated event(s) over 0.10ms
Jan 18 17:16:51 rylan-ThinkPad-E590 slack.desktop[14549]: [01/18/22, 17:16:51:696] info: [RTM] Setting a timeout of 92 ms to process more rtm events
Jan 18 17:16:52 rylan-ThinkPad-E590 slack.desktop[14549]: [01/18/22, 17:16:52:663] info: [RTM] Waited 92 ms, processing more rtm events now
Jan 18 17:16:52 rylan-ThinkPad-E590 slack.desktop[14549]: [01/18/22, 17:16:52:664] info: [RTM] (E7SAV7LAD) Processed 3 user_invalidated event(s) over 0.20ms
Jan 18 17:16:54 rylan-ThinkPad-E590 slack.desktop[14549]: [01/18/22, 17:16:54:654] info: [RTM] (E7SAV7LAD) Processed 1 user_invalidated event(s) over 0.10ms
Jan 18 17:16:55 rylan-ThinkPad-E590 slack.desktop[14549]: [01/18/22, 17:16:55:624] info: [RTM] (E7SAV7LAD) Processed 1 user_invalidated event(s) over 0.00ms
Jan 18 17:16:57 rylan-ThinkPad-E590 slack.desktop[14549]: [01/18/22, 17:16:57:330] info: [RTM] (E7SAV7LAD) Processed 1 user_invalidated event(s) over 0.10ms
Jan 18 17:16:58 rylan-ThinkPad-E590 slack.desktop[14549]: [01/18/22, 17:16:58:550] info: [RTM] (E7SAV7LAD) Processed 1 user_invalidated event(s) over 0.10ms
Jan 18 17:17:01 rylan-ThinkPad-E590 CRON[23583]: pam_unix(cron:session): session opened for user root by (uid=0)
Jan 18 17:17:01 rylan-ThinkPad-E590 CRON[23584]: (root) CMD (   cd / && run-parts --report /etc/cron.hourly)
Jan 18 17:17:01 rylan-ThinkPad-E590 CRON[23583]: pam_unix(cron:session): session closed for user root
Jan 18 17:17:11 rylan-ThinkPad-E590 slack.desktop[14549]: [01/18/22, 17:17:11:968] info: [RTM] (E01044K0LBZ) Processed 1 user_invalidated event(s) over 0.00ms
Jan 18 17:17:12 rylan-ThinkPad-E590 slack.desktop[14549]: [01/18/22, 17:17:12:477] info: [RTM] (E7SAV7LAD) Processed 1 user_invalidated event(s) over 0.10ms
Jan 18 17:17:19 rylan-ThinkPad-E590 slack.desktop[14549]: [01/18/22, 17:17:19:551] info: [RTM] (E7SAV7LAD) Processed 1 user_invalidated event(s) over 0.00ms
Jan 18 17:17:23 rylan-ThinkPad-E590 sudo[23632]:    rylan : TTY=pts/1 ; PWD=/home/rylan/Documents/physics-benchmarking-neurips2021/experiments/dominoes_redyellow_pilot ; USER=root ; COMMAND=/bin/systemctl start 
Jan 18 17:17:23 rylan-ThinkPad-E590 sudo[23632]: pam_unix(sudo:session): session opened for user root by (uid=0)
Jan 18 17:17:23 rylan-ThinkPad-E590 systemd[1]: Starting LSB: An object/document-oriented database...
-- Subject: Unit mongodb.service has begun start-up
-- Defined-By: systemd
-- Support: http://www.ubuntu.com/support
-- 
-- Unit mongodb.service has begun starting up.
Jan 18 17:17:23 rylan-ThinkPad-E590 mongodb[23648]:  * Starting database mongodb
Jan 18 17:17:24 rylan-ThinkPad-E590 mongodb[23648]:    ...fail!
Jan 18 17:17:24 rylan-ThinkPad-E590 systemd[1]: mongodb.service: Control process exited, code=exited status=1
Jan 18 17:17:24 rylan-ThinkPad-E590 systemd[1]: mongodb.service: Failed with result \'exit-code\'.
Jan 18 17:17:24 rylan-ThinkPad-E590 systemd[1]: Failed to start LSB: An object/document-oriented database.
-- Subject: Unit mongodb.service has failed
-- Defined-By: systemd
-- Support: http://www.ubuntu.com/support
-- 
-- Unit mongodb.service has failed.
-- 
-- The result is RESULT.
Jan 18 17:17:24 rylan-ThinkPad-E590 sudo[23632]: pam_unix(sudo:session): session closed for user root
Jan 18 17:17:24 rylan-ThinkPad-E590 slack.desktop[14549]: [01/18/22, 17:17:24:675] info: [RTM] (E7SAV7LAD) Processed 1 user_invalidated event(s) over 0.00ms
lines 1011-1066/1066 (END)

如何让 MongoDB 运行？

其他 SO 帖子中的任何建议都没有帮助。

编辑：一位朋友建议查看 MongoDB 日志，我发现：

\"Failed to unlink socket file\",\"attr\":{\"path\":\"/tmp/mongodb-27017.sock\",\"error\":\"Operation not permitted\"}}
{\"t\":{\"$date\":\"2022-01-18T15:51:35.538-08:00\"},\"s\":\"F\",  \"c\":\"-\",        \"id\":23091,   \"ctx\":\"initandlisten\",\"msg\":\"Fatal assertion\",\"attr\":{\"msgid\":40486,\"file\":\"src/mongo/transport/transport_layer_asio.cpp\",\"line\":989}}
{\"t\":{\"$date\":\"2022-01-18T15:51:35.538-08:00\"},\"s\":\"F\",  \"c\":\"-\",        \"id\":23092,   \"ctx\":\"initandlisten\",\"msg\":\"\\n\\n***aborting after fassert() failure\\n\\n\"}

我进一步调查，人们建议我需要更改 /tmp/mongodb-27017.sock 文件的所有者和组。我试过这个，错误仍然是一样的。

标签： mongodb

【解决方案1】：

对于有类似问题的任何人，清除和重新安装都有效。我不知道我第二次做了什么不同，我很害怕。

【讨论】：

【解决方案2】：

对于那些想知道如何进行清除而不是删除的人，我使用以下内容来确保正确删除。

sudo apt purge 软件包名称

在我们的例子中，特别是

sudo apt purge mongodb-org

或者

sudo apt purge mongodb-server

【讨论】：