[Bug]: lemmy_federate::worker: last successful id is higher than latest id in database

[wkelton]

Requirements

• Is this a bug report? For questions or discussions use https://lemmy.ml/c/lemmy_support
• Did you check to see if this issue already exists?
• Is this only a single bug? Do not put multiple bugs in one issue.
• Is this a backend issue? Use the lemmy-ui repo for UI / frontend issues.

Summary

Log is being flooded by these messages:

ERROR lemmy_federate::worker: <some remote instance>: last successful id 135 is higher than latest id 0 in database (did the db get cleared?)

Steps to Reproduce

I'm using docker to run a lemmy server. I upgraded to 0.19.2 and everything seemed fine. Started and stopped the container a few times (was upgrading to pict-rs 0.5.0), then saw these messages flooding the log.

Technical Details

See above.

Version

0.19.2

Lemmy Instance URL

No response

[Nutomic]

cc @phiresky

[phiresky]

@wkelton Did you manually make any changes in the database like clearing out the activities tables?

Or, was the last activity (create post, vote, comment) on your server more than a week ago?

Does it go away if you do a single action? (e.g. vote on something)

[wkelton]

I made no manual database changes. The only changes I made were do my docker-compose.yml / env files (for going to 0.19.2 and upgrading pictrs to 0.5 - required changing their env vars). However, there is some chance I may have inadvertently run lemmy with a previous version after I had run it with 0.19.2 - not sure if I did that though).

Indeed it has been more than a week for any activity. I voted on a comment and will post back if that resolves it.

[wkelton]

I appear to no longer be getting the error.

Was this just some weird corner case with old activity and upgrading, or is there a "requirement" for activity within a certain amount of time (so, if no activity within a week, this error will show up)?

[Nutomic]

I think the error message is wrong/misleading because it defaults to id 0 if none was found in the db. It should probably use an option instead, so that the default value isnt necessary.

[phiresky]

Well that part is intentional because it only shows up if there were activities before and there no longer are.

But I forgot that the activities are cleared automatically and small instances might not actually have an activity in that time period.

So probably we can just remove the error message. it's supposed to warn the people that put"truncate send_activities" in their crontab to save space that they are breaking federation.