Project

General

Profile

Actions
Copy link

Bug #6260

closed

GSMTAP sending fails with ENOSPC

Added by matanp 6 months ago. Updated 6 months ago.

Status:
Resolved
Priority:
Urgent
Assignee:
arehbein
Category:
-
Target version:
-
Start date:
11/18/2023
Due date:
% Done:

100%

Spec Reference:

Description

Running all the network stack - osmo-bsc, osmo-bts, osmocom-bb (or a real device with USRP) fails sending GSMTAP messages with:

<002d> osmo_io.c:377 iofd(gsmtap_inst.io_fd)enqueueing message failed (-28). Rejecting msgb

The exact same configuration used to work on November 8th (last time I checked)

Related issues

Related to libosmocore - Bug #6213: Use osmo_io in gsmtap_util.cResolvedarehbein10/05/2023

Actions
Actions
Copy link
 #1

Updated by laforge 6 months ago

  • Assignee set to arehbein
  • Priority changed from Normal to Urgent

I'd expect https://gerrit.osmocom.org/c/libosmocore/+/34743 to be related - this is where we moved gsmtap over to the osmo_io framework.

If this is referring to GSMTAP Um frames (as opposed to GSMTAP logging), https://gerrit.osmocom.org/c/libosmocore/+/35055 might fix it.

Actions
Copy link
 #2

Updated by laforge 6 months ago

  • Description updated (diff)
Actions
Copy link
 #3

Updated by laforge 6 months ago

  • Related to Bug #6213: Use osmo_io in gsmtap_util.c added
Actions
Copy link
 #5

Updated by arehbein 6 months ago

  • Status changed from New to Resolved
  • % Done changed from 0 to 100
Actions
Copy link

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 48.8 MB)