Vagrant experiment with Tomee, PostgreSQL, Ruby, RoR
vagrant -v
) have to be >= 1.4vagrant up
There is a software which is listening the port 5432 - have you Postgresql installed in your host? To fix it, open Vagrantfile with a text editor and change the 8th line:
config.vm.network :forwarded_port, guest: 5432, host: 5432 #postgresql
with
config.vm.network :forwarded_port, guest: 5432, host: 5431 #postgresql`
For linux/mac users: $ sed -i "s/host: 5432/host: 5431/g" Vagrantfile
Your virtualized PostgreSQL will be reacheable as localhost:5431
There is a software which is listening the port 8080. To fix it, open Vagrantfile with a text editor and change the 6th line:
config.vm.network :forwarded_port, guest: 8080, host: 8080 #tomee
with
config.vm.network :forwarded_port, guest: 8080, host: 8800 #tomee`
For linux/mac users: $ sed -i "s/host: 8080/host: 8800/g" Vagrantfile
Now you can see the webserver as localhost:8800
Try restarting web server:
For linux/mac users:
$ vagrant ssh # Get access to virtual server's shell
For windows users:
Open ssh.bat
then, for all:
$ sudo /opt/tomee/bin/shutdown.sh # take down a possible blocked process - it can return an error
$ sudo /opt/tomee/bin/startup.sh # start the webserver - it can't return errors
$ exit # back to host's shell
This error is caused by virtual machine which is not responding to Vagrant. To fix it, open Virtualbox and force shutdown of VM:
This problem is solved with the new version of project. To fix it without downloading again the project, you have to make a directory called lib near www.
From command line - for all platforms: mkdir lib
This IS NOT an error. It will appear everytime you start a VM after the first because it means you have already launched installation scripts successfully and if you want re-launch it intentionally run vagrant provision
Like above: this IS NOT an error. Don't care about it.