- cross-posted to:
- [email protected]
- cross-posted to:
- [email protected]
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 must log in or register to comment.
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?
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
Try the force-recreate option to make sure you are not only restarting the containers but actually recreating them.
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?
no that looks more like it has issues connecting to the database. Maybe the database container got renamed?
so what should I do now?
Should I restore the backup from before I ran the recreate command or do something else?
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
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?
Hello, I have the exact same problem as you, and it also happened to me at the time when my instance was running out of free space.
Did you by any chance solve it somehow?
No unfortunately I have been unable to fix it.
@[email protected] @[email protected] can you help us solve this problem
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. @[email protected] or ask in the pict-rs matrix channel.
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?
Good news - I fixed this issue prior to the upgrade
I had to restore an old backup because in no way had the problem resolved itself.
If you’re interested on GitHub they suggested this to me: https://github.com/LemmyNet/lemmy/issues/2653#issuecomment-1380541659 unfortunately the suggestion came after I restored the backup and I couldn’t try it.
If you’ll try it let me know if it works or not!
I uploaded the Docker Compose log here https://github.com/LemmyNet/lemmy/issues/2637#issuecomment-1374590645
While it is not displaying images from my instance it does from communities that are federated from other instances e.g. https://exploding-heads.com/c/[email protected]
