auto-launching a ROS job is not working
there is a ROS process called autostart that I would like to initiate itself on startup. I used robot_upstart package to do this, and the roslaunch script calls a node from a remotely connected machine (the machine that starts the autostart process has an IP address of yyy.yyy.yyy.yyy, and the remotely connected machine has an IP address of xxx.xxx.xxx.xxx). After rebooting, however, the process could not be started. When I typed the command sudo service autostart status, I got the following message
● autostart.service - "bringup autostart"
Loaded: loaded (/lib/systemd/system/autostart.service; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Fri 2018-02-02 14:15:09 EST; 39s ago
Process: 608 ExecStart=/usr/sbin/autostart-start (code=exited, status=1/FAILURE)
Main PID: 608 (code=exited, status=1/FAILURE)
Feb 02 14:15:08 tegra-ubuntu autostart-start[608]: Press Ctrl-C to interrupt
Feb 02 14:15:08 tegra-ubuntu autostart-start[608]: Done checking log file disk usage. Usage is <1GB.
Feb 02 14:15:08 tegra-ubuntu autostart-start[608]: [26B blob data]
Feb 02 14:15:08 tegra-ubuntu autostart-start[608]: started roslaunch server http://yyy.yyy.yyy.yyy:41853/
Feb 02 14:15:08 tegra-ubuntu autostart-start[608]: remote[xxx.xxx.xxx.xxx-0] starting roslaunch
Feb 02 14:15:08 tegra-ubuntu autostart-start[608]: remote[xxx.xxx.xxx.xxx-0]: creating ssh connection to 192.168.2.42:22, user[linuxmachine]
Feb 02 14:15:08 tegra-ubuntu autostart-start[608]: [xxx.xxx.xxx.xxx-0] killing on exit
Feb 02 14:15:09 tegra-ubuntu systemd[1]: autostart.service: Main process exited, code=exited, status=1/FAILURE
Feb 02 14:15:09 tegra-ubuntu systemd[1]: autostart.service: Unit entered failed state.
Feb 02 14:15:09 tegra-ubuntu systemd[1]: autostart.service: Failed with result 'exit-code'.
but when I typed the command sudo service autostart stop followed by sudo service autostart start, the process started without any trouble. Anybody would give me any hint as to what is happening when the machine gets booted up?
The machine is Ubuntu 16.04 by the way.
Hi, not sure if you've gotten anywhere with this, but I note that there is a reference to a log file
Done checking log file disk usage. Usage is <1GB, is the output that you've shared from that log, If so, can you customize the logging verbosity and see if DEBUG doesn't show you more info ?Did you manage to solve this?