Brand new install on a new DigitalOcean droplet. I am going to run replication into this cloud server from my local network. I was trying to install the same version etc. mysql5.6.50 and then run it on a external volume. My current db is 370gb and I will need some overhead. I created the droplet and added a 500gb drive, installed mysql started and verified proper base operation. Then I followed these instructions.
https://www.digitalocean.com/community/tutorials/how-to-change-a-mysql-data-directory-to-a-new-location-on-centos-7
When I run systemctl start mysqld. I seem to go into a endless wait.
Running status gives:
[root@centos-s-1vcpu-2gb-ny3-01 volume_ny3_04]# systemctl status mysqld -l
● mysqld.service - MySQL Community Server
Loaded: loaded (/usr/lib/systemd/system/mysqld.service; enabled; vendor preset: disabled)
Active: activating (start-post) since Thu 2022-01-06 22:43:38 UTC; 1min 25s ago
Process: 5351 ExecStart=/usr/bin/mysqld_safe --basedir=/usr (code=exited, status=0/SUCCESS)
Process: 5339 ExecStartPre=/usr/bin/mysql-systemd-start pre (code=exited, status=0/SUCCESS)
Main PID: 5351 (code=exited, status=0/SUCCESS); : 5352 (mysql-systemd-s)
CGroup: /system.slice/mysqld.service
└─control
├─5352 /bin/bash /usr/bin/mysql-systemd-start post
└─5800 sleep 1
Jan 06 22:43:38 centos-s-1vcpu-2gb-ny3-01 systemd[1]: Starting MySQL Community Server...
Jan 06 22:43:38 centos-s-1vcpu-2gb-ny3-01 mysql-systemd-start[5339]: /usr/sbin/restorecon: Warning no default label for /mnt/volume_ny3_04/mysql
Jan 06 22:43:38 centos-s-1vcpu-2gb-ny3-01 mysqld_safe[5351]: 220106 22:43:38 mysqld_safe Logging to '/var/log/mysqld.log'.
Jan 06 22:43:38 centos-s-1vcpu-2gb-ny3-01 mysqld_safe[5351]: 220106 22:43:38 mysqld_safe Starting mysqld daemon with databases from /mnt/volume_ny3_04/mysql
last line from journalctl -xe after repeated retries:
mysqld_safe[7451]: 220106 22:53:39 mysqld_safe mysqld from pid file /var/run/mysqld/mysqld.pid ended
Permissions etc appear to be ok!
