Mongodb崩溃得到信号15(终止) [英] Mongodb crash got signal 15 (Terminated)

查看:41
本文介绍了Mongodb崩溃得到信号15(终止)的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我的 mongodb 服务器突然收到信号 15(终止).我不知道为什么 mongodb 崩溃了.以下是日志消息.

my mongodb server suddenly got signal 15 (Terminated). I don't have any idea why the mongodb crashed. Below is the log messages.

Mon Jun 27 07:33:31.701 [signalProcessingThread] got signal 15 (Terminated), will terminate after current cmd ends
Mon Jun 27 07:33:31.704 [signalProcessingThread] now exiting
Mon Jun 27 07:33:31.704 dbexit: 
Mon Jun 27 07:33:31.704 [signalProcessingThread] shutdown: going to close listening sockets...
Mon Jun 27 07:33:31.704 [signalProcessingThread] closing listening socket: 9
Mon Jun 27 07:33:31.704 [signalProcessingThread] closing listening socket: 10
Mon Jun 27 07:33:31.704 [signalProcessingThread] closing listening socket: 11
Mon Jun 27 07:33:31.705 [signalProcessingThread] removing socket file: /tmp/mongodb-27017.sock
Mon Jun 27 07:33:31.705 [signalProcessingThread] shutdown: going to flush diaglog...
Mon Jun 27 07:33:31.705 [signalProcessingThread] shutdown: going to close sockets...
Mon Jun 27 07:33:31.706 [signalProcessingThread] shutdown: waiting for fs preallocator...
Mon Jun 27 07:33:31.706 [signalProcessingThread] shutdown: lock for final commit...
Mon Jun 27 07:33:31.706 [signalProcessingThread] shutdown: final commit...

下面是重启过程.

***** SERVER RESTARTED *****


Mon Jun 27 07:34:22.500 [initandlisten] MongoDB starting : pid=888 port=27017 dbpath=/var/lib/mongodb 64-bit host=jasa-online
Mon Jun 27 07:34:22.500 [initandlisten] db version v2.4.9
Mon Jun 27 07:34:22.500 [initandlisten] git version: nogitversion
Mon Jun 27 07:34:22.500 [initandlisten] build info: Linux orlo 3.2.0-58-generic #88-Ubuntu SMP Tue Dec 3 17:37:58 UTC 2013 x86_64 BOOST_LIB_VERSION=1_54
Mon Jun 27 07:34:22.500 [initandlisten] allocator: tcmalloc
Mon Jun 27 07:34:22.500 [initandlisten] options: { bind_ip: "0.0.0.0", config: "/etc/mongodb.conf", dbpath: "/var/lib/mongodb", journal: "true", logappend: "true", logpath: "/var/log/mongodb/mongodb.log" }
Mon Jun 27 07:34:22.531 [initandlisten] journal dir=/var/lib/mongodb/journal
Mon Jun 27 07:34:22.531 [initandlisten] recover : no journal files present, no recovery needed

MongoDB shell 版本是 2.4.9.我怎么能弄清楚为什么会这样?这是由运行超过 300 秒的长时间运行查询引起的吗?

The MongoDB shell version is 2.4.9. How can i figured out why this is happen ? Is that caused by long running query that run more than 300s ?

推荐答案

我知道这是旧的,但我遇到了这个问题并偶然发现了这个问题.我设法解决了.

I know this is old, but I was running into the issue and stumbled across this question. I managed to solve it.

我的问题是在 Ubuntu 18.04 上并尝试安装和运行 MongoDB 3.4/3.6.

My issue was on Ubuntu 18.04 and attempting to install and run MongoDB 3.4/3.6.

一个问题是缺少具有适当权限的/var/run/mongodb 目录,另一个是此错误.我仍然不能 100% 确定这个错误是否与目录有关,但它肯定与配置有关.

One issue was a missing /var/run/mongodb directory with the appropriate permissions, the other was this error. I'm still not 100% sure if this error was related to the directory or not, but it definitely had something to do with the configs.

我的 mongod.conf 最终将 processManagement - fork 设置为 true.将其更改为 false 允许它开始工作.

My mongod.conf ended up having processManagement - fork set to true. Changing that to false allowed it to start working.

这篇关于Mongodb崩溃得到信号15(终止)的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆