search

cloudera / cloudera-playbook

Cloudera deployment automation with Ansible
Apache License 2.0
198 stars 187 forks source link

Corrected mariadb pid file location #41

Closed Jimvin closed 5 years ago

Jimvin commented 5 years ago

On CentOS 7 mariadb creates the pid file in /var/run/mariadb, not /var/run/mysql. Installation using the playbooked worked, but mariadb would not start following reboot of the DB server.

dbeech commented 5 years ago

I think mariadb should put the file where we tell it to, but we're setting the pid-file option in my.cnf incorrectly. We're putting it in a [mysqld_safe] block rather than further up in the main [mysql] block.

dbeech commented 5 years ago

Ok, ignore that last comment. It doesn't fix it and I understand why now. It makes me wonder why we bother to set mysql_pid_dir and mysql_pid_file in the template at all? Surely leaving it to the defaults would be ok and then it will work on all platforms?

Jimvin commented 5 years ago

Agreed, removing it from the configuration would seem to be the best option.

On Mon, 2 Sep 2019 at 10:46, Dave Beech notifications@github.com wrote:

Ok, ignore that last comment. It doesn't fix it and I understand why now. It makes me wonder why we bother to set mysql_pid_dir and mysql_pid_file in the template at all? Surely leaving it to the defaults would be ok and then it will work on all platforms?

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/cloudera/cloudera-playbook/pull/41?email_source=notifications&email_token=AAPFGT4GJ6RC4HQKFQXDDPLQHTOGHA5CNFSM4IS24QQKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD5VKDQQ#issuecomment-527081922, or mute the thread https://github.com/notifications/unsubscribe-auth/AAPFGTZIRNYJ5ONKDTFLB3LQHTOGHANCNFSM4IS24QQA .

dbeech commented 5 years ago

Closing as fixed by @rafaelarana's PR #12.