search

chirpstack / chirpstack-ansible-playbook

Ansible playbook for setting up ChirpStack.
https://www.chirpstack.io
MIT License
84 stars 43 forks source link

Confliting - config.vm.network :forwarded_port #8

Closed ghost closed 7 years ago

ghost commented 7 years ago

Hi Brocaar,

I've already have run the loraserver-setup and everything was going well. But now, there was a new version from vagrant box to update. I've updated these days and appears a problem with the host conflicting . Here is the error message:

============================================================================ _roger@roger-Inspiron-5447:~/Documentos/Brocaar/loraserver-setup$ vagrant up Bringing machine 'vagrant' up with 'virtualbox' provider... ==> vagrant: Checking if box 'ubuntu/xenial64' is up to date... ==> vagrant: A newer version of the box 'ubuntu/xenial64' is available! You currently ==> vagrant: have version '20170419.0.0'. The latest is version '20170426.0.0'. Run ==> vagrant: vagrant box update to update. Vagrant cannot forward the specified ports on this VM, since they would collide with some other application that is already listening on these ports. The forwarded port to 1883 is already in use on the host machine.

To fix this, modify your current project's Vagrantfile to use another port. Example, where '1234' would be replaced by a unique host port:

config.vm.network :forwarded_port, guest: 1883, host: 1234

Sometimes, Vagrant will attempt to auto-correct this for you. In this case, Vagrant was unable to. This is usually because the guest machine is in a state which doesn't allow modifying port forwarding. You could try 'vagrant reload' (equivalent of running a halt followed by an up) so vagrant can attempt to auto-correct this upon booting. Be warned that any unsaved work might be lost.

============================================================================

The problem happens with host 8080, 1883, 1884. I guess some changes i would make maybe is not the correct way. 'vagrant reload' perform the same error message.

How may I proceed, please?

brocaar commented 7 years ago

The issue is that on your host the port is already taken. Vagrant tries to forward the ports you're mentioning for you, so that these become accessible on "localhost". However it failed because an other process is using them.

ghost commented 7 years ago

Hello Brocaar, sorry for the late and thanks for the "light". The problem have ocurred because I've also installed Mosquitto on my real pc. o the mosquitto started on boot and it used this hosts yet. I've uninstalled this (recovery my ubunto, i thought easier) and install again! Thanks !