https://osmocom.org/https://osmocom.org/favicon.ico?16647414092020-06-08T19:02:24ZOpen Source Mobile CommunicationsOsmoSGSN - Bug #4599: counter group sgsn:pdpctx already exists for index X, instead using Yhttps://osmocom.org/issues/4599?journal_id=186262020-06-08T19:02:24Zlaforge
<ul><li><strong>Related to</strong> <i><a class="issue tracker-1 status-1 priority-2 priority-default" href="/issues/4604">Bug #4604</a>: Lots of "Unusual event"</i> added</li></ul> OsmoSGSN - Bug #4599: counter group sgsn:pdpctx already exists for index X, instead using Yhttps://osmocom.org/issues/4599?journal_id=186902020-06-11T18:58:23Zlynxis
<ul><li><strong>Assignee</strong> changed from <i>lynxis</i> to <i>laforge</i></li></ul><p>This is a problem of the SGSN code and how it allocates rate counter groups.</p>
<p>The problem here is, that the sgsn tries to allocate a new rate counter for "sgsn:pdpctx" and use as identifier the nsapi. But the nsapi is only unique within a single MS. The rate counter expects this identifier to be unique across the SGSN.</p> OsmoSGSN - Bug #4599: counter group sgsn:pdpctx already exists for index X, instead using Yhttps://osmocom.org/issues/4599?journal_id=187152020-06-13T18:17:55Zlaforge
<ul><li><strong>Status</strong> changed from <i>Feedback</i> to <i>New</i></li><li><strong>Assignee</strong> changed from <i>laforge</i> to <i>4368</i></li></ul><p>Ok, so the rate counter group allocations should not simply use the NSAPI but some kind of number that is globally unique.</p> OsmoSGSN - Bug #4599: counter group sgsn:pdpctx already exists for index X, instead using Yhttps://osmocom.org/issues/4599?journal_id=196002020-09-09T10:05:11ZMPoslusny
<ul></ul><p>I confirm that I see this message on our installation often as well.<br />Could this have an effect on the MS connection time?</p>