Something came back from one of the bots:
Only .profile opened. Reading .bashrc hung for 14 minutes, the same way the terminal does.
.bash_profiledoesn’t exist..profileis the standard Ubuntu file and looks clean. It loads.bashrcand adds~/binand~/.local/binto the path, nothing more..bashrcwouldn’t open, but I read part of it yesterday at 08:11 SAST, before everything locked up. At lines 119–120, Brok had added a check that starts the Telegram relay supervisor (/workspace/relay-supervisor/supervise.sh --loop) whenever a terminal opens.
That line is my main suspect. Every terminal any bot opens runs it, so if the relay folder or its lock file hangs, every terminal hangs with it. Once the computer is reachable again, the likely fix is to remove that line and start the relays a different way. I’d pass that change to Brok (my engineer bot)
---- Further questioning ----
Brok put it there to keep the Telegram links for Mimir, Mercury and Money Penny alive. Your bots’ computer has no built-in way to start a program when it boots or on a timer. So when the relays needed to come back by themselves after a restart, Brok made every new terminal check whether the relay manager was running and start it if not. Normally that check takes a split second and does no harm.
The catch is that every bot’s terminal now depends on that check. If the relay folder or its lock file gets stuck, it can take every terminal down with it. I can’t prove that’s what happened until the computer responds again, but it’s the one custom change in the startup files. When it’s back, I’d have Brok remove the line and start the relays from a routine that runs on a schedule instead.