[SERVER-4406] Better warnings for missing SSL settings in mongod.conf Created: 01/Dec/11 Updated: 11/Jul/16 Resolved: 15/Dec/11 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Usability |
| Affects Version/s: | 2.0.1 |
| Fix Version/s: | 2.1.0 |
| Type: | Improvement | Priority: | Minor - P4 |
| Reporter: | Brandon Diamond | Assignee: | Brandon Diamond |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
SSL enabled 2.0.1 64bit linux |
||
| Issue Links: |
|
||||
| Participants: | |||||
| Description |
|
Can't start when using a mongod.conf file that has the sslPEMKeyFile value set and no value for sslOnNormalPorts or sslPEMKeyPassword. On the primary: Tue Nov 22 04:34:31 [conn3] replSet replSetInitiate admin command received from client On one of the other members: Tue Nov 22 04:34:31 [initandlisten] connection accepted from 1.1.3.4:54322 #4 Tue Nov 22 04:34:31 [conn4] end connection 1.1.3.4:54322 Fixing the mongod.conf to not set any of the 3 SSL options resolved the issue. It may be better to have the mongod config / command line validation create a more visible warning related to SSL settings |
| Comments |
| Comment by auto [ 14/Dec/11 ] |
|
Author: {u'login': u'', u'name': u'Brandon Diamond', u'email': u'brandon@10gen.com'}Message: |