-
Notifications
You must be signed in to change notification settings - Fork 443
Run roslaunch niryo_moveit part_2.launch but process has died [pid 10010, exit code 127 #392
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
same error, did you solve it? |
same error, wondering whether you've solved it |
Hi, here is how i solved it : |
I have the same problem as you. Have you solved it? |
I fix it. |
If the problem persists after changing the first line of the script to #!/usr/bin/env python3 check the file format.
|
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:
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

Environment (please complete the following information, where applicable):
Additional context
Hope my problem can be solved, thank you very much
The text was updated successfully, but these errors were encountered: