[SERVER-69892] WiredTiger error message (22) cannot be used until all column groups are created Created: 22/Sep/22 Updated: 23/Sep/22 Resolved: 23/Sep/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Alisher Abdullaev | Assignee: | Yuan Fang |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
18.04.3 LTS (Bionic Beaver) |
||
| Attachments: |
|
||||||||||||||||||||||||
| Issue Links: |
|
||||||||||||||||||||||||
| Operating System: | ALL | ||||||||||||||||||||||||
| Participants: | |||||||||||||||||||||||||
| Description |
|
Hello. a week ago, server were accidentally switched off, after (10-15min) I had again access to server, and when I tried "sudo service mongod restart" got the error below: {"t":\{"$date":"2022-09-22T09:37:10.559+00:00"},"s":"E", "c":"WT", "id":22435, "ctx":"initandlisten","msg":"WiredTiger error message","attr":{"error":22,"message": {"ts_sec":1663839430,"ts_usec":559186,"thread":"17310:0x7ff1250feac0","session_name":"WT_SESSION.verify","category":"WT_VERB_DEFAULT","category_id":9,"verbose_level":"ERROR","verbose_level_id":-3,"msg":"__wt_schema_get_table_uri:85:'table:sizeStorer' cannot be used until all column groups are created","error_str":"Invalid argument","error_code":22}}} I copied /var/lib/mongodb directory. Is it possible to restore collection and documents. We have orders, customers, doctors and etc. Now We have reinstalled mongodb. Sincerely, |
| Comments |
| Comment by Yuan Fang [ 23/Sep/22 ] |
|
Thank you for providing the data. Unfortunately, this error indicates that the disk corruption affected more than just the WiredTiger.wt file. In this situation, I would recommend checking the integrity of your disks and then restoring from a backup or resyncing from another node if possible. To avoid a problem like this in the future, it is our strong recommendation to:
For any assistance needed for restoring the collection, we'd like to encourage you to start by asking our community for help by posting on the MongoDB Developer Community Forums. If the discussion there leads you to suspect a bug in the MongoDB server, then we'd want to investigate it as a possible bug here in the SERVER project. Regards, Yuan |
| Comment by Alisher Abdullaev [ 23/Sep/22 ] |
|
Hello, Yuan. Thank you. Mongodb version 4.4, The diagnostic.data and other contents I sent to support uploader location. But mongod.log is not available now, I reinstalled ubuntu 18.04 and mongodb. Sincerely, Alisher |
| Comment by Yuan Fang [ 22/Sep/22 ] |
|
Thank you for all the information you provided so far. We still need additional information to diagnose the problem. Would you please provide the server version number, archive (tar or zip) the mongod.log files and the $dbpath/diagnostic.data directory (the contents are described here) and upload them to this support uploader location? Files uploaded to this portal are visible only to MongoDB employees and are routinely deleted after some time. Regards, Yuan |