-
-
Notifications
You must be signed in to change notification settings - Fork 647
Invalid command 'ProxyPassMatch' #379
Comments
If you're running from master and have Ansible installed locally, make sure you have force updated all the Ansible Galaxy roles using the command in the README. |
I have updated Ansible using |
It shouldn't be; what OS are you using? -Jeff Geerling
|
Host OS is |
And no, |
Can you do a diff of your config.yml vs |
Never mind. Re-downloaded the repo and all is well. |
Nice! Glad you could get it working. |
I have the exact same problem.
start rant: I'm really struggling getting drupal-vm to run correctly after VDD decided to bomb on me. drupal-vm seemed like the logical choice but it's been a huge pain to get it to work.
/rant |
@ptsimard another issue with the same error message is #394 (comment). Do you have the lines in |
@ptsimard - Believe me, I know your pain... the problem here is that Windows 7... to 8... to 10—every release had a HUGE number of breaking changes that broke parts of VirtualBox... parts of Vagrant... etc. On the Mac, and on most Linux distros, it has been effortless to support 10.7, 8, 9, 10, 11, Fedora 20, 21, 22, 23, Ubuntu 14, 15, (soon) 16, Arch, etc. The problem is Windows is currently somewhat a second class citizen in many different ways—I think Drupal VM is one of the very few VM projects that is fully tested on a Windows 10 laptop (and Fedora, Ubuntu, Mac OS X) before every single release. And in this case, the release (2.2.0) worked flawlessly. Then Ansible 2.0.0 was released, and Vagrant had a bug that made it's new (in 1.8.0) ansible_local provisioner start breaking. So now I'm (im)patiently awaiting Vagrant's 1.8.2 release, because most people don't have the time/inclination to patch Vagrant on Windows or install the dev version (instead of 1.8.1, which is broken). Anyways... long story short, this is a well known bug, and the fix in this case—does your
Also, are you updated to the latest release of Drupal VM (e.g. |
Hey tanks for the fast reply! Yes I have that line and I am running the master from 2 days ago (what the main download button on drupalvm.com is pointing to). So I'm actually using the vm right now but I don't know what might be broken since the provisioning does not complete. |
@ptsimard - At what point does provisioning fail - can you copy out the error message(s) or screenshot it at the point where it fails? |
it returns to command prompt there |
@ptsimard - Ah... in this case, the problem is that the next role (which would actually install the proper apache mod) isn't being run. Two options:
apache_mods_enabled:
- expires.load
- ssl.load
- rewrite.load
- proxy.load
- proxy_fcgi.load |
Tried option 2: it stopped there:
|
Uh... I've not seen that one before, though it indicates Python is trying to perform an operation with an expected string, but an integer was used instead. Do you have
|
oh I had that set to 7. made it master now, will see |
it completed! so if I wanted drush to be 7 it needs to be quoted?
Thanks for the debugging! |
Yeah; that's not entirely intuitive—it refers to a git branch name, tag, or commit hash, so it should be a string. |
Helps with #379: Set drush_version explicitly to a string
During a new build, I get the following error:
The relevant portion from
config.yml
:The text was updated successfully, but these errors were encountered: