Follow-up Comment #5, bug #21666 (project freeciv):

> Note that running Freeciv-web using Vagrant requires about 6Gb of memory
In that case I can't do a proper test before I have access to another

> It would be great if you could give it a new test, so that we know it works
on other systems as well.
It gets to the end but errors are reported. (Those could be caused by the port
not being forwarded yet or by the computer running out of memory) The out of
memory killer kills the virtual machine before I have time to forward port

End of the output:

This is the server for Freeciv version 2.5.99-dev
You can learn a lot about Freeciv at
2: Loading rulesets.
checking nginx
Spider mode enabled. Check if remote file exists.
--2014-02-20 13:28:09--  http://localhost/
Resolving localhost (localhost)...
Connecting to localhost (localhost)||:80... connected.
HTTP request sent, awaiting response... 502 Bad Gateway
Remote file does not exist -- broken link!!!

nginx not running!

checking resin
Spider mode enabled. Check if remote file exists.
--2014-02-20 13:28:10--  http://localhost:8080/
Resolving localhost (localhost)...
Connecting to localhost (localhost)||:8080... failed: Connection
resin not running!

checking freeciv-proxy
INFO:tornado.access:200 GET /status ( 1539.26ms
freeciv-proxy OK!
checking freeciv-web / publite2
freeciv-web OK!
Check done!
Freeciv-web started! Now try http://localhost/ on your host operating system.


Reply to this item at:


  Message sent via/by Gna!

Freeciv-dev mailing list

Reply via email to