Skip to main content

MySQL 8.0.19 install | MySQL 8.0.91 configure

MySQL 8.0.19 install | MySQL 8.0.91 configure:

Install MySQL 8.0.19 Community edition:

Remove Maria DB packages:
# yum remove mariadb-libs.x86_64*

Install MySQL 8.0.19 rpm packages:

# yum install mysql-community-common-8.0.19-1.el7.x86_64.rpm
# yum install mysql-community-libs-8.0.19-1.el7.x86_64.rpm
# yum install mysql-community-libs-compat-8.0.19-1.el7.x86_64.rpm
# yum install mysql-community-client-8.0.19-1.el7.x86_64.rpm
# yum install mysql-community-embedded-compat-8.0.19-1.el7.x86_64.rpm
# yum install mysql-community-devel-8.0.19-1.el7.x86_64.rpm
# yum install mysql-community-server-8.0.19-1.el7.x86_64.rpm
# yum install mysql-shell-8.0.19-1.el7.x86_64.rpm

At this point mysql daemon is up and running at default location /var/lib/mysql at default port 3306. If you would like to customize location and port and other configuration parameters, make sure to remove directory /var/lib/mysql and kill the existing mysqld process running.

Disable Firewall:

# systemctl stop firewalld
# systemctl disable firewalld

Set SELINUX:

Edit file /etc/sysconfig/selinux and set SELINUX to permissive

#SELINUX=enforcing
SELINUX=permissive

Reboot server:
#reboot

Edit file mysql.service:

Edit file /usr/lib/systemd/system/mysqld.service by including following lines
PIDFile=/mysql/msqa/msqa.pid

# Start main service
#ExecStart=/usr/sbin/mysqld $MYSQLD_OPTS
ExecStart=/usr/sbin/mysqld --defaults-file=/etc/my.cnf --daemonize --pid-file=/mysql/msqa.pid $MYSQLD_OPTS

Edit file /etc/my.cnf:

Edit file /etc/my.cnf and include following parameters

datadir=/mysql/<project_name>
socket=/mysql/<project_name>/<project_name>.sock
port=9987
server-id=9987
log-error=/mysql/<project_name>/<project_name>_error.log
default_authentication_plugin=mysql_native_password

Initialize mysqld:

#systemctl daemon-reload
#systemctl start mysqld

You should be able to see following process which has started mysql damon

/usr/sbin/mysqld --defaults-file=/etc/my.cnf --daemonize --pid-file=/mysql/<project_name>/<project_name>.pid

Connect mysql daemon and reset root password:

Sudo to user mysql if you are logged in using your AD ID
$ sudo su – mysql
Get temporary root user password from mysql error log file - /mysql/<project_name>/<project_name>_error.log
S mysql –uroot –p –S/mysql/<project_name>/<project_name>.sock
mysql > alter user `root`@`localhost` identified by `<your_ password>`;











 
Labels:
Location: San Francisco, CA, USA

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

MySQL slave Error_code: 1032 | MySQL slave drift | HA_ERR_KEY_NOT_FOUND

MySQL slave Error_code: 1032 | MySQL slave drift: With several MySQL, instance with master slave replication, I have one analytics MySQL, environment which is larger in terabytes, compared to other MySQL instances in the environment. Other MySQL instances with terabytes of data are running fine master, slave replication. But this analytics environment get started generating slave Error_code :1032. mysql> show slave status; Near relay log: Error_code: 1032; Can't find record in '<table_name>', Error_code: 1032; handler error HA_ERR_KEY_NOT_FOUND; the event's master log <name>-bin.000047, end_log_pos 5255306 Near master section: Could not execute Update_rows event on table <db_name>.<table_name>; Can't find record in '<table_name>', Error_code: 1032; Can't find record in '<table_name>', Error_code: 1032; handler error HA_ERR_KEY_NOT_FOUND; the event's master log <name>-bin.000047, end_l...
2 comments
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