[MXS-64] maxkeys and Maxpasswd do not produce informative error output Created: 2015-03-27 Updated: 2015-06-17 Resolved: 2015-04-30 |
|
| Status: | Closed |
| Project: | MariaDB MaxScale |
| Component/s: | Core |
| Affects Version/s: | 1.1.0 |
| Fix Version/s: | 1.1.1 |
| Type: | Bug | Priority: | Minor |
| Reporter: | markus makela | Assignee: | markus makela |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Issue Links: |
|
||||||||
| Description |
|
maxkeys and maxpasswd log to /tmp using the log manager but only produce a single error when used from the command line. Example output: This is produced when the secrets file is missing and on all other errors. |
| Comments |
| Comment by markus makela [ 2015-04-24 ] |
|
This needs an addition to log manager to print certain logs to stdout instead of file. This will allow utility tools to use the MaxScale internals while still printing to stdout/stderr. |
| Comment by markus makela [ 2015-04-30 ] |
|
Log manager now supports stdout as the output file. This needs to be configured at the code level. |
| Comment by Timofey Turenko [ 2015-05-06 ] |
|
closing this,m but other maxkeys and maxpasswrd issues are tracked in https://mariadb.atlassian.net/browse/MXS-125 |
| Comment by Timofey Turenko [ 2015-05-12 ] |
|
verified by manual running of maxkeys and maxpasswrd and checking output antdlogs |