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

Start php5-fpm service - Failing #205

Closed
riveramauro opened this issue Apr 30, 2015 · 6 comments
Closed

Start php5-fpm service - Failing #205

riveramauro opened this issue Apr 30, 2015 · 6 comments

Comments

@riveramauro
Copy link

I'm getting the following error when running vagrant provision.
Here is the log:

TASK: [php | Add PHP 5.6 PPA] ************************************************* 
ok: [default]

TASK: [php | Install PHP 5.6] ************************************************* 
ok: [default] => (item=php5-common,php5-fpm,php5-mysqlnd,php5-xmlrpc,php5-mcrypt,php5-curl,php5-gd,php5-cli,php-pear,php5-dev,php5-imap)

TASK: [php | Start php5-fpm service] ****************************************** 
failed: [default] => {"failed": true}

FATAL: all hosts have already failed -- aborting

PLAY RECAP ******************************************************************** 
           to retry, use: --limit @/Users/mauriciorivera/dev.retry

default                    : ok=29   changed=0    unreachable=0    failed=1   

Ansible failed to complete successfully. Any error output should be
visible above. Please fix these errors and try again.

Cloned the repo, and testing this new setup for the first time. Can't seem to figure what this error is. Any clues? Thanks.

@kalenjohnson
Copy link
Sponsor Contributor

I bet you're on Ansible 1.9.1

@riveramauro
Copy link
Author

Yes I am.... and I just notice "Ansible >= 1.8" in the documentation -_-

Could that be the reason?

@kalenjohnson
Copy link
Sponsor Contributor

Nope, this: ansible/ansible#10675

Either downgrade to 1.9.0.1 or remove these lines: https://github.com/roots/bedrock-ansible/blob/master/roles/php/tasks/main.yml#L20-21

@riveramauro
Copy link
Author

Can confirm. Downgraded to 1.9.0.1 and working as expected. Thanks!

@swalkinshaw
Copy link
Member

Leaving this open since it's technically a bug, just not ours. But we'll keep track of it through here.

@swalkinshaw
Copy link
Member

Closing this since it's been fixed in next Ansible release. 1.9.1 will forever be broken and that note about it will need to be left in the README for a little bit.

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