** Description changed: + [Impact] + + Bugs reported on mysql in Precise are very difficult to triage, because + apport doesn't submit logs and reporters don't even have them available. + Thus this impacts all mysql bugs in Precise, not just this one. + [Test Case] 1. install mysql-server 2. make sure it is running (service mysql start) 3. mysql -uroot -e "SHOW VARIABLES LIKE 'log_error'" -p - a broken mysql-server will show a blank answer - fixed package will show '/var/log/mysql/error.log' 4. Check that /var/log/mysql/error.log exists and is non-empty. [Regression Potential] Very low, as its just a config file change. People may not have been expecting this file to be written though. ------------ The errors for mysqld in 5.1 packages used to be written to /var/log/mysql/error.log, but that change was dropped from my.cnf in the transition to 5.5. This should be restored so the logs can be written properly.
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1014732 Title: log_error not set in my.cnf, errors not written anywhere To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-5.5/+bug/1014732/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
