Skip to main content
Tungsten Clustering

Connector Logging Configuration

The connector is able to modify what is logged using different configuration options.

Informational messages like those below indicate that a client-side session did not properly close connection to the connector using a regular mysql close() call.

WARN [MySQLBridge] - [10.3.1.240:35686] C>S ended. S>C streaming did not finish within
                                      bridgeServerToClientForcedCloseTimeout=500 (ms). 
                                      Will be closed anyway !

INFO [MySQLBridge] - [10.3.1.240:35686] Server>Client thread didn't finish cleanly - »
                                      return code was: 1

Load balancers (especially physical ones) tend to do this when testing the connector, so these messages are expected when behind a load-balancer. Since the same error could come from buggy application code, the default is to log these circumstances.

If you know where the disconnects are coming from, you can safely disable this feature by setting the tpm option connector-disable-connection-warnings=true

important

Updating these values require a connector restart (via tpm update), if enabled after installation, for the changes to be recognized.

Connector Logging to Syslog​

The Connector is able to send log information to Syslog.

You can control the full connector log by editing the tungsten-connector/conf/wrapper.conf file.

Depending on what you want to do, you can:

  • Send full connector log to the syslog:

    wrapper.syslog.loglevel=NONE => 
    wrapper.syslog.loglevel=INFO

  • Stop sending log to connector.log:

    wrapper.logfile.loglevel=INFO => 
    wrapper.logfile.loglevel=NONE

  • Change the log file path:

    wrapper.logfile=../../tungsten-connector/log/connector.log
note

For logging purposes, our software uses both the Tanuki wrapper and Apache's Log4J tool.

Valid log levels for the Tanuki wrapper include:

  • NONE for no output
  • FATAL to only show fatal error messages
  • ERROR to show all error messages
  • WARN to show all warning messages
  • STATUS to show all state changes
  • INFO shows all JVM output and informative messages
  • DEBUG shows detailed debug information

Valid log levels for Apache's log4j include: TRACE, DEBUG, INFO, WARN, ERROR and FATAL

Links to the full documentation for each are below: