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
 

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
[–] poVoq 3 points 2 years ago* (last edited 2 years ago) (1 children)

With a SSH terminal go to the directory where the specific docker-compose.yml file is and do this:

https://docs.docker.com/engine/reference/commandline/compose_up/

Just restarting the VM or the containers does not recreate them. Be sure all the persistent data is properly stored and backed up as recreating the container will overwrite the data otherwise.

But are you sure you want to run a public service with Docker if your level of understanding of it (and online search skills) is so low?

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

Thanks

I did the docker-compose restart. It is still not working.

So I went to post a test image so the logs would show what happens and I got this error in the UI

SyntaxError: Unexpected token 'R', "Request er"... is not valid JSON

[–] poVoq 1 points 2 years ago (1 children)

Try the force-recreate option to make sure you are not only restarting the containers but actually recreating them.

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

I ran the force-recreate option.

Now when I go to the instance I get a spinning wheel where the posts would normally appeal. I am assuming this is just rebuilding all the pages and may take some time? Would take be correct?

[–] poVoq 1 points 2 years ago (1 children)

no that looks more like it has issues connecting to the database. Maybe the database container got renamed?

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

so what should I do now?

Should I restore the backup from before I ran the recreate command or do something else?

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

I ran the up command with force recreate and seem to be back to where I started. Instance working except images no displaying

I posted a copy of the screen output here https://github.com/LemmyNet/lemmy/issues/2637#issuecomment-1374677294

It showed a bunch of errors

[–] poVoq 1 points 2 years ago* (last edited 2 years ago) (1 children)

Sorry I am not deep enough into hosting Lemmy (yet) to answer your question. I guess the Pict-rs container that is used as the image backend has some sort of issue?

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

Thanks for the help you have provided so far - if nothing else I learnt some stuff.