Re: admin web console waiting for connections on port 2 8017

1,211 views
Skip to first unread message

Gianfranco

unread,
Sep 5, 2012, 7:03:40 AM9/5/12
to mongod...@googlegroups.com
Hi Dan,

The d in mongod database process stands for daemon (or service in Windows) and therefore you can't type commands with it.

To connect to the database process (mongod), you'll have to run the mongo process (also called shell).
If you haven't changed the default port then it should work and you can then run any mongo command.

It's detailed in tutorial you mentioned.

Regards,
Gianfranco

On Wednesday, September 5, 2012 11:12:52 AM UTC+1, Dan Solo wrote:
Hi,

I'm trying to setup the MongoDB for the first time on a Windows 2008 platform and have been trying to follow the 'simple' install procedure at http://docs.mongodb.org/manual/tutorial/install-mongodb-on-windows/

However, whether I try to move the default database location to a different folder (by the command C:\mongodb\bin\mongod.exe --dbpath c:\mongodb\data) OR just start the main MongoDB database process using the existing default database location (by the command C:\mongodb\bin\mongod.exe) I get stuck at the same pair of command line prompts:

Wed Sep 05 11:35:24 [initandlisten] waiting for connections on port 27017
Wed Sep 05 11:35:24 [websvr] admin web console waiting for connections on port 2
8017

I've tried waiting patiently but with no signs of any action after 15mins+ the only way out is to Ctrl+C.

There's no mention of this error in the official install steps, nor in the troubleshooting guides or via a google search.

Any ideas?

Many thanks,
Dan

Gianfranco

unread,
Sep 5, 2012, 9:26:19 AM9/5/12
to mongod...@googlegroups.com
Maybe the tutorial doesn't distinguish the 2 processes explicitly, but that's how it's been designed.

The mongod is the process that when running on production server it doesn't require a shell (or prompt) all the time, that's why the 2 processes.

You'll need to run mongod first and then open another prompt and run mongo. Note that this last one is not the database process it self, is just a command line interface (CLI) to connect to the database and run queries, commands, etc

On Wednesday, September 5, 2012 12:35:24 PM UTC+1, Dan Solo wrote:
Hi Gianfranco,

Thanks for taking the time to reply.

Still don't get it I'm afraid. I'm following the tutorial line by line and am stuck at the following:

Start MongoDB

To start MongoDB, execute from the Command Prompt:

C:\mongodb\bin\mongod.exe

This will start the main MongoDB database process.


The database process just hangs with the original message I posted. Surely I'm supposed to start the database before trying to connect, if I try the mongo.exe process without having successfully run the above I get:

C:\>mongodb\bin\mongo.exe
MongoDB shell version: 2.2.0
connecting to: test
Wed Sep 05 13:11:06 Error: couldn't connect to server 127.0.0.1:27017 src/mongo/
shell/mongo.js:91
exception: connect failed

I can't see why the tutorial would instruct you to run the mongod.exe process if it couldn't be run?

Cheers,
Dan

Dan Solo

unread,
Sep 5, 2012, 11:48:08 AM9/5/12
to mongod...@googlegroups.com
Thanks Gianfranco,

Between yourself and Stephen's replies I've seen the error of my assumption and will move onto setting up the Windows Service now.

Cheers,
Dan

Gianfranco

unread,
Sep 6, 2012, 7:29:47 AM9/6/12
to mongod...@googlegroups.com
No worries.

I suggest you to try a free GUI program, to get familiar with mongodb
Reply all
Reply to author
Forward
0 new messages