Actions
Bug #4785
closedDozens of 'pcu_sock.c:870 PCU socket not connected, dropping message' when osmo-pcu disconnects/crashes
Start date:
10/09/2020
Due date:
% Done:
100%
Spec Reference:
Description
When using dynamic PDCH timeslots (TCH/F_TCH/H_PDCH), disconnection of the PCU (e.g. due to a crash) makes osmo-bts flood stderr with:
DPCU NOTICE pcu_sock.c:870 PCU socket not connected, dropping message DPCU NOTICE pcu_sock.c:870 PCU socket not connected, dropping message DPCU NOTICE pcu_sock.c:870 PCU socket not connected, dropping message DPCU NOTICE pcu_sock.c:870 PCU socket not connected, dropping message DPCU NOTICE pcu_sock.c:870 PCU socket not connected, dropping message DPCU NOTICE pcu_sock.c:870 PCU socket not connected, dropping message DPCU NOTICE pcu_sock.c:870 PCU socket not connected, dropping message DPCU NOTICE pcu_sock.c:870 PCU socket not connected, dropping message DPCU NOTICE pcu_sock.c:870 PCU socket not connected, dropping message DPCU NOTICE pcu_sock.c:870 PCU socket not connected, dropping message DPCU NOTICE pcu_sock.c:870 PCU socket not connected, dropping message DPCU NOTICE pcu_sock.c:870 PCU socket not connected, dropping message DPCU NOTICE pcu_sock.c:870 PCU socket not connected, dropping message DPCU NOTICE pcu_sock.c:870 PCU socket not connected, dropping message DPCU NOTICE pcu_sock.c:870 PCU socket not connected, dropping message DPCU NOTICE pcu_sock.c:870 PCU socket not connected, dropping message DPCU NOTICE pcu_sock.c:870 PCU socket not connected, dropping message
I guess we need to handle PCU disconnection gracefully and deactivate all PDCH slots.
Actions
