[SERVER-22680] WiredTiger fails to start after trying to upgrade from 3.2.1 to 3.2.2 Created: 17/Feb/16 Updated: 04/Mar/16 Resolved: 04/Mar/16 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | WiredTiger |
| Affects Version/s: | 3.2.3 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Ronald Feicht | Assignee: | Ramon Fernandez Marina |
| Resolution: | Duplicate | Votes: | 1 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
||||||||
| Issue Links: |
|
||||||||
| Operating System: | ALL | ||||||||
| Steps To Reproduce: | apt-get update && apt-get upgrade && apt-get dist-upgrade MongoDB data directory is attached - since it contains only test data there is no need to keep it secret. |
||||||||
| Participants: | |||||||||
| Description |
|
After upgrading MongoDB to version 3.2.2 the database fails to start with the following error:
Downgrading to 3.2.1 or 3.2.0 did NOT fix it. |
| Comments |
| Comment by Ramon Fernandez Marina [ 04/Mar/16 ] | ||||||||||||||
|
Thanks for the update scsynergy, and glad to hear you were able to upgrade to 3.2.3. Closing this ticket now. Cheers, | ||||||||||||||
| Comment by Ronald Feicht [ 18/Feb/16 ] | ||||||||||||||
|
I upgraded to 3.2.3 without problems. | ||||||||||||||
| Comment by Ronald Feicht [ 18/Feb/16 ] | ||||||||||||||
|
It seems that file versions from 3.2.2, 3.2.1 and 3.2.0 were mixed and garbled - I could not install any version due to errors. I guess all the upgrading, downgrading, removing, installing and purging at some point broke file version consistency. After I deleted all MongoDB files manually and then installed 3.2.1 I, too, can now start the database without problems. I do seem to remember that dpkg tried to start the database during an apt-get remove or purge or downgrade which failed, naturally, so I added 'exit 0' at the top of the init script to resolve that error. Could that have broken file version consistency? If so, you might want to change your packaging to not expect the database to start on package removal. Anyway, thanks for helping even when the problem was on my end. | ||||||||||||||
| Comment by Ramon Fernandez Marina [ 17/Feb/16 ] | ||||||||||||||
|
scsynergy, while I'm able to reproduce the issue with 3.2.2, if I downgrade to 3.2.1 I'm able to start mongod with the data files you sent without problems. I'm running Ubuntu 14.04 too, so I can't quite explain why a downgrade didn't work for you. Can you please send the same startup log when you try with 3.2.1 and/or 3.2.0? This is what I get:
Thanks, | ||||||||||||||
| Comment by Jacob Jewell [ 17/Feb/16 ] | ||||||||||||||
|
This happened in our testing environment too. Luckily we caught it before it could corrupt our production databases. | ||||||||||||||
| Comment by Ramon Fernandez Marina [ 17/Feb/16 ] | ||||||||||||||
|
Thanks for creating a new ticket scsynergy, we're investigating this issue now. |