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

mongo services on stopping gives Error 109 : Pipe has been ended

    • Type: Icon: Bug Bug
    • Resolution: Duplicate
    • Priority: Icon: Critical - P2 Critical - P2
    • None
    • Affects Version/s: 2.2.1
    • Component/s: Admin, Tools
    • Environment:
      WIndows 2008 R2 x64
    • Windows
    • Hide

      1- install the windows service for mongod using the following command
      mongod.exe --config "C:\mongo\conf\config.properties" --serviceName mdb27017 --serviceDisplayName "Mongo Instance 27017" --serviceDescription "MongoDB Instance running on 27017" --install
      2- start the service in Services MMC
      3- try stopping the services and you will the issue

      Show
      1- install the windows service for mongod using the following command mongod.exe --config "C:\mongo\conf\config.properties" --serviceName mdb27017 --serviceDisplayName "Mongo Instance 27017" --serviceDescription "MongoDB Instance running on 27017" --install 2- start the service in Services MMC 3- try stopping the services and you will the issue

      I installed mongo service from command line using mongod --install

      but when i am stopping the mongodb service it gives the Error 109: :Pipe has been ended
      PFA for screen capture on stopping service

      I analyzed the logs i found that mongo service is stopping fine.
      following are the logs at time of stopping it

      Fri Nov 23 12:10:04 [TTLMonitor] query test.system.indexes query: { expireAfterSeconds:

      { $exists: true }

      } ntoreturn:0 keyUpdates:0 locks(micros) r:38 nreturned:0 reslen:20 0ms
      Fri Nov 23 12:10:10 [serviceShutdown] got SERVICE_CONTROL_STOP request from Windows Service Control Manager, will terminate after current cmd ends
      Fri Nov 23 12:10:10 [serviceShutdown] now exiting
      Fri Nov 23 12:10:10 dbexit:
      Fri Nov 23 12:10:10 [serviceShutdown] shutdown: going to close listening sockets...
      Fri Nov 23 12:10:10 [serviceShutdown] closing listening socket: 344
      Fri Nov 23 12:10:10 [serviceShutdown] closing listening socket: 356
      Fri Nov 23 12:10:10 [serviceShutdown] shutdown: going to flush diaglog...
      Fri Nov 23 12:10:10 [serviceShutdown] shutdown: going to close sockets...
      Fri Nov 23 12:10:10 [serviceShutdown] shutdown: waiting for fs preallocator...
      Fri Nov 23 12:10:10 [serviceShutdown] shutdown: lock for final commit...
      Fri Nov 23 12:10:10 [serviceShutdown] shutdown: final commit...
      Fri Nov 23 12:10:10 [serviceShutdown] shutdown: closing all files...
      Fri Nov 23 12:10:10 [serviceShutdown] closeAllFiles() finished
      Fri Nov 23 12:10:10 [serviceShutdown] journalCleanup...
      Fri Nov 23 12:10:10 [serviceShutdown] removeJournalFiles
      Fri Nov 23 12:10:10 [serviceShutdown] removeJournalFiles end
      Fri Nov 23 12:10:10 [serviceShutdown] shutdown: removing fs lock...
      Fri Nov 23 12:10:10 [initandlisten] now exiting
      Fri Nov 23 12:10:10 dbexit: ; exiting immediately

            Assignee:
            Unassigned Unassigned
            Reporter:
            ajduke Abhijeet
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: