[SERVER-38127] BindIp option does not work correctly in a config file when moving from 3.6.2 to 3.6.8 Created: 14/Nov/18 Updated: 15/Nov/18 Resolved: 15/Nov/18 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Ian Hannah [X] | Assignee: | Danny Hatcher (Inactive) |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
| Operating System: | ALL |
| Participants: |
| Description |
|
Hi, I was using 3.6.2 and the attached configuration file worked correctly. When moving to 3.6.8 it no longer works - I get the following error:
Has the way that the IP address list has to be specified changed at all? Thanks Ian |
| Comments |
| Comment by Danny Hatcher (Inactive) [ 15/Nov/18 ] |
|
Hello Ian, The contents of bindIp should be whatever addresses are valid to contact the process on. For example, if your process was located at a server that was assigned the IP of 192.168.45.107 and you would expect clients to use that address, then you would set bindIp to 192.168.45.107. Thank you, Danny |
| Comment by Ian Hannah [X] [ 15/Nov/18 ] |
|
Hi Danny, The issue was that I specified two ip addresses in the BindIp option. I was confused and thought that is where the primary and secondary IP addresses should have been put. Now I only have one IP address in there it is working fine. I suspect that if you specify 127.0.0.1 (even though you don't need to) and the server IP address you may get the same issue but this was my mistake. |
| Comment by Ian Hannah [X] [ 14/Nov/18 ] |
|
My apologies - I did understand the bindIp option correctly. This can be closed. |