ESTADOS DE MADUREZ SEXUAL

The MySQL Enterprise Monitor Agent can be started and stopped at any time. When not running, information about the current status of your server is not available, and MySQL Enterprise Service Manager provides a warning if an agent and the MySQL server that it monitors is unavailable.

Starting/Stopping the Agent on Windows

Warning

If you are using Query Analyzer, turning off the agent prevents your applications from communicating with the MySQL server. See Section 13.2, “The Query Analyzer”.

5.7.1 Starting/Stopping the Agent on Windows

You have the option of starting the Monitor Agent from the final installation screen. Otherwise you can do this by going to the Start Menu and under Programs find MySQL and then the MySQL Enterprise Monitor Agent entry. Simply select the Start MySQL Enterprise Monitor Agent option.

Note

On Windows Vista or later, starting the agent requires administrative privileges —you must be logged in as an administrator. To start or stop the agent right- click the menu item and choose the Run as Administrator menu option. The same restriction applies to starting the agent from the command line. To open an administrator cmd window right-click the cmd icon and choose the Run as Administrator menu option.

Warning

To report its findings, the agent needs to be able to connect to the Monitor UI through the port specified during installation. The default value for this port is

18443; ensure that this port is not blocked. If you need help troubleshooting the agent installation see, Section 5.12, “Troubleshooting the Agent”.

Alternately, you can start the agent from the command line by entering:

shell> sc start MySQLEnterpriseMonitorAgent

or:

shell> net start MySQLEnterpriseMonitorAgent

You can also start the agent by issuing the command, agentctl.bat start. Stop the agent by passing the argument, stop. This batch file is found in the Agent directory.

For confirmation that the service is running you can open the Microsoft Management Console Services window. To do this go to the Control Panel, find Administrative Tools and click the link to

Services. Locate the service named MySQL Enterprise Monitor Agent and look under the

Status column.

You can also start the agent from this window rather than from the Start menu or the command line. Simply right-click MySQL Enterprise Monitor Agent and choose Start from the pop-up menu. Starting the agent from this window opens an error dialog box if the agent cannot connect to the MySQL server it is monitoring. No error is displayed if the agent is unable to connect to the MySQL Enterprise Service Manager.

The pop-up menu for starting the agent also offers the option of stopping the agent. To stop the agent from the command line you only need type:

shell> sc stop MySQLEnterpriseMonitorAgent

Starting/Stopping the Agent on Mac OS X

shell> net stop MySQLEnterpriseMonitorAgent

Note

MySQLEnterpriseMonitorAgent is the default name of the Monitor Agent service.

5.7.2 Starting/Stopping the Agent on Mac OS X

Using launchd

The preferred method is to use launchd to load the Agent as a service. After selecting "Install as a service" during the installation process, you may load or unload the Agent service using the following commands.

To start (load) the Agent:

shell> sudo launchctl load /Library/LaunchDaemons/mysql.agent.plist

To stop (unload) the Agent:

shell> sudo launchctl unload /Library/LaunchDaemons/mysql.agent.plist

Using init

Alternatively, an init.d script to start the Agent on Mac OS X is located in the /Applications/ mysql/enterprise/agent/etc/init.d directory. To start the Agent navigate to this directory and at the command line type:

shell> ./mysql-monitor-agent start

To stop the Agent, use the stop command:

shell> ./mysql-monitor-agent stop

If the agent cannot be stopped because the pid file that contains the agent's process ID cannot be found, you can use kill to send a TERM signal to the running process:

shell> kill -TERM PID

If you run more than one agent on a specific machine, you must also specify the path to the ini file when you stop the agent. Executing mysql-monitor-agent stop without an ini file only stops the agent associated with the default ini file.

To verify that the agent is running, use the following command:

shell> ./mysql-monitor-agent status

The resulting message indicates whether the agent is running. If the agent is not running, use the following command to view the last ten entries in the general Agent log file:

shell> tail /Applications/mysql/enterprise/agent/logs/mysql-monitor-agent.log

For further information on troubleshooting the agent, see Section 5.12, “Troubleshooting the Agent”. Installation creates the directory /Applications/mysql/enterprise/agent, and the logs

Starting/Stopping the Agent on Unix

To see all the command-line options available when running the monitor agent, navigate to the

/Applications/mysql/enterprise/agent/etc/init.d directory and execute mysql- monitor-agenthelp, which displays the usage message:

Usage: ./mysql-monitor-agent {start|stop|restart|status}

Warning

To report its findings, the agent connects to the Monitor UI through the port specified during installation. The default value for this port is 18443; ensure that this port is not blocked. To troubleshoot the agent installation, see Section 5.12, “Troubleshooting the Agent”.

5.7.3 Starting/Stopping the Agent on Unix

When installation is finished, you can start the monitor agent from the command line by typing:

shell> /opt/mysql/enterprise/agent/etc/init.d/mysql-monitor-agent start

For a non-root installation the command would be:

shell> /home/<user name>/mysql/enterprise/agent/etc/init.d/mysql-monitor-agent start

To stop the agent, use the stop command:

shell> ./mysql-monitor-agent stop

If the agent cannot be stopped because the pid file that contains the agent's process ID cannot be found, you can use kill to send a TERM signal to the running process:

shell> kill -TERM PID

To verify that the agent is running, use the following command:

shell> ./mysql-monitor-agent status

The resulting message indicates whether the agent is running. If the agent is not running, use the following command to view the last ten entries in the general Agent log file:

shell> tail /opt/mysql/enterprise/agent/logs/mysql-monitor-agent.log

For further information on troubleshooting the agent, see Section 5.12, “Troubleshooting the Agent”. Installation creates the directory /opt/mysql/enterprise/agent, with the logs directory is located immediately below the agent directory.

To see all the command-line options available when running the monitor agent, navigate to the /opt/ mysql/enterprise/agent/etc/init.d directory and execute mysql-monitor-agenthelp, which displays the usage message:

Usage: ./mysql-monitor-agent {start|stop|restart|status}

Warning

To report its findings, the agent connects to the Monitor UI through the port specified during installation. The default value for this port is 18443; ensure that this port is not blocked. To troubleshoot the agent installation, see Section 5.12, “Troubleshooting the Agent”.

sql_mode

5.7.4 sql_mode

On startup, the agent sets

sql_mode=STRICT_TRANS_TABLES,NO_ENGINE_SUBSTITUTION,NO_AUTO_CREATE_USER

on the monitored MySQL instance. If sql_mode=ONLY_FULL_GROUP_BY, agent queries can fail. The local agent of the MySQL Enterprise Service Manager also sets

sql_mode=STRICT_TRANS_TABLES,NO_ENGINE_SUBSTITUTION on the repository.