揭秘导致MongoDB服务启动失败的幕后黑手

最新推荐文章于 2025-05-16 10:04:18 发布
最新推荐文章于 2025-05-16 10:04:18 发布
阅读量633 收藏
点赞数 2
CC 4.0 BY-SA版权
分类专栏： MongoDB 文章标签： mongodb 数据库
版权声明：本文为博主原创文章，遵循 CC 4.0 BY-SA 版权协议，转载请附上原文出处链接和本声明。
本文链接：https://blog.youkuaiyun.com/AlienwareABC/article/details/143674679

##

揭秘导致MongoDB服务启动失败的幕后黑手

1、mongod 状态
[root@mydb ~]# systemctl status mongod
× mongod.service - MongoDB Database Server
     Loaded: loaded (/usr/lib/systemd/system/mongod.service; disabled; preset: disabled)
     Active: failed (Result: exit-code) since Sun 2024-07-14 16:34:42 CST; 2s ago
   Duration: 10ms
       Docs: https://docs.mongodb.org/manual
    Process: 1808 ExecStart=/mongodb/app/mongodb/bin/mongod $OPTIONS (code=exited, status=203/EXEC)
   Main PID: 1808 (code=exited, status=203/EXEC)
        CPU: 2ms

Jul 14 16:34:42 mydb systemd[1]: Started MongoDB Database Server.
Jul 14 16:34:42 mydb systemd[1808]: mongod.service: Failed to locate executable /mongodb/app/mongodb/bin/mongod: Permission denied
Jul 14 16:34:42 mydb systemd[1808]: mongod.service: Failed at step EXEC spawning /mongodb/app/mongodb/bin/mongod: Permission denied
Jul 14 16:34:42 mydb systemd[1]: mongod.service: Main process exited, code=exited, status=203/EXEC
Jul 14 16:34:42 mydb systemd[1]: mongod.service: Failed with result 'exit-code'.
2、日志信息
Jul 14 16:28:39 mydb systemd[1]: dbus-:1.1-org.fedoraproject.SetroubleshootPrivileged@4.service: Deactivated successfully.
Jul 14 16:28:39 mydb systemd[1]: dbus-:1.1-org.fedoraproject.SetroubleshootPrivileged@4.service: Consumed 1.019s CPU time.
Jul 14 16:28:42 mydb systemd[1]: setroubleshootd.service: Deactivated successfully.
Jul 14 16:28:42 mydb systemd[1]: setroubleshootd.service: Consumed 3.154s CPU time.
Jul 14 16:28:58 mydb systemd[1]: Started mongod.service.
Jul 14 16:28:58 mydb systemd[1613]: mongod.service: Failed to locate executable /mongodb/app/mongodb/bin/mongod: Permission denied
Jul 14 16:28:58 mydb systemd[1613]: mongod.service: Failed at step EXEC spawning /mongodb/app/mongodb/bin/mongod: Permission denied
Jul 14 16:28:58 mydb systemd[1]: mongod.service: Main process exited, code=exited, status=203/EXEC
Jul 14 16:28:58 mydb systemd[1]: mongod.service: Failed with result 'exit-code'.
Jul 14 16:28:58 mydb systemd[1]: Starting SETroubleshoot daemon for processing new SELinux denial logs...
Jul 14 16:28:59 mydb systemd[1]: Started SETroubleshoot daemon for processing new SELinux denial logs.
Jul 14 16:28:59 mydb systemd[1]: Started dbus-:1.1-org.fedoraproject.SetroubleshootPrivileged@5.service.
Jul 14 16:29:02 mydb setroubleshoot[1614]: SELinux is preventing /usr/lib/systemd/systemd from read access on the lnk_file mongodb. For complete SELinux messages run: sealert -l 0fdf4ad8-666d-4d14-90ea-8d0f61ad22b8
Jul 14 16:29:02 mydb setroubleshoot[1614]: SELinux is preventing /usr/lib/systemd/systemd from read access on the lnk_file mongodb.#012#012*****  Plugin catchall_labels (83.8 confidence) suggests   *******************#012#012If you want to allow systemd to have read access on the mongodb lnk_file#012Then you need to change the label on mongodb#012Do#012# semanage fcontext -a -t FILE_TYPE 'mongodb'#012where FILE_TYPE is one of the following:
3、处理并验证
[root@mydb ~]# vi /etc/selinux/config
[root@mydb ~]# setenforce 0
[root@mydb ~]#
[root@mydb ~]# systemctl start mongod
[root@mydb ~]# systemctl status mongod
● mongod.service - MongoDB Database Server
     Loaded: loaded (/usr/lib/systemd/system/mongod.service; disabled; preset: disabled)
     Active: active (running) since Sun 2024-07-14 16:40:30 CST; 3s ago
       Docs: https://docs.mongodb.org/manual
   Main PID: 1915 (mongod)
     Memory: 171.5M
        CPU: 1.162s
     CGroup: /system.slice/mongod.service
             └─1915 /mongodb/app/mongodb/bin/mongod -f /mongodb/data/mongod.conf

Jul 14 16:40:30 mydb systemd[1]: Started MongoDB Database Server.
Jul 14 16:40:30 mydb mongod[1915]: {"t":{"$date":"2024-07-14T08:40:30.052Z"},"s":"I",  "c":"CONTROL",  "id":7484500, "ctx":"main","msg":"Environment variable MONGODB_CONFIG_OVERRIDE_NOF>
lines 1-12/12 (END)
4、总结

验证了执行文件的权限，尝试PermissionsStartOnly均无疾而终。最后在日志中找到selinux。官网虽然有很详细的关于selinux的配置，但还是关了吧。

5、其它启动错误

还有一些权限导致的启动问题

Jul 14 17:25:46 mydb setroubleshoot[1261]: failed to retrieve rpm info for path '/mongodb/data/data/mongod.lock':
Jul 14 17:25:49 mydb setroubleshoot[1261]: SELinux is preventing /mongodb/app/mongodb-linux-x86_64-enterprise-rhel90-7.0.12/bin/mongod from lock access on the file /mongodb/data/data/mongod.lock. For complete SELinux messages run: sealert -l 77bb3298-bee6-4799-95ba-2e2db906ca16
Jul 14 17:25:49 mydb setroubleshoot[1261]: SELinux is preventing /mongodb/app/mongodb-linux-x86_64-enterprise-rhel90-7.0.12/bin/mongod from lock access on the file /mongodb/data/data/mongod.lock.#012#012*****  Plugin catchall_labels (83.8 confidence) suggests   *******************#012#012If you want to allow mongod to have lock access on the mongod.lock file#012Then you need to change the label on /mongodb/data/data/mongod.lock#012Do#012# semanage fcontext -a -t FILE_TYPE '/mongodb/data/data/mongod.lock'#012where FILE_TYPE is one of the following: 
...
...
Jul 14 17:25:49 mydb setroubleshoot[1261]: failed to retrieve rpm info for path '/mongodb/data/data/WiredTiger.lock':
Jul 14 17:25:49 mydb systemd[1]: systemd-hostnamed.service: Deactivated successfully.

{"t":{"$date":"2024-07-14T17:27:52.970+08:00"},"s":"E",  "c":"WT",       "id":22435,   "ctx":"initandlisten","msg":"WiredTiger error message","attr":{"error":13,"message":"[1720949272:969865][1292:0x7fae6360cb80], wiredtiger_open: [WT_VERB_DEFAULT][ERROR]: __posix_open_file, 815: /mongodb/data/data/WiredTiger.turtle: handle-open: open: Permission denied"}}
{"t":{"$date":"2024-07-14T17:27:52.970+08:00"},"s":"E",  "c":"WT",       "id":22435,   "ctx":"initandlisten","msg":"WiredTiger error message","attr":{"error":13,"message":"[1720949272:970344][1292:0x7fae6360cb80], wiredtiger_open: [WT_VERB_DEFAULT][ERROR]: __posix_open_file, 815: /mongodb/data/data/WiredTiger.turtle: handle-open: open: Permission denied"}}
{"t":{"$date":"2024-07-14T17:27:52.970+08:00"},"s":"E",  "c":"WT",       "id":22435,   "ctx":"initandlisten","msg":"WiredTiger error message","attr":{"error":13,"message":"[1720949272:970650][1292:0x7fae6360cb80], wiredtiger_open: [WT_VERB_DEFAULT][ERROR]: __posix_open_file, 815: /mongodb/data/data/WiredTiger.turtle: handle-open: open: Permission denied"}}
{"t":{"$date":"2024-07-14T17:27:52.970+08:00"},"s":"W",  "c":"STORAGE",  "id":22347,   "ctx":"initandlisten","msg":"Failed to start up WiredTiger under any compatibility version. This may be due to an unsupported upgrade or downgrade."}
{"t":{"$date":"2024-07-14T17:27:52.970+08:00"},"s":"F",  "c":"STORAGE",  "id":28595,   "ctx":"initandlisten","msg":"Terminating.","attr":{"reason":"13: Permission denied"}}
{"t":{"$date":"2024-07-14T17:27:52.970+08:00"},"s":"F",  "c":"ASSERT",   "id":23091,   "ctx":"initandlisten","msg":"Fatal assertion","attr":{"msgid":28595,"file":"src/mongo/db/storage/wiredtiger/wiredtiger_kv_engine.cpp","line":676}}
{"t":{"$date":"2024-07-14T17:27:52.970+08:00"},"s":"F",  "c":"ASSERT",   "id":23092,   "ctx":"initandlisten","msg":"\n\n***aborting after fassert() failure\n\n"}

{"t":{"$date":"2024-07-14T17:30:23.332+08:00"},"s":"I",  "c":"STORAGE",  "id":22315,   "ctx":"initandlisten","msg":"Opening WiredTiger","attr":{"config":"create,cache_size=3314M,session_max=33000,eviction=(threads_min=4,threads_max=4),config_base=false,statistics=(fast),log=(enabled=true,remove=true,path=journal,compressor=snappy),builtin_extension_config=(zstd=(compression_level=6)),file_manager=(close_idle_time=600,close_scan_interval=10,close_handle_minimum=2000),statistics_log=(wait=0),json_output=(error,message),verbose=[recovery_progress:1,checkpoint_progress:1,compact_progress:1,backup:0,checkpoint:0,compact:0,evict:0,history_store:0,recovery:0,rts:0,salvage:0,tiered:0,timestamp:0,transaction:0,verify:0,log:0],"}}
{"t":{"$date":"2024-07-14T17:30:23.986+08:00"},"s":"E",  "c":"WT",       "id":22435,   "ctx":"initandlisten","msg":"WiredTiger error message","attr":{"error":13,"message":{"ts_sec":1720949423,"ts_usec":986815,"thread":"1384:0x7f7dfac47b80","session_name":"connection","category":"WT_VERB_DEFAULT","category_id":9,"verbose_level":"ERROR","verbose_level_id":-3,"msg":"__posix_open_file:815:/mongodb/data/data/journal/WiredTigerLog.0000000012: handle-open: open","error_str":"Permission denied","error_code":13}}}
{"t":{"$date":"2024-07-14T17:30:23.994+08:00"},"s":"E",  "c":"WT",       "id":22435,   "ctx":"initandlisten","msg":"WiredTiger error message","attr":{"error":13,"message":{"ts_sec":1720949423,"ts_usec":994178,"thread":"1384:0x7f7dfac47b80","session_name":"connection","category":"WT_VERB_DEFAULT","category_id":9,"verbose_level":"ERROR","verbose_level_id":-3,"msg":"__posix_open_file:815:/mongodb/data/data/journal/WiredTigerLog.0000000012: handle-open: open","error_str":"Permission denied","error_code":13}}}
{"t":{"$date":"2024-07-14T17:30:24.000+08:00"},"s":"E",  "c":"WT",       "id":22435,   "ctx":"initandlisten","msg":"WiredTiger error message","attr":{"error":13,"message":{"ts_sec":1720949424,"ts_usec":736,"thread":"1384:0x7f7dfac47b80","session_name":"connection","category":"WT_VERB_DEFAULT","category_id":9,"verbose_level":"ERROR","verbose_level_id":-3,"msg":"__posix_open_file:815:/mongodb/data/data/journal/WiredTigerLog.0000000012: handle-open: open","error_str":"Permission denied","error_code":13}}}
{"t":{"$date":"2024-07-14T17:30:24.002+08:00"},"s":"W",  "c":"STORAGE",  "id":22347,   "ctx":"initandlisten","msg":"Failed to start up WiredTiger under any compatibility version. This may be due to an unsupported upgrade or downgrade."}
{"t":{"$date":"2024-07-14T17:30:24.002+08:00"},"s":"F",  "c":"STORAGE",  "id":28595,   "ctx":"initandlisten","msg":"Terminating.","attr":{"reason":"13: Permission denied"}}
{"t":{"$date":"2024-07-14T17:30:24.002+08:00"},"s":"F",  "c":"ASSERT",   "id":23091,   "ctx":"initandlisten","msg":"Fatal assertion","attr":{"msgid":28595,"file":"src/mongo/db/storage/wiredtiger/wiredtiger_kv_engine.cpp","line":676}}
{"t":{"$date":"2024-07-14T17:30:24.002+08:00"},"s":"F",  "c":"ASSERT",   "id":23092,   "ctx":"initandlisten","msg":"\n\n***aborting after fassert() failure\n\n"}
Job for mongod.service failed. See “systemctl status mongod.service“ and “journalctl -xe“ for detail
逸雅安然
06-30 1363
关于mongo 有许多情况，我在这里教你们如何去看错误，针对错误我们来解决 首先我们这是一个mongod 启动的时候报的错误，在执行service mongod start 启动时候报错 Job for mongod.service failed. See "systemctl status mongod.service" and "journalctl -xe" for details. 此时你可以执行控制台直接执行systemctl status mongod.service 或者journalct
MongoDB启动失败
qq_51574759的博客
10-30 2850
这里我已经配置好了，但是之前报错的时候，允许下面的可选项是有未选择的。翻译过来就是：试图在只读目录上创建锁定文件：…目录你下载下来之后可能是没有的，但是不着急，自己创建也可以。所以问题就显而易见了：文件夹权限不够。点击应用，退出再次执行启动命令。目录，并且在该目录下创建。目录，最后启动注意进入。
mongodb用systemctl启动code=killed, signal=ABRT
最新发布
kiramario的博客
05-16 432
在 Ubuntu 上安装 MongoDB Community Edition 后，启动 mongod 服务失败。通过 sudo systemctl status mongod 检查发现服务因信号 ABRT 终止。进一步查看日志文件 /var/log/mongodb/mongod.log，发现错误信息 Address already in use，表明端口 27017 已被占用。通过修改配置文件 /etc/mongod.conf，将 bindIp 从 127.0.0.1,::,0.0.0.0 改为 ::,0.
关于MongoDB无法启动服务
方少会
08-27 627
安装好了，启动服务出现无法启动 解决办法 用管理员身份打开：cmd 进入：H:\MongoDB\Server\3.4\bin   你的安装目录 输入：   mongod --bind_ip 0.0.0.0 --logpath E:\MongoDB\Server\3.4\data\logs\mongo.log --logappend --dbpath E:\MongoDB\S
mongodb 重启失败
weixin_40756083的博客
07-22 385
go相关学习资料：https://edu.51cto.com/video/4196.htmlMongoDB 重启失败的排查与解决 MongoDB 是一个高性能、高可用的 NoSQL 数据库。但在实际使用过程中，我们可能会遇到 MongoDB 重启失败的问题。本文将介绍 MongoDB 重启失败的原因、排查方法以及解决方案...
mongo数据库 启动报错
weixin_30298497的博客
10-16 264
报错信息如下： [root@166 bin]# mongoMongoDB shell version v3.4.6-22-ga109a23connecting to: mongodb://127.0.0.1:270172017-10-16T10:57:28.624+0800 W NETWORK [thread1] Failed to connect to 127.0.0.1:2701...
揭秘MySQL性能下降的幕后黑手：10个优化秘诀助你提升数据库性能
[揭秘MySQL性能下降的幕后黑手：10个优化秘诀助你提升数据库性能](https://ask.qcloudimg.com/http-save/yehe-8467455/kr4q3u119y.png) # 1. MySQL性能下降的幕后黑手** MySQL性能下降的原因多种多样，可能是由硬件...
JSON数据库性能瓶颈剖析：揭秘性能下降的幕后黑手
[JSON数据库性能瓶颈剖析：揭秘性能下降的幕后黑手](https://img-blog.csdnimg.cn/direct/6910ce2f54344953b73bcc3b89480ee1.png) # 1. JSON数据库简介 JSON数据库是一种以JSON格式存储和查询数据的数据库管理系统...
PHP数据库查询优化：揭秘查询慢的幕后黑手，优化策略大公开
[PHP数据库查询优化：揭秘查询慢的幕后黑手，优化策略大公开](https://p1-juejin.byteimg.com/tos-cn-i-k3u1fbpfcp/4a43bfd130964406a962ca06406879eb~tplv-k3u1fbpfcp-zoom-in-crop-mark:1512:0:0:0.awebp?...
数据库嵌套JSON索引失效分析与解决方案：揭秘索引失效的幕后黑手，保障数据查询性能
![数据库嵌套JSON索引失效分析与解决方案：揭秘索引失效的幕后黑手，保障数据查询性能]...# 1. 数据库嵌套JSON索引失效概述** 嵌套JSON索引失效是指数据库中对嵌套JSON数据创建的索引无法有效地用于查询优化的情况。...
MongoDB的安装问题之Service 'MongoDB Server' (MongoDB) failed to start
愿历尽千帆，仍保持最初的热爱，奔赴每一场山海，一如既往鲜活而明亮~
03-01 4361
前言   在安装MongoDB数据库的时候遇到了一些问题，导致无法正确安装或者无法正确启动，下面来一起看一下都有什么问题吧。 安装步骤： 一、安装MongoDB 问题一：   在安装过程中出现下面这个错误，这里我们先点‘Ignore’，先进行后续的安装。    二、安装可视化的图形化界面mongodb-compass 问题二：   打开mongodb-compass，点击CONNECT时出现错误：...
MongoDB无法启动的解决方法
kodmoqn的博客
08-01 160
MongoDB无法启动的解决方法
在linux安装mongodb后无法正常启动mongodb
出发行进
09-06 1545
在linux安装的mongod无法正常启动，寻找错误和解决错误的全部过程。
安装mongoDB出现服务启动失败--服务没有响应控制功能--Status:Service ‘MongoDB Server (MongoDB)‘ (MongoDB) failed tostart.
pjilysom的博客
04-19 3210
重点来了，重点来了，重点来了，重点来了，重点来了，重点来了，重点来了，重点来了，重点来了，重点来了，重点来了，重点来了，重点来了，重点来了，重点来了，重点来了，重点来了，重点来了，重点来了，重点来了，重点来了，重点来了，重点来了，重点来了，重点来了，重点来了，重点来了。没办法了，直接所有删除，安装删除，服务删除，文件夹删除，清空所有，再来一次。查了两个报错的情况，尝试了多种操作，最后选择了重装。先使用管理员权限，删除自动安装的mongodb服务。在下载好的安装包，启动安装文件，使用修复功能，
mongoDB安装报错failed to start
qq_44423029的博客
07-23 1954
错误信息：Service 'MongoDB Server (MongoDB)' (MongoDB) failed to start .Verify that you have sufficient privileges to start system services.
mongodb启动数据库失败
weixin_34018169的博客
07-11 335
1.今天在启动数据库的是出现了报错。大致内容如下：abouttoforkchildprocess,waitinguntilserverisreadyforconnections.alloutputgoingto:/root/mongodb-linux-x86_64-2.4.5/bin/mongodb.logforkedpro...
windows启动mongodb服务时报错，提示Windows无法启动MongoDB Server服务(位于本地计算机上)解决方案
StubbornCode的博客
06-25 1739
windows启动mongodb服务时报错，提示Windows无法启动MongoDB Server服务(位于本地计算机上)解决方案
MongoDB无法启动解决
Gavid0124的专栏
03-03 2648
问题描述： 1.直接报无法启动服务，报100错误在这里插入图片描述 2.当start时候说服务启动了，但是在stop的时候却说没有启动服务 以上两种情况都会让你的MongoDB服务无法启动，可能存在情况如下： 1.首先是没有用管理员执行net start MongoDB命令会出现这个情况，那么这时候只需要通过win+x+a进入管理员命令符执行命令即可。 2.没有正常关闭mongo...
Mongodb启动失败相关问题解决最全
qq_39038793的博客
08-28 3543
Mongodb启动失败相关问题解决最全
mongodb服务启动失败
12-02
以下是解决MongoDB服务启动失败的方法： 1. 查找mongod.lock文件并删除： ```shell find / -name mongod.lock -d rm -rf mongod.lock ``` 2. 重新启动MongoDB服务： ```shell /data/mongodb/bin/mongod --config /data/mongodb/bin/mongodb.conf --replSet cloud ``` 3. 如果上述方法无法解决问题，可以尝试通过修改配置文件的方式启动MongoDB服务： ```shell /data/mongodb/bin/mongod --repair -f /data/mongodb/bin/mongodb.conf --replSet cloud ``` 4. 校验配置文件的目录是否正确。 如果上述方法都无法解决问题，可以参考引用中的MongoDB安装过程以及问题记录，查找其他可能的解决方法。
评论
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

当前余额3.43元 前往充值 >
需支付：10.00元
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付元
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明：

1.余额是钱包充值的虚拟货币，按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载，可以购买VIP、付费专栏及课程。

余额充值