Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Mongo 3.4 uses a different string to indicate it is ready for connections #121

Merged
merged 1 commit into from
Feb 22, 2017

Conversation

jameinel
Copy link
Member

The line is specifically:
2017-02-22T12:51:41.107+0400 I NETWORK [thread1] waiting for connections on port 9999

I don't know if we are ready to support all of mongo 3.4, but this allows me to run the test suite on Mac OS X when I have whatever Mongo I could install from homebrew. It seems a safe enough change.

…ions.

The line is specifically:
  2017-02-22T12:51:41.107+0400 I NETWORK  [thread1] waiting for connections on port 9999
@jameinel jameinel changed the title Mongo 3.4 uses a different signal to indicate it is ready for connections Mongo 3.4 uses a different string to indicate it is ready for connections Feb 22, 2017
@jameinel
Copy link
Member Author

$$merge$$

@jujubot
Copy link
Contributor

jujubot commented Feb 22, 2017

Status: merge request accepted. Url: http://juju-ci.vapour.ws:8080/job/github-merge-juju-testing

@jujubot jujubot merged commit fce9bc4 into juju:master Feb 22, 2017
@jameinel jameinel deleted the mongo-3.4 branch February 22, 2017 09:17
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants