this post was submitted on 26 Aug 2023
34 points (94.7% liked)

Selfhosted

40394 readers
201 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 2 years ago
MODERATORS
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
34
Having an issue with pictrs after full disk (leemyalone.org)
submitted 1 year ago* (last edited 1 year ago) by [email protected] to c/[email protected]
20 comments fedilink hide all child comments
 

The virtual disk for my lemmy instance filled up which caused lemmy to throw a lot of errors. I resized the disk and expanded the filesystem but now the pictrs container is constantly restarting.

root@Lemmy:/srv/lemmy# le 
less         lessecho     lessfile     lesskey      lesspipe     let          letsencrypt  lexgrog      
root@Lemmy:/srv/lemmy# ls
leemyalone.org
root@Lemmy:/srv/lemmy# cd leemyalone.org/
root@Lemmy:/srv/lemmy/leemyalone.org# docker-compose ps
          Name                        Command                 State                           Ports                      
-------------------------------------------------------------------------------------------------------------------------
leemyaloneorg_lemmy-ui_1   docker-entrypoint.sh /bin/ ...   Up           1234/tcp                                        
leemyaloneorg_lemmy_1      /app/lemmy                       Up                                                           
leemyaloneorg_pictrs_1     /sbin/tini -- /usr/local/b ...   Restarting                                                   
leemyaloneorg_postfix_1    /root/run                        Up           25/tcp                                          
leemyaloneorg_postgres_1   docker-entrypoint.sh postgres    Up           5432/tcp                                        
leemyaloneorg_proxy_1      /docker-entrypoint.sh ngin ...   Up           80/tcp, 0.0.0.0:3378->8536/tcp,:::3378->8536/tcp
all 21 comments
sorted by: hot top controversial new old
[–] [email protected] 3 points 1 year ago

Might this be related?

In some cases, pict-rs might crash and be unable to start again. The most common reason for this is the filesystem reached 100% and pict-rs could not write to the disk, but this could also happen if pict-rs is killed at an unfortunate time. If this occurs, the solution is to first get more disk for your server, and then look in the sled-repo directory for pict-rs. It's likely that pict-rs created a zero-sized file called snap.somehash.generating. Delete that file and restart pict-rs.

https://git.asonix.dog/asonix/pict-rs#user-content-common-problems

[–] [email protected] 2 points 1 year ago (2 children)

Pictrs saves Thumbnails profile Images of users not just from your instance but also from other instances. Lemmy devs should look into optimising this like they did with the database.

[–] [email protected] 1 points 1 year ago (1 children)

That's all pictrs is for? Can it just be disabled without breaking anything else?

[–] [email protected] 7 points 1 year ago

Pictrs is for all image storage. But posted images stay on the source instance. Thumbnails and banners are federated.

[–] [email protected] 1 points 1 year ago

Have you checked the logs for the pictures container to see why it's restarting?

Could it be permissions?

[–] [email protected] 1 points 1 year ago

Acronyms, initialisms, abbreviations, contractions, and other phrases which expand to something larger, that I've seen in this thread:

Fewer Letters More Letters
Git Popular version control system, primarily for code
HTTP Hypertext Transfer Protocol, the Web
nginx Popular HTTP server

[Thread #83 for this sub, first seen 27th Aug 2023, 14:45] [FAQ] [Full list] [Contact] [Source code]

[–] [email protected] 0 points 1 year ago (1 children)

What do the logs say?

[–] [email protected] 1 points 1 year ago (2 children)

Can't see pictrs log because it never full starts.

root@Lemmy:/srv/lemmy/leemyalone.org# docker-compose logs leemyaloneorg_pictures_1
ERROR: No such service: leemyaloneorg_pictures_1
root@Lemmy:/srv/lemmy/leemyalone.org#
[–] [email protected] 2 points 1 year ago* (last edited 1 year ago)

If the pictrs container doesn't start check the docker logs.

journalctl -fexu docker

It'll typically tell you why a container isn't starting, usually a broken bind mount.

To prevent this from happening again, try migrating to an S3 backend; DigitalOcean have one that's fixed-price and includes egress, so you can't accidentally end up with a ridiculous bill one month!

[–] [email protected] 0 points 1 year ago* (last edited 1 year ago) (1 children)

You can still see the logs using docker logs container_name>. To get the container name you can use docker ps -a. It should list the pictrs container there. The container name is usually the last column of the output.

[–] [email protected] 3 points 1 year ago* (last edited 1 year ago) (1 children)

` ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ BACKTRACE ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

Run with COLORBT_SHOW_HIDDEN=1 environment variable to disable frame filtering. 2023-08-26T20:46:43.679371Z WARN sled::pagecache::snapshot: corrupt snapshot file found, crc does not match expected Error: 0: Error in database 1: Read corrupted data at file offset None backtrace ()

Location: src/repo/sled.rs:84

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ SPANTRACE ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

0: pict_rs::repo::sled::build with path="/mnt/sled-repo" cache_capacity=67108864 export_path="/mnt/exports" at src/repo/sled.rs:78 1: pict_rs::repo::open with config=Sled(Sled { path: "/mnt/sled-repo", cache_capacity: 67108864, export_path: "/mnt/exports" }) at src/repo.rs:464

root@Lemmy:~#`

[–] [email protected] 1 points 1 year ago (1 children)

Seems like your pictrs database is corrupted.

[–] [email protected] 3 points 1 year ago* (last edited 1 year ago) (2 children)

Is there a way to reset the pictrs DB without affecting the posts, commenst and users DB?

[–] [email protected] 1 points 1 year ago (2 children)

pictrs database is completely separate from lemmy database. If you want you just delete everything in the pictrs volume and start afresh. You will lose all images though.

[–] [email protected] 2 points 1 year ago (1 children)

There's only two local posts on my instance so i'm not worried about losing thoseabout.

Will the pictrs from subscribed communities in other instances be restored after a db reset?

[–] [email protected] 0 points 1 year ago

pictrs from subscribed communities in other instances

Dont worry about those. Those images are not stored by your pictrs instance. They are directly fetched from the native instances.

[–] [email protected] 1 points 1 year ago* (last edited 1 year ago) (1 children)

OK. I just deleted the pictrs folder from srv/lemmy/leemyalone.org/volumes but I am still having the same issue.

[–] [email protected] 2 points 1 year ago (1 children)

You'll have to check again. My guess is though you should not have deleted the pictrs folders. Just its contents. You can recreate the folder again though:

mkdir pictrs
sudo chown 991:991 pictrs

But check the logs first.

[–] [email protected] 3 points 1 year ago* (last edited 1 year ago)

In my previous comment I should have mentioned that I did recreate the pictrs folder. Your instruction to change set the ownership of the pictures folder to 991:991 did the trick.

Thank you so much for your help here. Much appreciated.

[–] [email protected] 1 points 1 year ago

You can try mounting a new folder as pictrs volume. I assume your other data will be safe since it is in the database.