Actions
Bug #5239
closedWeird logging during shutdown
Start date:
09/26/2021
Due date:
% Done:
0%
Spec Reference:
Description
Recent osmo-bts (9be6b56033b1bb9f06be90ce6d5ccab129d3755d) produces the following logging on shutdown:
^Csignal 2 received DOML NOTICE oml.c:90 OC=BTS INST=(00,ff,ff): Sending Process stopped to BSC: BTS: SIGINT received -> shutdown DOML NOTICE bts_shutdown_fsm.c:250 BTS_SHUTDOWN(bts0)[0x612000003ca0]{NONE}: Shutting down BTS, exit 1, reason: SIGINT DTRX INFO trx_if.c:255 phy0.0: Enqueuing TRX control command 'CMD SETPOWER -1' DTRX INFO trx_if.c:672 phy0.0: Response message: 'RSP SETPOWER 0 0' DL1C ERROR tx_power.c:200 (bts=0,trx=0) bts_model notifies us of -11000 mdBm TRX output power. However, it should be -10000 mdBm! DTRX INFO trx_if.c:255 phy0.0: Enqueuing TRX control command 'CMD RFMUTE 1' DTRX INFO trx_if.c:255 phy0.0: Enqueuing TRX control command 'CMD POWEROFF' DTRX INFO trx_if.c:672 phy0.0: Response message: 'RSP RFMUTE 0 1' DTRX INFO trx_if.c:672 phy0.0: Response message: 'RSP RFMUTE 0 1' DTRX NOTICE trx_if.c:696 phy0.0: Discarding duplicated RSP from old CMD 'RSP RFMUTE 0 1' DOML ERROR oml.c:220 (bts=0,trx=0): O&M Get Attributes [0], Manufacturer Dependent State is unsupported by TRX. Adding a osmo_fd that is already in the list. DLINP NOTICE ipa.c:128 127.0.0.1:3003 connection done DLINP NOTICE ipaccess.c:897 received ID_GET for unit ID 1801/0/0 DOML ERROR bts_trx.c:214 NM_BBTRANSC_OP(bts0-trx0)[0x6120000042a0]{ENABLED}: Event RSL_UP not permitted DOML NOTICE oml.c:1064 OC=CHANNEL(03) INST=(00,00,05): ADM STATE Shutdown -> Unlocked DOML NOTICE oml.c:1064 OC=CHANNEL(03) INST=(00,00,06): ADM STATE Shutdown -> Unlocked DOML NOTICE oml.c:1064 OC=CHANNEL(03) INST=(00,00,07): ADM STATE Shutdown -> Unlocked DTRX INFO trx_if.c:672 phy0.0: Response message: 'RSP POWEROFF 0' DL1C NOTICE scheduler_trx.c:500 GSM clock stopped DTRX NOTICE trx_if.c:1217 phy0.0: Closing TRXC/TRXD connections DOML NOTICE bts_shutdown_fsm.c:160 BTS_SHUTDOWN(bts0)[0x612000003ca0]{EXIT}: Shutdown process completed successfully, exiting process
In particular, this is what I find weird:
DOML ERROR oml.c:220 (bts=0,trx=0): O&M Get Attributes [0], Manufacturer Dependent State is unsupported by TRX. Adding a osmo_fd that is already in the list. DLINP NOTICE ipa.c:128 127.0.0.1:3003 connection done DLINP NOTICE ipaccess.c:897 received ID_GET for unit ID 1801/0/0 DOML ERROR bts_trx.c:214 NM_BBTRANSC_OP(bts0-trx0)[0x6120000042a0]{ENABLED}: Event RSL_UP not permitted DOML NOTICE oml.c:1064 OC=CHANNEL(03) INST=(00,00,05): ADM STATE Shutdown -> Unlocked DOML NOTICE oml.c:1064 OC=CHANNEL(03) INST=(00,00,06): ADM STATE Shutdown -> Unlocked DOML NOTICE oml.c:1064 OC=CHANNEL(03) INST=(00,00,07): ADM STATE Shutdown -> Unlocked
It looks like osmo-bts is trying to establish an A-bis/RSL link again?!?
Files
Updated by pespin over 2 years ago
- Status changed from New to Feedback
- Assignee changed from pespin to fixeria
I believe this shouldn't occur anymore since osmo-bts.git 1c3431db95950ea47938524921ce9ae6a7d2128b merged some days ago, which delays Abis reconnect until bts has shtudown properly.
Please fixeria reassign with new output if you still see issues.
Updated by fixeria over 2 years ago
- Status changed from Feedback to Resolved
pespin wrote:
I believe this shouldn't occur anymore since osmo-bts.git 1c3431db95950ea47938524921ce9ae6a7d2128b merged some days ago, which delays Abis reconnect until bts has shtudown properly.
I confirm that the logging messages I saw before are gone now. Thanks!
Actions