Hazelnoot
Important question for Sharkey Admins

Hi all! If you own or administrate a Sharkey instance, then I've got an important question for you. Over the last two weeks, have you experienced any unexpected crashes or restarts accompanied by a log message reading: [core] The process is going to exit with code 0?

If so, then please reach out! We're investigating a possible bug that none of our development team can reproduce. It would help us greatly if you could answer the poll below, even/especially if you haven't experienced a crash!

Boosts would be greatly appreciated, and thanks so much in advance! ​​

#Sharkey #SharkeyAdmins #SharkeyAdmin #FediAdmins
Sharkey 2025.4.2 or newer with Docker - I have experienced a crash
Sharkey 2025.4.2 or newer with Docker - I have **not** experienced this crash
Sharkey 2025.4.2 or newer from source - I have experienced a crash
Sharkey 2025.4.2 or newer from source - I have **not** experienced this crash
Sharkey 2025.2.2 or older with Docker - I have experienced a crash
Sharkey 2025.2.2 or older with Docker - I have **not** experienced this crash
Sharkey 2025.2.2 or older from source - I have experienced a crash
Sharkey 2025.2.2 or older from source - I have **not** experienced this crash
N/A or just show results
Poll ends at .
Jun 10, 2025 at 9:06pmWeb
Show threaddynamyc 🌷 Jun 10, 2025
@hazelnoot the main instance does seem to go down every once in a while on my end but I'm unsure if its cuz of something on my end (due to other things on the machine) or if its related. I never catch when it does exit, and since I have it set up in a way where it'll just auto-restart it if something happens, I don't really notice it, and my current logs don't go that far back anymore to check.

I can try to take a peek more often, but from rough memories, I never saw any logs during random exits. If there's a specific version that'd help troubleshoot it, I don't mind running that for a couple of days and seeing if it does show up during it.
Show threadHazelnootJun 10, 2025
@dynamyc thanks for the info!
Show threadfat synths at the function Jun 10, 2025
@hazelnoot i'm unsure how helpful i can be because if it does crash here i assume docker probably just restarts the process automatically ( and i wonder if that's just the case for everyone else running it in docker )
i do notice occasional freezes every once in a while where everything stops responding for a bit - but i'm unsure if it's related to this issue or if our workers just get clogged too often and stop being able to work
Show threadLatte macchiato  Jun 10, 2025
@hazelnoot checked both my workers, nothing out of the ordinary.
Currently on fc47460ae22a2050aebc1b261090631c06fed5c4
Show threadMarie Jun 10, 2025

@hazelnoot

"We're investigating a possible bug that none of our development team can reproduce"Me who said I ran into this issue on this instance 3 weeks ago with your response being that others also ran into it.

Also it doesn't seem reproducible to begin it it just randomly happens. it only happened that one time for me and then never again (unless it happened while I was sleeping but I wouldn't know)

Show threadHazelnootJun 10, 2025
@marie ah right, I forgot you were hit by it too
Show thread[GARLIC] Lunya 🧄Jun 10, 2025
@hazelnoot checked my logs, these messages appear twice since I updated to 2025.4.2 (first start after the update was on the 31st at 9:25:17, and it crashed on the 1st at 8:41:11 and 8:41:32, all UTC)

I also searched for restarts in general (not just the log message mentioned), none found except for these crashes and the first time after the update where one of the migrations timed out

if there's anything else I could do to help debug this feel free to ask
Show threadHazelnootJun 11, 2025
@luna thanks for the info!
Show threadMin Jun 14, 2025
@hazelnoot I'm not sure what the right answer for me here is because I'm using 2025.2.3. I've held off on updating because I heard there were some issues with 2024.4.2 and haven't heard otherwise since then. Anyway, I'm running in Docker and my instance has been up since April 30th.