Pricing
00
In productionProbeginnerNamespace

The action server cannot be found

Reconnect the mission client to Nav2 without removing the robot namespace.

Pairs with Nodes, names, and namespaces in ROS 2 Systems Debugging. Read the concept first, then diagnose it here.

Unlock this lab with Pro

Operator report

The client waits for `/navigate_to_pose`, while the server is visible under `/robot_1/navigate_to_pose`.

Ubuntu 24.04, ROS 2 Jazzy, Python and C++ nodes, browser telemetry workspace

01

System boundary

Trace only the relevant path.

3 nodes
  1. 01mission_client→
  2. 02/navigate_to_pose→
  3. 03Nav2 action serverOUT
02

How this lab works

You diagnose it. No command list.

Open the repair workspace and gather your own evidence in a real terminal. No diagnostic commands are handed to you - finding the fault is the exercise. Stuck? Progressive hints unlock inside the workspace.

03

Verification

Pass more than the visible symptom.

4 checks
  • Action server discovered
  • Goal accepted
  • Hidden regression behavior
  • Root cause explanation