[Bug 1014732] [NEW] log_error not set in my.cnf, errors not written anywhere
Launchpad Bug Tracker
1014732 at bugs.launchpad.net
Fri Oct 26 15:55:41 UTC 2012
You have been subscribed to a public bug by Robie Basak (racb):
[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.
** Affects: mysql-5.5 (Ubuntu)
Importance: High
Assignee: Clint Byrum (clint-fewbar)
Status: Fix Released
** Affects: mysql-5.5 (Ubuntu Precise)
Importance: High
Status: Triaged
--
log_error not set in my.cnf, errors not written anywhere
https://bugs.launchpad.net/bugs/1014732
You received this bug notification because you are a member of Ubuntu Sponsors Team, which is subscribed to the bug report.
More information about the Ubuntu-sponsors
mailing list