Local and federated timelines are stuck for only one user

[Kansattica]

Hello! I'm the admin for social.illegalpornography.com. I was on the cutting edge master branch release for a while, but this problem turned up after I went back to v2.5.0, which is what I'm currently running. I've tried restarting Docker a couple times, and also run the mastodon:feeds:clear_all and mastodon:feeds:build rake tasks. These didn't help.

The local timeline hasn't updated all day, and is showing me incredibly old posts. If I make a post, it will briefly show up in in the local timeline before disappearing on the next refresh. I see this issue in the desktop web interface, the mobile web interface, and Tusky. This only happens on my account on this instance. The left image below is what I see on the bugged account, the one on the right is what I see from a different, non-bugged account on the same instance.

The federated timeline is similar, except there's a slow trickle of posts that reach the bugged account. Is there anything I can do to fix this?

---

• I searched or browsed the repo’s other issues to ensure this is not a duplicate.
• This bug happens on a tagged release and not on master (If you're a user, don't worry about this).

[Kansattica]

Left is the slow, random trickle of posts through the relay into my federated timeline, right is what the non-bugged account on the same instance sees.

[nightpool]

the nastodon:feeds tasks only generate the Home timeline for individual users. since the local timeline is theoretically identical for all users, it's generated directly from the database and not stored in redis. you've said this bug is consistent accross all platforms? can you give some screenshots from a different client?

…

On Fri, Sep 28, 2018, 10:05 PM Grace ***@***.***> wrote: Left is the slow, random trickle of posts through the relay into my federated timeline, right is what the non-bugged account on the same instance sees. [image: image] <https://user-images.githubusercontent.com/10965841/46239732-6a6b8a00-c351-11e8-9afe-50b9e8cf956f.png> [image: image] <https://user-images.githubusercontent.com/10965841/46239735-75beb580-c351-11e8-8472-92002f05f514.png> — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#8824 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAORV-ZhEHX61a3C3MaGTmVyI1Ns-9d6ks5uftWGgaJpZM4XARau> .

[Kansattica]

Sure thing. The first two are from Tusky, the second two are from opening the mobile site on my phone.

[Kansattica]

Oh, I also recently moved my site from ~/mastodon to /mnt/mountname/mastodon, if that's been known to cause problems.

[Kansattica]

Do you guys need anything else from me, or does the closing mean I'm not getting any help here?

[Kansattica]

I've noticed that the posts that do show up in the local timeline:

• Start with a @, # or emojo
• Come from an account that doesn't have the bug (they don't show up if I toot them on my bugged account, but posts from before the bug showed up are there)

I don't know if this helps.

[hugogameiro]

@Kansattica Have you ever managed to solve this issue? I have ran into a very similar situation

[hugogameiro]

The same situation is happening on another instance that I manage where the Local Timeline doesn't update for a single user, all other users report no problems and that same user created a new test account and the issue is not present on the test account. So, the problem doesn't look to be on their end but after looking into everything I could think of I found nothing wrong.

Also the same situation where when a toot is posted from the problematic account it briefly shows up on the home timeline and then vanishes was reported.

I spoke with @Kansattica and the issue is also still present on the account that started this issue.

[hugogameiro]

OK, after jumping into the database I found what was wrong with the user I reported, the language filtering was on to only allow Japanese posts. After removing the language filtering it started working normally.

[Kansattica]

This solved my problem- turns out I had Portugese checked for some reason. Thank you so much!