Details
Description
The fix for MXS-5196 lead to maxctrl create record breaking when using syslog, e.g. with default installation on Ubuntu 22.04.
Prior to the MXS-5196 change lacking permissions would just lead to one section of the generated report being empty, now it prevents the whole report from being written:
$ maxctrl create report
|
Error: Server at http://127.0.0.1:8989 responded with 500 Internal Server Error to `GET maxscale/logs/data?page[size]=1000`
|
{
|
"errors": [
|
{
|
"detail": "Failed to read any data from the systemd journal. Make sure that the user that MaxScale is running as has the required permissions to read the log data. On most systems, this means that the 'maxscale' user must be a part of the 'systemd-journal' or 'wheel' groups. Alternatively, switch the log source to 'maxlog' by configuring 'maxlog=true' and 'syslog=false' under the '[maxscale]' section."
|
}
|
]
|
}
|
The report should just leave the log specific section empty as before when not being able to access this information, and at best also print a warning to stderr, but not completely fail.
Attachments
Issue Links
- is caused by
-
MXS-5196 /maxscale/logs/data may return no data if maxlog=0 and syslog=1
-
- Closed
-