Bug #19987 Porblem with logging on Windows

• Submitted: 21 May 2006 17:31
• Modified: 4 Dec 2007 21:47
• Reporter: Peter Laursen (Basic Quality Contributor)
• Status: Can't repeat
• Category: MySQL Server
• Severity: S3 (Non-critical)
• Version: 5.1.9
• OS: Windows (WinXP)
• Assigned to: Konstantin Osipov
• CPU Architecture: Any

[21 May 2006 17:31] Peter Laursen

Description:
Referring to:
http://dev.mysql.com/doc/refman/5.1/en/log-tables.html

I think this should be valid in a my.ini -file: 

#enable logging to file only
log-output=FILE
#set general log path
log = d:\mysqldb51\mylog.log
#set slow log path
log-slow-queries = d:\mysqldb51\myslowlog.log
#Log queries that are executed without benefit of any index.
log-queries-not-using-indexes
#Log some not critical warnings to the log file.
log-warnings

.. however whenever using 'log-output= ...' the server won't start.
When omitting the 'log-output' line server start OK, but no logs!
(and that is in accordance to the docs!)

On 5.0.x this works:

#set general log path
log = d:\mysqldb50\mylog.log
#set slow log path
log-slow-queries = d:\mysqldb50\myslowlog.log
#Log queries that are executed without benefit of any index.
log-queries-not-using-indexes
#Log some not critical warnings to the log file.
log-warnings

How to repeat:
try start server 5.1.9 with any variation of 'log-output'.
You can't.

Did I misunderstand ???

Suggested fix:
no idea ...

[21 May 2006 18:16] Peter Laursen

And it is the same with all 4 server binaries in the distribution for Windows.

[22 May 2006 9:21] Valeriy Kravchuk

Looks like a duplicate of bug #17368. Will be fixed in 5.1.10.

[22 May 2006 10:00] Peter Laursen

Are you sure that this is a dublicate and the fix also solves this?  The other issue only discusses logging to a TABLE.  And the fix was to enable the CSV storage engine with Windows ...

I am trying to log to a FILE (just as before 5.1), and that does not work either ... ?

[22 May 2006 12:47] Valeriy Kravchuk

Sorry, my fault. 5.1.9 on Windows does not recognise --log-output option. It is a (verified) bug. I do not know, will is it fixed in 5.0.10 (nothing about that at http://dev.mysql.com/doc/refman/5.1/en/news-5-1-10.html). But this option is surely recognised by 5.0.11 on Linux.

[17 Oct 2006 21:57] Eddie Schwalb

This is because you are not using '\\' and the server does not report the 'syntax error' upon restart.

Aparently, log='c:\query_log.txt' does work.  Maybe this is because there is a different code base for parsing the query log path... this one should probably be cleaned up.

One possible improvement will be to bubble up the expection to present a meaningful error on exit.

Eddie

[29 Sep 2007 18:57] Peter Laursen

Sorry .. I overlooked that this has been replied to!

From when has it become necessary to use escaping in file paths in my.ini?

[29 Sep 2007 19:10] Peter Laursen

I think we can close this now??

this

#enable logging to file only
log-output=FILE
#set general log path
log = c:\mylog.log
#set slow log path
log-slow-queries = c:\myslowlog.log
#Log queries that are executed without benefit of any index.
log-queries-not-using-indexes
#Log some not critical warnings to the log file.
log-warnings

and this

#enable logging to file only
log-output=FILE
#set general log path
log = mylog.log
#set slow log path
log-slow-queries = myslowlog.log
#Log queries that are executed without benefit of any index.
log-queries-not-using-indexes
#Log some not critical warnings to the log file.
log-warnings

... both work as expected on 5.1.22