Project

General

Profile

Actions

Bug #2778

closed

CTRL connection sockets are never closed, even on EOF

Added by laforge over 6 years ago. Updated over 6 years ago.

Status:
Closed
Priority:
Urgent
Assignee:
Category:
libosmoctrl
Target version:
-
Start date:
12/22/2017
Due date:
% Done:

100%

Spec Reference:

Description

Whenever a CTRL client is releasing the TCP connection, the Osmocom CTRL server implementation in libosmoctrl is not cleaning up any state, nor closing the FD :(

Actions #1

Updated by laforge over 6 years ago

  • Status changed from New to In Progress
  • % Done changed from 0 to 50
Actions #3

Updated by laforge over 6 years ago

BTW: found while executing with the TTCN-3 testsuite, as it starts a new CTRL connection for every test case, and (presumably at TRAP time) I would get lists of messages like

<0028> control_if.c:421 Failed to write message to the control connection.
<0028> control_if.c:421 Failed to write message to the control connection.
<0028> control_if.c:421 Failed to write message to the control connection.
<0028> control_if.c:421 Failed to write message to the control connection.
<0028> control_if.c:421 Failed to write message to the control connection.
<0028> control_if.c:421 Failed to write message to the control connection.
<0028> control_if.c:421 Failed to write message to the control connection.
<0028> control_if.c:421 Failed to write message to the control connection.
<0028> control_if.c:421 Failed to write message to the control connection.
<0028> control_if.c:421 Failed to write message to the control connection.
<0028> control_if.c:421 Failed to write message to the control connection.
<0028> control_if.c:421 Failed to write message to the control connection.
<0028> control_if.c:421 Failed to write message to the control connection.
<0028> control_if.c:421 Failed to write message to the control connection.
<0028> control_if.c:421 Failed to write message to the control connection.
<0028> control_if.c:421 Failed to write message to the control connection.
<0028> control_if.c:421 Failed to write message to the control connection.
<0028> control_if.c:421 Failed to write message to the control connection.
<0028> control_if.c:421 Failed to write message to the control connection.
<0028> control_if.c:421 Failed to write message to the control connection.
<0028> control_if.c:421 Failed to write message to the control connection.
<0028> control_if.c:421 Failed to write message to the control connection.
<0028> control_if.c:421 Failed to write message to the control connection.
<0028> control_if.c:421 Failed to write message to the control connection.
<0028> control_if.c:421 Failed to write message to the control connection.
<0028> control_if.c:421 Failed to write message to the control connection.
<0028> control_if.c:421 Failed to write message to the control connection.
<0028> control_if.c:421 Failed to write message to the control connection.

and that list was growing, so the conclusion was quite clear.

Actions #4

Updated by laforge over 6 years ago

  • Status changed from In Progress to Closed
  • % Done changed from 50 to 100
Actions

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 48.8 MB)