I'm trying to get Laravel Homestead set up on my mac. I am at the part where I run vagrant up and this is the error message I am receiving:
==> homestead-7: Failed to restart php7.0-fpm.service: Unit php7.0-fpm.service not found.
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.
Anyone have any ideas?
Share on your folders files with "7.1" and change it to "5.0"
Related
I used vagrant to deploy a virtual machine(The virtual machines runs Linux red hat OS) on virtualbox. I am trying to run vertica on the VM however every time I vagrant up provision fails and I get this error:
No such file or directory vertica-8.0.0-0.x86_64.RHEL6.rpm
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.
I downloaded vertica-8.0.0-0.x86_64.RHEL6.rpm from vertica portal and it is in the same directory as my Vagrantfile
I tried a bunch of other solutions online but nothing seems to work still
Does anybody know what the issue might be?
Vagrant is not able to halt / reload after the initial vagrant up (ie the one where the vm is provisioned). The initial vagrant up completes correctly, however after that I am not able to do the vagrant halt or reload.
The error message that I am getting is
==> default: Attempting graceful shutdown of VM...
The following SSH command responded with a non-zero exit status.
Vagrant assumes that this means the command failed!
shutdown -h now
Stdout from the command:
Stderr from the command:
stdin: is not a tty
bash: line 2: syntax error near unexpected token `||'
bash: line 2: `export SSH_AUTH_SOCK= || ||'
List of vagrant plugin I am using
- vagrant-proxyconf (1.5.2)
- vagrant-share (1.1.5, system)
Vagrant version is 1.8.1
Virtualbox [provider] version 4.3.34r104062
Host OS : Windows 7 Enterprise
I have tried re-installing, all the components, destroying the VMs, deleting the config files [ie ~/.VirtualBox & ~/.vagrant.d]
Please help me in resolving the issue
This is not the fix.
The error went away when I again downloaded the code base from github.
When I'm running:
:$ vagrant provision
or
:$ vagrant up
I'm getting this error:
nisevi#localhost processor (master):$ vagrant provision
An error occurred while downloading the remote file. The error
message, if any, is reproduced below. Please fix this error and try
again.
Couldn't resolve host 'www.getchef.com'
if anyone knows to what is related this error, I'm gonna be very grateful.
###################################EDIT
A colleague gave me this thread:
https://serverfault.com/questions/453185/vagrant-virtualbox-dns-10-0-2-3-not-working
as reference where I was able to find some interesting information about mi issue. But now I'm dealing with other problem: bit.ly/1BxehY0
Likely your VM doesn't have any network access due to an incorrect config and an incorrectly installed VirtualBox. Try commenting out the Chef provisioner and then log in to the VM using vagrant ssh. See if you can reach the internet from inside and if not, fix that before progressing. If you include the content of the Vagrantfile we might be able to help more.
For me following worked:
Did vagrant ssh (It threw error to do vagrant up).
Again did vagrant up.
That's all.
I'm trying to use Laravel Homestead for a Laravel 4.2.9 project. Here's what I'm running:
Windows 8.1 64-bit
VirtualBox 4.3.17
Vagrant 1.6.5
Latest Homestead version
When running the box with vagrant up for the first time or issuing the vagrant provision command, I get this:
==> default: Running provisioner: shell...
default: Running: inline script
==> default: /tmp/vagrant-shell: line 1: /home/vagrant/.ssh/$2: ambiguous redirect
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.
Contents of /tmp/vagrant-shell on the box:
echo "$1" > /home/vagrant/.ssh/$2 && chmod 600 /home/vagrant/.ssh/$2
This seems to be affecting nginx configuration as there is no default server conf and it's not listening on port 80 as expected. Presumably the provisioning script would handle that if it was able to proceed.
What might be causing this to happen?
I had the same problem and changed file homestead.rb in "scripts" directory by adding additional quotation marks and backslash around "$2".
s.inline = "echo \"$1\" > /home/vagrant/.ssh/\"$2\" && chmod 600 /home/vagrant/.ssh/\"$2\""
New to Laravel and Vagrant, never put up a virtual machine any way other than via MAMP.
New to using Terminal in general.
Running on Mac OSX 10.9.
Vagrantfile (and hopefully soon Laravel) is placed in a folder in Documents.
Receiving error:
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.
Log since 'vagrant up'
Used vagrant files
UPDATE: When accessing the designated VM address through my browser, I am greeted by a 403 Forbidden
EDIT: Link to terminal log updated after fixing laravel installation issues regarding mcrypt.
UPDATE: Tried solution described here by adding the following to /etc/sudoers. Problem not fixed.
vagrant ALL=(ALL) NOPASSWD:ALL
Defaults:vagrant !requiretty
The artisan file isn't there.
php artisan migrate #fails
I can't tell exactly what should be in /var/www, but it seems to me like Laravel isn't getting set up properly. Try vagrant ssh to snoop around in /var/www (ls /var/www) and see what's there/what's missing.
run:
vagrant ssh
when you success login, run the command like below:
sudo rm -f /etc/udev/rules.d/70-persistent-net.rules
maybe 70 or 60 is the begining of rules filename.
than reload your virtualbox,try it maybe the right way to solve the matter.
If you have this error, after
vagrant up
you can use
vagrant ssh
It let you launch your server.