Open deadmanIsARabbit opened 6 years ago
maxdwit
commented
6 years ago Out of curiosity: turn on exception Logging to a channel.
Do you get someting like:
WriteError({"code":11000,"index":0,"errmsg":"E11000 duplicate key error collection: parties.rocketchat_message index: _id_ dup key:
deadmanIsARabbit
commented
6 years ago It's funny but the problem seems to has solved itself. All affected users are now able to chat.
deadmanIsARabbit
commented
6 years ago @maxdwit It is here. It happened again and it is logged Rocket.Chat Version is 0.68.4
WriteError({"code":11000,"index":0,"errmsg":"E11000 duplicate key error collection: rocket_chat.rocketchat_message index: _id_ dup key: { : \"RD3NTJPxmEdtYrCpB\" }","op":{"_id":"RD3NTJPxmEdtYrCpB","rid":"WfNwe4Q8LAqaR9Q6kijAmbvm5Hfe9ogdqY","msg":"hello","ts":"2018-08-29T13:09:59.518Z","alias":"XXXX XXXXX","u":{"_id":"WfNwe4Q8LAqaR9Q6k","username":"YYYYYYY","name":"XXXXXX XXXXXX [extern]"},"_updatedAt":"2018-08-29T13:09:59.561Z","mentions":[],"channels":[]}}) at Function.MongoError.create (/srv/Rocket.Chat/programs/server/npm/node_modules/meteor/npm-mongo/node_modules/mongodb-core/lib/error.js:31:11) at toError (/srv/Rocket.Chat/programs/server/npm/node_modules/meteor/npm-mongo/node_modules/mongodb/lib/utils.js:139:22) at /srv/Rocket.Chat/programs/server/npm/node_modules/meteor/npm-mongo/node_modules/mongodb/lib/collection.js:668:23 at handleCallback (/srv/Rocket.Chat/programs/server/npm/node_modules/meteor/npm-mongo/node_modules/mongodb/lib/utils.js:120:56) at resultHandler (/srv/Rocket.Chat/programs/server/npm/node_modules/meteor/npm-mongo/node_modules/mongodb/lib/bulk/ordered.js:421:14) at /srv/Rocket.Chat/programs/server/npm/node_modules/meteor/npm-mongo/node_modules/mongodb-core/lib/connection/pool.js:469:18 at _combinedTickCallback (internal/process/next_tick.js:131:7) at process._tickDomainCallback (internal/process/next_tick.js:218:9)
What can i do about it?
Description:
Since upgrading to 0.66.3 from 0.65.2 a direct chat with new LDAP users is not possible. Separate rooms will be created for both users in which each user can write and not read and vice versa.
Steps to reproduce:
Expected behavior:
Alice get the message from Bob and can reply to him.
Actual behavior:
Alice sees a new message, but can't access the room with the message. She will be notified by mail about the message. If Alice searches for Bob and writes him a message Bob will get the message in a new room which he again can't access. If he tries to enter the room he gets thrown into the one which was created as he initially wrote to Alice.
Server Setup Information:
Additional context
To bypass this problem both users have to switch to the rocket.chat webbrowser version and the freshly created rooms have to be deleted by an admin. Then a chat between both parties can be stadted and afterwards both users can switch back to the desktop version.
Normally i say would this is a client issue BUT this bug is only reproducible with new or reimported LDAP users so the bug rather seems to be on the server side.