On Monday, May 9, 2016 at 4:14:44 PM UTC-5, Jeremy Mikola wrote:
stabbing in the dark...
On Mon, May 9, 2016 at 2:32 PM, <j...@xxxxxxxxxxxx> wrote:
That's great, thank you for your help. I'm running into this now:
'No suitable servers found (`serverselectiontryonce` set): [connection
timeout calling ismaster on '192.168.10.251:27017']'
I can only seem to find issues relating to ipv6 and localhost with this
issue, but those look like they've been fixed (My PECL MongoDB extension is
1.1.6). This is with the mongod.conf file set to 'requireSSL'. With
'preferSSL', everything connects fine, though I am assuming without SSL
Is there something else I should be looking at, or does this just seem
to indicate SSL issues?
That likely points to an SSL issue. Unfortunately, we don't yet have
visibility into the exact error on the client (this is pending
CDRIVER-841 <https://jira.mongodb.org/browse/CDRIVER-841>); however, you
may be able to correlate this with an error in the server logs, as was done
in that ticket.
Also, I just want to clarify that "sslAllowInvalidCertificates" (from
your original post) is not a supported URI option in our drivers. I assume
that was adapted from a command line option on various console clients that
ship with MongoDB (e.g. mongo, mongotop).
Sure, that makes sense. And the 'sslAllowInvalidCertificates' was just
So, server shows:
2016-05-09T16:37:50.562-0500 I NETWORK [initandlisten] connection
accepted from 192.168.10.100:62899 #1 (1 connection now open)
2016-05-09T16:37:50.563-0500 D - [conn1] User Assertion: 17189:The
server is configured to only allow SSL connections
2016-05-09T16:37:50.563-0500 I NETWORK [conn1] AssertionException
handling request, closing client connection: 17189 The server is configured
to only allow SSL connections
Which, I take to mean that the connection coming from PHP is not coming
over SSL. Would you all agree with that? I turned verbosity of system log
up to 3 and that's all I'm really seeing.