Rocket.Chat icon indicating copy to clipboard operation
Rocket.Chat copied to clipboard

RocketChat 6.11.1 prunes messages to the previous month

Open akong77 opened this issue 1 year ago • 9 comments

Description

My original setting was to delete messages from 3 years ago, but today some users reported that they only saw messages from the previous month. What happened? Server Setup Information

Version of Rocket.Chat Server:
Operating System: Ubuntu 20.04
Deployment Method: snap
Number of Running Instances: 1
DB Replicaset Oplog: 304
NodeJS Version: v14.21.2
MongoDB Version: 5.0.15
Proxy: caddy
Firewalls involved:

Any additional Information

圖片 圖片772×683 23.1 KB

But just see previous month message. 圖片 圖片1282×332 21.5 KB

My server is at least 2 years old

akong77 avatar Aug 26 '24 00:08 akong77

It's click say error.

akong77 avatar Aug 26 '24 00:08 akong77

I got this error 圖片

akong77 avatar Aug 26 '24 01:08 akong77

The link can't found any file.

akong77 avatar Aug 26 '24 01:08 akong77

Same happened to us, maybe related https://github.com/RocketChat/Rocket.Chat/pull/32425?

krzysztof-osiecki avatar Aug 26 '24 06:08 krzysztof-osiecki

I don't know if this problem affects it, but it is true that my historical records only have the last one month, but I set to clear the records from 3 years ago. I don't know what happened.

akong77 avatar Aug 26 '24 07:08 akong77

What do your logs say please?

The link can't found any file.

No idea why this is relevant.

reetp avatar Aug 26 '24 09:08 reetp

https://github.com/RocketChat/Rocket.Chat/issues/33010 <- still not implemented in 6.11.1 maybe?

teach404 avatar Aug 26 '24 16:08 teach404

https://github.com/RocketChat/Rocket.Chat/issues/33010 <- still not implemented in 6.11.1 maybe?

I think you are correct.

reetp avatar Aug 26 '24 18:08 reetp

#33010 <- still not implemented in 6.11.1 maybe?

I think you are correct.

I think 6.11.1 has this problem.

akong77 avatar Aug 27 '24 01:08 akong77

same behaviour here after upgrading from 6.6 to 6.11.1. All direct and group messages were pruned.

bombaata avatar Aug 30 '24 13:08 bombaata

This issue has been marked as stale because there has been no further activity in the last 10 days. If the issue remains stale for the next 4 days (a total of 14 days with no activity), then it will be assumed that the question has been resolved and the issue will be automatically closed.

github-actions[bot] avatar Sep 13 '24 18:09 github-actions[bot]

Same problem here. Is the issue already solved?

mextex avatar Sep 17 '24 08:09 mextex

Same problem here. Is the issue already solved?

Without you filling out your server details no one can tell....

We have no idea which version you are using.

You should check the releases pages to see if this issue mentioned.

reetp avatar Sep 17 '24 08:09 reetp

Sorry

Same problem here. Is the issue already solved?

Without you filling out your server details no one can tell....

We have no idea which version you are using.

You should check the releases pages to see if this issue mentioned.

We use the latest version (6.12.1) under a community licence. The issue is not addressed in the release notes.

mextex avatar Sep 17 '24 08:09 mextex

There was indeed a race condition issue in 6.11.1 (and other versions) that would prune messages when updating from an older version. It happened because the retention policy would default to 30 days due to the race condition and delete all messages older than 30 days.

The release notes of 6.11.1 were updated to mention it: https://github.com/RocketChat/Rocket.Chat/releases/tag/6.11.1. This issue was fixed in 6.13.0 (https://github.com/RocketChat/Rocket.Chat/pull/33237) and backported to 6.12.1, 6.11.3, and 6.10.6.

It seems to me that it could be the same bug that ended up affecting your workspace

julio-cfa avatar Sep 18 '24 20:09 julio-cfa

This issue has been marked as stale because there has been no further activity in the last 10 days. If the issue remains stale for the next 4 days (a total of 14 days with no activity), then it will be assumed that the question has been resolved and the issue will be automatically closed.

github-actions[bot] avatar Oct 03 '24 00:10 github-actions[bot]

This issue was closed because it has been inactive for 14 days since being marked as stale.

github-actions[bot] avatar Oct 17 '24 00:10 github-actions[bot]