[Bug 1014732] Re: log_error not set in my.cnf, errors not written anywhere

[Robie Basak]

Rebased on the security update 12.04.2 in precise-proposed. I've test
built this also, and reverified that mysql still appears to work, that
the new log file is created, rotates correctly, and checked that the
apport hook submits it.

** Patch added: "mysql-rebased.debdiff"
   https://bugs.launchpad.net/ubuntu/+source/mysql-5.5/+bug/1014732/+attachment/3419869/+files/mysql-rebased.debdiff

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1014732

Title:
  log_error not set in my.cnf, errors not written anywhere

Status in “mysql-5.5” package in Ubuntu:
  Fix Released
Status in “mysql-5.5” source package in Precise:
  Triaged

Bug description:
  [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.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mysql-5.5/+bug/1014732/+subscriptions