search

YunoHost-Apps / pixelfed_ynh

The federated image shareing service Pixelfed for YunoHost
https://pixelfed.org/
GNU Affero General Public License v3.0
44 stars 15 forks source link

Oops. Something went wrong after update #202

Closed Schdefoon closed 1 year ago

Schdefoon commented 1 year ago

Hello,

I did an update from 0.11.4-ynh4 to 0.11.4-ynh5 on February 19th and did not notice any error while updating. When posting a status now I always get a message "Oops. Something went wrong". I ignored this message because everything seemed to be ok. The status is visible in the timeline. Now I found out that there are problems: In the database tables "hashtag" and "status_hashtags" no new entries are written. And in the table "statuses" the field "entities" stays empty.

Is there a way to find what's the problem on my instance running on a local RaspberryPi?

Best regards

lapineige commented 1 year ago

What solved these strange errors for me in the past is… forcing an upgrade to the same version. Don't ask me why… Maybe you can try it ?

Schdefoon commented 1 year ago

Thank you very much for your help. What have I to do to force an upgrade for pixelfed? I tried the command yunohost app upgrade pixelfed The response was

I did not post a new status yet to see if the situation changed

lapineige commented 1 year ago

Use yunohost app upgrade pixelfed --force

Schdefoon commented 1 year ago

Ok, thanks a lot. But unfortunately the problem still exists on my pixelfed instance after the forced upgrade. I think I'll take the time to run some tests on my desktop PC with browser debugging tools and look at the log files. Maybe I can find some more hints.

lapineige commented 1 year ago

Is horizon service running ? What does it says in the admin interface ?

Schdefoon commented 1 year ago

I did several testings yesterday and found with Firefox Developer Tools that calling /api/compose/v0/publish resulted in an error 500 (internal server error). In the details of this element I could see a error message: Command 'ZPOPMIN' is not a registered Redis command. I searched for this message and finally found a Pixelfed discussion about another problem with version 0.11.4 where it was suggested to set the variable REDIS_CLIENT to phpredis instead of predis. So I set this in my .env file and cleared the cache. I don't know if there are disadvantages to change the default setting of REDIS_CLIENT, but in my case it seems to work. I have no "Oops." error any more when posting a status and the database tables are filled again with hashtag-values 😃

lapineige commented 1 year ago

Thanks for all that work !

I will change this on default config.