Open abate opened 5 years ago
+1
One more piece of information. I use blacklabelops/volumerize
to backup the mongodb volume... I'm wondering if this information might be relevant. The mongodb volume is shared with the volumerize container readonly.
+1
+1
does anybody have a temporary solution ?
There are lots of issue on the error:
E11000 duplicate key error collection
Please have a read through them and see if any are applicable or resolve your situation.
I have cleared the rocketchat_cron_history collection in mongo with the following commands in the mongo console:
use rocketchat
db.rocketchat_cron_history.remove({})
and it worked for me after restarted the rocketchat server.
@sawo is it save to delete the cron_history on a live environment?
@maxdwit to be frank with you, I do not know, what happens behind the scenes, when you truncate the rocketchat_cron_history table, but at least the app starts properly when the table is truncated before the app is started. I believe it is just for having some audit logs, or similar. I am not a developer of Rocket.Chat, so the workaround I mentioned above is not official, but I do it frequently in one of my servers, where I cannot upgrade the Rocket.Chat to newer version.
Any further information on this ? Currently on 0.74.2
It started to show after I turned on replica set after upgrade to 1.0.3. Here's my log: https://gist.github.com/MarPiRK/60c43a9abc4fd6744cd79da64f9cf537
version : 0.70.4 (from dockerhub) / mongodb 4.0.3
After a
docker-compose pull
, I got aMongoError: E11000 duplicate key error collection: rocketchat.rocketchat_cron_history index: intendedAt_1_name_1
.Somehow, I think, ricketchat wants to create a duplicated record, or a duplicated record ended up in the db.
how can I recover from this problem ?
This is the mongodb log at restart, and below the rocketchat log :