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
to
true
:
Click the link below to switch examples between Staging and INI methods...
shell>tpm query staging
tungsten@db1:/opt/continuent/software/tungsten-clustering-7.0.3-141 shell>echo The staging USER is `tpm query staging| cut -d: -f1 | cut -d@ -f1`
The staging USER is tungsten shell>echo The staging HOST is `tpm query staging| cut -d: -f1 | cut -d@ -f2`
The staging HOST is db1 shell>echo The staging DIRECTORY is `tpm query staging| cut -d: -f2`
The staging DIRECTORY is /opt/continuent/software/tungsten-clustering-7.0.3-141 shell>ssh {STAGING_USER}@{STAGING_HOST}
shell>cd {STAGING_DIRECTORY}
shell> ./tools/tpm configure alpha \
--connector-disable-connection-warnings=true
Run the tpm command to update the software with the Staging-based configuration:
shell> ./tools/tpm update
For information about making updates when using a Staging-method deployment, please see Section 10.3.7, “Configuration Changes from a Staging Directory”.
shell> vi /etc/tungsten/tungsten.ini
[alpha]
...
connector-disable-connection-warnings=true
Run the tpm command to update the software with the INI-based configuration:
shell>tpm query staging
tungsten@db1:/opt/continuent/software/tungsten-clustering-7.0.3-141 shell>echo The staging DIRECTORY is `tpm query staging| cut -d: -f2`
The staging DIRECTORY is /opt/continuent/software/tungsten-clustering-7.0.3-141 shell>cd {STAGING_DIRECTORY}
shell>./tools/tpm update
For information about making updates when using an INI file, please see Section 10.4.4, “Configuration Changes with an INI file”.
Updating these values require a connector restart (via tpm update) for the changes to be recognized.
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
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: