Bug #1878
closedRate ctr init is not added in osmopcu
100%
Description
Though the rate ctr framework is used in osmopcu in show bts statistics.
It is always 0 for the intervals.
Osmo-PCU> show bts statistics
BTS Statistics:
TBF DL Allocated : 13 (0/s 0/m 0/h 0/d)
TBF DL Freed : 12 (0/s 0/m 0/h 0/d)
TBF DL Aborted : 0 (0/s 0/m 0/h 0/d)
TBF UL Allocated : 377 (0/s 0/m 0/h 0/d)
TBF UL Freed : 376 (0/s 0/m 0/h 0/d)
TBF UL Aborted : 7 (0/s 0/m 0/h 0/d)
TBF Reused : 4 (0/s 0/m 0/h 0/d)
TBF Alloc Algo A : 0 (0/s 0/m 0/h 0/d)
TBF Alloc Algo B : 395 (0/s 0/m 0/h 0/d)
TBF Failed EGPRS-only: 0 (0/s 0/m 0/h 0/d)
The timer is not armed.
Updated by laforge over 7 years ago
On Wed, Dec 14, 2016 at 05:50:57AM +0000, sivasankari [REDMINE] wrote:
Though the rate ctr framework is used in osmopcu in show bts statistics.
It is always 0 for the intervals.
it seems like osmo-pcu is missing a call to rate_ctr_init() during
start-up, resulting in the rate_ctr periodic timer to never run/expire,
and thus not update the interval counters.
--
- Harald Welte <laforge@gnumonks.org> http://laforge.gnumonks.org/
============================================================================
"Privacy in residential applications is a desirable marketing option."
(ETSI EN 300 175-7 Ch. A6)
Updated by sivasankari over 7 years ago
Identified the issue.Will be releasing a patch with the fix.
Updated by arvind.sirsikar over 7 years ago
- Status changed from New to Closed
- Assignee set to sivasankari
- % Done changed from 0 to 100
- Estimated time set to 10:00 h
PCU commit : ee78bf0882d982ed69a98a0207dec1a1d00de32a