[SERVER-31199] If security.authorization is enabled mongos launched three process Created: 21/Sep/17 Updated: 27/Oct/23 Resolved: 22/Sep/17 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | 3.2.16, 3.4.0 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | EVGENIY CHISTYAKOV | Assignee: | Mark Agarunov |
| Resolution: | Works as Designed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
| Operating System: | ALL |
| Participants: |
| Description |
|
/etc/mongod.conf
/etc/mongos.conf
mongod launched via systemd: systemctl start mongod ps auxf
|
| Comments |
| Comment by EVGENIY CHISTYAKOV [ 26/Sep/17 ] |
|
Hello Mark, Thank you for the answer. |
| Comment by Mark Agarunov [ 22/Sep/17 ] |
|
Hello ch1s7ya, Thank you for providing this data. Looking over this, the behavior you are seeing seems to be caused by the lack of internal authentication between mongos and mongod. When using authorization on a sharded cluster internal authentication authentication is required between all members of the cluster. The internal authentication can be set up with keyFiles or x.509 certificates but must be configured if using authorization on a sharded cluster. Thanks, |
| Comment by EVGENIY CHISTYAKOV [ 22/Sep/17 ] |
|
Logs in the attachment |
| Comment by Mark Agarunov [ 21/Sep/17 ] |
|
Hello ch1s7ya, Thank you for the report. To get a better idea of what may be happening to cause this behavior, could you please provide the complete logs from all affected mongos and mongod nodes? Thanks, |
| Comment by EVGENIY CHISTYAKOV [ 21/Sep/17 ] |
|
When I try to start mongo i get next error: MongoDB shell version: 3.2.16 exception: connect failed |