1 comment:

Patchset:
- Patch Set #3:
  I am having problems running ttcn3-msc-test locally after upgrading libosmo-netif.
  The testsuite fails 2/3 times with the following verdict:
```
BSSMAP: Timeout waiting for RESET-ACK after sending RESET
```
  This is what I am seeing in osmo-msc logs:
```
20240412160137929 DLM3UA NOTICE 0: asp-asp-clnt-OsmoMSC-A: Received NOTIFY Type State Change:AS Inactive () (m3ua.c:622)
20240412160137929 DLSS7 NOTICE xua_default_lm(asp-clnt-OsmoMSC-A)[0x5f3290453540]{ACTIVE}: Ignoring primitive M-ASP_ACTIVE.confirm (xua_default_lm_fsm.c:400)
20240412160137929 DLM3UA NOTICE 0: asp-asp-clnt-OsmoMSC-A: Received NOTIFY Type State Change:AS Active () (m3ua.c:622)
20240412160138921 DLGSUP NOTICE GSUP connecting to 127.0.0.1:4222 (gsup_client.c:74)
20240412160139246 DLINP NOTICE CLICONN(asp-clnt-OsmoMSC-A,r=127.0.0.1:2905<->l=127.0.0.1:35677){CONNECTED} received result -11 in response to recvmsg (stream_cli.c:508)
20240412160139246 DLSS7 NOTICE xua_default_lm(asp-clnt-OsmoMSC-A)[0x5f3290453540]{ACTIVE}: Ignoring primitive M-ASP_DOWN.indication (xua_default_lm_fsm.c:400)
```
  -11 is `Resource Temporarily Unavailable`.
  Reverting this patch makes osmo-msc stable again.
  Somehow Jenkins is not affected.

To view, visit change 36354. To unsubscribe, or for help writing mail filters, visit settings.