Bug #47370 Proxy does not log what port it is listening on or proxying to
Submitted: 16 Sep 2009 12:18 Modified: 17 Aug 2011 14:25
Reporter: Eric Herman Email Updates:
Status: Closed Impact on me:
Category:MySQL Proxy Severity:S3 (Non-critical)
Version:0.8 OS:Any
Assigned to: Kay Roepke CPU Architecture:Any

[16 Sep 2009 12:18] Eric Herman
At "log-level=messge", the proxy logs that it starts, but does not log what port is listens on, nor what back end addresses it is a proxy for.

How to repeat:
start proxy with --log-level=debug notice the information is not in the log.

Suggested fix:
Add Logging of listen port and back-end addresses
[16 Sep 2009 12:32] Eric Herman
patch pushed to: https://code.launchpad.net/~eric-rnd/mysql-proxy/mysql-proxy-fixes/+merge/11873
[16 Sep 2009 13:06] Simon Mudd
Please also add this logging always so that the merlin startup always shows the startup "state" of the proxy. This is useful to ensure that we know if the proxy starts correctly or not and how it is configured.
[14 Jan 2010 11:33] Kay Roepke
committed to mysql proxy trunk:
revno: 952 [merge]
author: Eric Herman <eric@mysql.com>
committer: Kay Roepke <kay@sun.com>
branch nick: trunk
timestamp: Thu 2010-01-14 12:03:21 +0100
  fix for BUG#47370 'Proxy does not log what port it is listening on or proxying to'
[20 Jan 2010 17:37] Enterprise Tools JIRA Robot
Eric Herman writes: 
This should be resolved, however, should more work need to be done on this after I'm gone, perhaps Kay can take a look at it.
[17 Aug 2011 14:25] Jon Stephens
Fixed in 2.3.3.