John, so, I used your testcase on MySQL 5.5.29 and still had the same issue.
As a test, I installed Log4Perl (sudo perl -MCPAN -e'install Log::Log4perl') and the error log now contained all the correct information strings.
To make sure, I uninstall Log4Perl (sudo perl -MCPAN -e 'install App::pmuninstall' ; sudo /usr/local/bin/pm-uninstall Log::Log4perl) and re-checked: all info was gone from the log as per the original description.
So, there is some interaction issue with Log4Perl it seems. Bernt may be able to help?
Can you re-check on your end with uninstall of log4Perl?
John, so, I used your testcase on MySQL 5.5.29 and still had the same issue.
As a test, I installed Log4Perl (sudo perl -MCPAN -e'install Log::Log4perl') and the error log now contained all the correct information strings.
To make sure, I uninstall Log4Perl (sudo perl -MCPAN -e 'install App::pmuninstall' ; sudo /usr/local/ bin/pm- uninstall Log::Log4perl) and re-checked: all info was gone from the log as per the original description.
So, there is some interaction issue with Log4Perl it seems. Bernt may be able to help?
Can you re-check on your end with uninstall of log4Perl?
Ftm, I have already updated the RQG manual with this new [workaround?] requirement: /github. com/RQG/ RQG-Documentati on/wiki/ RandomQueryGene ratorQuickStart #wiki-43_ LogLog4perl_ module_ required_ for_properly_ printing_ things_ for_example_ in_ErrorLogAlar m
https:/