Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-34854

Backtrace during SSL downgrade of a sharded cluster

XMLWordPrintableJSON

    • Type: Icon: Bug Bug
    • Resolution: Duplicate
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: Security
    • Labels:
      None
    • ALL
    • Hide
      1. Set up a MongoDB 3.7.9 2-shard PSA cluster with 3 config servers and 2 mongoses with sslMode set to disabled
      2. Restart each member with sslMode set to allowSSL
      3. Run db.adminCommand( { setParameter: 1, sslMode: "preferSSL" }

        ) on each member

      4. Run db.adminCommand( { setParameter: 1, sslMode: "requireSSL" }

        )

      5. Restart each member with sslMode set to preferSSL.  Some of the members will backtrace during this time.
      Show
      Set up a MongoDB 3.7.9 2-shard PSA cluster with 3 config servers and 2 mongoses with sslMode set to disabled Restart each member with sslMode set to allowSSL Run db.adminCommand( { setParameter: 1, sslMode: "preferSSL" } ) on each member Run db.adminCommand( { setParameter: 1, sslMode: "requireSSL" } ) Restart each member with sslMode set to preferSSL.  Some of the members will backtrace during this time.
    • Platforms 2018-05-21

      I get backtraces on 4 members of a  MongoDB 3.7.9 sharded cluster while attempting an SSL downgrade from requireSSL to preferSSL.  The downgrade was attempted by restarting MongoDB with sslMode set to preferSSL.

      This is a 2-shard cluster with each shard having 3 members, 1 of which is an arbiter.  There are 3 config servers and 2 mongoses.

      The cluster first went through an upgrade of SSL from disabled to requireSSL.  This was done by first restarting each member with allowSSL.  Then there was one round of upgrading to preferSSL using setParameter, and then another round of setParameter to get to requireSSL.

      Then after that the downgrade was attempted (via restarting, not setParameter).

      I am attaching log files for all cluster members.  The following log files show backtraces:

      mongos2.2018-05-04T09-17-03.log
      shardA-2.2018-05-04T09-16-25.log
      shardB-1.2018-05-04T09-16-27.log
      shardB-3.2018-05-04T09-16-28.log

       

        1. cfg1.2018-05-04T09-15-04.log.gz
          133 kB
        2. cfg1.2018-05-04T09-15-52.log.gz
          5 kB
        3. cfg1.log.gz
          9 kB
        4. cfg2.2018-05-04T09-10-03.log.gz
          9 kB
        5. cfg2.2018-05-04T09-16-26.log.gz
          10 kB
        6. cfg2.log.gz
          17 kB
        7. cfg3.2018-05-04T09-13-11.log.gz
          58 kB
        8. cfg3.2018-05-04T09-17-24.log.gz
          17 kB
        9. mongos1.2018-05-04T09-10-33.log.gz
          28 kB
        10. mongos1.2018-05-04T09-15-49.log.gz
          52 kB
        11. mongos1.log.gz
          45 kB
        12. mongos2.2018-05-04T09-13-47.log.gz
          4 kB
        13. mongos2.2018-05-04T09-17-03.log.gz
          16 kB
        14. mongos2.log.gz
          13 kB
        15. shardB-3.2018-05-04T09-16-28.log.gz
          11 kB
        16. shardB-3.log.gz
          5 kB
        17. shardA-1.2018-05-04T09-13-00.log.gz
          13 kB
        18. shardA-1.2018-05-04T09-57-27.log.gz
          464 kB
        19. shardA-2.2018-05-04T09-11-38.log.gz
          54 kB
        20. shardA-2.2018-05-04T09-16-25.log.gz
          61 kB
        21. shardA-2.2018-05-04T09-57-27.log.gz
          401 kB
        22. shardA-3.2018-05-04T09-10-02.log.gz
          4 kB
        23. shardA-3.2018-05-04T09-15-52.log.gz
          6 kB
        24. shardA-3.2018-05-04T09-57-27.log.gz
          364 kB
        25. shardB-1.2018-05-04T09-10-03.log.gz
          7 kB
        26. shardB-1.2018-05-04T09-16-27.log.gz
          14 kB
        27. shardB-1.2018-05-04T09-57-27.log.gz
          7 kB
        28. shardB-2.2018-05-04T09-09-33.log.gz
          6 kB
        29. shardB-2.2018-05-04T09-16-01.log.gz
          6 kB
        30. shardB-2.2018-05-04T09-17-13.log.gz
          6 kB
        31. shardB-3.2018-05-04T09-09-17.log.gz
          4 kB
        32. shardB-3.2018-05-04T09-15-47.log.gz
          4 kB

            Assignee:
            mira.carey@mongodb.com Mira Carey
            Reporter:
            tim.olsen@mongodb.com Timothy Olsen (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            10 Start watching this issue

              Created:
              Updated:
              Resolved: