-
Notifications
You must be signed in to change notification settings - Fork 466
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
Ch06 - task 'create a postgres user' fails if control machine has additional locales #6
Comments
I met the similar issue as yours. vagrant@vagrant-ubuntu-trusty-64:~/mezzanine-example$ sudo locale then add zh_CN.UTF-8 by command "sudo locale-gen zh_CN.UTF-8" Then the postgresql can startup . |
Thanks for your suggestion. I was generating additional locales on the remote machine as well. But this issue is about fixing vagrant and/or vagrant playbook so that (manually) modifying the remote machine is not necessary anymore. |
I do this by adding an ugly specfic task, but this could be diff from all other enviroments
|
This sounds good to me. Sorry, I did not get it in the first place. |
Working through chapter 6 running
ansible-playbook mezzanine.yml
fails at this pointdebugging Vagrant host
locales of my control machine
Validating a running postgres service
Adding missing locales to remote machine
Following the advice from AskUbuntu
Now Ansible tasks for Postgres succeed
Just noticed I even added option
module_lang
toansible.cfg
The problem itself is well known to people used to work with Postgresql and/or Ansible/Vagrant. To me it is not clear how to fix the playbook and how my machine locales affect the problem. I hope the book author can resolve this. BTW - it is an awesome book.
Environment
Vagrant - Ubuntu/Trusty64
Ansible
References
The text was updated successfully, but these errors were encountered: