Bug #78555 Make [logger] section optional
Submitted: 25 Sep 2015 9:07 Modified: 1 Oct 2015 17:27
Reporter: Geert Vanderkelen Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Router Configuration Severity:S3 (Non-critical)
Version:2.0.2 OS:Any
Assigned to: CPU Architecture:Any

[25 Sep 2015 9:07] Geert Vanderkelen 
Description:
We should make the [logger] optional and add it when missing.

How to repeat:
Remove the section from the configuration file:

[logger]

It says it missing logger.

Suggested fix:
Add the logger section when it is missing in Config::do_read_stream
[30 Sep 2015 20:32] Geert Vanderkelen 
Posted by developer:
 
commit 14104fc27a989e9d05983401549d9436718dc344
Author: Geert Vanderkelen <geert.vanderkelen@oracle.com>
Date:   Tue Sep 29 15:21:05 2015 +0200

    BUG21899753 Make [logger] section optional
    
    We make the [logger] section optional by adding it to the
    configuration when it is missing. We also add the possibility
    to define the log level. Default log level is INFO, which means
    that debugging messages will not be logged.
    
    Example:
    
      [logger]
      level = DEBUG
    
    Valid values for the level option are FATAL, ERROR, WARNING, INFO,
    or DEBUG (levels are case insensitive).
[1 Oct 2015 17:27] Philip Olson 
Posted by developer:
 
Fixed as of the upcoming MySQL Router 2.0.2 release, and here's the changelog entry:

Logger levels were added: FATAL, ERROR, WARNING, DEBUG, and INFO. The
default value is INFO. 

Also, adding [logger] to the configuration file is now optional. INFO 
is the default behavior.

Thank you for the bug report.

Also, the configuration documentation was updated to include this information.