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

mongod does not response after closing and starting windows service versions 3.4.0,3.4.1

XMLWordPrintableJSON

    • Type: Icon: Bug Bug
    • Resolution: Cannot Reproduce
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: 3.4.0, 3.4.1
    • Component/s: Admin
    • Labels:
    • ALL
    • Hide

      start a 3.4.1 mongod windows service.
      stop it. you will get an error as posted in SERVER-27782.
      restart the service.
      try to connect with the mongo shell.
      after 5 seconds you will get the message:
      2017-01-26T08:45:14.613+0200 W NETWORK [main] Failed to connect to xx.xx.xx.xxx:<port number> after 5000ms milliseconds, giving up.
      2017-01-26T08:45:14.620+0200 E QUERY [main] Error: couldn't connect to server <machine name>:<port number>, connection attempt failed :
      connect@src/mongo/shell/mongo.js:234:13
      @(connect):1:6
      exception: connect failed

      In order to successfully connect you will have to stop the service and restart it again

      Show
      start a 3.4.1 mongod windows service. stop it. you will get an error as posted in SERVER-27782 . restart the service. try to connect with the mongo shell. after 5 seconds you will get the message: 2017-01-26T08:45:14.613+0200 W NETWORK [main] Failed to connect to xx.xx.xx.xxx:<port number> after 5000ms milliseconds, giving up. 2017-01-26T08:45:14.620+0200 E QUERY [main] Error: couldn't connect to server <machine name>:<port number>, connection attempt failed : connect@src/mongo/shell/mongo.js:234:13 @(connect):1:6 exception: connect failed In order to successfully connect you will have to stop the service and restart it again

      On versions 3.4.0 and 3.4.1
      after stopping a mongod windows service and starting it again the mongod process does not respond.
      this happens also after a system shut down.
      I don't know if it relates to SERVER-6065 and or SERVER-27782 but it's a real problem.

      Needless to say that that situation prevents us from deploying our 3.4 solution.

        1. MongoShellFailedConnection.json
          27 kB
        2. MongoShellFailedConnection.pcapng
          5 kB
        3. mydblog.log
          2.12 MB
        4. mydblog.log
          2.02 MB
        5. mydblog.log
          1.48 MB
        6. mydblog.log
          1.27 MB
        7. mydblog.log.2017-03-12T12-16-34
          407 kB
        8. mydblog.log.2017-03-12T12-29-17
          696 kB
        9. mydblog.log.2017-03-14T10-03-20
          191 kB
        10. mydblog.log.2017-03-14T10-21-57
          4.06 MB
        11. mydblog.log.2017-03-14T11-36-51
          8.38 MB
        12. mydblog.log.2017-03-14T11-40-08
          1.38 MB

            Assignee:
            mark.benvenuto@mongodb.com Mark Benvenuto
            Reporter:
            itzikkg Itzhak Kagan
            Votes:
            2 Vote for this issue
            Watchers:
            11 Start watching this issue

              Created:
              Updated:
              Resolved: