[SERVER-5035] mongo behaves strangely Created: 22/Feb/12  Updated: 15/Aug/12  Resolved: 22/Feb/12

Status: Closed
Project: Core Server
Component/s: Tools
Affects Version/s: 1.8.5
Fix Version/s: None

Type: Bug Priority: Major - P3
Reporter: Tomas Pecholt Assignee: Unassigned
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Win2003


Attachments: Text File bug.txt    
Operating System: ALL
Participants:

 Description   

if I try to connect with mongo.exe to database server and I don't specify the port number mongo issues weird error message and doesn't connect. If i specify port number it works. I see 2 problems here:
1) mongo thinks I want to connect to localhost but I don't
2) why do I have to specify port number. Isn't 27018 the default port number?

sample session attached



 Comments   
Comment by Eliot Horowitz (Inactive) [ 22/Feb/12 ]

the default port is 27017, not 27018

--shardsvr puts it on 27018 as a non-default port so that you have to be explicit

Comment by Tomas Pecholt [ 22/Feb/12 ]

same applies to db.runCommand(

{addshard:server}

)
I have to specify port name even if it is the default port

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