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
  • admin@leemyalone.orgOPEnglish
    3·
    1 year ago

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

    • SpecGeo@lemmy.worldEnglish
      1·
      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.

    • sobuddywhoneedsyou@lemmygrad.mlEnglish
      21·
      1 year ago

      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.

      • admin@leemyalone.orgOPEnglish
        1·
        1 year ago

        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?

        • sobuddywhoneedsyou@lemmygrad.mlEnglish
          11·
          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.

      • admin@leemyalone.orgOPEnglish
        1·
        1 year ago

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

        root@Lemmy:/srv/lemmy/leemyalone.org/volumes# sudo rm -r pictrs pictrs_corrupt/ root@Lemmy:/srv/lemmy/leemyalone.org/volumes# LS -bash: LS: command not found root@Lemmy:/srv/lemmy/leemyalone.org/volumes# ls lemmy-ui postgres root@Lemmy:/srv/lemmy/leemyalone.org/volumes# mkdir pictrs root@Lemmy:/srv/lemmy/leemyalone.org/volumes# docker-compose stop && docker-compose rm && docker-compose up -d --build Stopping leemyaloneorg_proxy_1 ... done Stopping leemyaloneorg_lemmy-ui_1 ... done Stopping leemyaloneorg_lemmy_1 ... done Stopping leemyaloneorg_pictrs_1 ... done Stopping leemyaloneorg_postfix_1 ... done Stopping leemyaloneorg_postgres_1 ... done Going to remove leemyaloneorg_proxy_1, leemyaloneorg_lemmy-ui_1, leemyaloneorg_lemmy_1, leemyaloneorg_pictrs_1, leemyaloneorg_postfix_1, leemyaloneorg_postgres_1 Are you sure? [yN] y Removing leemyaloneorg_proxy_1 ... done Removing leemyaloneorg_lemmy-ui_1 ... done Removing leemyaloneorg_lemmy_1 ... done Removing leemyaloneorg_pictrs_1 ... done Removing leemyaloneorg_postfix_1 ... done Removing leemyaloneorg_postgres_1 ... done Creating leemyaloneorg_postgres_1 ... done Creating leemyaloneorg_pictrs_1 ... done Creating leemyaloneorg_postfix_1 ... done Creating leemyaloneorg_lemmy_1 ... done Creating leemyaloneorg_lemmy-ui_1 ... done Creating leemyaloneorg_proxy_1 ... done root@Lemmy:/srv/lemmy/leemyalone.org/volumes# docker ps CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES 2e9a781c0136 nginx:1-alpine "/docker-entrypoint.…" 15 seconds ago Up 12 seconds 80/tcp, 0.0.0.0:3378->8536/tcp, :::3378->8536/tcp leemyaloneorg_proxy_1 cc68969ca802 dessalines/lemmy-ui:0.18.4 "docker-entrypoint.s…" 17 seconds ago Up 14 seconds 1234/tcp leemyaloneorg_lemmy-ui_1 f47b59d3b801 dessalines/lemmy:0.18.4 "/app/lemmy" 20 seconds ago Up 17 seconds leemyaloneorg_lemmy_1 a6eda85afa9d mwader/postfix-relay "/root/run" 23 seconds ago Up 20 seconds 25/tcp leemyaloneorg_postfix_1 fa066bad4327 asonix/pictrs:0.4.0 "/sbin/tini -- /usr/…" 23 seconds ago Restarting (1) 3 seconds ago leemyaloneorg_pictrs_1 04fad001a73f postgres:15-alpine "docker-entrypoint.s…" 23 seconds ago Up 20 seconds 5432/tcp leemyaloneorg_postgres_1 root@Lemmy:/srv/lemmy/leemyalone.org/volumes# ls lemmy-ui pictrs postgres root@Lemmy:/srv/lemmy/leemyalone.org/volumes# ls -lah total 20K drwxr-xr-x 5 root root 4.0K Aug 26 21:40 . drwxr-xr-x 3 root root 4.0K Aug 26 20:41 .. drwxr-xr-x 3 root root 4.0K Aug 17 08:31 lemmy-ui drwxr-xr-x 2 root root 4.0K Aug 26 21:40 pictrs drwx------ 19 70 root 4.0K Aug 26 21:41 postgres root@Lemmy:/srv/lemmy/leemyalone.org/volumes#

        • sobuddywhoneedsyou@lemmygrad.mlEnglish
          31·
          1 year ago

          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.

          • admin@leemyalone.orgOPEnglish
            2·
            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.