Hey @Radient737,
From what we can see, every Shell command on your bot’s computer has been stalling before it starts since about 08:30 SAST, for all of your bots. The Reset at about 09:34 SAST did finish and moved the computer onto a fresh machine with your files restored, but commands still stall. That points to something in your saved files, not the machine itself.
Every Shell command first starts a login shell, and that runs the computer’s shell startup files. If one of them waits on something (for example a line that starts a service, runs sudo, waits for a login or network, or calls a script), every command hangs exactly like this. A very similar case was solved this way: Grok Bot shared computer fully wedged.
The good part is that your bots can still read files on their computer, because reading doesn’t go through that login shell. Saving fails because bots save files by running a command, which is the part that’s stuck.
Could you try this:
- Ask one of your bots to open these three files on its own computer (not your PC) with its file reading tool, not with Shell (Shell will hang):
/home/box/.bashrc,/home/box/.profileand/home/box/.bash_profile. If it can’t find them there, try~/.bashrc,~/.profileand~/.bash_profile. - Ask it to tell you whether anything looks recently added, especially near the end of each file.
- Reply here with a short description of what it finds. No need to paste the full contents or anything private.
In the meantime, please hold off on another Reset or Update, since a Reset restores the same files.