URL:
  <http://gna.org/bugs/?21666>

                 Summary: Freeciv web: Bundled vagrant script don't work
                 Project: Freeciv
            Submitted by: sveinung
            Submitted on: Mon 17 Feb 2014 09:19:47 PM UTC
                Category: freeciv-web
                Severity: 3 - Normal
                Priority: 5 - Normal
                  Status: None
             Assigned to: None
        Originator Email: 
             Open/Closed: Open
                 Release: 
         Discussion Lock: Any
        Operating System: None
         Planned Release: 

    _______________________________________________________

Details:

On Debian testing.
Freeciv web version: aed38fa33029c636b1aaade9fcb5a3e8df655a7a
VirtualBox version: 4.3.2-dfsg-1+b1 (debian package)
Vagrant version: 1.4.3-1
Could be related: on an old laptop. Under 1 Gb storage space left.

$ vagrant up
Bringing machine 'default' up with 'virtualbox' provider...
[default] Importing base box 'ubuntu64'...
[default] Matching MAC address for NAT networking...
[default] Setting the name of the VM...
[default] Clearing any previously set forwarded ports...
[default] Clearing any previously set network interfaces...
[default] Preparing network interfaces based on configuration...
[default] You are trying to forward to privileged ports (ports <= 1024). Most
operating systems restrict this to only privileged process (typically
processes running as an administrative user). This is a warning in case
the port forwarding doesn't work. If any problems occur, please try a
port higher than 1024.
[default] Forwarding ports...
[default] -- 22 => 2222 (adapter 1)
[default] -- 80 => 80 (adapter 1)
[default] Running 'pre-boot' VM customizations...
[default] Booting VM...
[default] Waiting for machine to boot. This may take a few minutes...
Timed out while waiting for the machine to boot. This means that
Vagrant was unable to communicate with the guest machine within
the configured ("config.vm.boot_timeout" value) time period. This can
mean a number of things.

If you're using a custom box, make sure that networking is properly
working and you're able to connect to the machine. It is a common
problem that networking isn't setup properly in these boxes.
Verify that authentication configurations are also setup properly,
as well.

If the box appears to be booting properly, you may want to increase
the timeout ("config.vm.boot_timeout") value




    _______________________________________________________

Reply to this item at:

  <http://gna.org/bugs/?21666>

_______________________________________________
  Message sent via/by Gna!
  http://gna.org/


_______________________________________________
Freeciv-dev mailing list
Freeciv-dev@gna.org
https://mail.gna.org/listinfo/freeciv-dev

Reply via email to