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

Configuration Check failed #34

Open
shahbaz-dev1 opened this issue May 24, 2018 · 0 comments
Open

Configuration Check failed #34

shahbaz-dev1 opened this issue May 24, 2018 · 0 comments

Comments

@shahbaz-dev1
Copy link

I am having the issue with installation on

Windows 10
Vagrant 2.1.1
Virtual Box 5.2.12

Here are the results When I run vagrant up

Bringing machine 'default' up with 'virtualbox' provider...
==> default: Checking if box 'ubuntu/trusty64' is up to date...
==> default: Clearing any previously set forwarded ports...
==> default: Clearing any previously set network interfaces...
==> default: Preparing network interfaces based on configuration...
    default: Adapter 1: nat
    default: Adapter 2: hostonly
==> default: Forwarding ports...
    default: 22 (guest) => 2222 (host) (adapter 1)
==> default: Running 'pre-boot' VM customizations...
==> default: Booting VM...
==> default: Waiting for machine to boot. This may take a few minutes...
    default: SSH address: 127.0.0.1:2222
    default: SSH username: vagrant
    default: SSH auth method: private key
==> default: Machine booted and ready!
==> default: Checking for guest additions in VM...
    default: The guest additions on this VM do not match the installed version of
    default: VirtualBox! In most cases this is fine, but in rare cases it can
    default: prevent things such as shared folders from working properly. If you see
    default: shared folder errors, please make sure the guest additions within the
    default: virtual machine match the version of VirtualBox you have installed on
    default: your host and reload your VM.
    default:
    default: Guest Additions Version: 4.3.36
    default: VirtualBox Version: 5.2
==> default: [vagrant-hostsupdater] Checking for host entries
==> default: [vagrant-hostsupdater] Writing the following entries to (C:/WINDOWS/system32/drivers/etc/hosts)
==> default: [vagrant-hostsupdater]   192.168.123.10  civi.dev  # VAGRANT: a16bb0b2673a8b35cde49c6cc2212bb1 (default) / 85b375ff-ff3c-483c-b03d-b153c6a4ccd1
==> default: [vagrant-hostsupdater]   192.168.123.10  civi.dev  # VAGRANT: a16bb0b2673a8b35cde49c6cc2212bb1 (default) / 85b375ff-ff3c-483c-b03d-b153c6a4ccd1
==> default: [vagrant-hostsupdater]   192.168.123.10  d7-46.dev  # VAGRANT: a16bb0b2673a8b35cde49c6cc2212bb1 (default) / 85b375ff-ff3c-483c-b03d-b153c6a4ccd1
==> default: [vagrant-hostsupdater]   192.168.123.10  d7-master.dev  # VAGRANT: a16bb0b2673a8b35cde49c6cc2212bb1 (default) / 85b375ff-ff3c-483c-b03d-b153c6a4ccd1
==> default: [vagrant-hostsupdater]   192.168.123.10  wp-46.dev  # VAGRANT: a16bb0b2673a8b35cde49c6cc2212bb1 (default) / 85b375ff-ff3c-483c-b03d-b153c6a4ccd1
==> default: [vagrant-hostsupdater]   192.168.123.10  wp-master.dev  # VAGRANT: a16bb0b2673a8b35cde49c6cc2212bb1 (default) / 85b375ff-ff3c-483c-b03d-b153c6a4ccd1
==> default: [vagrant-hostsupdater]   192.168.123.10  d8-46.dev  # VAGRANT: a16bb0b2673a8b35cde49c6cc2212bb1 (default) / 85b375ff-ff3c-483c-b03d-b153c6a4ccd1
==> default: [vagrant-hostsupdater]   192.168.123.10  d8-master.dev  # VAGRANT: a16bb0b2673a8b35cde49c6cc2212bb1 (default) / 85b375ff-ff3c-483c-b03d-b153c6a4ccd1
==> default: [vagrant-hostsupdater]   192.168.123.10  b-46.dev  # VAGRANT: a16bb0b2673a8b35cde49c6cc2212bb1 (default) / 85b375ff-ff3c-483c-b03d-b153c6a4ccd1
==> default: [vagrant-hostsupdater]   192.168.123.10  b-master.dev  # VAGRANT: a16bb0b2673a8b35cde49c6cc2212bb1 (default) / 85b375ff-ff3c-483c-b03d-b153c6a4ccd1
==> default: [vagrant-hostsupdater] This operation requires administrative access. You may skip it by manually adding equivalent entries to the hosts file.
==> default: Setting hostname...
==> default: Configuring and enabling network interfaces...
==> default: Mounting shared folders...
    default: /srv/www => E:/cividev/www
    default: /srv/log => E:/cividev/log
    default: /vagrant => E:/cividev
    default: /srv/config => E:/cividev/config
    default: /srv/database => E:/cividev/database
==> default: Machine already provisioned. Run `vagrant provision` or use the `--provision`
==> default: flag to force provisioning. Provisioners marked to run always will still run.
==> default: Running provisioner: shell...
    default: Running: inline script
    default: mysql stop/waiting
    default: mysql start/running, process 2277
==> default: Running provisioner: shell...
    default: Running: inline script
    default:  * Restarting web server apache2
    default:    ...fail!
    default:  * The apache2 configtest failed.
    default: Output of config test was:
    default: (2)No such file or directory: AH02291: Cannot access directory '/home/vagrant/.amp/log/' for error log of vhost defined at /etc/apache2/conf-enabled/civi.dev.conf:3
    default: AH00014: Configuration check failed
    default: Action 'configtest' failed.
    default: The Apache error log may have more information.
The SSH command responded with a non-zero exit status. Vagrant
assumes that this means the command failed. The output for this command
should be in the log above. Please read the output to determine what
went wrong.

Am I doing something wrong

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

1 participant