This section shows the location of the log and configuration files associated with the various components that make up the MySQL Enterprise Service Manager. These files can prove useful for debugging purposes.

All log files except catalina.out are rotated to ensure they do not grow beyond 10MB in size.

All of these logs are viewable within MySQL Enterprise Dashboard. For more information, see Section 5.6, “Logs”.

On all operating systems, the Apache/Tomcat, and Repository directories contain both access and error files.

These log files are called bitrock_installer.log.

On Windows these files are stored in the temporary directory defined by the variable %TEMP%. To determine the value of %TEMP% on your system, type echo %TEMP% at the command line. Alternately, you may open the Run command window, enter %TEMP% and press OK. To find this file on Unix and Mac OS X check the value of the environment variable, $TMPDIR. If this variable is not defined, look in the /tmp directory.

If the file bitrock_installer.log already exists, a file called bitrock_installer_xxxx.log (where xxxx stands for an arbitrary series of numerals) will be created.

To determine if an installation file belongs to the Monitor Agent or the Service Manager you must open the file in a text editor.

The locations of the agent log files are as follows:

On any platform, the location of the agent log file may be changed. You may also change the name of the log file. To confirm the location and the name, check the settings in the mysql-monitor-agent.ini file.

The maximum size of a log file may be limited to 2GB. If MySQL Enterprise Monitor Agent is unable to add information to the configured logfile, then information will instead be sent to the standard output.

Because the size of the log files can become quite large, you can use a tool such as logrotate (Unix/Linux) or logadm (Solaris) to automatically rotate the logs. For example, a sample logrotate definition is shown below:

/opt/mysql/enterprise/agent/mysql-monitor-agent.log {
    rotate 5
    daily
    minsize 1G
    postrotate
        /usr/bin/killall -HUP mysql-monitor-agent
    endscript
}

The above will rotate the log before it reaches 1GB in size, keeping up to 5 files at a time.

If you want to use your own system, you can copy the log file, flush the contents, and then send the SIGHUP signal to the agent process. On Windows, you need to shutdown, copy the log, and restart the agent.

The locations of the agent pid files are as follows:

On any platform, the location of the agent log file may be changed. You may also change the name of the log file. To confirm the location and the name, check the settings in the mysql-monitor-agent.ini file.

A MIB file is a requirement for using SNMP traps. A table showing the location of this file follows.

The repository user name and password are stored in in the config.properties file. A table showing the location of this file follows:

You should make sure that the file is secured at the file system level so that it cannot be read by anybody but the administrator or Enterprise monitor.