[SERVER-17366] weird WT startup error Created: 24/Feb/15  Updated: 27/Apr/15  Resolved: 02/Mar/15

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

Type: Bug Priority: Major - P3
Reporter: Mathias Stearn Assignee: Michael Cahill (Inactive)
Resolution: Won't Fix Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Backwards Compatibility: Fully Compatible
Operating System: ALL
Participants:

 Description   

I got this one-off error when starting in gdb. I tried starting mongod again and everything went fine. Should we be concerned?

2015-02-24T12:35:36.198-0500 I CONTROL  [initandlisten] db version v3.1.0-pre-
2015-02-24T12:35:36.198-0500 I CONTROL  [initandlisten] git version: 63f13260be445a1b629a75fd75bea36df5bd6b09
2015-02-24T12:35:36.198-0500 I CONTROL  [initandlisten] build info: Linux redbeard 3.18.6-1-ARCH #1 SMP PREEMPT Sat Feb 7 08:44:05 CET 2015 x86_64 BOOST_LIB_VERSION=1_56
2015-02-24T12:35:36.198-0500 I CONTROL  [initandlisten] allocator: tcmalloc
2015-02-24T12:35:36.198-0500 I CONTROL  [initandlisten] options: { storage: { dbPath: "/tmp/data", engine: "wiredTiger" } }
2015-02-24T12:35:36.215-0500 I STORAGE  [initandlisten] wiredtiger_open config: create,cache_size=15G,session_max=20000,eviction=(threads_max=4),statistics=(fast),log=(enabled=true,archive=true,path=journal,compressor=snappy),checkpoint=(wait=60,log_size=2GB),statistics_log=(wait=0),
2015-02-24T12:35:36.215-0500 E STORAGE  [initandlisten] WiredTiger (22) [1424799336:215294][22901:0x7ffff7fa7b80], wiredtiger_open: WiredTiger.basecfg exists before database creation: Invalid argument
2015-02-24T12:35:36.215-0500 I -        [initandlisten] Fatal Assertion 28561

> ll /tmp/data #between failure and successful startup.
total 1010M
-rw-r--r-- 1 mstearn mstearn 1010M Feb 17 18:20 collection-0-2138100414903764394.wt
-rw-r--r-- 1 mstearn mstearn   36K Feb 17 18:20 collection-0-3102749743758751424.wt
-rw-r--r-- 1 mstearn mstearn   16K Feb 17 18:20 collection-0-3467117757960361238.wt
-rw-r--r-- 1 mstearn mstearn   36K Feb 17 18:20 index-1-3102749743758751424.wt
-rw-r--r-- 1 mstearn mstearn   16K Feb 17 18:20 index-1-3467117757960361238.wt
drwxr-xr-x 2 mstearn mstearn    80 Feb 17 14:11 journal/
-rw-r--r-- 1 mstearn mstearn   36K Feb 17 18:20 _mdb_catalog.wt
-rwxr-xr-x 1 mstearn mstearn     0 Feb 17 18:20 mongod.lock*
-rw-r--r-- 1 mstearn mstearn   36K Feb 17 18:20 sizeStorer.wt
-rw-r--r-- 1 mstearn mstearn    95 Feb 13 12:34 storage.bson
-rw-r--r-- 1 mstearn mstearn    49 Feb 24 12:35 WiredTiger
-rw-r--r-- 1 mstearn mstearn   496 Feb 13 12:34 WiredTiger.basecfg
-rw-r--r-- 1 mstearn mstearn    21 Feb 24 12:35 WiredTiger.lock
-rw-r--r-- 1 mstearn mstearn   885 Feb 17 18:20 WiredTiger.turtle
-rw-r--r-- 1 mstearn mstearn   52K Feb 17 18:20 WiredTiger.wt



 Comments   
Comment by Daniel Pasette (Inactive) [ 02/Mar/15 ]

Believe this to be user error.

Comment by Keith Bostic (Inactive) [ 24/Feb/15 ]

This error means the file "WiredTiger.basecfg" already existed in the database directory when the thread acquiring the initial lock file (and creating the database directory), was running.

If there's a way that file might have been left over from a previous (debugging?) run, or a corrupted database directory, then that would explain it.

Looking at the file list, it looks like the "WiredTiger" and "WiredTiger.lock" files were created today, but everything else is from a week ago, any idea how that might have happened? Those files are created when WiredTiger first starts running, and are never subsequently removed by WiredTiger.

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