I think this means that something is wrong with lemmy-ui
, but I’m not sure what.
ETA: I’m eleanorOpossum on beehaw.org.
EDIT: FIGURED IT OUT
Cause: I deleted everything in the pictrs folder after the CSAM raid on lemmy.world. The UI was crashing because it couldn’t load the site icon.
Solution:
TL; DR: I ran this UPDATE site SET icon = NULL FROM local_site WHERE site.id = local_site.site_id;
in the database.
My install uses lemmy-ansible, so my DB was in a docker container.
- I ran
docker ps
to find the id of the container running the DB - Then I ran this to connected to it
docker exec -it $CONTAINER_ID_FROM_DOCKER_PS pqsql -U lemmy -d lemmy
- Then I searched for my instance in the
- And then I ran this SQL expression to set my site icon to
null
;UPDATE site SET icon = NULL FROM local_site WHERE site.id = local_site.site_id;
Based on this comment and the rest of that thread (along with some basic SQL knowledge)
Do you by chance have the logs from lemmy-ui’s container?
Still, OP, just replying from my Beehaw account since I can’t see your comment on my instance. (That’s also why it took me a day to respond…) Yes!
Constant spam of this. Gonna check the GH issues
lemmy-ui_1 | Error: Input bit Array is empty lemmy-ui_1 | at Sharp._createInputDescriptor (/app/node_modules/sharp/lib/input.js:56:13) lemmy-ui_1 | at new Sharp (/app/node_modules/sharp/lib/constructor.js:351:29) lemmy-ui_1 | at Sharp (/app/node_modules/sharp/lib/constructor.js:173:12) lemmy-ui_1 | at /app/dist/js/server.js:2:1229532 lemmy-ui_1 | at tryCatch (/app/node_modules/@babel/runtime/helpers/regeneratorRuntime.js:44:17) lemmy-ui_1 | at Generator. (/app/node_modules/@babel/runtime/helpers/regeneratorRuntime.js:125:22) lemmy-ui_1 | at Generator.next (/app/node_modules/@babel/runtime/helpers/regeneratorRuntime.js:69:21) lemmy-ui_1 | at asyncGeneratorStep (/app/node_modules/@babel/runtime/helpers/asyncToGenerator.js:3:24) lemmy-ui_1 | at _next (/app/node_modules/@babel/runtime/helpers/asyncToGenerator.js:22:9) lemmy-ui_1 | at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
Tried restarting the stack?
Yep, restarted it a couple of times. (Sorry, my instance wasn’t federated with this one so I didn’t see the comment) Still, OP, just replying from my Beehaw account since I can’t see your comment on my instance.
What did you do before this started?