Failed to configure sockets at startup. dbexit: rc: 48 error in mongodb

Question

I updated mongo to version 3.2, now I get this error. I used to get no errors. Only after updating mongo do I get this error. I even tried to stop and restart the mongod service, but still it shows the same error.

rahul ~ $ mongod 2016-01-10T23:39:51.696+0530 I CONTROL [initandlisten] MongoDB starting : pid=6630 port=27017 dbpath=/data/db 64-bit host=rahulcomp24-HP-ENVY-15-Notebook-PC 2016-01-10T23:39:51.696+0530 I CONTROL [initandlisten] db version v3.2.0 2016-01-10T23:39:51.696+0530 I CONTROL [initandlisten] git version: 45d947729a0315accb6d4f15a6b06be6d9c19fe7 2016-01-10T23:39:51.696+0530 I CONTROL [initandlisten] OpenSSL version: OpenSSL 1.0.1f 6 Jan 2014 2016-01-10T23:39:51.696+0530 I CONTROL [initandlisten] allocator: tcmalloc 2016-01-10T23:39:51.696+0530 I CONTROL [initandlisten] modules: none 2016-01-10T23:39:51.696+0530 I CONTROL [initandlisten] build environment: 2016-01-10T23:39:51.696+0530 I CONTROL [initandlisten] distmod: ubuntu1404 2016-01-10T23:39:51.696+0530 I CONTROL [initandlisten] distarch: x86_64 2016-01-10T23:39:51.696+0530 I CONTROL [initandlisten] target_arch: x86_64 2016-01-10T23:39:51.696+0530 I CONTROL [initandlisten] options: {} 2016-01-10T23:39:51.717+0530 E NETWORK [initandlisten] listen(): bind() failed errno:98 Address already in use for socket: 0.0.0.0:27017 2016-01-10T23:39:51.717+0530 E NETWORK [initandlisten] addr already in use 2016-01-10T23:39:51.717+0530 E STORAGE [initandlisten] Failed to set up sockets during startup. 2016-01-10T23:39:51.717+0530 I CONTROL [initandlisten] dbexit: rc: 48 

`

 rahul ~ $ mongo MongoDB shell version: 3.2.0 connecting to: test Server has startup warnings: 2016-01-10T23:38:16.095+0530 I CONTROL [initandlisten] 2016-01-10T23:38:16.095+0530 I CONTROL [initandlisten] ** WARNING: /sys/kernel/mm/transparent_hugepage/enabled is 'always'. 2016-01-10T23:38:16.095+0530 I CONTROL [initandlisten] ** We suggest setting it to 'never' 2016-01-10T23:38:16.095+0530 I CONTROL [initandlisten] 2016-01-10T23:38:16.095+0530 I CONTROL [initandlisten] ** WARNING: /sys/kernel/mm/transparent_hugepage/defrag is 'always'. 2016-01-10T23:38:16.095+0530 I CONTROL [initandlisten] ** We suggest setting it to 'never' 2016-01-10T23:38:16.095+0530 I CONTROL [initandlisten] 

Answer 1

Locate the process running on port 27017:

 C:\Users\hughes> netstat -aon | findstr 27017 TCP 0.0.0.0:27017 0.0.0.0:0 LISTENING 3344 

The last column shows the PID (3344). Find the process name for this PID:

 C:\Users\hughes> tasklist /fi "pid eq 3344" Image Name PID Session Name Session# Mem Usage ========================= ======== ================ =========== ============ VirtualBox.exe 3344 Console 1 101,908 K 

For me, it turned out that VirtualBox port forwarding was a problem.

Answer 2

therefore mongod output reports

 listen(): bind() failed errno:98 Address already in use for socket: 0.0.0.0:27017" 

which means that some process is already using the same socket. For example, if I try to start mongod when it is already running, I get exactly this output. Are you sure this is none of your business? I would have guessed since the shell of the mango seems to connect successfully ...

Answer 3

check if db is working, run:

 ps aux | grep mongo 

find db (e.g. 77071) and kill it, run:

 kill -9 77071