[debian-mysql] Bug#526632: mysql-proxy doesn't have logging ?

Olivier B. ob.reportbug at daevel.fr
Sat May 2 11:10:51 UTC 2009


Package: mysql-proxy
Version: 0.6.1-5~bpo40+1
Severity: important

Hi,

mysql-proxy sometime crash on my system, so I was searching on logs to try to identify the problem but I don't find anything.
It seems that mysql-proxy doesn't have logging at all.

I don't know if "start-stop-daemon" allow this, but the STDOUT/STDERR of mysql-proxy should maybe redirect to a logging file.

I don't think it matters, but my options are :
    ENABLED="true"
    OPTIONS="--proxy-backend-addresses=87.98.x.x:3306 --proxy-address=/var/run/mysqld/mysqld.sock --proxy-skip-profiling"

Olivier

-- System Information:
Debian Release: 4.0
  APT prefers oldstable
  APT policy: (500, 'oldstable')
Architecture: amd64 (x86_64)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.27.5-dae-core2-ovh
Locale: LANG=fr_FR at euro, LC_CTYPE=fr_FR at euro (charmap=UTF-8) (ignored: LC_ALL set to fr_FR.UTF-8)

Versions of packages mysql-proxy depends on:
ii  libc6                  2.3.6.ds1-13etch9 GNU C Library: Shared libraries
ii  libevent1              1.3e-3~bpo40+1    An asynchronous event notification
ii  libglib2.0-0           2.12.4-2+etch1    The GLib library of C routines
ii  liblua5.1-0            5.1.1-2           Simple, extensible, embeddable pro

mysql-proxy recommends no packages.

-- no debconf information





More information about the pkg-mysql-maint mailing list