[SERVER-41647] not able to see data Created: 12/Jun/19  Updated: 15/Nov/21  Resolved: 29/Jul/19

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

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

Participants:

 Description   

Hi Team,

Not able to see the data in database but exist in data directory. 

the sequence of getting error is as per below,

*2019-06-12T16:21:51.518+0530 I CONTROL [conn14940] Stack trace failed, SymInitialize failed with error 3765269347*
*2019-06-12T16:21:51.518+0530 F - [conn14940] out of memory.*

 

After that we start database service manually then we got below error,

 

 

2019-06-12T17:00:32.499+0530 I CONTROL [main] Trying to start Windows service 'MongoDB'
2019-06-12T17:00:32.500+0530 I STORAGE [thread1] Service running
2019-06-12T17:00:32.500+0530 I CONTROL [initandlisten] MongoDB starting : pid=15672 port=27017 dbpath=D:\MongoDBData\QA\data 64-bit host=vitmumrec01
2019-06-12T17:00:32.501+0530 I CONTROL [initandlisten] targetMinOS: Windows 7/Windows Server 2008 R2
2019-06-12T17:00:32.501+0530 I CONTROL [initandlisten] db version v3.2.1
2019-06-12T17:00:32.501+0530 I CONTROL [initandlisten] git version: a14d55980c2cdc565d4704a7e3ad37e4e535c1b2
2019-06-12T17:00:32.501+0530 I CONTROL [initandlisten] OpenSSL version: OpenSSL 1.0.1p-fips 9 Jul 2015
2019-06-12T17:00:32.501+0530 I CONTROL [initandlisten] allocator: tcmalloc
2019-06-12T17:00:32.501+0530 I CONTROL [initandlisten] modules: enterprise 
2019-06-12T17:00:32.501+0530 I CONTROL [initandlisten] build environment:
2019-06-12T17:00:32.501+0530 I CONTROL [initandlisten] distmod: windows-64
2019-06-12T17:00:32.501+0530 I CONTROL [initandlisten] distarch: x86_64
2019-06-12T17:00:32.501+0530 I CONTROL [initandlisten] target_arch: x86_64
2019-06-12T17:00:32.501+0530 I CONTROL [initandlisten] options: \{ config: "C:\MongoConfig\QAMongodb.conf", net: { port: 27017 }, service: true, storage: \{ dbPath: "D:\MongoDBData\QA\data", directoryPerDB: false, wiredTiger: { engineConfig: { cacheSizeGB: 2 } } }, systemLog: \{ destination: "file", path: "D:\MongoDBData\QA\log\mongod.log" } }
2019-06-12T17:00:32.509+0530 I - [initandlisten] Detected data files in D:\MongoDBData\QA\data created by the 'wiredTiger' storage engine, so setting the active storage engine to 'wiredTiger'.
2019-06-12T17:00:32.510+0530 W - [initandlisten] Detected unclean shutdown - D:\MongoDBData\QA\data\mongod.lock is not empty.
2019-06-12T17:00:32.510+0530 W STORAGE [initandlisten] Recovering data from the last clean checkpoint.
2019-06-12T17:00:32.511+0530 I STORAGE [initandlisten] wiredtiger_open config: create,cache_size=2G,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),
*2019-06-12T17:00:33.363+0530 I NETWORK [HostnameCanonicalizationWorker] Starting hostname canonicalization worker*
*2019-06-12T17:00:33.364+0530 I FTDC [initandlisten] Initializing full-time diagnostic data capture with directory 'D:/MongoDBData/QA/data/diagnostic.data'*
2019-06-12T17:00:33.411+0530 I NETWORK [initandlisten] waiting for connections on port 27017
2019-06-12T17:00:33.422+0530 I NETWORK [initandlisten] connection accepted from 192.168.172.83:58350 #1 (1 connection now open)
2019-06-12T17:00:33.554+0530 I NETWORK [initandlisten] connection accepted from 192.168.170.158:51257 #2 (2 connections now open)
2019-06-12T17:00:33.642+0530 I NETWORK [initandlisten] connection accepted from 192.168.170.158:51258 #3 (3 connections now open)
2019-06-12T17:00:33.644+0530 I NETWORK [initandlisten] connection accepted from 192.168.172.53:55822 #4 (4 connections now open)
2019-06-12T17:00:33.662+0530 I NETWORK [initandlisten] connection accepted from 192.168.170.158:51259 #5 (5 connections now open)
2019-06-12T17:00:33.886+0530 I NETWORK [initandlisten] connection accepted from 10.1.75.31:57344 #6 (6 connections now open)
*2019-06-12T17:00:34.026+0530 I FTDC [ftdc] Unclean full-time diagnostic data capture shutdown detected, found interim file, some metrics may have been lost. OK*
*2019-06-12T17:00:34.125+0530 W FTDC [ftdc] Uncaught exception in 'UnknownError Caught std::exception of type class boost::filesystem::filesystem_error: boost::filesystem::file_size: The system cannot find the file specified: "D:\MongoDBData\QA\data\diagnostic.data\metrics.interim.temp"' in full-time diagnostic data capture subsystem. Shutting down the full-time diagnostic data capture subsystem.*

 

 

After this we take down the database and fire mongod --Repair with data directory and logpath, still not able to see data in mongo shell which exist in data directory.

 

Kindly help in recover the data. If require any info will provide you.



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

Closing due to lack of response.

Comment by Danny Hatcher (Inactive) [ 21/Jun/19 ]

Can you try upgrading to MongoDB 3.4.21 and see if you can access the data? If that doesn't work, unfortunately there's not much else we can do. We strongly recommend utilizing a replica set for any important data in order to avoid situations like this.

Comment by Yogesh Jadhav [ 19/Jun/19 ]

The data is present in dataDirectory but we are not able to see all databases except one of them via mongo shell, yesterday I was trying to take full dump but dump got complete with only one Database

Comment by Danny Hatcher (Inactive) [ 18/Jun/19 ]

I do not actually see a data-related error in the logs. The snippet you linked in the original description shows our background diagnostic system failing but that does not affect any of your data.

Can you please confirm what you mean when you say that you can't "see" your data? Can you not see any database / collections at all? Can you see some information but not all of it?

Comment by Yogesh Jadhav [ 18/Jun/19 ]

Hi Danial,

 

For your reference I have uploaded Logs which are covering the original shutdown until now Kindly Help....

Logs are in rar format named as MongoLogs.

Comment by Danny Hatcher (Inactive) [ 14/Jun/19 ]

Hello,

In order for us to see what went wrong, could you please upload the complete mongod logs from before the original shutdown until now to our Secure Upload Portal. Please rest assured that only MongoDB Engineers will be able to access the files.

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