[SERVER-9755]  15874:couldn't uncompress journal section [reopen] Created: 22/May/13  Updated: 10/Dec/14  Resolved: 26/Jun/14

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

Type: Bug Priority: Critical - P2
Reporter: ham.lee Assignee: Ramon Fernandez Marina
Resolution: Incomplete Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

CentOS release 5.9 (Final) 64


Operating System: ALL
Participants:

 Description   

Thu May 23 02:08:12.986 [initandlisten] recover begin
Thu May 23 02:08:12.986 [initandlisten] recover lsn: 5025215
Thu May 23 02:08:12.986 [initandlisten] recover /home/mongodb/db/QDWTB_DATA/journal/j._11
Thu May 23 02:08:12.986 [initandlisten] recover skipping application of section seq:4965384 < lsn:5025215
Thu May 23 02:08:14.778 [initandlisten] recover create file /home/mongodb/db/QDWTB_DATA/QDWTB.25 2047MB
Thu May 23 02:08:48.429 [initandlisten] couldn't uncompress journal section ...
Thu May 23 02:08:48.429 [initandlisten] Assertion: 15874:couldn't uncompress journal section
Thu May 23 02:08:48.434 [initandlisten] dbexception during recovery: 15874 couldn't uncompress journal section
Thu May 23 02:08:48.434 [initandlisten] exception in initAndListen: 15874 couldn't uncompress journal section, terminating
Thu May 23 02:08:48.434 dbexit:



 Comments   
Comment by Balint Szente [ 27/Jun/14 ]

Hello!

I also forgot about this issue. In the mean time we found out that the motherboard had design issues, and random reboots/freeze may occur if all the 4 DIMM slots are populated (see: http://forum.giga-byte.co.uk/index.php/topic,12563.0.html). So in my case the issue is solved and the HW was faulty.

Thanks,
Balint

Comment by Ramon Fernandez Marina [ 05/Jun/14 ]

All, looks like we let this ticket fall through the cracks – very sorry about that.

The logs indicate that the journal file got corrupted somehow; when the server encounters this situation, it errs on the side of caution and shuts itself down. A filesystem/disk error is the most likely culprit, but if there was a software error there's not enough information to track it down. In the case of the shutdown with poweroff, it seems that the init scripts did not shut down MongoDB properly, as there's no indication of a shutdown in the logs. While the goal of the journal is precisely to protect against this situation, it appears that the journal got corrupted during the OS shutdown; I would suggest reviewing the init scripts to make sure MongoDB is properly terminated during the OS shutdown process to protect against this situation.

Please let us know if there's something else we can help you with. Again, apologies for the late reply.

Regards,
Ramón.

Comment by Balint Szente [ 15/Jul/13 ]

I encountered the same issue. Here is the relevant part of the log.

...
Fri Jul 12 13:53:29 [conn2255] query hermess.data query: { _id: ObjectId('51df62433fdb8176d02deae5') } ntoreturn:1 idhack:1 reslen:1048640 102ms
Fri Jul 12 13:53:29 [conn2255] query hermess.data query: { _id: ObjectId('51df62553fdb8176d02debc7') } ntoreturn:1 idhack:1 reslen:1048640 116ms
Fri Jul 12 13:53:31 [conn2750] update hermess.data query: { _id: ObjectId('51dfe0273fdb8176d034060f') } update: { $set: { usage: 1048576 }, $set: { data: BinData } } idhack:1 1311ms
Fri Jul 12 13:53:31 [initandlisten] connection accepted from 127.0.0.1:53417 #2751
Fri Jul 12 13:53:31 [conn2751]  authenticate: { authenticate: 1, nonce: "8f56bb9a971c8cd2", user: "hermess", key: "15107af46ae0afd03ff92a9318e97643" }
Fri Jul 12 13:53:31 [initandlisten] connection accepted from 127.0.0.1:53418 #2752
Fri Jul 12 13:53:31 [conn2752]  authenticate: { authenticate: 1, nonce: "e6e97ba165d6d685", user: "hermess", key: "cd0f5b424e6c454b090e2ee42e32757e" }
Fri Jul 12 13:53:31 [initandlisten] connection accepted from 127.0.0.1:53419 #2753
Fri Jul 12 13:53:31 [conn2753]  authenticate: { authenticate: 1, nonce: "7e0f88c4e65a052f", user: "hermess", key: "d06c391907866c9c48f2733fa436c900" }
Fri Jul 12 13:53:31 [conn2738] end connection 127.0.0.1:53404
Fri Jul 12 13:53:31 [conn2750] end connection 127.0.0.1:53416
Fri Jul 12 13:53:31 [initandlisten] connection accepted from 127.0.0.1:53420 #2754
Fri Jul 12 13:53:31 [conn2754]  authenticate: { authenticate: 1, nonce: "4ff24a785fc9f431", user: "hermess", key: "6900d7258ddc290c43648c32192f07f8" }
Fri Jul 12 13:53:31 [conn2751] end connection 127.0.0.1:53417
Fri Jul 12 13:53:31 [initandlisten] connection accepted from 127.0.0.1:53421 #2755
Fri Jul 12 13:53:31 [conn2755]  authenticate: { authenticate: 1, nonce: "278835b40951e0e2", user: "hermess", key: "ddaf5908b1e4455253fd9c5ddde5b180" }
Fri Jul 12 13:53:31 [initandlisten] connection accepted from 127.0.0.1:53422 #2756
Fri Jul 12 13:53:31 [conn2756]  authenticate: { authenticate: 1, nonce: "6f033a47118dadea", user: "hermess", key: "e936385ca777661098605487ad152fd3" }
Fri Jul 12 13:53:31 [conn2733] end connection 127.0.0.1:53399
Fri Jul 12 13:53:31 [conn2752] end connection 127.0.0.1:53418
Fri Jul 12 13:53:31 [initandlisten] connection accepted from 127.0.0.1:53423 #2757
Fri Jul 12 13:53:31 [conn2757]  authenticate: { authenticate: 1, nonce: "43f82aa827610162", user: "hermess", key: "4e1a2431e0d74a3f80b7733004e25d04" }
Fri Jul 12 13:53:31 [initandlisten] connection accepted from 127.0.0.1:53424 #2758
Fri Jul 12 13:53:31 [conn2755] end connection 127.0.0.1:53421
Fri Jul 12 13:53:31 [conn2758]  authenticate: { authenticate: 1, nonce: "a5314733d4088787", user: "hermess", key: "501787f4c9e62fef125f72ad7a3ca58b" }
Fri Jul 12 13:53:31 [conn2754] end connection 127.0.0.1:53420
Fri Jul 12 13:53:31 [initandlisten] connection accepted from 127.0.0.1:53425 #2759
Fri Jul 12 13:53:31 [conn2759]  authenticate: { authenticate: 1, nonce: "fec9259c51db5ccf", user: "hermess", key: "6c02d089cbc706fc47ed4222c7d662b6" }
Fri Jul 12 13:53:31 [conn2757] end connection 127.0.0.1:53423
Fri Jul 12 13:53:31 [initandlisten] connection accepted from 127.0.0.1:53426 #2760
Fri Jul 12 13:53:31 [conn2760]  authenticate: { authenticate: 1, nonce: "bae1999ada4262da", user: "hermess", key: "4a7cc545db86af19cf618883af8e3c07" }
Fri Jul 12 13:53:31 [initandlisten] connection accepted from 127.0.0.1:53427 #2761
Fri Jul 12 13:53:31 [conn2761]  authenticate: { authenticate: 1, nonce: "1d077d2a8b82a712", user: "hermess", key: "0b23537f9aa90c7542a297d8ba9eb023" }
Fri Jul 12 13:53:31 [conn2756] end connection 127.0.0.1:53422
Fri Jul 12 13:53:31 [initandlisten] connection accepted from 127.0.0.1:53428 #2762
Fri Jul 12 13:53:31 [conn2762]  authenticate: { authenticate: 1, nonce: "b464f630ac437b50", user: "hermess", key: "cb547ecd382e324ddccd4be478e7ffa3" }
Fri Jul 12 13:53:31 [conn2759] end connection 127.0.0.1:53425
Fri Jul 12 13:53:31 [initandlisten] connection accepted from 127.0.0.1:53429 #2763
Fri Jul 12 13:53:31 [conn2763]  authenticate: { authenticate: 1, nonce: "349f6ded2c97dfeb", user: "hermess", key: "c121318838dae30377e780b15d372c93" }
Fri Jul 12 13:53:31 [conn2753] end connection 127.0.0.1:53419
Fri Jul 12 13:53:31 [initandlisten] connection accepted from 127.0.0.1:53430 #2764
Fri Jul 12 13:53:31 [conn2764]  authenticate: { authenticate: 1, nonce: "4ded12a042945927", user: "hermess", key: "c90b778e3c955908e50dc37b0c412139" }
Fri Jul 12 13:53:31 [conn2761] end connection 127.0.0.1:53427
Fri Jul 12 13:53:31 [initandlisten] connection accepted from 127.0.0.1:53431 #2765
Fri Jul 12 13:53:31 [conn2765]  authenticate: { authenticate: 1, nonce: "3f240d1c77bf9ba8", user: "hermess", key: "7d48f665769dc1ea463f7d7d887e481c" }
Fri Jul 12 13:53:31 [conn2762] end connection 127.0.0.1:53428
Fri Jul 12 13:53:31 [conn2758] end connection 127.0.0.1:53424
Fri Jul 12 13:53:31 [conn2763] end connection 127.0.0.1:53429
Fri Jul 12 13:53:31 [initandlisten] connection accepted from 127.0.0.1:53432 #2766
Fri Jul 12 13:53:31 [conn2766]  authenticate: { authenticate: 1, nonce: "1305d1bcf6ba2a5c", user: "hermess", key: "567c8a7928f629c7b8d2d1d687036283" }
Fri Jul 12 13:53:31 [conn2765] end connection 127.0.0.1:53431
Fri Jul 12 13:53:31 [initandlisten] connection accepted from 127.0.0.1:53433 #2767
Fri Jul 12 13:53:31 [conn2767]  authenticate: { authenticate: 1, nonce: "5dc76192e0f20de9", user: "hermess", key: "3ebd60752bdea83bbc88ee72bf0e4361" }
Fri Jul 12 13:53:31 [conn2739] end connection 127.0.0.1:53405
Fri Jul 12 13:53:31 [initandlisten] connection accepted from 127.0.0.1:53434 #2768
Fri Jul 12 13:53:31 [conn2768]  authenticate: { authenticate: 1, nonce: "d06b41c530a9361a", user: "hermess", key: "1ccbcb9c2816907e874e65073375c7f4" }
Fri Jul 12 13:53:31 [initandlisten] connection accepted from 127.0.0.1:53435 #2769
Fri Jul 12 13:53:31 [conn2769]  authenticate: { authenticate: 1, nonce: "f545e17cb967824b", user: "hermess", key: "dde61c44d95acd2c733011eee18c7179" }
Fri Jul 12 13:53:31 [conn2767] end connection 127.0.0.1:53433
Fri Jul 12 13:53:31 [conn2606] end connection 127.0.0.1:53272
Fri Jul 12 13:53:31 [initandlisten] connection accepted from 127.0.0.1:53436 #2770
Fri Jul 12 13:53:31 [conn2770]  authenticate: { authenticate: 1, nonce: "c3639a495918352e", user: "hermess", key: "0efb658b20a8e96073c84f157a699e04" }
Fri Jul 12 13:53:31 [conn2764] end connection 127.0.0.1:53430
Fri Jul 12 13:53:35 [FileAllocator] allocating new datafile /mnt/storage/mongodb/hermess.318, filling with zeroes...
Fri Jul 12 13:53:35 [FileAllocator] done allocating datafile /mnt/storage/mongodb/hermess.318, size: 2047MB,  took 0.158 secs
Fri Jul 12 13:53:39 [conn2255] query hermess.data query: { _id: ObjectId('51df643a3fdb8176d02e041b') } ntoreturn:1 idhack:1 reslen:1048640 237ms
Fri Jul 12 13:53:40 [conn2255] query hermess.data query: { _id: ObjectId('51df643d3fdb8176d02e043b') } ntoreturn:1 idhack:1 reslen:1048640 392ms
Fri Jul 12 13:53:43 [conn2255] query hermess.data query: { _id: ObjectId('51df64a03fdb8176d02e0939') } ntoreturn:1 idhack:1 reslen:1048640 104ms
Fri Jul 12 13:53:45 [conn2255] query hermess.data query: { _id: ObjectId('51df65133fdb8176d02e0ef9') } ntoreturn:1 idhack:1 reslen:1048640 107ms
Fri Jul 12 13:53:49 [journal] old journal file will be removed: /mnt/storage/mongodb/journal/j._1097
Fri Jul 12 13:53:49 [journal] old journal file will be removed: /mnt/storage/mongodb/journal/j._1098
Fri Jul 12 13:53:49 [journal] DR101 latency warning on journal file open 251ms
Fri Jul 12 13:53:58 [conn2255] query hermess.data query: { _id: ObjectId('51df684d3fdb8176d02e3823') } ntoreturn:1 idhack:1 reslen:1048640 229ms
Fri Jul 12 13:53:59 [conn2255] query hermess.data query: { _id: ObjectId('51df688f3fdb8176d02e3b63') } ntoreturn:1 idhack:1 reslen:1048640 101ms
Fri Jul 12 13:54:00 [conn2255] query hermess.data query: { _id: ObjectId('51df68a03fdb8176d02e3c41') } ntoreturn:1 idhack:1 reslen:1048640 327ms
Fri Jul 12 13:54:01 [conn2255] query hermess.data query: { _id: ObjectId('51df68ee3fdb8176d02e4023') } ntoreturn:1 idhack:1 reslen:1048640 132ms
Fri Jul 12 13:54:01 [conn2255] query hermess.data query: { _id: ObjectId('51df68f13fdb8176d02e4041') } ntoreturn:1 idhack:1 reslen:1048640 115ms
Fri Jul 12 13:54:01 [conn2255] query hermess.data query: { _id: ObjectId('51df68f93fdb8176d02e40a1') } ntoreturn:1 idhack:1 reslen:1048640 238ms
Fri Jul 12 13:54:02 [conn2255] query hermess.data query: { _id: ObjectId('51df69263fdb8176d02e42e1') } ntoreturn:1 idhack:1 reslen:1048640 336ms
Fri Jul 12 13:54:02 [conn2255] query hermess.data query: { _id: ObjectId('51df692b3fdb8176d02e431f') } ntoreturn:1 idhack:1 reslen:1048640 136ms
Fri Jul 12 13:54:04 [conn2255] query hermess.data query: { _id: ObjectId('51df692d3fdb8176d02e433b') } ntoreturn:1 idhack:1 reslen:1048640 162ms
Fri Jul 12 13:54:04 [conn2255] query hermess.data query: { _id: ObjectId('51df69323fdb8176d02e437f') } ntoreturn:1 idhack:1 reslen:1048640 121ms
 
 
***** SERVER RESTARTED *****
 
 
Fri Jul 12 18:32:09 [initandlisten] MongoDB starting : pid=2286 port=27017 dbpath=/mnt/storage/mongodb 64-bit host=koios
Fri Jul 12 18:32:09 [initandlisten] db version v2.0.6, pdfile version 4.5
Fri Jul 12 18:32:09 [initandlisten] git version: nogitversion
Fri Jul 12 18:32:09 [initandlisten] build info: Linux z6 3.8-trunk-amd64 #1 SMP Debian 3.8.3-1~experimental.1 x86_64 BOOST_LIB_VERSION=1_49
Fri Jul 12 18:32:09 [initandlisten] options: { auth: "true", bind_ip: "127.0.0.1", command: [ "run" ], config: "/etc/mongodb.conf", dbpath: "/mnt/storage/mongodb", journal: "true", logappend: "true", logpath: "/var/log/mongodb/mongodb.log", quota: "true", quotaFiles: 4050, unixSocketPrefix: "/var/run/mongodb" }
Fri Jul 12 18:32:09 [initandlisten] journal dir=/mnt/storage/mongodb/journal
Fri Jul 12 18:32:09 [initandlisten] recover begin
Fri Jul 12 18:32:09 [initandlisten] recover lsn: 85767561
Fri Jul 12 18:32:09 [initandlisten] recover /mnt/storage/mongodb/journal/j._1099
Fri Jul 12 18:32:17 [initandlisten] couldn't uncompress journal section
Fri Jul 12 18:32:17 [initandlisten] Assertion: 15874:couldn't uncompress journal section
0x5d74b3 0x5ddcd9 0x72ec0d 0x72d16e 0x72d3e9 0x72d7d2 0x72da6e 0x72e494 0x72e887 0x724de4 0x8d1365 0x8d22d8 0x58f02c 0x7f5dc9cdaead 0x58f8e9 
 /usr/bin/mongod(_ZN5mongo15printStackTraceERSo+0x23) [0x5d74b3]
 /usr/bin/mongod(_ZN5mongo11msgassertedEiPKc+0xb9) [0x5ddcd9]
 /usr/bin/mongod() [0x72ec0d]
 /usr/bin/mongod(_ZN5mongo3dur11RecoveryJob14processSectionEPKNS0_11JSectHeaderEPKvjPKNS0_11JSectFooterE+0x28e) [0x72d16e]
 /usr/bin/mongod(_ZN5mongo3dur11RecoveryJob17processFileBufferEPKvj+0x129) [0x72d3e9]
 /usr/bin/mongod(_ZN5mongo3dur11RecoveryJob11processFileEN5boost11filesystem210basic_pathISsNS3_11path_traitsEEE+0xd2) [0x72d7d2]
 /usr/bin/mongod(_ZN5mongo3dur11RecoveryJob2goERSt6vectorIN5boost11filesystem210basic_pathISsNS4_11path_traitsEEESaIS7_EE+0xce) [0x72da6e]
 /usr/bin/mongod(_ZN5mongo3dur8_recoverEv+0x824) [0x72e494]
 /usr/bin/mongod(_ZN5mongo3dur7recoverEv+0x37) [0x72e887]
 /usr/bin/mongod(_ZN5mongo3dur7startupEv+0x24) [0x724de4]
 /usr/bin/mongod(_ZN5mongo14_initAndListenEi+0x435) [0x8d1365]
 /usr/bin/mongod(_ZN5mongo13initAndListenEi+0x18) [0x8d22d8]
 /usr/bin/mongod(main+0x2ebc) [0x58f02c]
 /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xfd) [0x7f5dc9cdaead]
 /usr/bin/mongod() [0x58f8e9]
Fri Jul 12 18:32:17 [initandlisten] exception during recovery
Fri Jul 12 18:32:17 [initandlisten] exception in initAndListen: 15874 couldn't uncompress journal section, terminating
Fri Jul 12 18:32:17 dbexit: 
Fri Jul 12 18:32:17 [initandlisten] shutdown: going to close listening sockets...
Fri Jul 12 18:32:17 [initandlisten] shutdown: going to flush diaglog...
Fri Jul 12 18:32:17 [initandlisten] shutdown: going to close sockets...
Fri Jul 12 18:32:17 [initandlisten] shutdown: waiting for fs preallocator...
Fri Jul 12 18:32:17 [initandlisten] shutdown: lock for final commit...
Fri Jul 12 18:32:17 [initandlisten] shutdown: final commit...
Fri Jul 12 18:32:20 [initandlisten] shutdown: closing all files...
Fri Jul 12 18:32:20 [initandlisten] closeAllFiles() finished
Fri Jul 12 18:32:20 [initandlisten] shutdown: removing fs lock...
Fri Jul 12 18:32:20 dbexit: really exiting now

Notes:

  1. The computer was shut down properly with the poweroff command, however as you see from the log, mongod did not shut down properly for unknown reason.
  2. After the next boot, the assert appeared.
  3. Tried --repair but the logs have the same assert.
  4. The filesystem is not corrupted, fsck.ext4 gives no error, no IO errors in the logs, etc. The hardware is very new, only few weeks old, S.M.A.R.T. monitored, mdadm monitored etc.

System:

  • Debian 7 x86_64 up to date, with MongoDB from repo, just simple MongoDB, no sharding, no replica
  • 6 x 3TB SATA3 HDDs in RAID10 for MongoDB, 32GB RAM, Intel Core i7-4770 CPU

My question is, what could happen to MongoDB at the shutdown process that broke so severely the database?

Comment by Eliot Horowitz (Inactive) [ 13/Jun/13 ]

I would give generally the same advice.
CAn you check /var/log/messages for disk io errors and run fsck on the disk?

Comment by ham.lee [ 22/May/13 ]

Hi all,https://jira.mongodb.org/browse/SERVER-4882 do have this issue closed,but there is none solution displayed,Eliot Horowitz said:"Please keep the same issues on the same ticket.Overall it looks like your filesystem is very corrupted.I would check your disks."

but nothing more news add,is there anyone can help me?
----------------------detail logs---------------
Thu May 23 02:08:12.986 [initandlisten] recover begin
Thu May 23 02:08:12.986 [initandlisten] recover lsn: 5025215
Thu May 23 02:08:12.986 [initandlisten] recover /home/mongodb/db/QDWTB_DATA/journal/j._11
Thu May 23 02:08:12.986 [initandlisten] recover skipping application of section seq:4965384 < lsn:5025215
Thu May 23 02:08:14.778 [initandlisten] recover create file /home/mongodb/db/QDWTB_DATA/QDWTB.25 2047MB
Thu May 23 02:08:48.429 [initandlisten] couldn't uncompress journal section
Thu May 23 02:08:48.429 [initandlisten] Assertion: 15874:couldn't uncompress journal section
0xdcf361 0xd90a1b 0x92ada1 0x92b424 0x92c559 0x92c982 0x92d29c 0x92d502 0x91886f 0x6d557c 0x6d5dad 0x6dc88f 0x6de4d9 0x38c761d9c4 0x6ce389
/home/mongodb/bin/mongod(_ZN5mongo15printStackTraceERSo+0x21) [0xdcf361]
/home/mongodb/bin/mongod(_ZN5mongo11msgassertedEiPKc+0x9b) [0xd90a1b]
/home/mongodb/bin/mongod(_ZN5mongo3dur11RecoveryJob14processSectionEPKNS0_11JSectHeaderEPKvjPKNS0_11JSectFooterE+0x561) [0x92ada1]
/home/mongodb/bin/mongod(_ZN5mongo3dur11RecoveryJob17processFileBufferEPKvj+0x134) [0x92b424]
/home/mongodb/bin/mongod(_ZN5mongo3dur11RecoveryJob11processFileEN5boost11filesystem34pathE+0xd9) [0x92c559]
/home/mongodb/bin/mongod(_ZN5mongo3dur11RecoveryJob2goERSt6vectorIN5boost11filesystem34pathESaIS5_EE+0x122) [0x92c982]
/home/mongodb/bin/mongod(_ZN5mongo3dur8_recoverEv+0x1dc) [0x92d29c]
/home/mongodb/bin/mongod(_ZN5mongo3dur7recoverEv+0x22) [0x92d502]
/home/mongodb/bin/mongod(_ZN5mongo3dur7startupEv+0x7f) [0x91886f]
/home/mongodb/bin/mongod(_ZN5mongo14_initAndListenEi+0x3ec) [0x6d557c]
/home/mongodb/bin/mongod(_ZN5mongo13initAndListenEi+0x1d) [0x6d5dad]
/home/mongodb/bin/mongod [0x6dc88f]
/home/mongodb/bin/mongod(main+0x9) [0x6de4d9]
/lib64/libc.so.6(__libc_start_main+0xf4) [0x38c761d9c4]
/home/mongodb/bin/mongod(__gxx_personality_v0+0x499) [0x6ce389]
Thu May 23 02:08:48.434 [initandlisten] dbexception during recovery: 15874 couldn't uncompress journal section
Thu May 23 02:08:48.434 [initandlisten] exception in initAndListen: 15874 couldn't uncompress journal section, terminating
Thu May 23 02:08:48.434 dbexit:
Thu May 23 02:08:48.434 [initandlisten] shutdown: going to close listening sockets...
Thu May 23 02:08:48.434 [initandlisten] shutdown: going to flush diaglog...
Thu May 23 02:08:48.434 [initandlisten] shutdown: going to close sockets...
Thu May 23 02:08:48.434 [initandlisten] shutdown: waiting for fs preallocator...
Thu May 23 02:08:48.434 [initandlisten] shutdown: lock for final commit...
Thu May 23 02:08:48.434 [initandlisten] shutdown: final commit...
Thu May 23 02:08:55.420 [initandlisten] shutdown: closing all files...
Thu May 23 02:08:55.432 [initandlisten] closeAllFiles() finished
Thu May 23 02:08:55.432 [initandlisten] shutdown: removing fs lock...
Thu May 23 02:08:55.432 dbexit: really exiting now

Generated at Thu Feb 08 03:21:21 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.