Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Retention policy not working #13916

Closed
cchbr opened this issue Mar 27, 2019 · 4 comments · Fixed by #15252
Closed

Retention policy not working #13916

cchbr opened this issue Mar 27, 2019 · 4 comments · Fixed by #15252

Comments

@cchbr
Copy link

cchbr commented Mar 27, 2019

Description:

The automatic pruning of messages does not work. I had messages that were several months old and set the maximum message age to one day but it didn't remove anything. Now I've manually pruned all old messages in the hope that the automatic pruning will work when new messages are older than one day, but that doesn't work either.

Steps to reproduce:

  1. Activate Retention policy.
  2. Set the precision to once an hour and maximum message age to one day.
  3. Activate the feature for channels but deactivate for everything else.

Expected behavior:

The messages older than one day in all public channels should be removed.

Actual behavior:

No messages are removed, regardless of how old they are.

Server Setup Information:

  • Version of Rocket.Chat Server: 0.74.3
  • Operating System: Ubuntu
  • Deployment Method: Docker
  • Number of Running Instances: 1
  • MongoDB Version: 3.2

Additional context

The logs show that the runner is started once an hour, but it still doesn't delete anything.

Relevant logs:

SyncedCron ➔ info Starting "Prune old messages by retention policy".
SyncedCron ➔ info Finished "Prune old messages by retention policy".

@CodazziS
Copy link

CodazziS commented Apr 2, 2019

Hello,

Same problem for me ( #12862 )

@engelgabriel
Copy link
Member

@sampaiodiego closed this in #15252

@engelgabriel
Copy link
Member

@piotrkochan
Copy link
Contributor

same today on v3.6.3

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants