[SERVER-23865] DB getting shut down if no space for audit log file. Created: 22/Apr/16 Updated: 09/Jul/18 Resolved: 27/Apr/16 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Logging, Security |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Kingsly J | Assignee: | Unassigned |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
| Participants: | |
| Case: | (copied to CRM) |
| Description |
|
Hi Team, Regards, |
| Comments |
| Comment by Ramon Fernandez Marina [ 27/Apr/16 ] | ||||||||||||||||||||||||
|
Not being able to write to the log is not a fatal condition, and the server continues to operate. I've verified that on my end. The stack trace you pasted above shows the following:
which is a call to add an entry in the audit log. This is not related to regular logging. I looked at the configuration files provided and I don't see the audit log enabled or configured, so I'm not able to provide any more insight without further information. You may want to send the audit and server logs to different filesystems and verify that the reason for the shutdown is the inability to write to the audit log. | ||||||||||||||||||||||||
| Comment by Kingsly J [ 27/Apr/16 ] | ||||||||||||||||||||||||
|
Hi Ramon, Regards, | ||||||||||||||||||||||||
| Comment by Ramon Fernandez Marina [ 26/Apr/16 ] | ||||||||||||||||||||||||
|
jebas.kings@gmail.com, what the error log is trying to say is that you've run out of space for your audit log, so the server is shutting itself down. This behavior is expected: when the audit log is enabled, it's not a good security practice to allow operations that should be audited but can't. Please ensure there's enough space to write to your audit log files. Regards, | ||||||||||||||||||||||||
| Comment by Kingsly J [ 26/Apr/16 ] | ||||||||||||||||||||||||
|
Hi Team, | ||||||||||||||||||||||||
| Comment by Kingsly J [ 25/Apr/16 ] | ||||||||||||||||||||||||
|
Hi Ramon,
| ||||||||||||||||||||||||
| Comment by Kingsly J [ 25/Apr/16 ] | ||||||||||||||||||||||||
|
Hi Ramon, Regards, | ||||||||||||||||||||||||
| Comment by Ramon Fernandez Marina [ 22/Apr/16 ] | ||||||||||||||||||||||||
|
I'm not able to reproduce this behavior (3.2.5, 2-shard cluster, 2-node replica set per shard, CSRS). Can you please send us either the configuration files for all nodes in this cluster or the startup logs for them? Also, which nodes are you seeing affected by this behavior (config servers, data nodes, mongos nodes, all of the above)? Thanks, |