Skip to content

docs(troubleshooting): explain reconnect flow after host reboot#904

Closed
WuKongAI-CMU wants to merge 1 commit into
NVIDIA:mainfrom
WuKongAI-CMU:docs/469-reconnect-after-reboot
Closed

docs(troubleshooting): explain reconnect flow after host reboot#904
WuKongAI-CMU wants to merge 1 commit into
NVIDIA:mainfrom
WuKongAI-CMU:docs/469-reconnect-after-reboot

Conversation

@WuKongAI-CMU

@WuKongAI-CMU WuKongAI-CMU commented Mar 25, 2026 •
edited by coderabbitai Bot
Loading

Copy link
Copy Markdown
Contributor

Summary

  • add a troubleshooting section for reconnecting after the host machine reboots
  • document the recovery order: start the container runtime, inspect sandbox state, reconnect, then restart auxiliary services if needed
  • point users back to nemoclaw onboard when the sandbox does not recover

Testing

  • not run (docs-only change)

Fixes #469

Summary by CodeRabbit

  • Documentation
    • Added troubleshooting guide for recovering from host reboot scenarios, including container runtime verification, sandbox status checks, and service restart procedures.

@WuKongAI-CMU
docs(troubleshooting): explain reconnect flow after host reboot
35f8573 
Signed-off-by: peteryuqin <peter.yuqin@gmail.com>
@github-actions

github-actions Bot commented Mar 25, 2026

Copy link
Copy Markdown
Contributor

This repository limits contributors to 10 open pull requests. Please close or merge existing PRs before opening new ones.

@github-actions github-actions Bot closed this Mar 25, 2026
@coderabbitai

coderabbitai Bot commented Mar 25, 2026 •
edited
Loading

Copy link
Copy Markdown
Contributor

Caution

Review failed

The pull request is closed.

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: a653d33c-21e5-4225-819a-6b0086ad1931

📥 Commits

Reviewing files that changed from the base of the PR and between 0ef5dd2 and 35f8573.

📒 Files selected for processing (1)
  • docs/reference/troubleshooting.md
📝 Walkthrough

Walkthrough

Added a troubleshooting guide section documenting the process to reconnect to an existing nemoclaw sandbox after a host reboot, including steps to start the container runtime, verify sandbox status, and reconnect using nemoclaw commands.

Changes

Cohort / File(s) Summary
Documentation
docs/reference/troubleshooting.md		 Added new "Reconnect after a host reboot" troubleshooting section with step-by-step recovery flow: start container runtime, verify sandbox readiness with openshell sandbox list, reconnect with nemoclaw <name> connect, restart services, or fall back to nemoclaw onboard if needed.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Poem

🐰 After reboots that make your sandbox sleep,
Docker awakes, and reconnections run deep,
nemoclaw connect brings you back online fast,
Resume your work—no more restart from the past!

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests

Comment @coderabbitai help to get the list of available commands and usage tips.

@WuKongAI-CMU WuKongAI-CMU mentioned this pull request Mar 25, 2026
Closed
This was referenced Mar 25, 2026
Closed
Merged
@WuKongAI-CMU WuKongAI-CMU mentioned this pull request Mar 25, 2026
Closed
@wscurran wscurran added the chore Build, CI, dependency, or tooling maintenance label Jun 8, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

chore Build, CI, dependency, or tooling maintenance

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

Please add restart commands to documentation

2 participants

@WuKongAI-CMU @wscurran