Actions
Bug #4599
opencounter group sgsn:pdpctx already exists for index X, instead using Y
Status:
New
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
Start date:
06/08/2020
Due date:
% Done:
0%
Spec Reference:
Description
When using OsmoSGSN (current nightly) in a setup with 3rd party 2G BSS and 3G RAN, we are running quite often into the following error message:
<0020> rate_ctr.c:224 counter group 'sgsn:pdpctx' already exists for index 5, instead using index 8. This is a software bug that needs fixing.
I wonder how this happens. It basically means we want to allocate a PDP context for the same NSAPI where we already have a PDP context.
The only path that calls sgsn_pdp_ctx_alloc() is sgsn_create_pdp_ctx() via activate_ggsn() originating from do_act_pdp_req() and the latter actually chekcs if we already have a PDP context fro the NSAPI in sgsn_pdp_ctx_by_nsapi. weird.
lynxis any ideas?
Related issues
Actions
