Error on vagrant up - Windows 8.1

trellis
1

Hi guys,
After some tinkering and getting used to the new changes I get the following error after running ‘vagrant up’:

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

FATAL: all hosts have already failed -- aborting

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

127.0.0.1                  : ok=29   changed=13   unreachable=0    failed=1

I’ve cloned both bedrock and sage as per the example:

For vagrant I have installed the vagrant-hostsupdater and have cloned @kalenjohnson 's windows compat branch:
https://github.com/kalenjohnson/bedrock-ansible/tree/windows-compat

As I have found to be the case I have started the git-bash console with admin priviledges as it otherwise won’t have enough permissions to change the hosts file.

I’ve tried to minimize errors by not changing much in my development file:

mysql_root_password: devpw

web_user: vagrant

wordpress_sites:
  roots.dev:
    site_hosts:
      - roots.dev
    local_path: '../site' # path targeting local Bedrock site directory (relative to Ansible root)
    repo: git@github.com:roots/bedrock.git
    site_install: true
    site_title: roots Site
    admin_user: admin
    admin_password: admin
    admin_email: admin@roots.dev
    multisite:
      enabled: false
      subdomains: false
    ssl:
      enabled: false
    system_cron: true
    env:
      wp_home: http://roots.dev
      wp_siteurl: http://roots.dev/wp
      wp_env: development
      db_name: example_dev
      db_user: example_dbuser
      db_password: example_dbpassword

php_error_reporting: 'E_ALL'
php_display_errors: 'On'
php_display_startup_errors: 'On'
php_track_errors: 'On'
php_mysqlnd_collect_memory_statistics: 'On'
php_opcache_enable: 0

xdebug_install: false
php_xdebug_remote_enable: true
php_xdebug_remote_connect_back: true
php_xdebug_remote_host: localhost
php_xdebug_remote_port: 9000
php_xdebug_remote_log: /tmp/xdebug.log
php_xdebug_idekey: XDEBUG
php_max_nesting_level: 200

Any help would be very welcome

Thanks

2

Ok so it seems to be related with Ansible version 1.9.1 as mentioned by @kalenjohnson: https://github.com/roots/bedrock-ansible/pull/203

How could I revert back to version 1.9.0.1 as mentioned in the pull request?

Thanks

3

You’re running into an issue with Ansible 1.9.1 specifically. https://github.com/roots/bedrock-ansible/issues/205

4

Yes @kalenjohnson I finally figured it out.
I was wondering however if there is a way for me to revert back to 1.9.0.1 as you mention on github.

Thanks

5

I looked into that, but it didn’t seem like the Ansible PPA allows installing previous versions. Hopefully the next version with the fix is out soon

6

Thanks a lot. This would be the next version on Ansible or bedrock-ansible?

So if I were to use a bedrock-ansible, bedrock & Sage combination right now with Windows what would be my best bet?

Thanks

7

The next version of Ansible, it’s an Ansible bug. You can remove this section, as it’s not even necessary if you haven’t changed the default Vagrant box, as php5-fpm is already installed and running: https://github.com/roots/bedrock-ansible/blob/master/roles/php/tasks/main.yml#L20-21

Although if you use bedrock-ansible to provision a staging/production server you may need to add that back in.

8

Thanks that worked. Now I’m running into the directory length problem with npm:

OSError: [Errno 2] No such file or directory: '/srv/www/roots.dev/current/web/app/themes/sage/node_modules/asset-builder/node_modules/main-bower-files/node_modules/vinyl-fs/node_modules/glob-stream/node_modules/unique-stream/node_modules/es6-set/node_modules/es5-ext/node_modules/es6-symbol/test/is-native-implemented.js'

The file it’t there, however it seems that Ansible (Vagrant?) is not able to go beyond the 260 character limit.

I’m wondering if anybody else is running into this problem as it hasn’t been raised until now.

Thanks,

Mauro

9

I don’t know much about that. I’ve seen people ask about that issue in Windows but I don’t know the fix. I don’t actually use Windows on any of my machines for development :slight_smile:

10

Not a problem :slight_smile: Thanks for all your help. Hopefully with Vagrant 1.7.3 and UNC fix the problem will be corrected.

Thanks again