Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Comms TCP/IP failure #1005

Open
peci1 opened this issue Aug 23, 2021 · 0 comments
Open

Comms TCP/IP failure #1005

peci1 opened this issue Aug 23, 2021 · 0 comments
Labels
bug Something isn't working

Comments

@peci1
Copy link
Collaborator

peci1 commented Aug 23, 2021

In one of our local simulations, we have seen this error in the comms client node:

[rosout][WARNING] 2021-08-22 02:07:00,173: Inbound TCP/IP connection failed: timed out
[rospy.internal][ERROR] 2021-08-22 02:07:00,175: Inbound TCP/IP connection failed:
Traceback (most recent call last):
  File "/opt/ros/melodic/lib/python2.7/dist-packages/rospy/impl/tcpros_base.py", line 325, in _tcp_server_callback
    header = read_ros_handshake_header(sock, StringIO(), buff_size)
  File "/opt/ros/melodic/lib/python2.7/dist-packages/rosgraph/network.py", line 357, in read_ros_handshake_header
    d = sock.recv(buff_size)
timeout: timed out

I assume it is generated by a timeout in the service call from SubT ROS relay when a message is sent to the client. After this error, the comms client did not receive any comms for about a minute (of real time).

I'm not really sure this has a solution, but I wanted to report the error so that other teams have one more place to look at when debugging.

@nkoenig nkoenig added the bug Something isn't working label Oct 11, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants