I face the following problem:
UPNP Servers not found
Device running volumio:
DIY X86 PC with Gigabyte Mainboard GA-H81M-D2W, i7-4770K, 16GB Ram.
onboard network, video and audio ( analog out)
Volumio booting from USB Stick. Version 3.114
logfile:http://logs.volumio.org/volumiobuster/nJAMsC1.html
I got the same general network problems i also faced with different volumio 2 and other volumio 3 versions on several older intel platforms: partially network is not working: i’m able to play internetradio see internet pages etc. but UPNP media servers are not shown in the media servers list and/or not found - even not after hours.
Either they are all ( 2+ ) there or none.
But!: I can play from the last 100 list from my (not found !) media servers and NAS. But i cannot choose new albums etc.
It seems it even got more worse with volumio 3.
Sometimes ( but seldom) reboot helps, sometimes using a fixed IP helps.
Usually once it worked fine it continues to work ( at least with volumio 2)
I am using wired 1 GBit/s network only, no WLAN - Wireless is not installed and always switched off.
In conjunction with this i made some tests ( changing from fixed to dynamic IP) and was surprised that all the time i saved the settings there was an error message in red on the upper right corner , telling me that the wireless network could not be restarted although its switched off through the volumio settings.
I use several other UPNP streamers and systems ( e.g. foobar2000 for windows on the same machine , bubble UPNP, YAMAHA MusicCast ) ) and had never issues finding the UPNP server on my NAS - this happens only with volumio.
The Synology DS920+ NAS is always up due to a surveillance video system running all the time and the FRitz!Box router and UPNP server, too as it is my primary Network router and Gateway.
Volumio is able to receive the IP from that gateway when using dynamic IP but the UPNP server on the same device is not found/shown !??.
It would be fine to solve this otherwise volumio is not usable for me on my various X86 platforms.
ADDITION: This is the error that prevents it from starting
Oct 18 08:24:39 volumioh81md2w volumio[828]: Unhandled rejection Error: No sockets available, cannot start.
Oct 18 08:24:39 volumioh81md2w volumio[828]: at SsdpClient.SSDP._createSockets (/volumio/node_modules/node-ssdp/lib/index.js:186:11)
Oct 18 08:24:39 volumioh81md2w volumio[828]: at SsdpClient.SSDP._start (/volumio/node_modules/node-ssdp/lib/index.js:229:10)
Oct 18 08:24:39 volumioh81md2w volumio[828]: at /volumio/node_modules/node-ssdp/lib/client.js:60:10
Oct 18 08:24:39 volumioh81md2w volumio[828]: at Promise._execute (/volumio/node_modules/bluebird/js/release/debuggability.js:384:9)
Oct 18 08:24:39 volumioh81md2w volumio[828]: at Promise._resolveFromExecutor (/volumio/node_modules/bluebird/js/release/promise.js:518:18)
Oct 18 08:24:39 volumioh81md2w volumio[828]: at new Promise (/volumio/node_modules/bluebird/js/release/promise.js:103:10)
Oct 18 08:24:39 volumioh81md2w volumio[828]: at SsdpClient.start (/volumio/node_modules/node-ssdp/lib/client.js:54:10)
Oct 18 08:24:39 volumioh81md2w volumio[828]: at SsdpClient.search (/volumio/node_modules/node-ssdp/lib/client.js:82:17)
Oct 18 08:24:39 volumioh81md2w volumio[828]: at ControllerUPNPBrowser.onStart (/volumio/app/plugins/music_service/upnp_browser/index.js:126:12)
Oct 18 08:24:39 volumioh81md2w volumio[828]: at PluginManager.startCorePlugin (/volumio/app/pluginmanager.js:380:24)
Oct 18 08:24:39 volumioh81md2w volumio[828]: at HashMap. (/volumio/app/pluginmanager.js:478:31)
Oct 18 08:24:39 volumioh81md2w volumio[828]: at HashMap.forEach (/volumio/node_modules/hashmap/hashmap.js:171:10)
Oct 18 08:24:39 volumioh81md2w volumio[828]: at HashMap.proto. [as forEach] (/volumio/node_modules/hashmap/hashmap.js:201:7)
Oct 18 08:24:39 volumioh81md2w volumio[828]: at PluginManager.startCorePlugins (/volumio/app/pluginmanager.js:477:20)
Oct 18 08:24:39 volumioh81md2w volumio[828]: at Promise._successFn (/volumio/app/pluginmanager.js:142:29)
Oct 18 08:24:39 volumioh81md2w volumio[828]: at nextTickCallback (/volumio/node_modules/kew/kew.js:47:28)
Sorry - i am not very familiar with linux and network sockets.
Is this an development issue ?
Can i do anything to bypass this issue ?
Does this somehow depend on the quantity of network devices or streamers online in the network ? I got a quite large network with many devices in my house ( i guess 30+)
Each of my Pcs is a streamer and there app. 10 other devices able to stream that are most of the time online: TVs (4), Audio Receivers (3) , Audio streamer (3), Sat Receiver (2).