Project

General

Profile

Bug #4197

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

Added by keith about 1 month ago. Updated about 1 month ago.

Status:
Feedback
Priority:
Normal
Assignee:
Target version:
-
Start date:
09/11/2019
Due date:
% Done:

70%

Resolution:

Description

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 127.0.0.1 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(172.16.0.1:5050;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:

After=network-online.target
Wants=network-online.target

However, I'm no systemd expert.

History

#1 Updated by keith about 1 month ago

  • Description updated (diff)

#2 Updated by keith about 1 month ago

  • Description updated (diff)

#3 Updated by fixeria about 1 month ago

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

#4 Updated by lynxis about 1 month 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 about 1 month ago

  • Assignee set to lynxis

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 48.8 MB)