[SERVER-31996] Couldn't start the mongo config server Created: 16/Nov/17  Updated: 27/Jul/18  Resolved: 01/Dec/17

Status: Closed
Project: Core Server
Component/s: WiredTiger
Affects Version/s: 3.2.9
Fix Version/s: None

Type: Bug Priority: Major - P3
Reporter: Prinsha Tom Assignee: Mark Agarunov
Resolution: Incomplete Votes: 0
Labels: envns, rns, rpns, wtc
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Operating System: Linux
Participants:

 Description   

Couldn't start the mongo config server.

Please find the log below,

2017-11-16T05:41:53.269-0500 I CONTROL  [initandlisten] MongoDB starting : pid=6136 port=27018 dbpath=/data/configRS_22 64-bit host=xspl50c343x.pharma.aventis.com
2017-11-16T05:41:53.269-0500 I CONTROL  [initandlisten] db version v3.2.9
2017-11-16T05:41:53.269-0500 I CONTROL  [initandlisten] git version: 22ec9e93b40c85fc7cae7d56e7d6a02fd811088c
2017-11-16T05:41:53.269-0500 I CONTROL  [initandlisten] OpenSSL version: OpenSSL 1.0.1e-fips 11 Feb 2013
2017-11-16T05:41:53.269-0500 I CONTROL  [initandlisten] allocator: tcmalloc
2017-11-16T05:41:53.269-0500 I CONTROL  [initandlisten] modules: none
2017-11-16T05:41:53.269-0500 I CONTROL  [initandlisten] build environment:
2017-11-16T05:41:53.269-0500 I CONTROL  [initandlisten]     distmod: rhel62
2017-11-16T05:41:53.269-0500 I CONTROL  [initandlisten]     distarch: x86_64
2017-11-16T05:41:53.269-0500 I CONTROL  [initandlisten]     target_arch: x86_64
2017-11-16T05:41:53.269-0500 I CONTROL  [initandlisten] options: { config: "/etc/mongod.conf", net: { port: 27018 }, processManagement: { fork: true }, replication: { replSetName: "configRS" }, sharding: { clusterRole: "configsvr" }, storage: { dbPath: "/data/configRS_22", engine: "wiredTiger" }, systemLog: { destination: "file", path: "/data/configRS_22/mongodb.log" } }
2017-11-16T05:41:53.297-0500 I STORAGE  [initandlisten] wiredtiger_open config: create,cache_size=8G,session_max=20000,eviction=(threads_max=4),config_base=false,statistics=(fast),log=(enabled=true,archive=true,path=journal,compressor=snappy),file_manager=(close_idle_time=100000),checkpoint=(wait=60,log_size=2GB),statistics_log=(wait=0),
2017-11-16T05:41:53.308-0500 E STORAGE  [initandlisten] WiredTiger (-31802) [1510828913:308822][6136:0x7f783c6e6d40], connection: Bad log file name 'WiredTigerPreplog.0000000005.gz': WT_ERROR: non-specific WiredTiger error
2017-11-16T05:41:53.310-0500 I -        [initandlisten] Assertion: 28595:-31802: WT_ERROR: non-specific WiredTiger error
2017-11-16T05:41:53.310-0500 I STORAGE  [initandlisten] exception in initAndListen: 28595 -31802: WT_ERROR: non-specific WiredTiger error, terminating
2017-11-16T05:41:53.310-0500 I CONTROL  [initandlisten] dbexit:  rc: 100

Please assist, Thanks in advance.



 Comments   
Comment by Mark Agarunov [ 01/Dec/17 ]

Hello tom.tommy089@gmail.com,

We haven’t heard back from you for some time, so I’m going to mark this ticket as resolved. If this is still an issue for you, please provide additional information and we will reopen the ticket.

Thanks,
Mark

Comment by Mark Agarunov [ 16/Nov/17 ]

Hello tom.tommy089@gmail.com,

Thank you for the report. To help us understand what's going on here, I've assembled a list of routine questions about data storage and the configuration of your environment. We can use this to begin debugging the underlying issue, but beware in these sorts of situations it can be difficult to understand the cause of the corruption without a straightforward reproduction.

  1. What kind of underlying storage mechanism are you using? Are the storage devices attached locally or over the network? Are the disks SSDs or HDDs? What kind of RAID and/or volume management system are you using?
  2. Would you please check the integrity of your disks?
  3. Has the database always been running this version of MongoDB? If not please describe the upgrade/downgrade cycles the database has been through.
  4. Have you manipulated (copied or moved) the underlying database files? If so, was mongod running?
  5. Have you ever restored this instance from backups?
  6. What method do you use to create backups?
  7. When was the underlying filesystem last checked and is it currently marked clean?

Thanks,
Mark

Generated at Thu Feb 08 04:28:51 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.