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

Improve storage engine logging at startup to include additional failure information

    • Type: Icon: Improvement Improvement
    • Resolution: Duplicate
    • Priority: Icon: Minor - P4 Minor - P4
    • None
    • Affects Version/s: 3.2.10
    • Component/s: WiredTiger
    • None
    • Storage NYC 2018-07-02, Storage NYC 2018-07-16

      I've encountered the following in on a test system running 3.2.10 on Windows:

      2017-01-26T11:07:37.724-0500 I CONTROL  [main] ***** SERVER RESTARTED *****
      2017-01-26T11:07:37.729-0500 I CONTROL  [main] Hotfix KB2731284 or later update is not installed, will zero-out data files
      2017-01-26T11:07:37.729-0500 I CONTROL  [initandlisten] MongoDB starting : pid=7856 port=27200 dbpath=C:\ProgramData\Connexion.Integrator\Mongo 64-bit host=D0077-IMP-UMY
      2017-01-26T11:07:37.729-0500 I CONTROL  [initandlisten] targetMinOS: Windows Vista/Windows Server 2008
      2017-01-26T11:07:37.729-0500 I CONTROL  [initandlisten] db version v3.2.10
      2017-01-26T11:07:37.729-0500 I CONTROL  [initandlisten] git version: 79d9b3ab5ce20f51c272b4411202710a082d0317
      2017-01-26T11:07:37.729-0500 I CONTROL  [initandlisten] allocator: tcmalloc
      2017-01-26T11:07:37.729-0500 I CONTROL  [initandlisten] modules: none
      2017-01-26T11:07:37.729-0500 I CONTROL  [initandlisten] build environment:
      2017-01-26T11:07:37.729-0500 I CONTROL  [initandlisten]     distarch: x86_64
      2017-01-26T11:07:37.729-0500 I CONTROL  [initandlisten]     target_arch: x86_64
      2017-01-26T11:07:37.729-0500 I CONTROL  [initandlisten] options: { config: "C:\ProgramData\Connexion.Integrator\Conf\mongo.config", net: { bindIp: "127.0.0.1", port: 27200 }, storage: { dbPath: "C:\ProgramData\Connexion.Integrator\Mongo", engine: "wiredTiger", journal: { enabled: true }, wiredTiger: { collectionConfig: { blockCompressor: "zlib" }, engineConfig: { cacheSizeGB: 1, journalCompressor: "zlib" } } }, systemLog: { destination: "file", logAppend: true, path: "C:\ProgramData\Connexion.Integrator\Logs\mongo.log", quiet: true, timeStampFormat: "iso8601-local" } }
      2017-01-26T11:07:37.729-0500 W -        [initandlisten] Detected unclean shutdown - C:\ProgramData\Connexion.Integrator\Mongo\mongod.lock is not empty.
      2017-01-26T11:07:37.730-0500 W STORAGE  [initandlisten] Recovering data from the last clean checkpoint.
      2017-01-26T11:07:37.730-0500 I STORAGE  [initandlisten] wiredtiger_open config: create,cache_size=1G,session_max=20000,eviction=(threads_max=4),config_base=false,statistics=(fast),log=(enabled=true,archive=true,path=journal,compressor=zlib),file_manager=(close_idle_time=100000),checkpoint=(wait=60,log_size=2GB),statistics_log=(wait=0),
      2017-01-26T11:07:37.731-0500 I -        [initandlisten] Assertion: 28595:2: No such file or directory
      2017-01-26T11:07:37.731-0500 I STORAGE  [initandlisten] exception in initAndListen: 28595 2: No such file or directory, terminating
      2017-01-26T11:07:37.731-0500 I CONTROL  [initandlisten] dbexit:  rc: 100
      

      All the folders listed exist and are writeable, and none are locked. Clearly there has been an "unclean shutdown" which has caused some corruption - but it's difficult to know what the proper action would be in this case:

      Restore from backup, clear mongo.lock etc.

      If possible, additional logging information here would be appreciated.

            Assignee:
            xiangyu.yao@mongodb.com Xiangyu Yao (Inactive)
            Reporter:
            nick@innsenroute.com Nick Judson
            Votes:
            0 Vote for this issue
            Watchers:
            6 Start watching this issue

              Created:
              Updated:
              Resolved: