[SERVER-35101] Handle differently a badly formed bindIp argument Created: 18/May/18 Updated: 29/Oct/23 Resolved: 12/Jun/18 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Networking |
| Affects Version/s: | 3.6.4 |
| Fix Version/s: | 3.6.6, 4.0.1, 4.1.1 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Daniel Coupal | Assignee: | Adam Cooper (Inactive) |
| Resolution: | Fixed | Votes: | 5 |
| Labels: | neweng | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Backwards Compatibility: | Minor Change | ||||||||
| Backport Requested: |
v4.0, v3.6
|
||||||||
| Sprint: | Platforms 2018-06-18 | ||||||||
| Participants: | |||||||||
| Description |
|
mongod should properly handle a "poorly" formed bind_ip argument, for example when it contains whitespace.
However, the process starts, listening on 127.0.0.1 1) Starting the process, without one of the IP the user specified, should abort. 2) since the most common issue is having a space in the config or cmd-line argument, mongod should start by triming the spaces. |
| Comments |
| Comment by Githook User [ 02/Jul/18 ] |
|
Author: {'username': 'super-cooper', 'name': 'Adam Cooper', 'email': 'adam.cooper@mongodb.com'}Message: |
| Comment by Githook User [ 02/Jul/18 ] |
|
Author: {'username': 'super-cooper', 'name': 'Adam Cooper', 'email': 'adam.cooper@mongodb.com'}Message: (cherry picked from commit 84ccd279f2910a73b10678685b2a6a90bb6dd8fb) |
| Comment by Githook User [ 11/Jun/18 ] |
|
Author: {'name': 'Adam Cooper', 'email': 'adam.cooper@mongodb.com'}Message: |