Where can I find the log files after a crash?

asked 2015-08-14 14:52:57 -0600

Sebastian gravatar image

updated 2015-08-14 15:52:38 -0600

move_base keeps crashing and I am trying to figure out why. The error is as follows:

[move_base-9] process has died [pid 11340, exit code -11, cmd /opt/ros/indigo/lib/move_base/move_base cmd_vel:=mobile_base/commands/velocity __name:=move_base __log:=/home/sebastian/.ros/log/6c0459b4-42bc-11e5-91ba-c8f733552779/move_base-9.log].
log file: /home/sebastian/.ros/log/6c0459b4-42bc-11e5-91ba-c8f733552779/move_base-9*.log

The error seems to give the directory of a log file, however no such file exists.

Does anyone have tips on how to debug this move_base crash? I think it is something to do with the global planner plugin I wrote.

Here are the contents of the directory:

total 264
-rw-rw-r-- 1 sebastian sebastian      0 Aug 14 12:41 base_footprint_broadcaster-6-stdout.log
-rw-rw-r-- 1 sebastian sebastian      0 Aug 14 12:41 diagnostic_aggregator-4-stdout.log
-rw-rw-r-- 1 sebastian sebastian   3714 Aug 14 12:42 gmapping-7-stdout.log
-rw-rw-r-- 1 sebastian sebastian      0 Aug 14 12:41 laser_tf_broadcaster-5-stdout.log
-rw-rw-r-- 1 sebastian sebastian 102228 Aug 14 12:49 master.log
-rw-rw-r-- 1 sebastian sebastian    435 Aug 14 12:49 mobile_base-3-stdout.log
-rw-rw-r-- 1 sebastian sebastian   1540 Aug 14 12:49 mobile_base_nodelet_manager-2-stdout.log
-rw-rw-r-- 1 sebastian sebastian  66499 Aug 14 12:49 roslaunch-sebastian-rostop-10960.log
-rw-rw-r-- 1 sebastian sebastian    155 Aug 14 12:41 rosout-1-stdout.log
-rw-rw-r-- 1 sebastian sebastian  74983 Aug 14 12:49 rosout.log
edit retag flag offensive close merge delete


I am using gdb to debug move_base, which is fine, but I am still curious about these log files.

Sebastian gravatar image Sebastian  ( 2015-08-14 15:22:33 -0600 )edit

can you post the contents of that directory? e.g., ls -l /home/sebastian/.ros/log/6c0459b4-42bc-11e5-91ba-c8f733552779

Morgan gravatar image Morgan  ( 2015-08-14 15:43:12 -0600 )edit

Ok, edited. This is actually a problem that I noticed for any errors (says there is a log file, but I can't find it).

Sebastian gravatar image Sebastian  ( 2015-08-14 15:53:01 -0600 )edit

hmm, I wonder if the custom global planner plugin is causing move_base to crash immediately on startup, even before the log file is created. Can you try it again without the custom global planner plugin, and see if then the log file appears as expected?

Morgan gravatar image Morgan  ( 2015-08-14 16:27:01 -0600 )edit

Move_base had been running for a minute before this crash occurred. Maybe I have a parameter configured to not output the log? This happens every time any node dies. It says to look at a log file which doesn't exist. Is it possible the log file is empty, so it was never created?

Sebastian gravatar image Sebastian  ( 2015-08-14 16:54:09 -0600 )edit

It's possible the default log level for move_base is lower than expected. Are you printing log messages in your custom planner plugin with a high level (i.e., ROS_ERROR) ?

Morgan gravatar image Morgan  ( 2015-08-14 17:29:43 -0600 )edit