-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
process has died [pid 5825, exit code -11, #1159
Comments
A good rule of thumb with error debugging is to identify the first line of a list of errors. The first error that occurs may set off a "cascade" chain reaction of errors in systems that are affected by the first failure. If the first error is resolved then the subsequent errors may disappear. In your log, the first error is: WARNING [140127390017280] (ds5-timestamp.cpp:76) UVC metadata payloads not available. @doronhi the RealSense ROS wrapper developer offers advice on this error in the link below. |
That’s not an error , it’s a warning |
It looks like the subsequent backend errors are generated from backend-v4l2.h https://github.com/IntelRealSense/librealsense/blob/master/src/linux/backend-v4l2.h#L183 |
I get same log here is my log �[0m[ INFO] [1586448339.349322896]: Loading nodelet /camera/realsense2_camera of type realsense2_camera/RealSenseNodeFactory to manager realsense2_camera_manager with the following remappings:�[0m |
roslaunch realsense2_camera rs_camera.launch started roslaunch server http://mike-Blade:40965/ SUMMARYPARAMETERS
NODES auto-starting new master setting /run_id to 1921acf8-7a7d-11ea-99ff-a0cec81fb9c9 [ INFO] [1586448830.997020490]: Device with physical ID /sys/devices/pci0000:00/0000:00:14.0/usb2/2-1/2-1:1.0/video4linux/video0 was found. |
@mikeNike9 Thanks a lot for adding your discussion link! That discussion is likely to be the best place for yourself and @jediofgever to get assistance with this problem, as it has the attention of two Intel guys (Doronhi and RealSenseCustomerSupport). I'm still learning about ROS, so they should be able to provide better advice on the subject of these errors right now. |
Honestly @MartyG-RealSense @doronhi @RealSenseCustomerSupport Our company will be using this ros wrapper frequently with our new core products |
@mikeNike9 Thanks so much for your support for RealSense! If you have code for the wrapper that you think can be of benefit, a "pull request" can be submitted for review at the link below. |
please look carefully to see what I call an error and a "WARNING". Back to the issue, yes seems like we are having the same issue. I saw the content of the link you provided. Its a bitter experience with realsense, they dont have a stable version of pair of their lib and ROS wrapper, with each update there is a new issue worse than previous one. |
This case will be closed after 7 days from the time of writing this message if there are no further comments. Thank you. |
@jediofgever I am sorry that the outcome of this case was not to your satisfaction. It is a problem though that requires developer attention. As a member of the support team (not the developer team), I do not have the ability to create a solution for the get_device_time_ms() error. A fix for it is awaiting developer approval for merging into the RealSense SDK. |
some info;
Note; I get this issue in other kernel versions as well.
what could be the possible reasons of what happens in following
I start my camera node and log is ;
The error I get is ;
process has died
in the log file it points;
The text was updated successfully, but these errors were encountered: