Bug #4197

"running broken" if configured IP is not assigned at startup

Added by keith over 1 year ago. Updated about 1 year ago.

Target version:
Start date:
Due date:
% Done:


Spec Reference:


I observed on a Debian system that systemd is starting the osmo-sip-connector before the system is fully up and all network interfaces are configured.
This results in:

DLGLOBAL NOTICE <0004> telnet_interface.c:104 Available via telnet 4256
DMNCC NOTICE <0001> mncc.c:1021 Scheduling MNCC connect
DSIP NOTICE <0000> :0 su_source_port_create() returns 0x55a3df9dd5d0
DSIP NOTICE <0000> :0 nta: bind(;transport=*): Cannot assign requested address
DSIP NOTICE <0000> :0 nua: initializing SIP stack failed
DSIP ERROR <0000> main.c:163 Failed to initialize SIP. Running broken

This is not terribly useful.

Instead we could:

1) exit (in the hopes that the OS will bring us back up again and now the interface is configured).

2) retry to bind at regular intervals.

3) In the case of systemd, add the following (i believe) to the service file:

However, I'm no systemd expert.


#1 Updated by keith over 1 year ago

  • Description updated (diff)

#2 Updated by keith over 1 year ago

  • Description updated (diff)

#3 Updated by fixeria over 1 year ago

+1, I also experienced this problem with OsmoSIPCon, and probably with OsmoGGSN too.

#4 Updated by lynxis over 1 year ago

what's the use of a "Running broken". Does it have any feature we could use? Or does it recover?

If there aren't any, exit(1) would my way of fixing this.

#6 Updated by lynxis over 1 year ago

  • Assignee set to lynxis

#7 Updated by laforge about 1 year ago

  • Status changed from Feedback to Closed
  • % Done changed from 70 to 100

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 48.8 MB)