Closed tkem closed 8 years ago
Note this workaround requires Mopidy v1.0 due to mopidy/mopidy#1257.
Problem persists.
Try calling Release
on the manager object so dleyna-server can exit.
Early implementation with Release
showed same behavior, so delaying this.
Just noted that even new media Servers will not be recognized in this state, so this is probably a dleyna issue. Unless that gets resolved, a complete restart if the dleyna process will probably be necessary.
For better or worse, this hasn't shown up on my "production system" for several week now. Closing this for now, with some sense of doubt...
Sometimes, usually after a couple of days running without problems, DLNA media servers get "lost" and will not be found again, even after library refresh.
This could be due to local network problems or dLeyna/Mopidy/Mopidy-dLeyna signal/notification issues. Until this is analyzed in more detail, a library refresh should also actively refresh the known servers and not depend on found/lost signals.