[MXS-3056] A full disk disables logging instead of pausing it Created: 2020-06-29 Updated: 2020-08-20 Resolved: 2020-08-20 |
|
| Status: | Closed |
| Project: | MariaDB MaxScale |
| Component/s: | N/A |
| Affects Version/s: | None |
| Fix Version/s: | N/A |
| Type: | Bug | Priority: | Minor |
| Reporter: | markus makela | Assignee: | Niclas Antti |
| Resolution: | Not a Bug | Votes: | 1 |
| Labels: | None | ||
| Sprint: | MXS-SPRINT-111, MXS-SPRINT-112, MXS-SPRINT-113 |
| Description |
|
When MaxScale attempts to log a message when the disk is full, the logging will be disabled. The way to enable isn't obvious from the error message:
Improving the message with the steps to enable the logging would make the problem easier to solve. A better solution might be to treat a full disk differently and continue writing to it after the next log rotation. |
| Comments |
| Comment by markus makela [ 2020-08-20 ] |
|
I think this bug can be closed as it looks like the problem was present in the older logging implementation and is no longer present in the current one. I must have submitted this based only on the log message without checking the actual version that it was generated with. |