在打开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. 开启session

    在index.php中开启 session_start();

  2. CodeForces 816B 前缀和

    To stay woke and attentive during classes, Karen needs some coffee! Karen, a coffee aficionado, want ...

  3. NodeJS让前端与后端更友好的分手

    学问   最近“上层建筑”在兴起国学热,所以公司几个月前决定开发一款名叫“学问”的有关于国学的app.     APP的详情页面还是由web来显现具体内容,有些类似于新闻页,图文混排什么的web是最适 ...

  4. node.js 基础篇

    日志输出方式 node test.js 2>error.log 1>info.log 如果需要日志文件追加 node test.js 2>>error.log 1>> ...

  5. 树形dp（B - Computer HDU - 2196 ）

    题目链接:https://cn.vjudge.net/contest/277955#problem/B 题目大意:首先输入n代表有n个电脑,然后再输入n-1行,每一行输入两个数,t1,t2.代表第(i ...

  6. vuejs心法和技法

    原文地址:http://www.cnblogs.com/kidsitcn/p/5409994.html 所有的vuejs组件都是被扩展的vue实例: var MyComponent = Vue.ext ...

  7. 【Python项目】爬取新浪微博签到页

    基于微博签到页的微博爬虫 项目链接:https://github.com/RealIvyWong/WeiboCrawler/tree/master/WeiboLocationCrawler 1 实现功 ...

  8. MySQL GTID你知多少【转】

    MySQL在5.6的版本推出了GTID复制,相比传统的复制,GTID复制对于运维更加友好,这个事务是谁产⽣,产⽣多少事务,⾮常直接的标识出来,当然GTID也有限制,对于什么是GTID可以参考我之前的文 ...

  9. 一步一步搭建11gR2 rac+dg之安装rac出现问题解决(六)【转】

    一步一步在RHEL6.5+VMware Workstation 10上搭建 oracle 11gR2 rac + dg 之安装rac出现的问题 (六) 本文转自 一步一步搭建11gR2 rac+dg之 ...

  10. java 内部类与控制框架

    应用程序控制框架(application framework)就是设计解决某类特殊问题的一个类,或一组类,要运用某个应用程序框架,通常是继承一个类或多个类,并覆盖这些方法.在覆盖的方法中编写代码定制应 ...