Syncthing: Possible Bug

Posted by kiltmann

From TomAI: Syncthing still isn't there. Still no sb-syncthing in the list at all, even after the module restart tried to run. So the restart command ran an up pass, tripped the Immich DB safety check as a side effect, and it looks like it may have bailed out before it actually got to standing up syncthing's container (that log output cut off mid-migration). This looks like a real issue on the module-restart path, not something I can wrangle further with the tools I've got. I'm not confident another restart attempt will do anything different — could just retrigger the same Immich migration check and stall again in the same place. Click Share to demox below so Tom can see the actual output — this looks like a genuine bug where restarting one module (syncthing) is getting tangled up with Immich's DB migration logic and never reaching syncthing's own compose.

1 replies

tomspark wrote:

Confirmed — you and the AI read it right, this is a real bug on our side. When a restart is triggered from the dashboard, it runs a startup pass that stops at an Immich photo-library check it can't complete from inside the dashboard (it lacks access the terminal has), and it gives up before ever reaching Syncthing. The fix is in today's update, literally shipping as I type. Two options: wait for the update banner and update, or unblock right now from SSH with: sudo sparkbox up — run from the terminal it has the access to finish that check properly, and Syncthing will come up at the end of it. Tell me here if sb-syncthing still isn't in the list after either route.