Revision history [back]

Not an answer yet, but I share some things to look at installation issue with robot_upstart (not limited to these):

• Does the service have an access to:
  • the ROS packages you defined in the launch file you passed to the install script?
  • ROS-related environment variables e.g. ROS_PACKAGE_PATH?
• For a list of resources the install script shows at the end of its run, do you still see them at each location after reboot?
• Do you see your application's log under /var/log/upstart/? If so do you see any errors.

Not an answer yet, but I share some things to look at installation issue with robot_upstart (not limited to these):

• Does the service have an access to: to the following? Log on as the user that runs the service process and see:
  • the ROS packages you defined in the launch file you passed to the install script?
  • ROS-related environment variables e.g. ROS_PACKAGE_PATH?
• For a list of resources the install script shows at the end of its run, do you still see them at each location after reboot?
• Do you see your application's log under /var/log/upstart/? If so do you see any errors.

Not an answer yet, but I share some things to look at installation issue with robot_upstart (not limited to these):

• Does the service have an access to the following? Log on as the user user account (i.e. usually root for upstart) that runs the service process and see:
  • the ROS packages you defined in the launch file you passed to the install script?
  • ROS-related environment variables e.g. ROS_PACKAGE_PATH?
• For a list of resources the install script shows at the end of its run, do you still see them at each location after reboot?
• Do you see your application's log under /var/log/upstart/? If so do you see any errors.