Ask Your Question
1

Problem with log and home directories and roslaunch handlers

asked 2015-11-11 14:06:13 -0500

tslator gravatar image

updated 2015-11-12 01:53:43 -0500

gvdhoorn gravatar image

I'm having a problem robot_upstart. When I start the service it uses a different value for ROS_LOG_DIR, it says that HOME is not defined, and also reports there are no handlers for roslaunch. I've pasted a log below:

hal@arlobot:~/catkin_ws/src/ArloBot/src/arlobot_apps/arlobot_webif/www$ sudo tail /var/log/upstart/arlobot.log -f
[sudo] password for hal:
logger: arlobot: Using workspace setup file /home/hal/catkin_ws/devel/setup.bash
logger: arlobot: Launching ROS_HOSTNAME=arlobot, ROS_IP=, ROS_MASTER_URI=http://127.0.0.1:11311, ROS_LOG_DIR=/tmp
ls: cannot access /etc/ros/indigo/arlobot.d/*.xacro: No such file or directory
logger: arlobot: Generated launchfile: /tmp/arlobot.launch
logger: arlobot: Started roslaunch as background process, PID 9009, **ROS_LOG_DIR=/tmp
WARNING: cannot create log directory [/tmp/852af2b6-88a5-11e5-8d69-408d5c19117e]. Please set ROS_LOG_DIR to a writable location.**
Checking log directory for disk usage. This may take awhile.
Press Ctrl-C to interrupt
Done checking log file disk usage. Usage is <1GB.

logger: arlobot: Using workspace setup file /home/hal/catkin_ws/devel/setup.bash
logger: arlobot: Launching ROS_HOSTNAME=arlobot, ROS_IP=, ROS_MASTER_URI=http://127.0.0.1:11311, ROS_LOG_DIR=/tmp
ls: cannot access /etc/ros/indigo/arlobot.d/*.xacro: No such file or directory
logger: arlobot: Generated launchfile: /tmp/arlobot.launch
logger: arlobot: Started roslaunch as background process, PID 9146, ROS_LOG_DIR=/tmp
WARNING: cannot create log directory [/tmp/a7c12afe-88a8-11e5-88de-408d5c19117e]. Please set ROS_LOG_DIR to a writable location.
Checking log directory for disk usage. This may take awhile.
Press Ctrl-C to interrupt
Done checking log file disk usage. Usage is <1GB.

**No handlers could be found for logger "roslaunch"
environment variable 'HOME' is not set**
The traceback for the exception was written to the log file
logger: arlobot: Using workspace setup file /home/hal/catkin_ws/devel/setup.bash
logger: arlobot: Launching ROS_HOSTNAME=arlobot, ROS_IP=, ROS_MASTER_URI=http://127.0.0.1:11311, ROS_LOG_DIR=/tmp
ls: cannot access /etc/ros/indigo/arlobot.d/*.xacro: No such file or directory
logger: arlobot: Generated launchfile: /tmp/arlobot.launch
logger: arlobot: Started roslaunch as background process, PID 9225, ROS_LOG_DIR=/tmp
WARNING: cannot create log directory [/tmp/a86bd620-88a8-11e5-9cab-408d5c19117e]. Please set ROS_LOG_DIR to a writable location.
Checking log directory for disk usage. This may take awhile.
Press Ctrl-C to interrupt
Done checking log file disk usage. Usage is <1GB.
edit retag flag offensive close merge delete

1 Answer

Sort by ยป oldest newest most voted
0

answered 2016-01-27 04:12:34 -0500

Peter Heim gravatar image

May be a bit late but I had a similar error my upstart was working then it gave the above errors I put in a extra launch line to start COB face recognition when i remove the line robot upstart worked as before

edit flag offensive delete link more

Comments

Did you ever find a fix for this other than removing functionality. I am getting the same errors trying to start an openCV haar cascade filter on startup.

shoemakerlevy9 gravatar image shoemakerlevy9  ( 2016-08-17 11:58:22 -0500 )edit

no I never fixed the cause I just start it manually when required

Peter Heim gravatar image Peter Heim  ( 2016-08-18 15:34:21 -0500 )edit

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer

Question Tools

Stats

Asked: 2015-11-11 14:06:13 -0500

Seen: 1,072 times

Last updated: Jan 27 '16