# Snap 2.1 Update Issues **URL:** \ **Category:** Announcements\ **Created:** [November 6, 2019, 12:22am UTC](https://forums.rocket.chat/t/snap-2-1-update-issues/5019 "2019-11-06T00:22:17Z")\ **Posts on this page:** 1\ **Showing post:** 37
**Author:** ![dw-dlh](https://avatars.discourse-cdn.com/v4/letter/d/e36b37/32.png) [@dw-dlh](https://forums.rocket.chat/u/dw-dlh)\ **Post date:** [November 6, 2019, 3:13pm UTC](https://forums.rocket.chat/t/snap-2-1-update-issues/5019/37 "2019-11-06T15:13:29Z")
The log you’ve posted indicates you still have the 3.4 upgrade incomplete. One of the above steps might have been missed somehow - maybe didn’t wait long enough for the db to do the upgrade? If you want to hit it with a sledgehammer, you can try my method. If your chat server is production, I recommend you take a snapshot or backup before trying it though. **to be clear - this is not an official fix from the Rocket.Chat team!** > [@Suddenly, mongod is not starting](https://forums.rocket.chat/t/suddenly-mongod-is-not-starting/4983/2): > > I had the same problem, and fixed mine. Apparently the snap tried to ‘jump’ too many mongodb versions? NOTE: this ‘repair’ might get broken by the devs when they fix this. I’m running snaps, your mileage might vary. I fixed mine I got a copy of mongodb 3.4 from [https://fastdl.mongodb.org/linux/mongodb-linux-x86\_64-3.4.23.tgz](https://fastdl.mongodb.org/linux/mongodb-linux-x86_64-3.4.23.tgz) (the “linux legacy” release) and unpacked it into root’s home folder I cd’d into the unpacked directory/bin and ran ./mongod --repair --dbpath /var/snap/rocketch… --- _[View the full topic](https://forums.rocket.chat/t/snap-2-1-update-issues/5019)._