[SERVER-27619] Mongodb 3.2 does Not start After enabling authorization Created: 10/Jan/17 Updated: 10/Jan/17 Resolved: 10/Jan/17 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Heman | Assignee: | Mark Agarunov |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
| Operating System: | ALL |
| Participants: |
| Description |
|
Below I Have Attached My Conf And Log File
security: #replication: #sharding:
#auditLog: #snmp: Error==> |
| Comments |
| Comment by Mark Agarunov [ 10/Jan/17 ] |
|
Hello hemanparbhakar, According to the logs, this appears to be a permission issue with the socket file. Please note that SERVER project is for reporting bugs or feature suggestions for the MongoDB server. For MongoDB-related support discussion please post on the mongodb-user group or Stack Overflow with the mongodb tag. A question like this involving more discussion would be best posted on the mongodb-user group. |