Project

General

Profile

Bug #2689

osmo-pcu exits if BTS not yet available after connecting successfully to the unix socket

Added by pespin about 2 months ago. Updated 9 days ago.

Status:
New
Priority:
Normal
Assignee:
Target version:
-
Start date:
11/28/2017
Due date:
% Done:

0%

Spec Reference:

Description

If the unix socket is not yet available, osmo-pcu delays the operation and tries again later without dying:

20171128192520877 DL1IF <0001> /home/pespin/dev/sysmocom/git/osmo-pcu/src/osmobts_sock.cpp:229 Opening OsmoPCU L1 inter
face to OsmoBTS
20171128192520878 DL1IF <0001> /home/pespin/dev/sysmocom/git/osmo-pcu/src/osmobts_sock.cpp:266 Failed to connect to the
 osmo-bts PCU socket, delaying... '/tmp/pcu_bts'
20171128192525883 DL1IF <0001> /home/pespin/dev/sysmocom/git/osmo-pcu/src/osmobts_sock.cpp:229 Opening OsmoPCU L1 inter
face to OsmoBTS
20171128192525883 DL1IF <0001> /home/pespin/dev/sysmocom/git/osmo-pcu/src/osmobts_sock.cpp:266 Failed to connect to the
 osmo-bts PCU socket, delaying... '/tmp/pcu_bts'

However, once it successfully connects, it tries to get information from BTS. If BTS says it is not avaialable, osmo.pcu exits the process instead of waiting for new instructions or change of status from BTS, or try re-connecting to the unix socket and trying again with a delay:

20171128192519079 DL1IF <0001> /home/pespin/dev/sysmocom/git/osmo-pcu/src/osmobts_sock.cpp:229 Opening OsmoPCU L1 inter
face to OsmoBTS
20171128192519079 DL1IF <0001> /home/pespin/dev/sysmocom/git/osmo-pcu/src/osmobts_sock.cpp:288 osmo-bts PCU socket /tmp
/pcu_bts has been connected
20171128192519079 DL1IF <0001> /home/pespin/dev/sysmocom/git/osmo-pcu/src/osmobts_sock.cpp:292 Sending version 0.4.0.7-
a5eb to BTS.
20171128192519079 DL1IF <0001> /home/pespin/dev/sysmocom/git/osmo-pcu/src/pcu_l1_if.cpp:107 Sending 0.4.0.7-a5eb TXT as
 PCU_VERSION to BTS
20171128192519079 DL1IF <0001> /home/pespin/dev/sysmocom/git/osmo-pcu/src/pcu_l1_if.cpp:413 Info indication received:
20171128192519079 DL1IF <0001> /home/pespin/dev/sysmocom/git/osmo-pcu/src/pcu_l1_if.cpp:416 BTS not available
[Inferior 1 (process 16689) exited normally]

History

#1 Updated by laforge about 2 months ago

And once the PCU exits, the BTS also restarts? Or why exactly is this a bug? If it's just the PCU that respawns, nothing is hurt, right?

Yes, in general we should probably work towards living without relying on respawning of processes. But that's more like a new feature than a bugfix?

#2 Updated by pespin about 1 month ago

Well, it's a feature or a bug fix depending on what you expect the good behaviour to be. For me the good behaviour would be that the process is not restarted unless I tell it to do so or because it crashes (unexpectedly). I don't really care whether we take this as a bug or as a feature, but current behaviour should be improved to have a more reliable system without depending on systemd or other means to restart the process.

#3 Updated by laforge 9 days ago

  • Assignee set to stsp

Also available in: Atom PDF