| Bug #65592 | Mysqld --console don't show anythings | ||
|---|---|---|---|
| Submitted: | 12 Jun 2012 14:53 | Modified: | 9 Jan 2013 0:07 |
| Reporter: | MASSIMO PETRINI | Email Updates: | |
| Status: | Closed | Impact on me: | |
| Category: | MySQL Server: Windows | Severity: | S3 (Non-critical) |
| Version: | 5.5.25 | OS: | Windows (2008r2, XP) |
| Assigned to: | CPU Architecture: | Any | |
| Tags: | --console | ||
[12 Jun 2012 14:53]
MASSIMO PETRINI
[12 Jun 2012 15:33]
MySQL Verification Team
if you comment out the "log-error" option from your my.ini it should write to the console when given --console option.
[12 Jun 2012 15:37]
Peter Laursen
With MySQL 5.5.23 and Windows 7 I do not see the problem: C:\Program Files\MySQL\MySQL Server 5.5\bin>mysqld --console 120612 17:34:28 [Note] Plugin 'FEDERATED' is disabled. 120612 17:34:28 InnoDB: The InnoDB memory heap is disabled 120612 17:34:28 InnoDB: Mutexes and rw_locks use Windows interlocked functions 120612 17:34:28 InnoDB: Compressed tables use zlib 1.2.3 120612 17:34:28 InnoDB: Initializing buffer pool, size = 106.0M 120612 17:34:28 InnoDB: Completed initialization of buffer pool 120612 17:34:28 InnoDB: highest supported file format is Barracuda. 120612 17:34:29 InnoDB: Waiting for the background threads to start 120612 17:34:30 InnoDB: 1.1.8 started; log sequence number 146248115 120612 17:34:30 [Note] Event Scheduler: Loaded 0 events 120612 17:34:30 [Note] mysqld: ready for connections. Version: '5.5.23' socket: '' port: 3307 MySQL Community Server (GPL) Peter (not a MySQL person)
[12 Jun 2012 15:38]
Peter Laursen
(and I do not have an explicit --log-error option).
[12 Jun 2012 16:10]
MASSIMO PETRINI
Yes it is true (in my.ini there log-error); if i omit this line, the output is visible; but in previous version, like 5.5.19, the output was visible anyway
[12 Jun 2012 18:59]
MySQL Verification Team
Some tests: mysqld --no-defaults --log-error=go.txt --console 5.1.63: output is seen on console. 5.1.46: output is seen on console. 5.5.25: no output on console 5.5.3 : no output on console 5.5.2 : output is seen on console. 5.0.96: output is seen on console. So the behavior changed since 5.5.3, I'm not sure why. Maybe re-factoring of the code when utf32/utf16 went in?
[13 Jun 2012 3:07]
MySQL Verification Team
I couldn't repeat with current source server: d:\dbs\5.5>bin\mysqld --console 120613 0:06:03 [Note] Plugin 'FEDERATED' is disabled. 120613 0:06:03 InnoDB: !!!!!!!! UNIV_DEBUG switched on !!!!!!!!! 120613 0:06:03 InnoDB: The InnoDB memory heap is disabled 120613 0:06:03 InnoDB: Mutexes and rw_locks use Windows interlocked functions 120613 0:06:03 InnoDB: Compressed tables use zlib 1.2.3 120613 0:06:03 InnoDB: Initializing buffer pool, size = 128.0M 120613 0:06:03 InnoDB: Completed initialization of buffer pool 120613 0:06:03 InnoDB: highest supported file format is Barracuda. 120613 0:06:04 InnoDB: Waiting for the background threads to start 120613 0:06:05 InnoDB: 1.1.8 started; log sequence number 70878338 120613 0:06:05 [Note] Server hostname (bind-address): '0.0.0.0'; port: 3306 120613 0:06:05 [Note] - '0.0.0.0' resolves to '0.0.0.0'; 120613 0:06:05 [Note] Server socket created on IP: '0.0.0.0'. 120613 0:06:05 [Note] Event Scheduler: Loaded 0 events 120613 0:06:05 [Note] bin\mysqld: ready for connections. Version: '5.5.26-debug' socket: '' port: 3306 Source distribution
[13 Jun 2012 3:11]
MySQL Verification Team
If you run the command prompt window as Administrator what happens?. Thanks.
[13 Jun 2012 5:19]
MASSIMO PETRINI
It is the same;no result
[13 Jun 2012 8:21]
Valeriy Kravchuk
Verified on Windows XP also. These options are essential to demonstrate the problem independently of any existing my.ini settings: --no-defaults --log-error=go.txt --console
[21 Jun 2012 23:00]
Omer Barnir
On windows platforms, mysqld starts by default as a service (no screen outputs). you need to add the --standalone option to get the above to work. See http://dev.mysql.com/doc/refman/4.1/en/server-options.html#option_mysqld_standalone
[9 Jan 2013 0:07]
Philip Olson
Fixed as of MySQL Server 5.7.0, and here's the changelog entry: Passing in both "--console" and "--log-error" would write to the log file but not the console, as of MySQL Server 5.5.3. Previous behavior was restored, so it now only outputs to the console. Thank you for the bug report. Also, the documentation has been updated.
[16 Apr 2013 17:41]
Paul DuBois
Revised changelog entry: On Windows, starting the server with --log-error and --console caused the server to write to the log file but not the console. Before MySQL 5.5.3, this occurred only if --log-error was specified after --console. Now, --console overrides --log-error no matter the option order so that --console produces console output in all cases.
