How to install phpmyadmin for mysql 8 in Centos 7

To install mysql 8 on centos 7, please follow here.

Install epel-release

# yum install -y epel-release

Install phpmyadmin, httpd and php

# yum install -y phpmyadmin httpd php 

Change the ip allowed to access phpmyadmin by changing 127.0.0.1 to your network's ip (in my case, I want to allow all machine with 192.168.0 ip to be able to access the phpmyadmin page)

# sed -i 's/127.0.0.1/192.168.0/g'  /etc/httpd/phpMyAdmin.conf

Start httpd

# systemctl start httpd

Allow http on firewall

# firewall-cmd --add-service http

# firewall-cmd --add-service http --permanent

Change your mysql user's password to use mysql_native_password

# mysql -u root -p

mysql> ALTER USER 'root'@'localhost' IDENTIFIED WITH mysql_native_password BY 'MyNewPassword!123';

You should be able to access phpmyadmin, by pointing your browser to the server's ip address, followed by /phpmyadmin

And the you can login into phpmyadmin by supplying mysql username and password

How to install mysql 8 in Centos 7

Install mysql yum repo

# yum install -y https://dev.mysql.com/get/mysql80-community-release-el7-3.noarch.rpm

Install mysql-community-server

# yum install -y mysql-community-server

Start mysql server

# systemctl start mysqld

Get the default mysql root password from mysqld.log

# grep 'temporary password' /var/log/mysqld.log

Login to the mysql console, and change the root password

# mysql -u root -p

mysql> ALTER USER 'root'@'localhost' IDENTIFIED BY 'MyNewP@ssword!123';

mysql> exit

If you are using centos internal firewall, allow access to mysql port

# firewall-cmd --add-service mysql

# firewall-cmd --add-service mysql --permanent

Reference: https://dev.mysql.com/doc/mysql-yum-repo-quick-guide/en/

Create a mini lab for practicing ansible using docker

To practice ansible, you need to have at least 2 machines. I suggest using containers rather than VM, since containers can be quickly spawned, and are light on the resources.

First, make sure you have docker Community Edition installed. If not, follow the install guide here.

Check your docker version

# docker version

Start the docker engine

# sudo systemctl start docker 

In this exercise, we will use ubuntu as our base operating system. So, run a container using the ubuntu image from docker hub. The options are -i for interactive, -t to allocate pseudo TTY and -d to run the container in the background

# docker run -it -d --name="ansible-master" ubuntu

The ubuntu image does not come with ssh, which is needed for ansible, so we need to install that, together with vim text editor 

# docker exec -it apt update; apt install vim openssh-server -y

Change the root password

# docker exec -it ansible-master passwd 

Permit root login for ssh

# docker exec -it ansible-master /bin/bash

ansible-master: # cat >> /etc/ssh/sshd_config <<EOF

PermitRootLogin yes

EOF

Start ssh

ansible-master: # service ssh start; exit

Create an image based on ansible-master. This image will be used later to create ansible-client1 container

# docker commit -m "ubuntu with vim and openssh-server" ansible-master myubuntu:2019041001

Run a container called ansible-client1 from the image created above

# docker image ls

REPOSITORY          TAG                 IMAGE ID            CREATED             SIZE

myubuntu            2019041001          17f43a3ef384        10 minutes ago      265MB

# docker run -d -it --name="ansible-client1" myubuntu:2019041001

Start ssh service on ansible-client1

# docker exec -it ansible-client1 service ssh start

Try to ssh into both machines. Get the ip address of the containers using "docker inspect" command

# docker inspect ansible-client1 | grep -w IPAddress

            "IPAddress": "172.17.0.3",

                    "IPAddress": "172.17.0.3",

# docker inspect ansible-master | grep -w IPAddress

            "IPAddress": "172.17.0.2",

                    "IPAddress": "172.17.0.2",

# ssh root@172.17.0.2

# ssh root@172.17.0.3

Install ansible on ansible-master

# docker exec -it ansible-master apt install ansible -y

Check ansible version

# docker exec -it ansible --version

Create ssh-key without password

# docker exec -it ssh-keygen

Transfer the key to ansible-client1

# docker exec -it ssh-copy-id 172.17.0.3

Edit /etc/ansible/hosts to include all nodes

# docker exec -it ansible-master /bin/bash

ansible-master: # cat >> /etc/ansible/hosts <<EOF

localhost

ansible-client1 ansible_host=172.17.0.3

[all]

localhost

ansible-client1

EOF

Test ansible using ping module

# docker exec -it ansible-master -m ping all

localhost | SUCCESS => {

    "changed": false, 

    "ping": "pong"

}

ansible-client1 | SUCCESS => {

    "changed": false, 

    "ping": "pong"

}

Congratulations, now you have your own mini ansible lab, using docker. You can add more clients as you wish later.

Troubleshooting sshd fail to start

I encountered this issue, and journalctl just does not give enough information on what has happened to make ssh failed to start. So after searching around, I found that I can check the /etc/ssh/sshd_conf for any syntax error, just by running it with extended test (-T) flag. What this flag do is, check the validity of /etc/ssh/sshd_config, throw out error if any, and exit. So to check the issue in the configuration file, just run:

# /usr/sbin/sshd -T

Another way is, you can also start sshd manually with debug flag (-d), and it will throw out any error that stopping it from starting:

# /usr/sbin/sshd -d

/boot Keeps Filling Up On Kernel Update

This is an issue I encountered in one of my friend's ubuntu 16.04 box. He tried to do kernel update, but the /boot keeps filling up with old initramfs image files, making the update process failed. Then I found a post here, that says that if /var/lib/initramfs-tools is not being cleaned up from old kernel files, /boot will keep on being filled up with old initramfs images. So to clean it up:

# uname -r 

4.15.0-46-generic

# cd /var/lib/initramfs-tools

# rm `ls | grep -v 4.15.0-46`

Once cleaned up, update your current initramfs, using:

# update-initramfs -u -k all

where -u is to generate initramfs for current kernel, and '-k all' to generate initramfs for kernel version newer than current kernel.

Once that done, you can safely reboot your machine. It will be rebooted using the latest kernel.