Run roslaunch niryo_moveit part_2.launch but process has died [pid 10010, exit code 127

未關閉
#392 6 則留言 1 個 reaction 已指派 0 人 在 GitHub 檢視

還沒有人認領這個 Issue。

評估

難度
2/5
預估耗時
1-3 小時
新手友好度
35/100
Issue 類型
缺陷
描述清晰度
基本清楚
活躍度
停滯
技術堆疊
python, unity
領域
robotics

研究方向

Start with the roslaunch niryo_moveit part_2.launch entry point and the referenced ros_tcp_endpoint/src/ros_tcp_endpoint/default_server_endpoint.py command, then reproduce the launch after sourcing the workspace. Check the endpoint startup against the reported '/usr/bin/env: python: No such file or directory' log; done means the server_endpoint process starts without restarting or exiting with code 127.

由索引模型根據 Issue 內容生成。

描述

Describe the bug
In Pick-and-Place Tutorial Part 2: ROS–Unity Integration
I Run roslaunch niryo_moveit part_2.launch
but See error
process has died [pid 10010, exit code 127

To Reproduce
Steps to reproduce the behavior:

  1. Go to my workspace
  2. run catkin_make && source devel/setup.bash
  3. Run roslaunch niryo_moveit part_2.launch
  4. See error

Console logs / stack traces
process[server_endpoint-2]: started with pid [10010]
/usr/bin/env: ‘python’: No such file or directory
[server_endpoint-2] process has died [pid 10010, exit code 127, cmd /home/lz/ROS/src/ros_tcp_endpoint/src/ros_tcp_endpoint/default_server_endpoint.py --wait __name:=server_endpoint __log:=/home/lz/.ros/log/fa595246-cb21-11ed-b866-086ac5a336a7/server_endpoint-2.log].
log file: /home/lz/.ros/log/fa595246-cb21-11ed-b866-086ac5a336a7/server_endpoint-2*.log
[server_endpoint-2] restarting process

Expected behavior
I hope to get the same result as in the tutorial.

Screenshots
image

Environment (please complete the following information, where applicable):

  • Unity Version: [e.g. Unity 2020.3.11f1]
  • Unity machine OS + version: [e.g. Windows 10]
  • ROS machine OS + version: [e.g. WSL Ubuntu 20.04, ROS Noetic]

Additional context
Hope my problem can be solved, thank you very much

主要語言
C#
星號
2.6k
分支
473
PR 合併指標
30 天內沒有已合併 PR

環境準備

  • 沒有 Dockerfile 或 Docker Compose 檔案
  • 有 Pull Request 範本
  • 沒有貢獻指南

從這裡開始

  1. 先讀完整個 Issue,再讀專案的貢獻指南。
  2. 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
  3. Fork 儲存庫,在一個分支上完成修改。
  4. 送出 Pull Request,並在描述裡引用這個 Issue 編號。

Unity-Technologies/Unity-Robotics-Hub 的其他 Issue

查看 Unity-Technologies/Unity-Robotics-Hub 的全部 Issue

相似的 Issue

更多 C# Issue

把新 issue 寄到你的電子郵件信箱

精選適合新手參與的 GitHub issue 摘要。