Skip to main content

Install MySQL Enterprise Monitor (MEM ) agent in unattended mode

Install MySQL agent unattended mode / non-interactive mode:

01. Get file mysqlmonitoragent-8.0.3.8197-linux-x86-64bit-installer.bin from Oracle e-delivery.
02. Copy file mysqlmonitoragent-8.0.3.8197-linux-x86-64bit-installer.bin to /tmp/ of the target server where agent need to install.
03. Create options file - options.txt and include following parameters.
debuglevel=4
installer-language=en
debugtrace=/mysql/MEM803/agent/install.debugtrace.monitor.log
mode=unattended
# User defined installation location of agent
installdir=/mysql/MEM803/agent/
# Following is the server where MySQL Service Manager is running
managerhost=<MEM Server>
managerport=<Port No. of MEM server>
# Following is the user created on MEM and not in MySQL database
agentuser=msqlagent
agentpassword=<code>
# database type of installation will monitor server and database
agent_installtype=database
# Mysql user of the server where agent is installed
mysqluser=root
mysqlpassword=<code>
# Mysql server where agent is up and running
mysqlhost=<Server Name agent where installed >
# Mysql database port on which agent is up and running
mysqlport=<MySQL DB port>
04. You can install agent as a root or mysql user.
05. Execute following command to install agent
$./mysqlmonitoragent-8.0.3.8197-linux-x86-64bit-installer.bin --optionfile /mysql/MEM803/agent/options.txt
06. Start agent using following command
/mysql/MEM803/agent/etc/init.d/mysql-monitor-agent start
07. Check agent status using following command
/mysql/MEM803/agent/etc/init.d/mysql-monitor-agent status
08. To troubleshoot MySQL agent installation, check log files in log directory.
09. To change configuration after installation edit /mysql/MEM803/agent/etc/bootstrap.properties
#Agent configuration updated
#Fri Nov 09 16:01:09 PST 2018
agent-item-files=etc/custom.xml
agent-mgmt-username=mysqlagent
agent-mgmt-hostname=https\://<MEM Server>\:<Port No.>
agent-mgmt-password=<Encrypted password>

Ref.: https://dev.mysql.com/doc/mysql-monitor/8.0/en/mem-unattended-installation-cmdline-options-agent.html

Labels

Labels:

Comments

Post a Comment

Popular posts from this blog

MySQL InnoDB cluster troubleshooting | commands

Cluster Validation: select * from performance_schema.replication_group_members; All members should be online. select instance_name, mysql_server_uuid, addresses from  mysql_innodb_cluster_metadata.instances; All instances should return same value for mysql_server_uuid SELECT @@GTID_EXECUTED; All nodes should return same value Frequently use commands: mysql> SET SQL_LOG_BIN = 0;  mysql> stop group_replication; mysql> set global super_read_only=0; mysql> drop database mysql_innodb_cluster_metadata; mysql> RESET MASTER; mysql> RESET SLAVE ALL; JS > var cluster = dba.getCluster() JS > var cluster = dba.getCluster("<Cluster_name>") JS > var cluster = dba.createCluster('name') JS > cluster.removeInstance('root@<IP_Address>:<Port_No>',{force: true}) JS > cluster.addInstance('root@<IP add>,:<port>') JS > cluster.addInstance('root@ <IP add>,:<port> ') JS > dba.getC...
Post a Comment
Read more

InnoDB cluster Remove Instance Force | Add InnoDB instance

InnoDB cluster environment UUID is different on node: To fix it stop group replication, remove instance (use force if require), add instance back Identify the node which is not in sync: Execute following SQL statement on each node and identify the node has different UUID on all nodes. mysql> select * from mysql_innodb_cluster_metadata.instances; Stop group replication: Stop group replication on the node which does not have same UUID on all nodes. mysql > stop GROUP_REPLICATION; Remove instances from cluster: Remove all secondary node from the cluster and add them back if require. $mysqlsh JS >\c root@<IP_Address>:<Port_No> JS > dba.getCluster().status() JS > dba.getCluster () <Cluster:cluster_name> JS > var cluster = dba.getCluster("cluster_name"); JS >  cluster.removeInstance('root@<IP_Address>:<Port_No>'); If you get "Cluster.removeInstance: Timeout reached waiting......" JS > cluster.removeInstance(...
2 comments
Read more

Oracle E-Business Suite Online Patch Phases executing adop

Following description about Oracle E-Business Suite is high level and from documentation https://docs.oracle.com/cd/E26401_01/doc.122/e22954/T202991T531062.htm#5281339 for in depth and detail description refer it. The online patching cycle phases: Prepare Apply Finalize Cutover Cleanup Prepare phase: Start a new online patching cycle, Prepares the environment for patching. $ adop phase=prepare Apply phase: Applies the specified patches to the environment. Apply one or more patches to the patch edition. $ adop phase=apply patches=123456,789101 workers=8 Finalize phase: Performs any final steps required to make the system ready for cutover. Perform the final patching operations that can be executed while the application is still online. $ adop phase=finalize Cutover phase: Shuts down application tier services, makes the patch edition the new run edition, and then restarts application tier services. This is the only phase that involves a brief ...
Post a Comment
Read more