dirkaholic / vagrant-php-dev-box

PHP 7 vagrant development box with nginx, php-fpm, MySQL, Symfony, Laravel, ... on Ubuntu 16.04
477 stars 141 forks source link

Fails on 'vagrant up' #13

Closed vadi2 closed 8 years ago

vadi2 commented 11 years ago

Here is the output: http://pastebin.com/qmEWv3Ns

Notable pieces are:

err: /Stage[main]/Devbox_php_fpm/Php::Module[xhprof]/Package[php-xhprof]/ensure: change from purged to present failed: Execution of '/usr/bin/apt-get -q -y -o DPkg::Options::=--force-confold install php5-xhprof' returned 100: Reading package lists...
Building dependency tree...
Reading state information...
E: Unable to locate package php5-xhprof

err: /Stage[main]/Devbox_php_fpm/Php::Module[apc]/Package[php-apc]/ensure: change from purged to present failed: Execution of '/usr/bin/apt-get -q -y -o DPkg::Options::=--force-confold install php5-apc' returned 100: Reading package lists...
Building dependency tree...
Reading state information...
E: Unable to locate package php5-apc

At the end:

The following SSH command responded with a non-zero exit status.
Vagrant assumes that this means the command failed!

cd /tmp/vagrant-puppet/manifests && puppet apply --verbose --modulepath '/etc/puppet/modules:/tmp/vagrant-puppet/modules-0' default.pp --detailed-exitcodes || [ $? -eq 2 ]

I've tried doing vagrant destroy and vagrant up again, but the same result happens. What is wrong?

twsystemhaus commented 11 years ago

same here

floodedcodeboy commented 11 years ago

It would probably help the developer if you provided some more of the information : ie: Vagrant Version, Virtualbox Version

sourbell commented 11 years ago

I'm stuck on vagrant up, but i can access the file through localhost:8181/app_dev.php

The last log i got is this one: notice: /Stage[main]/Symfony-standard/Exec[install composer for symfony when needed]/returns: executed successfully

Vagrant version: 1.2.7 VirtuaBox version: 4.2.18

mzeis commented 10 years ago

I'm in the same situation as @sourbell.

Vagrant: 1.5.3 VirtualBox: 4.3.8

dirkaholic commented 8 years ago

Just upgraded to a new version using the ansible privisioner and therefor will close this issue.