After migration to 3.4.7: [Errno 42] Protocol option not available

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Fixed
    • Priority: Major - P3
    • 3.5.1
    • Affects Version/s: 3.5
    • Component/s: Connection Mgmt
    • None
    • Environment:
      NetBSD web.mx.plus 6.1_STABLE NetBSD 6.1_STABLE (GENERIC) #3: Thu Jul 27 20:35:53 CEST 2017 bjjl@web.mx.plus:/data/stable/obj/sys/arch/i386/compile/GENERIC i386
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      After upgrading my Replica Set to 3.4.7, coming from 3.4.6, and upgrading pymongo from 3.4.0 to 3.5.0 (the latest one available through pip), my app does not start anymore:

      File "/usr/pkg/lib/python2.7/site-packages/pymongo/topology.py", line 189, in select_servers
      self._error_message(selector))
      pymongo.errors.ServerSelectionTimeoutError: mx2.db.zone:45017: [Errno 42] Protocol option not available,mx1.db.zone:45017: [Errno 42] Protocol option not available
      unable to load app 0 (mountpoint='') (callable not found or import error)

      All servers from the Replica Set are reachable (and DNS resolvable) from the app.

      Using this connection string:

      MONGO_URI = 'mongodb://myuser:mypasswordxxx@mx1.db.zone:45017,mx2.db.zone:45017/qwabbl?replicaSet=mxplus&connect=false'

            Assignee:
            Bernie Hackett
            Reporter:
            Benjamin Lorenz
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: