[SERVER-42072] Server refusing to come up (with possible data issues) Created: 03/Jul/19  Updated: 29/Jul/19  Resolved: 29/Jul/19

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

Type: Bug Priority: Major - P3
Reporter: Dharshan Rangegowda Assignee: Danny Hatcher (Inactive)
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: Zip Archive data.zip    
Operating System: ALL
Participants:

 Description   

MongoDB server is not coming up during restart. The logs and data files are attached

 

2019-07-02T08:14:49.548+0000 I CONTROL [main] ***** SERVER RESTARTED *****
2019-07-02T08:14:49.573+0000 I CONTROL [initandlisten] MongoDB starting : pid=3901 port=27017 dbpath=/mongodb_data 64-bit host=vm74861095d3
2019-07-02T08:14:49.573+0000 I CONTROL [initandlisten] db version v4.0.1
2019-07-02T08:14:49.573+0000 I CONTROL [initandlisten] git version: 54f1582fc6eb01de4d4c42f26fc133e623f065fb
2019-07-02T08:14:49.573+0000 I CONTROL [initandlisten] OpenSSL version: OpenSSL 1.0.1e-fips 11 Feb 2013
2019-07-02T08:14:49.573+0000 I CONTROL [initandlisten] allocator: tcmalloc
2019-07-02T08:14:49.573+0000 I CONTROL [initandlisten] modules: none
2019-07-02T08:14:49.573+0000 I CONTROL [initandlisten] build environment:
2019-07-02T08:14:49.573+0000 I CONTROL [initandlisten] distmod: rhel62
2019-07-02T08:14:49.573+0000 I CONTROL [initandlisten] distarch: x86_64
2019-07-02T08:14:49.573+0000 I CONTROL [initandlisten] target_arch: x86_64
2019-07-02T08:14:49.573+0000 I CONTROL [initandlisten] options: { config: "/etc/mongod.conf", net: { bindIp: "0.0.0.0", port: 27017, ssl:

{ PEMKeyFile: "/etc/ssl/mongodb.pem", allowInvalidCertificates: true, allowInvalidHostnames: true, mode: "requireSSL" }

}, processManagement: { fork: true, pidFilePath: "/var/run/mongodb/mongod.pid" }, security: { authorization: "enabled" }, storage: { dbPath: "/mongodb_data", engine: "wiredTiger", journal:

{ enabled: true }

, wiredTiger: { collectionConfig:

{ blockCompressor: "none" }

} }, systemLog: { destination: "file", logAppend: true, path: "/var/log/mongodb/mongod.log" } }
2019-07-02T08:14:49.645+0000 I STORAGE [initandlisten] wiredtiger_open config: create,cache_size=256M,session_max=20000,eviction=(threads_min=4,threads_max=4),config_base=false,statistics=(fast),log=(enabled=true,archive=true,path=journal,compressor=snappy),file_manager=(close_idle_time=100000),statistics_log=(wait=0),verbose=(recovery_progress),
2019-07-02T08:14:51.056+0000 I STORAGE [initandlisten] WiredTiger message [1562055291:56230][3901:0x7f1cdb04ea60], txn-recover: Main recovery loop: starting at 8/41216
2019-07-02T08:14:51.056+0000 I STORAGE [initandlisten] WiredTiger message [1562055291:56687][3901:0x7f1cdb04ea60], txn-recover: Recovering log 8 through 9
2019-07-02T08:14:51.523+0000 I STORAGE [initandlisten] WiredTiger message [1562055291:523216][3901:0x7f1cdb04ea60], file:collection-12--1784503479178086004.wt, txn-recover: Recovering log 9 through 9
2019-07-02T08:14:51.589+0000 I STORAGE [initandlisten] WiredTiger message [1562055291:589212][3901:0x7f1cdb04ea60], file:collection-12--1784503479178086004.wt, txn-recover: Set global recovery timestamp: 5d1b05cc00000001
2019-07-02T08:14:51.661+0000 I RECOVERY [initandlisten] WiredTiger recoveryTimestamp. Ts: Timestamp(1562052044, 1)
2019-07-02T08:14:51.661+0000 I STORAGE [initandlisten] Triggering the first stable checkpoint. Initial Data: Timestamp(1562052044, 1) PrevStable: Timestamp(0, 0) CurrStable: Timestamp(1562052044, 1)
2019-07-02T08:14:52.495+0000 I STORAGE [initandlisten] Starting WiredTigerRecordStoreThread local.oplog.rs
2019-07-02T08:14:52.496+0000 I STORAGE [initandlisten] The size storer reports that the oplog contains 182 records totaling to 20587 bytes
2019-07-02T08:14:52.496+0000 I STORAGE [initandlisten] Scanning the oplog to determine where to place markers for truncation
2019-07-02T08:14:53.100+0000 F - [initandlisten] Fatal Assertion 34433 at src/mongo/db/storage/wiredtiger/wiredtiger_record_store.cpp 637
2019-07-02T08:14:53.100+0000 F - [initandlisten]

***aborting after fassert() failure



 Comments   
Comment by Danny Hatcher (Inactive) [ 29/Jul/19 ]

Closing due to lack of response.

Comment by Danny Hatcher (Inactive) [ 08/Jul/19 ]

Hello Dharshan,

Could you please download the 4.0.10 binaries and use them to start the server with the --repair flag? We've made improvements to the repair process in 4.0.10 that may resolve this issue.

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