[SERVER-17541] getting error when starting mongod Created: 11/Mar/15  Updated: 13/Mar/15  Resolved: 11/Mar/15

Status: Closed
Project: Core Server
Component/s: Admin
Affects Version/s: 3.0.0
Fix Version/s: None

Type: Question Priority: Major - P3
Reporter: sampat Assignee: Unassigned
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Participants:

 Description   

2015-03-11T18:32:22.157+0530 I CONTROL  [initandlisten] MongoDB starting : pid=2156 port=27017 dbpath=/data/db 64-bit host=ubuntu1
2015-03-11T18:32:22.158+0530 I CONTROL  [initandlisten] ** WARNING: You are running this process as the root user, which is not recommended.
2015-03-11T18:32:22.158+0530 I CONTROL  [initandlisten]
2015-03-11T18:32:22.158+0530 I CONTROL  [initandlisten] db version v3.0.0
2015-03-11T18:32:22.158+0530 I CONTROL  [initandlisten] git version: a841fd6394365954886924a35076691b4d149168
2015-03-11T18:32:22.158+0530 I CONTROL  [initandlisten] OpenSSL version: OpenSSL 1.0.1f 6 Jan 2014
2015-03-11T18:32:22.158+0530 I CONTROL  [initandlisten] build info: Linux ip-10-179-177-12 3.13.0-24-generic #46-Ubuntu SMP Thu Apr 10 19:11:08 UTC 2014 x86_64 BOOST_LIB_VERSION=1_49
2015-03-11T18:32:22.159+0530 I CONTROL  [initandlisten] allocator: tcmalloc
2015-03-11T18:32:22.159+0530 I CONTROL  [initandlisten] options: {}
2015-03-11T18:32:22.211+0530 E NETWORK  [initandlisten] listen(): bind() failed errno:98 Address already in use for socket: 0.0.0.0:27017
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
2015-03-11T18:32:22.211+0530 E NETWORK  [initandlisten]   addr already in use
2015-03-11T18:32:22.277+0530 I JOURNAL  [initandlisten] journal dir=/data/db/journal
2015-03-11T18:32:22.277+0530 I JOURNAL  [initandlisten] recover : no journal files present, no recovery needed
2015-03-11T18:32:22.284+0530 I JOURNAL  [durability] Durability thread started
2015-03-11T18:32:22.285+0530 I JOURNAL  [journal writer] Journal writer thread started
2015-03-11T18:32:22.369+0530 I CONTROL  [initandlisten] now exiting
2015-03-11T18:32:22.369+0530 I NETWORK  [initandlisten] shutdown: going to close listening sockets...
2015-03-11T18:32:22.369+0530 I NETWORK  [initandlisten] shutdown: going to flush diaglog...
2015-03-11T18:32:22.369+0530 I NETWORK  [initandlisten] shutdown: going to close sockets...
2015-03-11T18:32:22.369+0530 I STORAGE  [initandlisten] shutdown: waiting for fs preallocator...
2015-03-11T18:32:22.370+0530 I STORAGE  [initandlisten] shutdown: final commit...
2015-03-11T18:32:22.377+0530 I JOURNAL  [initandlisten] journalCleanup...
2015-03-11T18:32:22.377+0530 I JOURNAL  [initandlisten] removeJournalFiles
2015-03-11T18:32:22.382+0530 I JOURNAL  [initandlisten] Terminating durability thread ...
2015-03-11T18:32:22.472+0530 I JOURNAL  [journal writer] Journal writer thread stopped
2015-03-11T18:32:22.472+0530 I JOURNAL  [durability] Durability thread stopped
2015-03-11T18:32:22.473+0530 I STORAGE  [initandlisten] shutdown: closing all files...
2015-03-11T18:32:22.476+0530 I STORAGE  [initandlisten] closeAllFiles() finished
2015-03-11T18:32:22.476+0530 I STORAGE  [initandlisten] shutdown: removing fs lock...
2015-03-11T18:32:22.477+0530 I CONTROL  [initandlisten] dbexit:  rc: 48



 Comments   
Comment by sampat [ 12/Mar/15 ]

The error still persist even after taking just one connection. and i have even tried by using --port arguement

Comment by sampat [ 12/Mar/15 ]

Thank you

Comment by Kaloian Manassiev [ 11/Mar/15 ]

This is expected behaviour.

The error means that most likely you have another mongodb server running on the same host.

You can use the --port argument to specify a different port for this second instance that you are trying to start.

Generated at Thu Feb 08 03:44:50 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.