Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Handling of non-standard datadir #88

Open
eliasp opened this issue Aug 19, 2015 · 2 comments
Open

Handling of non-standard datadir #88

eliasp opened this issue Aug 19, 2015 · 2 comments

Comments

@eliasp
Copy link

eliasp commented Aug 19, 2015

Right now, there's no handling at all for non-default locations of datadir.

  • a fresh deployment doesn't create the datadir
  • changing an existing deployment doesn't move the existing datadir to its new location (shutdown of mysql service, moving datadir, starting mysql service again)

There might be some difficulties involved in this, as the package management of some distributions adds mechanisms (postinst etc.) to the MySQL package which expects the default path (/var/lib/mysql) and otherwise might break the package installation/always re-create the datadir, etc.

@hgfischer
Copy link

Yes, this is annoying. The configuration exists, but it only creates the datadir for some distributions. For Ubuntu or Debian, for example, it doesn't.

@noelmcloughlin
Copy link
Member

related issue copied from #81

Non-standard 'datadir' needs AppArmor changes on Ubuntu

When using a non-standard datadir on Ubuntu, changes to AppArmor are required, otherwise MySQL won't start anymore.
See also: https://blogs.oracle.com/jsmyth/entry/apparmor_and_mysql Similar changes are most likely required for SELinux enabled systems.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants