this post was submitted on 07 Jan 2023
3 points (100.0% liked)

Lemmy Support

4652 readers
1 users here now

Support / questions about Lemmy.

Matrix Space: #lemmy-space

founded 5 years ago
MODERATORS
dessalines@lemmy.ml
3
Images not displaying on my instance (exploding-heads.com)
submitted 2 years ago by letstry@lemmy.ml to c/lemmy_support@lemmy.ml
18 comments fedilink hide all child comments
 

I ran out of space on my instance which is hosted on linode. I used their automated system to upgrade the node so it had more hard drive space.

Since I did that, images have not displayed on my instance. Either from existing posts or new posts. How do I fix this?

I submited a question on GitHub https://github.com/LemmyNet/lemmy/issues/2637 and was asked to provide a "the docker compose logs" and to try restarting "docker compose".

I rebooted the virtual server, which I assume would restart the docker compose. If not, how do I restart it?

Also can you give me the exact commands to:

  • do a docker compose restart and where I do it from
  • generate the docker compose logs and how to limit the size if it is likely to be to big to upload to github and where to run the commands from.

Thanks in advance for your help.

you are viewing a single comment's thread
view the rest of the comments
[–] dessalines@lemmy.ml 1 points 2 years ago (1 children) 
pictrs_1    | Error: Error in DB, Read corrupted data at file offset None backtrace ()
pictrs_1    | 
pictrs_1    | Caused by:
pictrs_1    |     Read corrupted data at file offset None backtrace ()

Its a pictrs issue, not with lemmy. @asonix@lemmy.ml or ask in the pict-rs matrix channel.

[–] letstry@lemmy.ml 1 points 2 years ago (1 children)

I still have not been able to fix this problem.

I see V0.17 makes some changes to images - would the upgrade solve the problem for me?

If not, should I set up a new instance and export the database from my existing instance and import into the new? If so, any tips on how I would do this?

Any other suggestions?

[–] letstry@lemmy.ml 1 points 2 years ago

Good news - I fixed this issue prior to the upgrade