Actions
Bug #6260
closedGSMTAP sending fails with ENOSPC
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
Updated by laforge 11 days 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.
Updated by matanp 10 days ago
https://gerrit.osmocom.org/c/libosmocore/+/35055 did fix it, thanks!
Actions
