Rocket.Chat
Rocket.Chat copied to clipboard
5.0.1 breaks message update
Description:
When sending and receiving messages, the chat messages no longer update, both in the app and on Desktop. Must refresh the page to see new sent or received messages.
Steps to reproduce:
- Go to any channel or PM
- Send a message
- The message is and remains grey or even invisible definitively
- The other side receives a notification, but does not see the new message until the page is refreshed
Expected behavior:
Messages should appear as soon as they are sent or received.
Actual behavior:
Notifications are received, but messages do not appear until reload
Server Setup Information:
- Version of Rocket.Chat Server: 5.0.1
- Operating System: Docker
- Deployment Method: docker
- Number of Running Instances: 1
- Rocket.Chat Version: 5.0.1
- NodeJS Version: 14.19.3 - x64
- MongoDB Version: 5.0.5
- MongoDB Engine: wiredTiger
- Platform: linux
Client Setup Information
- Desktop App or Browser Version: Firefox 91.11.0esr AND Android Rocket.Chat App 4.29.0.34199
- Operating System: Debian AND Android
Relevant logs:
Not sure if relevant, but JS logs give every time a message is sent:
TypeError: 'microphone' (value of 'name' member of PermissionDescriptor) is not a valid value for enumeration PermissionName.
We are having the same issue
Same problem here since 5.0.0
Still affected: 5.0.2
I have a user seeing the issue on Safari, we are on server version 5.0.1
The same issue after upgrade to v5. Just an idea / it is reproducible after mongo restart. It seems like rocket.chat cannot connect the oplog again to stream updates. After the update to rocket to v5, mongo memory usage increased a lot and OOM kills it very often, after no status updates in rocket.chat.
The same issue Chat 5.0.2 Mongo 5.0.5 with oplog
Same issue after upgrade to 5 (currently 5.0.2 and still present)
The new 5.0.3 release seems to have fixed this for us.
5.0.3 still affected for Firefox 91.12.0esr
https://docs.rocket.chat/quick-start/deploying-rocket.chat/rapid-deployment-methods/docker-and-docker-compose/docker-containers/high-availability-install#install-mongodb-replicaset
So I had an issue similar to this when upgrading to 4.8 something from 3.8.1. I was able to fix our messages not looking like they had updated by making sure the oploguser had the correct cluster role permission. This happened after upgrading MongoDB to 5 from 3.
db.createUser({user: "oploguser", pwd: "password", roles: [{role: "read", db: "local"}, {role: "clusterMonitor", db: "admin"}]}).
One quick way you may be able to determine if this is your issue is by checking your MongoDB version in the Info section. If it shows "unknown", then you may be affected by this.
It should look something like this:
Thanks for your suggestion! My output is: 5.0.5 / wiredTiger (oplog Enabled)
, so this is looking fine.
Updated to 5.0.3, still same issue. mongo db
Same issue at Server 5.0.3
Even worse, now notifications are lost as well. This is getting very frustrating and I am forced to downgrade, as Rocket Chat is effectively unusable in 5.x.
Our users are getting really annoyed about this issue.
This needs to be escalated. If a chat product doesn't show messages this is a big problem.
RC 5.0.4 Mongo 5.0.11 / wiredTiger (oplog Enabled)
I normally update as soon as rocket.cat sends a message about new releases, so also updated to 5.0.0, and had no issues with that. When updating to 5.0.1 i had the issue too, but I had also just updated my mongodb from 5.x to 6.0.1 so was unsure what broke it, downgrading to 5.0.0 fixed it for me. I updated to 5.5.5 and that seemed to work for about one day, then the issue reappeared and i had do downgrade to 5.0.0 I have just updated to 5.1.0 to see if that is better, but considering the release notes does not mention it, I don't have high hopes. Such a shame the devs are ignorering this.
I started noticing this on our own server now too. When you send a message or attachment and hit enter, it's like it just vanishes. I retyped the same message and hit send and it worked the second time. After refreshing the client, the message was there twice! Very frustrating.
Ok - I just asked my contacts at RC and they indeed know about the issue and believe it may be fixed in 5.1. Expect some kind of communication on this thread in the next day or too (please keep in mind it is the weekend).
And the problem is back, so NOT fixed in 5.1.0
(please keep in mind it is the weekend)
Was it the weekend the last 30 days? RC has aspirations of being a true prime time comms hub but their attitude towards user issues is just negligent.
Time after time real usability issues languish for weeks, months or even years.
I normally update as soon as rocket.cat sends a message about new releases, so also updated to 5.0.0, and had no issues with that. When updating to 5.0.1 i had the issue too, but I had also just updated my mongodb from 5.x to 6.0.1 so was unsure what broke it, downgrading to 5.0.0 fixed it for me. I updated to 5.5.5 and that seemed to work for about one day, then the issue reappeared and i had do downgrade to 5.0.0 I have just updated to 5.1.0 to see if that is better, but considering the release notes does not mention it, I don't have high hopes. Such a shame the devs are ignorering this.
I'm confused. I'm reading the problem does not occur with mongodb 5.0.x. Is that right?
I'm even more confused -- there was a comment by someone (@debdutdeb?) a few days ago that has since disappeared:
No, others using mongodb 5 also have the issue. And no, it is not fixed in rocketchat 5.1.0
Just to be clear. This happens to every single message you send @skadefro? Or is it one of ten? By the way, I do not see such behaviour on a few of my instances but the plan is to upgrade our production chat to 5.1.1 soon. So I'm very interested. :)
Just to be clear. This happens to every single message you send @skadefro?
Hard to say. It seems to go away if you restart rocket chat, but then comes back after a while. last time it worked for 1½ day I would hate to be the dev trying to find the issue, nothing worse than an issue that is not consistent.
Just to be clear. This happens to every single message you send @skadefro? Or is it one of ten?
For me, it's essentially all the time. If I refresh the (Safari) window, it will show the missing content and perhaps will show new content for a few exchanges. But it inevitably freezes again (necessitating a browser-window refresh). Interestingly, even when the window stops updating, I still get Safari notifications when new content is sent (by others) to the affected channel -- and others see anything that I send (even though I can't see what I sent -- until I refresh the browser-window).
So we're talking about Safari here? Are other browsers affected as well?
Am 8. September 2022 20:01:11 MESZ schrieb Jeff Frontz @.***>:
Just to be clear. This happens to every single message you send @skadefro? Or is it one of ten?
For me, it's essentially all the time. If I refresh the (Safari) window, it will show the missing content and perhaps will show new content for a few exchanges. But it inevitably freezes again (necessitating a browser-window refresh). Interestingly, even when the window stops updating, I still get Safari notifications when new content is sent (by others) to the affected channel -- and others see anything that I send (even though I can't see what I sent).
The electron app on windows, chrome on windows, the app on ios and chrome on ios ( so safari )
Strange. Usually this kind of behaviour comes from mongodb connection problems. Something in the logs? Did you try to raise the debug level if nothing shows up?
Am 8. September 2022 20:23:14 MESZ schrieb Allan Zimmermann @.***>:
The electron app on windows, chrome on windows, the app on ios and chrome on ios ( so safari )
I have auto scaling enabled, ( using mongodb atlas ) it might have triggered after at up/down scale some of the other times, but since last restart of my rocket chat, it has not scaled up or down