[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?
|
| 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. |