[SERVER-12839] Unable to access HTTP Status Interface + Exception Created: 21/Feb/14 Updated: 10/Dec/14 Resolved: 26/Feb/14 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | HTTP Console, Networking |
| Affects Version/s: | 2.6.0-rc0 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Minor - P4 |
| Reporter: | David Docteur [X] | Assignee: | Unassigned |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | mongod | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
||||||||
| Issue Links: |
|
||||||||
| Operating System: | ALL | ||||||||
| Steps To Reproduce: | Here is what I've done in order to get this issue : sudo mongod --dbpath /var/data/db --port 65536 or even sudo mongod --dbpath /var/data/db --port -1 |
||||||||
| Participants: | |||||||||
| Description |
|
Hi guys, I was just curious to see what would happen if mongod would be initialised running above the port 65535 and below the port 1. In fact, the HTTP Status Interface runs, from what mentions the documentation 2.4.8, on the same port as the primary mongod instance + 1000, it would be impossible to have access to it on the port 66535 for example. I obtain an assertion failure in src/mongo/db/client.h 235. |
| Comments |
| Comment by Daniel Pasette (Inactive) [ 26/Feb/14 ] | ||
|
The invalid port issue was fixed in the 2.5 dev cycle. See To answer the question about the httpinterface, if the port is designated >= to 64537, the web server will fail to start with the following msg in the logs:
| ||
| Comment by David Docteur [X] [ 22/Feb/14 ] | ||
|
And also, how to access the HTTP Interface if mongod is listening on the port 65500 for example ? Does the HTTP Interface run on the mongod's port - 1000 ? Thank you ! |