Bug #27858 Failing to log to a log table doesn't log anything to error log.
Submitted: 16 Apr 2007 20:03 Modified: 23 Oct 2007 21:50
Reporter: Tobias Asplund
Status: Closed
Category:Server: Logging Severity:S3 (Non-critical)
Version:5.1.18 OS:Linux
Assigned to: Marc Alff Target Version:

[16 Apr 2007 20:03] Tobias Asplund 
Description:
When the server fails to write to the general log table, it doesn't log any errors.
This happens when the log_output is set to file, but it seems all errors happening when
logging to a table is silenced.

How to repeat:
See http://bugs.mysql.com/27857 for a way to generate an error that will not be logged.

Suggested fix:
Log with a warning to the error log when an entry can't be written.
In this case maybe you just want to write it once, since every query would probably spam
the log to infinity and beyond... but a one-time entry on that we can't enter data to the
log would be nice at least.
[17 Apr 2007 1:18] Sveta Smirnova 
Thank you for the report.

Verified as described.
[2 Aug 2007 0:21] Bugs System 
A patch for this bug has been committed. After review, it may
be pushed to the relevant source trees for release in the next
version. You can access the patch from:

  http://lists.mysql.com/commits/31986

ChangeSet@1.2570, 2007-08-01 16:18:56-06:00, malff@weblab.(none) +3 -0
  Bug#27858 (Failing to log to a log table doesn't log anything to error log)
  
  Before this patch, failures to write to the log tables (mysql.slow_log
  and mysql.general_log) were improperly printed (the time was printed twice),
  or not printed at all.
  
  With this patch, failures to write to the log tables is reported in the
  error log, for all cases of failures.
[6 Oct 2007 3:19] Bugs System 
A patch for this bug has been committed. After review, it may
be pushed to the relevant source trees for release in the next
version. You can access the patch from:

  http://lists.mysql.com/commits/35027

ChangeSet@1.2619, 2007-10-05 19:20:02-06:00, malff@weblab.(none) +3 -0
  Bug#27858 (Failing to log to a log table doesn't log anything to error log)
  
  Before this patch, failures to write to the log tables (mysql.slow_log
  and mysql.general_log) were improperly printed (the time was printed twice),
  or not printed at all.
  
  With this patch, failures to write to the log tables is reported in the
  error log, for all cases of failures.
[12 Oct 2007 1:55] Bugs System 
A patch for this bug has been committed. After review, it may
be pushed to the relevant source trees for release in the next
version. You can access the patch from:

  http://lists.mysql.com/commits/35428

ChangeSet@1.2619, 2007-10-11 17:55:18-06:00, malff@weblab.(none) +3 -0
  Bug#27858 (Failing to log to a log table doesn't log anything to error log)
  
  Before this patch, failures to write to the log tables (mysql.slow_log
  and mysql.general_log) were improperly printed (the time was printed twice),
  or not printed at all.
  
  With this patch, failures to write to the log tables is reported in the
  error log, for all cases of failures.
[19 Oct 2007 20:53] Bugs System 
Pushed into 5.1.23-beta
[23 Oct 2007 21:50] Paul DuBois 
Noted in 5.1.23 changelog.