Bug #1838

Race conditions between CONNMAN and SMB and UPnP clients

Added by Leonid Protasov almost 7 years ago. Updated almost 7 years ago.

Status:FixedStart date:01/07/2014
Priority:HighDue date:
Assignee:Andreas Smas% Done:

100%

Category:UPnP & DLNA
Target version:4.4
Found in version:all Platform:RPi

Description

When RPI powers on and loading ST, ST loads quickier then CONNMAN ups ethernet connection
00:00:00.558: Settings [DEBUG]:Read /stos/persistent/showtime/settings/upnp -- 52 bytes. File OK
00:00:00.603: thread [DEBUG]:Created detached thread: connman
00:00:00.758: Settings [DEBUG]:Trying to load /stos/persistent/showtime/settings/connman -- No such file or directory
00:00:03.796: SMB [DEBUG]:Unable to connect to 192.168.0.190:445 - No route to host
00:00:04.049: CONNMAN [DEBUG]:Technologies: ([(objectpath '/net/connman/technology/ethernet', {'Name': <'Wired'>, 'Type': <'ethernet'>, 'Powered': <true>, 'Connected': <true>, 'Tethering': <false>})],)
00:00:06.561: SMB [DEBUG]:Unable to connect to 192.168.0.190:445 - No route to host

In the example above you see that SMB share connection tries to connect before interface is up. Logically it's better to wait until interface is up. There's no sense to try to connect if interface is down.
Also if interface is down - UPnP client startup fails and doesn't work at all even if interface is up. Cured only by restarting ST.
This issue affects all platforms.

Associated revisions

Revision 6ea6761a
Added by Andreas Smas almost 7 years ago

ssdp: If we fail to bind, retry later

Fixes #1838

Change included in version 4.3.673

History

#1 Updated by Andreas Smas almost 7 years ago

  • Status changed from New to Fixed
  • % Done changed from 0 to 100

Applied in changeset git|commit:6ea6761a8c35bffe24e88442909089057d807d16.

Also available in: Atom PDF