ROS Resources: Documentation | Support | Discussion Forum | Index | Service Status | ros @ Robotics Stack Exchange
Ask Your Question
0

roscore doesn't start normally anymore?

asked 2016-01-11 05:01:43 -0500

Sietse gravatar image

Hello all,

since a week or so, starting roscore doesn't work normally om my machine. The program hangs most of the time, there is nothing more than the command I entered. It only starts if I Ctrl-C the hanging roscore, then it suddenly starts. Very strange.

If I, e.g., start rviz it has the same behaviour (often), it only really starts when I ctrl-C the hanging program.

There were no ros-updates in the last month I think. I am running ubuntu 14.04 and indigo, all standard.

What can we wrong here? Thanks in advance,

Sietse

edit retag flag offensive close merge delete

1 Answer

Sort by ยป oldest newest most voted
0

answered 2016-01-11 05:24:47 -0500

gvdhoorn gravatar image

It only starts if I Ctrl-C the hanging roscore, then it suddenly starts.

It normally takes care of this by itself, but sometimes ROS needs a little help: run a rosclean check and see if it also hangs (or takes a very long time to complete). That is the program that is run first by roscore: it keeps tabs on the nr of log files (and their total size). On a regular HDD (so not an SSD), that can take quite some time.

If rosclean check also 'hangs', you can either run rosclean purge, or manually rm ~/.ros/log/*.log. In both cases make sure you have nothing there you'd like to keep.

edit flag offensive delete link more

Comments

rosclean check check returns immediately, there was 109MB logging. After rosclean purge nothing is changed, so that isn't the problem... Any other possibility?

Sietse gravatar image Sietse  ( 2016-01-11 06:25:02 -0500 )edit
3

Make sure you don't have any incorrect info in your /etc/hosts, or a wrong ROS_IP / ROS_HOSTNAME in your .bashrc. Especially on university / corporate networks (where addressing may change without notice) that sometimes leads to strange (and hard to diagnose) issues.

gvdhoorn gravatar image gvdhoorn  ( 2016-01-11 06:27:28 -0500 )edit

Thanks, that was it! It was some mixup between an extra network interface (to connect to our robots) and the university-linux-network-setup.

Sietse gravatar image Sietse  ( 2016-01-11 07:33:40 -0500 )edit

/etc/hosts /etc/nss and /etc/nsswitch.conf check . ping 127.0.0.1 slowly

robtos gravatar image robtos  ( 2023-07-02 23:59:41 -0500 )edit

Question Tools

1 follower

Stats

Asked: 2016-01-11 05:01:43 -0500

Seen: 5,046 times

Last updated: Jan 11 '16