Hello,
I'm new to setting up a lemmy instance. Followed the guide using docker compose. I have everything running for the most part, but I'm noticing this error in the logs.
lemmy-pictrs | 2024-10-28T01:58:48.048727Z WARN pict_rs::tmp_file: TmpFolder - Blocking remove of directory "/tmp/pict-rs/0192d0d8-e3ec-7dcd-be4e-d1ef1cc09fca/0192d0d8-e3ed-71d6-a5dc-5dc150e868f1"
lemmy-pictrs | 2024-10-28T01:58:48.048891Z WARN pict_rs::tmp_file: TmpDir - Blocking remove of "/tmp/pict-rs/0192d0d8-e3ec-7dcd-be4e-d1ef1cc09fca"
lemmy-pictrs | Error:
lemmy-pictrs | 0: Error in database
lemmy-pictrs | 1: IO error: Permission denied (os error 13)
lemmy-pictrs |
lemmy-pictrs | Location:
lemmy-pictrs | src/repo/sled.rs:130
lemmy-pictrs |
lemmy-pictrs | ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ SPANTRACE ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
lemmy-pictrs |
lemmy-pictrs | 0: pict_rs::repo::sled::build with path="/mnt/sled-repo" cache_capacity=67108864 export_path="/mnt/exports"
lemmy-pictrs | at src/repo/sled.rs:124
lemmy-pictrs | 1: pict_rs::repo::open
lemmy-pictrs | at src/repo.rs:889
lemmy-pictrs |
lemmy-pictrs | ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ BACKTRACE ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
lemmy-pictrs | <empty backtrace>
Any help on how to go about debugging this would be helpful! As I understand the pictrs container isn't able to access the volume for postgres. But not sure why.
I just setup my own instance a few days ago, if it interests you, do give it a shot!
IIRC reading about it, all data for posts is set to be deleted automatically on a schedule. The catch is that schedule is every 6 months, and it is not configurable currently. From what I read, textual posts of lemmy doesn't consume that much, many reported anywhere from 1-10 GB of data over 6 months - ofcourse it all depends on what kinds of communities are subscribed to your instance.
Not sure if you can restrict image sizes or numbers - atleast not through the admin UI, maybe it's possible through config. You can set global rate limit on image uploads though to not go too crazy.
You can set it so only admins can create communities, or admin would have to approve new communities, or free for all.
If you already have a server, try it out. It shouldn't be tricky, particularly if you're familiar with docker.