在打开mongod之后如果不用了就按ctrl + c ,就不会出现以下的问题了

执行mongod报错

 mongod
2016-08-03T14:31:15.691+0800 I CONTROL [initandlisten] MongoDB starting : pid=13659 port=27017 dbpath=/data/db 64-bit host=yishiyaonie.local
2016-08-03T14:31:15.691+0800 I CONTROL [initandlisten] db version v3.2.8
2016-08-03T14:31:15.691+0800 I CONTROL [initandlisten] git version: ed70e33130c977bda0024c125b56d159573dbaf0
2016-08-03T14:31:15.691+0800 I CONTROL [initandlisten] OpenSSL version: OpenSSL 1.0.2h 3 May 2016
2016-08-03T14:31:15.691+0800 I CONTROL [initandlisten] allocator: system
2016-08-03T14:31:15.692+0800 I CONTROL [initandlisten] modules: none
2016-08-03T14:31:15.692+0800 I CONTROL [initandlisten] build environment:
2016-08-03T14:31:15.692+0800 I CONTROL [initandlisten] distarch: x86_64
2016-08-03T14:31:15.692+0800 I CONTROL [initandlisten] target_arch: x86_64
2016-08-03T14:31:15.692+0800 I CONTROL [initandlisten] options: {}
2016-08-03T14:31:15.692+0800 E NETWORK [initandlisten] listen(): bind() failed errno:48 Address already in use for socket: 0.0.0.0:27017
2016-08-03T14:31:15.692+0800 E NETWORK [initandlisten] addr already in use
2016-08-03T14:31:15.692+0800 E STORAGE [initandlisten] Failed to set up sockets during startup.
2016-08-03T14:31:15.692+0800 I CONTROL [initandlisten] dbexit: rc: 48
原因是端口被占用了
咋办呢?
➜ xushukui ps -aux | grep mongod
root 17820 2.7 1.3 277020 52520 pts/19 Tl 20:24 0:00 mongod
root 17857 0.0 0.0 15984 984 pts/19 S+ 20:24 0:00 grep --color=auto --exclude-dir=.bzr --exclude-dir=CVS --exclude-dir=.git --exclude-dir=.hg --exclude-dir=.svn mongod
➜ xushukui kill -9 17820
[1] + 17820 killed mongod
然后重启ok了:
mongod
2018-03-19T20:25:05.986+0800 I CONTROL [initandlisten] MongoDB starting : pid=17904 port=27017 dbpath=/data/db 64-bit host=xushukui-Lenovo-Erazer-Z41-70
2018-03-19T20:25:05.986+0800 I CONTROL [initandlisten] db version v3.2.19
2018-03-19T20:25:05.986+0800 I CONTROL [initandlisten] git version: a9f574de6a566a58b24d126b44a56718d181e989
2018-03-19T20:25:05.986+0800 I CONTROL [initandlisten] OpenSSL version: OpenSSL 1.0.2g 1 Mar 2016
2018-03-19T20:25:05.986+0800 I CONTROL [initandlisten] allocator: tcmalloc
2018-03-19T20:25:05.986+0800 I CONTROL [initandlisten] modules: none
2018-03-19T20:25:05.986+0800 I CONTROL [initandlisten] build environment:
2018-03-19T20:25:05.986+0800 I CONTROL [initandlisten] distmod: ubuntu1604
2018-03-19T20:25:05.986+0800 I CONTROL [initandlisten] distarch: x86_64
2018-03-19T20:25:05.986+0800 I CONTROL [initandlisten] target_arch: x86_64
2018-03-19T20:25:05.986+0800 I CONTROL [initandlisten] options: {}
2018-03-19T20:25:06.017+0800 I - [initandlisten] Detected data files in /data/db created by the 'wiredTiger' storage engine, so setting the active storage engine to 'wiredTiger'.
2018-03-19T20:25:06.017+0800 W - [initandlisten] Detected unclean shutdown - /data/db/mongod.lock is not empty.
2018-03-19T20:25:06.017+0800 W STORAGE [initandlisten] Recovering data from the last clean checkpoint.
2018-03-19T20:25:06.017+0800 I STORAGE [initandlisten] wiredtiger_open config: create,cache_size=1G,session_max=20000,eviction=(threads_min=4,threads_max=4),config_base=false,statistics=(fast),log=(enabled=true,archive=true,path=journal,compressor=snappy),file_manager=(close_idle_time=100000),checkpoint=(wait=60,log_size=2GB),statistics_log=(wait=0),verbose=(recovery_progress),
2018-03-19T20:25:06.257+0800 I STORAGE [initandlisten] WiredTiger [1521462306:257852][17904:0x7f1bca6a5c80], txn-recover: Main recovery loop: starting at 6/128
2018-03-19T20:25:06.258+0800 I STORAGE [initandlisten] WiredTiger [1521462306:258184][17904:0x7f1bca6a5c80], txn-recover: Recovering log 6 through 7
2018-03-19T20:25:06.273+0800 I STORAGE [initandlisten] WiredTiger [1521462306:273354][17904:0x7f1bca6a5c80], file:index-1-3052586711455020830.wt, txn-recover: Recovering log 7 through 7
2018-03-19T20:25:07.021+0800 I CONTROL [initandlisten] ** WARNING: You are running this process as the root user, which is not recommended.
2018-03-19T20:25:07.022+0800 I CONTROL [initandlisten]
2018-03-19T20:25:07.022+0800 I CONTROL [initandlisten]
2018-03-19T20:25:07.022+0800 I CONTROL [initandlisten] ** WARNING: /sys/kernel/mm/transparent_hugepage/enabled is 'always'.
2018-03-19T20:25:07.022+0800 I CONTROL [initandlisten] ** We suggest setting it to 'never'
2018-03-19T20:25:07.022+0800 I CONTROL [initandlisten]
2018-03-19T20:25:07.022+0800 I CONTROL [initandlisten] ** WARNING: /sys/kernel/mm/transparent_hugepage/defrag is 'always'.
2018-03-19T20:25:07.022+0800 I CONTROL [initandlisten] ** We suggest setting it to 'never'
2018-03-19T20:25:07.022+0800 I CONTROL [initandlisten]
2018-03-19T20:25:07.023+0800 I NETWORK [HostnameCanonicalizationWorker] Starting hostname canonicalization worker
2018-03-19T20:25:07.023+0800 I FTDC [initandlisten] Initializing full-time diagnostic data capture with directory '/data/db/diagnostic.data'
2018-03-19T20:25:07.023+0800 I NETWORK [initandlisten] waiting for connections on port 27017

解决mongo 端口占用问题的更多相关文章

  1. 【Docker】安装MySQL彻底解决3306端口占用问题

    1.问题闪现: 初次up mysql报3306端口被占用 yunduo@YunDuo:~/Work/Learning/Docker/docker_compose$ docker-compose up ...

  2. windows下关闭指定端口服务,解决tomcat端口占用问题

    http://blog.aizhet.com/Server/640.html 在windows下做java EE的开发时:搭建 Eclipse+tomcat的java web开发环境:在应用之中经常遇 ...

  3. 解决eclipse端口占用问题

    在eclipse中开启tomcat服务器时报错:端口已被占用. 这是因为在tomcat开启的状态下,eclipse异常关闭,导致tomcat一直占用端口. 解决方法 在cmd窗口中输入命令-- net ...

  4. 解决nginx端口占用问题

    1.键入命令:netstat -ano | findstr 80 查看80端口被哪个程序占用: 2.键入命令:netsh http show servicestate 查看http服务状态(注:解决后 ...

  5. 解决ADB端口占用问题

    方式一5037为adb默认端口,若5037端口被占用,查看占用端口的进程PIDC:\Users\wwx229495>netstat -aon|findstr 5037   TCP    127. ...

  6. window service 2008 解决80端口占用

    1.进入cmd使用netstat 命令查看指定端口netstat -ano | findstr :802.如下所示:本地的80端口被进程为4的占用 TCP    0.0.0.0:80          ...

  7. 一分钟 解决Tomcat端口 占用问题

    打开 cmd命令 在 命令界面中输入 netstat -ano|findstr 8080 使用 命令 taskill /pid 端口号  /f    结束占用

  8. 【android】Android ADB 端口占用问题解决方案

    解决ADB端口占用问题 方式一5037为adb默认端口,若5037端口被占用,查看占用端口的进程PIDC:\Users\wwx229495>netstat -aon|findstr 5037  ...

  9. windows下Jmeter压测端口占用问题(亲测有效)

    windows下Jmeter压测端口占用问题 1 报错信息描述 压测的初期,在设置了 150qps/s 的并发数下压测几分钟后 Jmeter 就出现了如下报错. JAVA.NET.BINDEXCEPT ...

随机推荐

  1. POJ 1128 Frame Stacking (拓扑排序)

    题目链接 Description Consider the following 5 picture frames placed on an 9 x 8 array. ........ ........ ...

  2. Java并发编程(2) AbstractQueuedSynchronizer的设计与实现

    一 前言 上一篇分析AQS的内部结构,其中有介绍AQS是什么,以及它的内部结构的组成,那么今天就来分析下前面说的内部结构在AQS中的具体作用(主要在具体实现中体现). 二 AQS的接口和简单示例 上篇 ...

  3. aarch64_j1

    JSCookMenu-2.0.4-13.fc26.noarch.rpm 2017-02-14 07:06 37K fedora Mirroring Project Java-WebSocket-1.3 ...

  4. WCF ServiceContract,OperationContract

    代码如下 [ServiceContract] //服务协定定义 using System.ServiceModel; public interface IInterface1 { [Operation ...

  5. 【日记】NOIP2018

    day-2: 最后一次走出机房,刚下过几天的雨,感受到的是彻骨的寒意.下午离开教室,跟班主任请了接下来几天的假,班主任斜视了我一眼,哼了一声,确认了一下,不再理会我了.班里的同学或是忙着自己的作业,或 ...

  6. 【小程序开发】上拉加载更多demo

    wxml: <scroll-view class='swiper-scroll' scroll-y="{{true}}" bindscrolltolower="lo ...

  7. css-概述和选择器

    一:CSS 概述 CSS 指层叠样式表 (Cascading Style Sheets) 样式定义如何显示 HTML 元素 样式通常存储在样式表中 把样式添加到 HTML 4.0 中,是为了解决内容与 ...

  8. TImage 显示 资源中 的图片、TResourceStream、资源文件

    unit Unit5; interface uses Winapi.Windows, Winapi.Messages, System.SysUtils, System.Variants, System ...

  9. CNN细节

    1.各层作用 输入层 输入层是整个神经网络的输入,一般代表的是图片的像素矩阵(一般为三维矩阵,即像素x像素x通道) 卷积层 每一层卷积都会提取数据特征,再经过组合和抽象形成更高阶的特征. 池化层 保留 ...

  10. Python输入/输出

    1.在python2.x中raw_input( )和input( ),两个函数都存在,其中区别为 raw_input( )---将所有输入作为字符串看待,返回字符串类型 input( )-----只能 ...