Grok Bot shell dead since Oct 22 – every command stalls 840s; .bashrc unreadable + .profile autostart loop; Update/Reset don't help

Support Bug Reports
,
14

Hey @beartester,

You’re right about line 30 of .profile! We ran it in the same login shell your bots use: the shell finishes, but the background copy it starts keeps the command’s output open, so the command never registers as started and times out at 840 seconds. Every bot command goes through that startup, so they all stall.

That line isn’t part of the standard setup. By default .profile ends at line 27, and nothing on our side adds to it. Since it starts your ledger-api folder, most likely one of your bots added it while setting ledger-api up to autostart.

It began with the automatic update on Oct 22 around 8:11 AM IST, right after your last working command. Every restart since (your Update and both Resets) re-runs the saved .profile, so none could clear it. The file reader hanging on /home/box/.bashrc while other files open instantly suggests that file is huge or not a normal file, so replace it too.

Your bots can’t save files right now (saving goes through the stuck command step), but they can still copy files to and from your PC. If they can reach your Ubuntu PC:

  1. Have a bot copy /etc/skel/.bashrc to your PC as ~/bashrc-stock using CopyFromBox, not Shell. That’s the stock .bashrc. If the copy fails, run cp /etc/skel/.bashrc ~/bashrc-stock on your PC instead
    Ubuntu’s version is nearly identical.
  2. Have a bot copy /home/box/.profile to your PC as ~/profile-fixed the same way. Open it and put a # at the start of line 30 (the ledger-api line). If the copy fails, have a bot read the file with its file reading tool and save the full text as ~/profile-fixed yourself.
  3. Have a bot copy ~/bashrc-stock to /home/box/.bashrc and ~/profile-fixed to /home/box/.profile using CopyToBox, not Shell.
  4. Run Update Bot’s Computer once. Stuck commands only clear on restart.
  5. Have a bot run echo ok.

Step 3 overwrites the current .bashrc, so anything your bots added there is gone. Once commands work, a bot can re-add settings you need (environment variables, for example), but not lines that start programs. The ledger-api loops stop on their own at the restart in step 4. If you want ledger-api to autostart later, do it from a scheduled routine rather than .profile or .bashrc, since anything those files leave running blocks every command.