search

mikewhitby / magento-ansible

A Vagrant box, built with Ansible, intended for running Magento
18 stars 2 forks source link

Apache start failing #3

Open jeffbritts opened 9 years ago

jeffbritts commented 9 years ago

failed: [192.168.56.101] => {"failed": true} msg: Output of config test was: AH00112: Warning: DocumentRoot [/vagrant/public] does not exist (2)No such file or directory: AH02291: Cannot access directory '/vagrant/logs/apache/' for error log of vhost defined at /etc/apache2/sites-enabled/000-vagrant.conf:2 AH00014: Configuration check failed Action 'configtest' failed.

earlier in the install, there was this message. Not sure if related ==> default: Bindfs seems to not be installed on the virtual machine

Latest versions of vagrant and Vbox vagrant-bindfs plugin installed

mikewhitby commented 9 years ago

Hey Jeff, it looks like the NFS share didn't work - the whole directory containing the project should be shared to the guest at /vagrant.

Don't worry about that bindfs message, it's normal (I'll add this to the readme).

What is your host operating system? I've only tested the build on OS X Yosemite (I'll add this to the readme too).

A couple of debugging steps:

  1. Run cat /etc/exports from a terminal and check you see an entry that looks like below (but substitute the path for the directory you cloned the repo in to):

    # VAGRANT-BEGIN: 501 b5f70cc7-d40e-42c4-a901-beff511ec5fe
"/Users/mike/Projects/magento-ansible" 192.168.56.101 -alldirs -mapall=501:20
# VAGRANT-END: 501 b5f70cc7-d40e-42c4-a901-beff511ec5fe
  2. vagrant ssh to the guest and run ls /vagrant and check the output produces a directory listing

Note you could always just try running vagrant reload --provision from the host to see if that helps, it often can.

mikewhitby commented 9 years ago

Have updated the readme a bit as per my comments.

jeffbritts commented 9 years ago

Hi Mike,

I'm using OSX Yosemite. I had tried the reload, as I have run into mapping issues in the past where reload fixed them.

It looks like the mapping has happened

VAGRANT-BEGIN: 110077484 30b9d15c-9c77-4f0a-948f-e12f428b43a2

"/Users/jbritts/vagrant/magento-ansible" 192.168.56.101 -alldirs -mapall=110077484:110077484

VAGRANT-END: 110077484 30b9d15c-9c77-4f0a-948f-e12f428b43a2

If I ssh in, there is no /vagrant directory. But the /mnt/bindfs was mounted to the host. So it looks like the binding from that to /vagrant isnt happening. the /mnt/bindfs/public directory is empty (not sure if its supposed to be)

I tried uninstalling the bindfs plugin. Apache then started, Mailcatcher and XHProfUI worked. Magento came up with File Not Found.
There was a /vagrant directory on the VM.

If I can grab some time I will investigate further. I havent used bindfs before. I'd like to get it working as I think it may help with something else I'm working on.

-J

On 3/14/15 5:49 AM, Mike Whitby wrote:

Have updated the readme a bit as per my comments.

— Reply to this email directly or view it on GitHub https://github.com/mikewhitby/magento-ansible/issues/3#issuecomment-80236032.

mikewhitby commented 9 years ago

Hi Jeff, that all sounds like it's working as expected expect for the bindfs - you mentioned public being empty, that's normal - I chose to keep it empty so you can put whatever version of Magento in there you wish.

It definitely sounds purely bindfs related owing ot the fact you can see /mnt/bindfs. I did have an issue installing the bindfs plugin on my work macbook - it was moaning about a gem (I can't remember the name), did you get issues when installing the plugin? I resolved them in the end by just upgrading my vagrant version.

Oh, on a related note, you might want to do a pull, as there was an issue (#4) which won't be causing what you're seeing, but could be confused as such in certain situations.

Cheers, Mike