I suspect it's due to these lines in your /etc/hosts: > 127.0.0.1 prometheus > 192.168.1.102 prometheus localhost I'm not a network admin, but AFAIK localhost should be probably mapped to 127.0.0.1 for IPv4. - Ken On Wed, Aug 18, 2010 at 12:16 PM, Max B wrote: > I never had boxturtle. This happens with every launchfile. > $ more hosts > 127.0.0.1 prometheus > # The following lines are desirable for IPv6 capable hosts > ::1 localhost ip6-localhost ip6-loopback > fe00::0 ip6-localnet > ff00::0 ip6-mcastprefix > ff02::1 ip6-allnodes > ff02::2 ip6-allrouters > ff02::3 ip6-allhosts > 192.168.1.102 prometheus localhost > No one else uses this machine. > On Wed, Aug 18, 2010 at 2:35 PM, Ken Conley wrote: >> >> It would be helpful to have more information on your setup to try and >> narrow this sort of thing down, as it is very uncommon, thus not >> easily diagnosed. >> >> For example: >> >> 1) did this work with boxturtle? >> 2) does this happen with any roslaunch file, or just a particular file? >> 3) what does your /etc/hosts look like, your ifconfig, etc... >> 4) are other people using the same machine >> >>  - Ken >> >> On Tue, Aug 17, 2010 at 10:35 AM, Max B wrote: >> > To Ken: >> >> >> >> As above, there is likely a network issue. >> > >> > >> > What kind of network issue? Nothing on the ROS troubleshooting page >> > helped. >> > I tried adding a rule for port 11311 in ufw, and that didn't help. nmap >> > says >> > that port 11311 is open. >> > From, >> >    Max >> > _______________________________________________ >> > ros-users mailing list >> > ros-users@code.ros.org >> > https://code.ros.org/mailman/listinfo/ros-users >> > >> > >> _______________________________________________ >> ros-users mailing list >> ros-users@code.ros.org >> https://code.ros.org/mailman/listinfo/ros-users > > _______________________________________________ > ros-users mailing list > ros-users@code.ros.org > https://code.ros.org/mailman/listinfo/ros-users > >