Not sure why php is not getting installed. #110
Comments
|
Hey @harikt! The provisioning didn't run, that's why PHP is not installed at the end. Nothing was executed in the box. It seems like Vagrant is not finding the provisioning files. I'm not sure if this can be related to the box. Could you show how your directory is structured? Your application folder should look similar to this: . |
ansible
├── files
│ └── authorized_keys
├── inventories
│ └── dev
├── playbook.yml
├── roles
│ ├── app
│ │ └── tasks
│ │ └── main.yml
│ ├── init
│ │ ├── tasks
│ │ │ └── main.yml
│ │ └── templates
│ │ └── timezone.tpl
│ ├── nginx
│ │ ├── handlers
│ │ │ └── main.yml
│ │ ├── tasks
│ │ │ └── main.yml
│ │ └── templates
│ │ └── default.tpl
│ ├── php5-cli
│ │ └── tasks
│ │ └── main.yml
│ ├── php5-fpm
│ │ ├── handlers
│ │ │ └── main.yml
│ │ └── tasks
│ │ └── main.yml
│ └── phpcommon
│ └── tasks
│ └── main.yml
├── vars
│ ├── apachephp.yml
│ ├── common.yml
│ ├── nginxphp.yml
│ └── ws_defaults.yml
└── windows.sh |
|
Hmm, for me the problem is here: So seems you don't have this folders/files? I'll try to download that box and run a default playbook this week and report back. |
|
Hi again. I've downloaded that box and created a new playbook. You can see log here: http://pastebin.com/xgSLExX3 As you can see in my case the provisioning is being executed. If there is more info that you can provide it may help. |
|
@naxhh I wonder whether it is specifically with ubuntu or *nix flavor for your is running on windows ? |
|
In what folder are you running the command vagrant up ? |
|
@harikt I've tried in a win machine because is what I have at work :( I'll try on a *nix at home. |
|
@mikeSimonson where the Vagrantfile exists. So the root folder of the project. |
|
@harikt Do you have a vagrant folder anywhere ? |
\w > \u@\h [php:5.5.9-system]\n$ ls -la
total 20
drwxrwxr-x 4 hari hari 4096 Nov 27 06:46 .
drwxrwxr-x 10 hari hari 4096 Nov 27 06:44 ..
drwxrwxr-x 6 hari hari 4096 Nov 27 06:44 ansible
drwxrwxr-x 3 hari hari 4096 Nov 27 06:46 .vagrant
-rw-rw-r-- 1 hari hari 1862 Nov 27 06:45 Vagrantfile |
|
@harikt Weird error, but it's hard to know what's going on from here. |
|
Hi again @harikt. Today I've had a bit more time to test this problem. I tried with a *nix machine and works ok. I guess that if this happen to you with puphpet is something in your setup. Anyway, reading puphpet issue and this one. I don't get at all why you are downloading the box. I'm closing this as I'm not able to reproduce this in any way... |
|
Hi @naxhh ,
I have a limited bandwidth , and the internet connection is slow. I don't wish to do a I wanted to make use of the box which puphpet itself is downloading. So I just downloaded the box earlier and then the same box can be used on different projects. Hope that make sense why I am keeping the box url. Thank you for taking your time to look into the issue. |
|
Ah ok, you want to share same box between two projects. |
Yes, I want to share box with many projects.
:-/ . Not sure then what the cause may be. |
|
I'll guess you are using windows.sh... If that is true, ansible is being executed inside the box... check your nfs configurations. Apart of that I don't have any idea where the problem could be |
Nope. I am not. I am using ubuntu os and not windows just to make things clear. |
|
Yes, name of the file is confusing. We use The file installs ansible in the VM and provisions from there. |
|
I'm using osx as a host. Downloaded generated zip, unpacked, typed "vagrant up" and ended up with the same error. full log: |
|
Which may be important - I'm trying to install configuration with php 5.4 |
|
If I should guess I'll say it has something to do with #71 Thanks! |
Hi,
In order to save the time/bandwidth I downloaded a box from https://vagrantcloud.com/ubuntu/boxes/trusty64/versions/14.04/providers/virtualbox.box and used to change the
config.vm.box = "file:///home/hari/Downloads/virtualbox.box". It can download easily. A few errors I noticed seems not respect to box, may be you can help with . Same is happening with @puphpet . See issue puphpet/puphpet#1224The text was updated successfully, but these errors were encountered: