Unknown error initiating TCP/IP socket

edit

Hello,

I'm using an actionlib server to control a Jaco arm in Gazebo. After sending a few thousand actions repeatedly, I lose connection with Gazebo, which returns a segmentation fault and suggests to look at the log file.

The log file shows an "Unknown error initiating TCP/IP socket". This is due to self.read_buff which returns None instead of returning a BytesIO() object, see /opt/ros/melodic/lib/python2.7/dist-packages/rospy/impl/tcpros_base.py, line 662

This is very similar to this or this but it didn't help.

Does anybody know what is causing this communication issue?

Error returned by Gazebo:

Segmentation fault (core dumped)
[gazebo-2] process has died [pid 2316, exit code 139, cmd /opt/ros/kinetic/lib/gazebo_ros/gzserver -u -e ode /home/<name>/catkin_ws/src/kinova-ros/kinova_gazebo/worlds/jaco.world __name:=gazebo __log:=/home/<name>/.ros/efc60178-7915-11ea-958a-0242ac110005/gazebo-2.log].
log file: /home/<name>/.ros/efc60178-7915-11ea-958a-0242ac110005/gazebo-2*.log

Log file:

[rospy.client][INFO] 2020-04-22 14:33:50,220: init_node, name[/kinova_client], pid[29534]
[xmlrpc][INFO] 2020-04-22 14:33:50,220: XML-RPC server binding to 0.0.0.0:0
[xmlrpc][INFO] 2020-04-22 14:33:50,220: Started XML-RPC server [http://<hostname>:36845/]
[rospy.init][INFO] 2020-04-22 14:33:50,220: ROS Slave URI: [http://<hostname>:36845/]
[rospy.impl.masterslave][INFO] 2020-04-22 14:33:50,220: _ready: http://<hostname>:36845/
[rospy.registration][INFO] 2020-04-22 14:33:50,221: Registering with master node http://localhost:11311
[xmlrpc][INFO] 2020-04-22 14:33:50,221: xml rpc node: starting XML-RPC server
[rospy.init][INFO] 2020-04-22 14:33:50,321: registered with master
[rospy.rosout][INFO] 2020-04-22 14:33:50,321: initializing /rosout core topic
[rospy.rosout][INFO] 2020-04-22 14:33:50,325: connected to core topic /rosout
[rospy.simtime][INFO] 2020-04-22 14:33:50,326: initializing /clock core topic
[rospy.simtime][INFO] 2020-04-22 14:33:50,328: connected to core topic /clock
[rospy.internal][INFO] 2020-04-22 14:33:50,330: topic[/clock] adding connection to [http://<hostname>:41419/], count 0
[rospy.internal][INFO] 2020-04-22 14:33:50,341: topic[/j2n6s300/effort_joint_trajectory_controller/follow_joint_trajectory/status] adding connection to [http://<hostname>:41419/], count 0
[rospy.internal][INFO] 2020-04-22 14:33:50,372: topic[/j2n6s300/effort_joint_trajectory_controller/follow_joint_trajectory/result] adding connection to [http://<hostname>:41419/], count 0
[rospy.internal][INFO] 2020-04-22 14:33:50,374: topic[/j2n6s300/effort_joint_trajectory_controller/follow_joint_trajectory/feedback] adding connection to [http://<hostname>:41419/], count 0
[rospy.internal][INFO] 2020-04-22 14:33:50,488: topic[/j2n6s300/effort_joint_trajectory_controller/follow_joint_trajectory/goal] adding connection to [/gazebo], count 0
[rospy.internal][INFO] 2020-04-22 14:33:50,566: topic[/rosout] adding connection to [/rosout], count 0
[rospy.internal][INFO] 2020-04-22 14:33:50,589: topic[/j2n6s300/effort_joint_trajectory_controller/follow_joint_trajectory/cancel] adding connection to [/gazebo], count 0
[rospy.internal][INFO] 2020-04-22 14:33:50,593: topic[/gazebo/set_model_state] adding connection to [/gazebo], count 0
[rospy.internal][INFO] 2020-04-22 14:33:52,943: topic[/j2n6s300/joint_states] adding connection to [http://<hostname>:41419/], count 0
[rospy.internal][INFO] 2020-04-22 14:33:52,961: topic impl's ref count is zero ...