Unable to find/localize log file

asked 2019-08-27 08:26:05 -0500

Shortfollower gravatar image

Hi everyone

I was trying to run Bezier_examples package but for some reason after starting example launch file

roslaunch bezier_examples fanuc_m10ia_surfacing.launch surfacing_mode:=true mesh_cad:=plane/plane_defect.ply

rviz crushes instantly. To resolve this problem I need to read log file but for some reason the file which path is given in console does not exist.

REQUIRED process [bezier_examples_surfacing-6] has died!
process has died [pid 24603, exit code -6, cmd /home/brian/catkin_workspace/devel/lib/bezier_examples/bezier_examples_surfacing __name:=bezier_examples_surfacing __log:=/home/brian/.ros/log/754af8fe-c8cb-11e9-b951-080027af27c1/bezier_examples_surfacing-6.log].
log file: /home/brian/.ros/log/754af8fe-c8cb-11e9-b951-080027af27c1/bezier_examples_surfacing-6*.log

Does anyone had the similar problem before? What can be the cause for log file not to be saved ?

My Setup: Ubuntu 18.04 VM with Melodic distro

Full log:

root@brian-VirtualBox:~/catkin_workspace# roslaunch bezier_examples fanuc_m10ia_surfacing.launch surfacing_mode:=true mesh_cad:=plane/plane_defect.ply
... logging to /home/brian/.ros/log/754af8fe-c8cb-11e9-b951-080027af27c1/roslaunch-brian-VirtualBox-24558.log
Checking log directory for disk usage. This may take awhile.
Press Ctrl-C to interrupt
Done checking log file disk usage. Usage is <1GB.

xacro: in-order processing became default in ROS Melodic. You can drop the option.
started roslaunch server http://brian-VirtualBox:36149/

SUMMARY
========

PARAMETERS
 * /controller_joint_names: ['joint_1', 'join...
 * /mesh_cad_param: plane/plane_defec...
 * /mesh_defect_param: 
 * /move_group/allow_trajectory_execution: True
 * /move_group/capabilities: 
 * /move_group/controller_list: [{'joints': ['joi...
 * /move_group/disable_capabilities: 
 * /move_group/generic_hw_control_loop/cycle_time_error_threshold: 0.01
 * /move_group/generic_hw_control_loop/loop_hz: 300
 * /move_group/hardware_interface/joints: ['joint_1', 'join...
 * /move_group/hardware_interface/sim_control_mode: 1
 * /move_group/jiggle_fraction: 0.05
 * /move_group/joint_state_controller/publish_rate: 50
 * /move_group/joint_state_controller/type: joint_state_contr...
 * /move_group/manipulator/default_planner_config: LBKPIECE
 * /move_group/manipulator/longest_valid_segment_fraction: 0.005
 * /move_group/manipulator/planner_configs: ['SBL', 'EST', 'L...
 * /move_group/manipulator/projection_evaluator: joints(joint_1,jo...
 * /move_group/max_range: 5.0
 * /move_group/max_safe_path_cost: 1
 * /move_group/moveit_controller_manager: moveit_simple_con...
 * /move_group/moveit_manage_controllers: True
 * /move_group/moveit_sim_hw_interface/joint_model_group: controllers_initi...
 * /move_group/moveit_sim_hw_interface/joint_model_group_pose: controllers_initi...
 * /move_group/octomap_resolution: 0.025
 * /move_group/planner_configs/BFMT/balanced: 0
 * /move_group/planner_configs/BFMT/cache_cc: 1
 * /move_group/planner_configs/BFMT/extended_fmt: 1
 * /move_group/planner_configs/BFMT/heuristics: 1
 * /move_group/planner_configs/BFMT/nearest_k: 1
 * /move_group/planner_configs/BFMT/num_samples: 1000
 * /move_group/planner_configs/BFMT/optimality: 1
 * /move_group/planner_configs/BFMT/radius_multiplier: 1.0
 * /move_group/planner_configs/BFMT/type: geometric::BFMT
 * /move_group/planner_configs/BKPIECE/border_fraction: 0.9
 * /move_group/planner_configs/BKPIECE/failed_expansion_score_factor: 0.5
 * /move_group/planner_configs/BKPIECE/min_valid_path_fraction: 0.5
 * /move_group/planner_configs/BKPIECE/range: 0.0
 * /move_group/planner_configs/BKPIECE/type: geometric::BKPIECE
 * /move_group/planner_configs/BiEST/range: 0.0
 * /move_group/planner_configs/BiEST/type: geometric::BiEST
 * /move_group/planner_configs/BiTRRT/cost_threshold: 1e300
 * /move_group/planner_configs/BiTRRT/frountier_node_ratio: 0.1
 * /move_group/planner_configs/BiTRRT/frountier_threshold: 0.0
 * /move_group/planner_configs/BiTRRT/init_temperature: 100
 * /move_group/planner_configs/BiTRRT/range: 0.0
 * /move_group/planner_configs/BiTRRT/temp_change_factor: 0.1
 * /move_group/planner_configs/BiTRRT/type: geometric::BiTRRT
 * /move_group/planner_configs/EST/goal_bias: 0.05
 * /move_group/planner_configs/EST/range: 0.0
 * /move_group/planner_configs/EST/type: geometric::EST
 * /move_group/planner_configs/FMT/cache_cc: 1
 * /move_group/planner_configs/FMT/extended_fmt: 1
 * /move_group/planner_configs/FMT/heuristics: 0
 * /move_group/planner_configs/FMT/nearest_k: 1
 * /move_group/planner_configs/FMT/num_samples: 1000
 * /move_group/planner_configs/FMT/radius_multiplier: 1.1
 * /move_group/planner_configs/FMT/type: geometric::FMT
 * /move_group/planner_configs/KPIECE/border_fraction: 0.9
 * /move_group/planner_configs/KPIECE/failed_expansion_score_factor: 0.5
 * /move_group/planner_configs/KPIECE/goal_bias: 0.05
 * /move_group/planner_configs/KPIECE/min_valid_path_fraction: 0.5
 * /move_group/planner_configs/KPIECE/range: 0.0 ...
(more)
edit retag flag offensive close merge delete

Comments

Not an answer, but:

My Setup: Ubuntu 18.04 VM with Melodic distro

RViz (and Gazebo) in a VM has been very difficult in the past. You may want to verify whether the crash also happens on a non-VM install.

gvdhoorn gravatar imagegvdhoorn ( 2019-08-27 09:17:27 -0500 )edit

what is the latest log in your log directory? To check it, type:

roscd log

then list the logs by date with:

ls -lt
ermanas gravatar imageermanas ( 2019-08-27 09:26:03 -0500 )edit

Most likely there is no log. RViz crashes too soon.

gvdhoorn gravatar imagegvdhoorn ( 2019-08-27 10:46:22 -0500 )edit

Try removing or commenting out the rviz included launch and see if that isolates. You could run it separatately too. I hate to suggest it but do you have all of the dependencies installed?

prefpkg21 gravatar imageprefpkg21 ( 2019-08-27 11:08:09 -0500 )edit

When it comes to log files that’s what I got

-rw-r--r-- 1 root root  1365 srp 28 08:15 master.log
-rw-r--r-- 1 root root   151 srp 28 08:15 rosout-1-stdout.log
-rw-r--r-- 1 root root    37 srp 28 08:15 rosout.log
-rw-r--r-- 1 root root 12017 srp 28 08:15 roslaunch-brian-VirtualBox-2692.log

There is no really much info about crush in those logs. I tried to reinstall package, but problem is still there. The only clue I got is the warning while building Bezier_examples package

/usr/bin/ld: warning: libboost_system.so.1.65.1, needed by /opt/ros/melodic/lib/libmoveit_move_group_interface.so, may conflict with libboost_system.so.1.58.0
cd /home/brian/catkin_workspace/build/bezier_examples; catkin build --get-env bezier_examples | catkin env -si  /usr/bin/make --jobserver-fds=6,7 -j; cd -

After commenting out the rviz launch problem was still there. So I commented out the Bezier ...(more)

Shortfollower gravatar imageShortfollower ( 2019-08-28 05:19:35 -0500 )edit

I tried to run it separately but for some reason node also have some issues.

~/catkin_workspace# rosrun bezier_examples painting.cpp 
/home/brian/catkin_workspace/src/bezier_examples/bezier_examples/src/painting.cpp: line 1: //: Is a directory
/home/brian/catkin_workspace/src/bezier_examples/bezier_examples/src/painting.cpp: line 5: //#pragma: No such file or directory
/home/brian/catkin_workspace/src/bezier_examples/bezier_examples/src/painting.cpp: line 6: //#pragma: No such file or directory
/home/brian/catkin_workspace/src/bezier_examples/bezier_examples/src/painting.cpp: line 9: //#pragma: No such file or directory
/home/brian/catkin_workspace/src/bezier_examples/bezier_examples/src/painting.cpp: line 17: /bin: Is a directory

If resolving the issue with library conflict won’t help, I will try to reinstall everything on non-VM machine and check if the problem is repeatable on it. Thanks for help

Shortfollower gravatar imageShortfollower ( 2019-08-28 05:21:20 -0500 )edit

The Boost conflict is a likely candidate. It's very likely that it is causing the crash.

re: rosrun bezier_examples painting.cpp: you cannot execute a .cpp source file directly. It's not a script, it must be compiled first (and bezier_examples painting.cpp is not the node, it's one of the source files that make up the node, after compilation).

gvdhoorn gravatar imagegvdhoorn ( 2019-08-28 05:28:48 -0500 )edit