Jump to content

Argus

Members
  • Content Count

    3
  • Joined

  • Last visited

Community Reputation

0 Neutral
  1. well i thought that is what the step in the tutorial was taking care of but i dont know exactly... frankly i dont know anything about app armor... i guess that is another thing to sort out in my studies... thank you for you time looking into this.
  2. so basically i went back and changed datadir= /var/lib/mysql and my alias changes and restarted app armor and (mv mysql.bak mysql) the /var/lib/mysql. and restarted the mysql server and it came back up with out a hitch... just like it never happened.... so there has to be something not being done correctly or it is something with the fact ubuntu was upgraded from 16.04 to 18.04 and previously haveing MySQL on there and apt remove mysql should have perhaps had an apt purge mysql as well before having MariaDB installed... not sure, but once i got the database server running again i did drop
  3. so i was following the very helpful tutorial https://linuxhint.com/change_mysql_data_directory_ubuntu/ and when i got to the near end where i issue the systemctl start mariadb i get a failure. ● mariadb.service - MariaDB 10.1.44 database server Loaded: loaded (/lib/systemd/system/mariadb.service; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Sat 2020-07-11 09:00:54 EDT; 1min 54s ago Docs: man:mysqld(8) https://mariadb.com/kb/en/library/systemd/ Process: 14717 ExecStart=/usr/sbin/mysqld $MYSQLD_OPTS $_WSREP_NEW_CLUSTER $_WSREP_S
×
×
  • Create New...