Project

General

Profile

Bug #2775

osmo-sgsn crashes after "counter group 'sgsn:mmctx' already exists for index 0"

Added by lynxis 4 months ago. Updated 3 months ago.

Status:
Closed
Priority:
Immediate
Assignee:
Category:
-
Target version:
-
Start date:
12/19/2017
Due date:
% Done:

100%

Spec Reference:

Description

version 41505ae1d3485533d743d4c46e6c2269f64f0533

      DRANAP <001a> ../../../src/osmo-iuh/src/iu_client.c:509 handle_co_initial(dir=1, proc=19)
      DRANAP <001a> ../../../src/osmo-iuh/src/iu_client.c:229 RNC 23: new LAC 24358 RAC 22
      DMM <0002> ../../../../src/osmo-sgsn/src/gprs/gprs_gmm.c:1271 MM(---/ffffffff) -> GMM ATTACH REQUEST MI(3427325924) type="GPRS attach" 
      DLGLOBAL <001d> ../../../src/libosmocore/src/rate_ctr.c:195 counter group 'sgsn:mmctx' already exists for index 0
      DMM <0002> ../../../../src/osmo-sgsn/src/gprs/gprs_sgsn.c:272 MM(/00000000) Cannot allocate counter group

      Program received signal SIGSEGV, Segmentation fault.
      gsm48_rx_gmm_att_req (llme=0x0, msg=0x555555886950, ctx=0x0) at ../../../../src/osmo-sgsn/src/gprs/gprs_gmm.c:1375
      1375                          ctx->p_tmsi = tmsi;

History

#1 Updated by lynxis 4 months ago

pcap file with whole traffic is present.

#2 Updated by neels 4 months ago

  • Subject changed from crash when using nano3g together with osmo-sgsn to osmo-sgsn crashes after "counter group 'sgsn:mmctx' already exists for index 0"
  • Status changed from New to In Progress
  • Priority changed from Normal to Immediate
  • % Done changed from 0 to 90

the interesting bit is just above the bt you posted.
A fix of the libosmocore trigger is https://gerrit.osmocom.org/5516
and of the segfault https://gerrit.osmocom.org/5517

#3 Updated by neels 4 months ago

  • Description updated (diff)

#4 Updated by neels 4 months ago

  • Assignee set to neels

#5 Updated by neels 4 months ago

  • % Done changed from 90 to 100

https://gerrit.osmocom.org/5516 merged, which fixes the issue in osmo-sgsn.
https://gerrit.osmocom.org/5517 is related to failure handling in osmo-sgsn at that place, but with this osmo-sgsn would still fail to establish more than one mm context.

#6 Updated by neels 4 months ago

  • Status changed from In Progress to Resolved

#7 Updated by laforge 3 months ago

  • Status changed from Resolved to Closed

Also available in: Atom PDF