[SERVER-36251] change logfile permissions. Created: 24/Jul/18 Updated: 27/Oct/23 Resolved: 09/Aug/18 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Admin, Logging |
| Affects Version/s: | 3.6.5 |
| Fix Version/s: | None |
| Type: | Question | Priority: | Major - P3 |
| Reporter: | bae eunmi | Assignee: | Nick Brewer |
| Resolution: | Works as Designed | Votes: | 1 |
| Labels: | security | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
MongoDB shell version v3.6.5 |
||
| Issue Links: |
|
||||||||
| Participants: | |||||||||
| Description |
|
There are some questions about mongod permissions. When you restart or start mongod, the permissions of the mongo log are 644. And I do not want to change the log permissions. I need 644.
=========================================== 1). mongo --version
2. lsb_release -a
|
| Comments |
| Comment by bae eunmi [ 10/Aug/18 ] |
|
I will apply it. nick.brewer thank you! |
| Comment by Nick Brewer [ 09/Aug/18 ] |
|
piook You can instruct MongoDB log rotation to honor the system umask via the honorSystemUmask server parameter. Note that this must be applied when the server is started. -Nick |
| Comment by Nick Brewer [ 25/Jul/18 ] |
|
I'm passing this along to our Platform team for additional investigation. -Nick |
| Comment by lee mingyu [ 25/Jul/18 ] |
|
I have the same problem so I can't read the mongod log file (for example td-agent, logstash and so on) |
| Comment by Nick Brewer [ 24/Jul/18 ] |
|
Thanks for your report - so far I have been able to recreate this in my testing. I'm going to continue looking into it, and I should have more information for you soon. Regards, |