[SERVER-18000] Mongodb socket permissions Created: 12/Apr/15  Updated: 13/Apr/15  Resolved: 12/Apr/15

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: 3.0.0, 3.0.1, 3.0.2
Fix Version/s: None

Type: Question Priority: Critical - P2
Reporter: Mall Johnson Assignee: Unassigned
Resolution: Done Votes: 0
Labels: connection, performance
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Ubuntu, Debian
MongoDB 3.x


Issue Links:
Related
is related to SERVER-13022 AF_UNIX socket file should not force ... Closed
is related to DOCS-4999 No documentation for: net.unixDomainS... Closed
is related to DOCS-5203 3.0 compatibility notes should mentio... Closed
Backwards Compatibility: Fully Compatible
Participants:

 Description   

Hello,
the problem is that the mongodb 3.x socket in /tmp/ is created with 700 permissions. Other processes, for example PHP, cannot use the socket anymore and receive a permission denied error. In the Versions before 3.0 the socket was created with 777 permissions. I have tried it in Ubuntu Server and debian on different hardware -> same error/bug.

Thanks for your attention.



 Comments   
Comment by Mall Johnson [ 13/Apr/15 ]

Ok, thank you very much for your time!

greetings Mall

Comment by Stennie Steneker (Inactive) [ 12/Apr/15 ]

Hi Mall,

The default socket file permissions in MongoDB 3.0 are more restrictive as per SERVER-13022. A `filePermissions` config option was added to allow setting more generous permissions, but unfortunately it looks like mention of this change is missing in the current 3.0 documentation (DOCS-4999).

I've just raised an issue to make sure this is noted in the compatibility release notes as well: DOCS-5203.

Regards,
Stephen

Generated at Thu Feb 08 03:46:15 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.