Skip to content

MODULES-3601 Move binary logging configuration to take place after pa… #868

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

Merged
merged 2 commits into from
Jul 20, 2016

Conversation

QuentinMoss
Copy link
Contributor

@ebuzzz
Copy link

ebuzzz commented Jul 20, 2016

Wouldn't this still result in errors when the binary log directory is unavailable during setup? The installation of the mysql-server package normally auto-starts the server. The config file has been setup to work with the log-bin directory, but that directory is created after the service has been started.

@QuentinMoss
Copy link
Contributor Author

@eborned Here is a test deployment on CentOS 7 with binary log options defined:

https://gist.github.com/QuentinMoss/14f560dfc7cac76282639a66462f0392

@hunner
Copy link
Contributor

hunner commented Jul 20, 2016

I think just installing the package on debian/ubuntu auto-starts the service, but this will at least fix the currrent issue and allow it to work on redhat.

@hunner hunner merged commit bc2a902 into puppetlabs:master Jul 20, 2016
@QuentinMoss QuentinMoss deleted the fix-binarylog-order branch July 20, 2016 23:22
@bwitt
Copy link

bwitt commented Sep 21, 2016

Yes installing the package on ubuntu auto-starts the service, which results in a failure.

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

Successfully merging this pull request may close these issues.

5 participants