Inbound TCP/IP connection failed... help?
Hi,
Has anyone come across the warning message:
[WARN] [WallTime 1395255145.292842] Inbound TCP/IP connection failed: connection from sender terminated before handshake header received. 0 bytes were received. Please check sender for additional details.
I experience this multiple times when running different nodes in my system. The only thing they have in common is a class that I made to handle a lot of the communication such that all the publishers and subscribers together. Could launching several instances of this class in each node cause an error such as above?
I am lost as regards what the problem may be as I haven't noticed any actual loss of functionality but given that it is to be used for a control system I would prefer it not to continuously give warning messages!
I am using ROS on a ubuntu 12.04 LTS machine with 8 core i7 processor.
Any ideas much appreciated :)
Please don't open duplicates. It seems nobody knows the answer, and opening your question over and over again doesn't convince people to investige for you.
Sorry I know this looks bad but actually it was a problem trying to log in resulting in my question being posted multiple times!
Oh ok, thanks for clarifying ;-). I hope you can login fine now. Sorry I can't help with the question. You could try dig in the code and see where this message comes from exactly.
getting the same problem over and over again
I never found a solution to this and instead switched away from using topics to solely using the parameter server. Its okay for my application where the data throughput isn't that high but certainly isn't as efficient as using topics.
@lvsteenson: you are using the parameter server as a surrogate for topics?
@lvsteenson: if you can share that 'common class' somehow, we can perhaps find out why this is happening. Are you creating/destroying publishers/subscribers at a high rate?
Basically my system now uses the parameter server to save the latest data from all of the sensors, the controller setpoints etc. Before I was simply creating a publisher once upon the node being launched as would be normal but any other node that was subscribed would have that warning.