You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Feb 12, 2024. It is now read-only.
Why not just wait for a successful connection for the socket in the script before trying to start services which depend on it? For example, checking the exit status of the following should do the trick:
echo "~." | telnet -r localhost 27017 > /dev/null
This can be done in a loop with a bit of a sleep and an eventual timeout in case something takes too long.
I don't have a machine to test this on right now, but that sounds
reasonable. Feel free to implement it :)
On Apr 29, 2014 12:00 AM, "Michael Mior" notifications@github.com wrote:
Why not just wait for a successful connection for the socket in the script
before trying to start services which depend on it? For example, checking
the exit status of the following should do the trick:
echo "~." | telnet -r localhost 27017 > /dev/null
This can be done in a loop with a bit of a sleep and an eventual timeout
in case something takes too long.
—
Reply to this email directly or view it on GitHubhttps://github.com//issues/81#issuecomment-41639768
.
Sometimes when mongod is run for the first time with our config, it takes a while to start, and Flask crashes when
make local
is run.We can monitor a mongo log file to ensure it starts properly, or perhaps just "warm up" mongo after a fresh installation.
This only seems to affect Linux and not Mac.
More details in discussions of #64
The text was updated successfully, but these errors were encountered: