-
Notifications
You must be signed in to change notification settings - Fork 57
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
[Other issue]: rmf_traffic_schedule crash #422
Comments
In the future please use gist.github.com to upload large walls of terminal output. The pertinent log output is this one:
To help us debug the root cause of the problem, you can run follow these steps:
Then copy/paste a link to your gist into a comment here. Once you've done all the above steps, you can run |
@mxgrey, I reformatted the PC before I seeing your reply. The problem is gone now. |
Right the error had to do with failing to parse that file. If we could've seen its contents then maybe we could identify a cause for how it got into a bad state and implement a fix. |
Before proceeding, is there an existing issue or discussion for this?
Description
rmf_demo office fail to launch with the following error code:
[rmf_traffic_schedule-1] [FATAL] [1706509151.310826378] [rmf_traffic_schedule_primary]: Failed to correctly load participant registry: yaml-cpp: error at line 9, column 16: bad conversion
[rmf_traffic_schedule-1]
[rmf_traffic_schedule-1] terminate called after throwing an instance of 'std::exception'
[rmf_traffic_schedule-1] what(): std::exception
.
.
[ERROR] [rmf_traffic_schedule-1]: process has died [pid 115816, exit code -6, cmd '/home/krms/kj_ws/install/rmf_traffic_ros2/lib/rmf_traffic_ros2/rmf_traffic_schedule --ros-args -r __node:=rmf_traffic_schedule_primary --params-file /tmp/launch_params_pnrvbg7u'].
I tried both binary and build from source but error persists.
I am using Humble-release and the default launch command shown below:
ros2 launch rmf_demos_gz_classic office.launch.xml
Tried changing the DDS as recommended by #258 (comment) but did not resolve the error.
I have the same configurations running on another PC but did not see this error. Have you experienced this intermittent error?
Full log shown below:
https://gist.github.com/mxgrey/0e0bb9aa2ff62de02be9e3c6f9aad02f
The text was updated successfully, but these errors were encountered: