MongoDB - Connection refused

[GoogleCodeExporter]

This is an intermittent problem that we have only confirmed in Xen runs.
When starting MongoDB, the code looks something like this:

start mongo on port 27017
wait for port 27017 to be open
create the users and apps tables in mongo

The third step sometimes fails with a connection refused on port 27017
message, which is odd since we are waiting for this port to be open.

We plan on remedying this by putting it in a try/catch block and retrying
up to three times if this occurs.

Original issue reported on code.google.com by shattere...@gmail.com on 9 Dec 2009 at 6:28

[GoogleCodeExporter]

Pulled newest code, unable to reproduce. Will close for now and keep an eye out 
for
this in the future.

Original comment by shattere...@gmail.com on 12 Dec 2009 at 3:26

• Changed state: Invalid

[GoogleCodeExporter]

Post-mortem analysis suspects that, similarly to the MySQL issue
(http://code.google.com/p/appscale/issues/detail?id=128), an old version of the 
code
may have been tested, which exhibited this problem.

However, we have opened a new issue for modifying the prime_* scripts to be 
able to
recover from connection refused errors to prevent this from occurring again. The
issue is (http://code.google.com/p/appscale/issues/detail?id=131).

Original comment by shattere...@gmail.com on 14 Dec 2009 at 7:18