Acer54 writes

Hi, upmpdcli was exactelly what I was looking for. Initially I have tried it on my Ubuntu 16.04, installed via the PPA "ppa:jean-francois-dockes/upnpp1" . After a first successful trial, I tried to install upmpdcli to my Raspberry Pi (Rasbian Jessy), (was using the way via creating a new sources.list with the unstable repo) but after successful installation on the pi, I get ":2:libupnpp/upnpplib.cxx:149::UpnpInit :-205: UPNP_E_OUTOF_SOCKET" after calling upmpdcli from my terminal. Any idea what is wrong here ?

Acer54 writes

Additional Info: Just tried it with another Pi (running Wheezy instead of Jessie) - > Installed and running with no Problem with the same approach like above.

medoc92 writes

libupnp returns this error when a socket() call fails. If you try "man socket", you will see that there are a number of possible conditions to cause this: such as kernel out of open file entries, protocol not supported etc. My best guess is that this is a kernel configuration issue. Maybe no support for multicast ? Except if you have a lot of stuff running on this rpi, or you love dealing with kernel parameters, I’d just reinstall it from scratch. The way to debug this would be to enable or add traces in libupnp to check which calls fails and with what errno, but, given that I’ve never seen this happen before, I’m not sure it’s worth the trouble.

Acer54 writes

Hey Medoc, thanks for your reponse. Good to here that I am the only one with this error-message… Maybe I´ve messed up things during previouse tries.

empierre writes

Same issue for me

medoc92 writes

Please describe your configuration: machine, system, exactly what package you installed and from where.

empierre writes

Volumio 1.5 image Linux volumio 3.18.5-v7+ #748 SMP PREEMPT Wed Feb 4 21:33:52 GMT 2015 armv7l GNU/Linux PRETTY_NAME="Raspbian GNU/Linux 8 (jessie)" have this on command line, although the one launched from volumio seems to start

empierre writes

so in fact no logging, so launching it as volumio I have this in log:

 /usr/bin/upmpdcli -f volumio -l 2
libupnpp/upnpplib.cxx:92::UpnpInit :-205: UPNP_E_OUTOF_SOCKET

medoc92 writes

And when launched from volumio it works ??

empierre writes

don’t know th at is why I was looking at it… bubbleupnp does not see it

wlan0 Link encap:Ethernet HWaddr 7c:dd:90:7e:ba:ee inet addr:192.168.0.19 Bcast:192.168.0.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:5045 errors:0 dropped:1471 overruns:0 frame:0 TX packets:1658 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:932811 (910.9 KiB) TX bytes:1095858 (1.0 MiB)

medoc92 writes

A few more questions: - What board are you using (rpi 1/2/3…) ? - Any reason why you are using an old volumio release ? (not that I think it’s related, just curious). - Have you got a possibility to try this with a wired connection ?

empierre writes

Hi,

  • PI2

  • volumio2 samba/nfs support was not working (at the last time I tried it) so went back on a working version

  • no wired sadly…

medoc92 writes

Ok, I’ll download volumio 1.5 and give it a try…

empierre writes

trying with your repo on my jessie, same issue

On Sun, Jun 4, 2017 at 9:34 PM, Jean-Francois Dockes < notifications@github.com > wrote:

> Ok, I'll download volumio 1.5 and give it a try...
>
> —
> You are receiving this because you commented.
> Reply to this email directly, view it on GitHub
> <https://www.lesbonscomptes.com/upmpdcli/github-issues/upmpdcli-html/issue-58.html#issuecomment-306061791 >,
> or mute the thread
> <https://github.com/notifications/unsubscribe-auth/AG8xijPyHjV4QVOq6c5qqoc7Gxi-3r1qks5sAwawgaJpZM4KaIKu >
> .
>

medoc92 writes

I have it running here on wheezy, the ifconfig output on wlan0 is very similar.

What does the full ifconfig output look like (lo and eth0) ?

I wonder if it might be trying to use the wrong interface (really poking in the dark here). You could try setting:

upnpiface = wlan0

in /etc/upmpdcli.conf

empierre writes

root@volumio:~# ifconfig lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 UP LOOPBACK RUNNING MTU:65536 Metric:1 RX packets:1595 errors:0 dropped:0 overruns:0 frame:0 TX packets:1595 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:190083 (185.6 KiB) TX bytes:190083 (185.6 KiB)

wlan0 Link encap:Ethernet HWaddr 7c:dd:90:7e:ba:ee inet addr:192.168.0.19 Bcast:192.168.0.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:63154 errors:0 dropped:2815 overruns:0 frame:0 TX packets:13243 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:77239063 (73.6 MiB) TX bytes:2670105 (2.5 MiB)

I did already pass -i wlan0 on command line with same result

On Sun, Jun 4, 2017 at 9:56 PM, Jean-Francois Dockes < notifications@github.com > wrote:

> I have it running here on wheezy, the ifconfig output on wlan0 is very
> similar.
>
> What does the full ifconfig output look like (lo and eth0) ?
>
> I wonder if it might be trying to use the wrong interface (really poking
> in the dark here). You could try setting:
>
> upnpiface = wlan0
>
> in /etc/upmpdcli.conf
>
> —
> You are receiving this because you commented.
> Reply to this email directly, view it on GitHub
> <https://www.lesbonscomptes.com/upmpdcli/github-issues/upmpdcli-html/issue-58.html#issuecomment-306063084 >,
> or mute the thread
> <https://github.com/notifications/unsubscribe-auth/AG8xigvb7Jzy-giFRpEH_cmgrdlrjdCRks5sAwvfgaJpZM4KaIKu >
> .
>

empierre writes

hmmm… will try to bypass this running it from an odroid XU3 linked to the mpd from volumio.

launched it fine on this platform !

On Sun, Jun 4, 2017 at 10:05 PM, Emmanuel PIERRE <epierre@e-nef.com > wrote:

> root@volumio:~# ifconfig
> lo        Link encap:Local Loopback
>           inet addr:127.0.0.1  Mask:255.0.0.0
>           UP LOOPBACK RUNNING  MTU:65536  Metric:1
>           RX packets:1595 errors:0 dropped:0 overruns:0 frame:0
>           TX packets:1595 errors:0 dropped:0 overruns:0 carrier:0
>           collisions:0 txqueuelen:0
>           RX bytes:190083 (185.6 KiB)  TX bytes:190083 (185.6 KiB)
>
> wlan0     Link encap:Ethernet  HWaddr 7c:dd:90:7e:ba:ee
>           inet addr:192.168.0.19  Bcast:192.168.0.255  Mask:255.255.255.0
>           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>           RX packets:63154 errors:0 dropped:2815 overruns:0 frame:0
>           TX packets:13243 errors:0 dropped:0 overruns:0 carrier:0
>           collisions:0 txqueuelen:1000
>           RX bytes:77239063 (73.6 MiB)  TX bytes:2670105 (2.5 MiB)
>
> I did already pass -i wlan0 on command line with same result
>
>
> On Sun, Jun 4, 2017 at 9:56 PM, Jean-Francois Dockes <
> notifications@github.com > wrote:
>
> > I have it running here on wheezy, the ifconfig output on wlan0 is very
> > similar.
> >
> > What does the full ifconfig output look like (lo and eth0) ?
> >
> > I wonder if it might be trying to use the wrong interface (really poking
> > in the dark here). You could try setting:
> >
> > upnpiface = wlan0
> >
> > in /etc/upmpdcli.conf
> >
> > —
> > You are receiving this because you commented.
> > Reply to this email directly, view it on GitHub
> > <https://www.lesbonscomptes.com/upmpdcli/github-issues/upmpdcli-html/issue-58.html#issuecomment-306063084 >,
> > or mute the thread
> > <https://github.com/notifications/unsubscribe-auth/AG8xigvb7Jzy-giFRpEH_cmgrdlrjdCRks5sAwvfgaJpZM4KaIKu >
> > .
> >
>
>

medoc92 writes

Well yes, upmpdcli does work in general :) There must be a very specific problem here because I only heard of it twice, and there are quite probably many thousands of working installations…

There is something weird in the ifconfig output though: it does not list eth0. Even if this is not connected, it should be listed. On my wireless pi, I have the following as part of the dmesg output:

----` eth0 Link encap:Ethernet HWaddr b8:27:eb:94:14:a2 UP BROADCAST MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

----`

I don’t know that this is significant, but we’re looking for something weird anyway… a pi2 should have eth0

Also: anything showing in dmesg when you get the out of sockets error ?

empierre writes

Hello,

  I did put down the eth0 witout any change, this is the reason you don't
see it.
Nothing in the dmesg, I did a lot of reboot but never any message.

On Mon, Jun 5, 2017 at 4:54 AM, Jean-Francois Dockes < notifications@github.com > wrote:

> Well yes, upmpdcli does work in general :) There must be a very specific
> problem here because I only heard of it twice, and there are quite probably
> many thousands of working installations...
>
> There is something weird in the ifconfig output though: it does not list
> eth0. Even if this is not connected, it should be listed. On my wireless
> pi, I have the following as part of the dmesg output:
>
> eth0      Link encap:Ethernet  HWaddr b8:27:eb:94:14:a2
>           UP BROADCAST MULTICAST  MTU:1500  Metric:1
>           RX packets:0 errors:0 dropped:0 overruns:0 frame:0
>           TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
>           collisions:0 txqueuelen:1000
>           RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)
>
> I don't know that this is significant, but we're looking for something
> weird anyway... a pi2 should have eth0
>
> Also: anything showing in dmesg when you get the out of sockets error ?
>
> —
> You are receiving this because you commented.
> Reply to this email directly, view it on GitHub
> <https://www.lesbonscomptes.com/upmpdcli/github-issues/upmpdcli-html/issue-58.html#issuecomment-306091617 >,
> or mute the thread
> <https://github.com/notifications/unsubscribe-auth/AG8xis1Tz-wjaOwA8x0AIIM_xHZtGKJGks5sA23jgaJpZM4KaIKu >
> .
>

medoc92 writes

Up or down, it should show in ifconfig output ?

Anything special about your jessie system configuration ? If it’s vanilla, I think that we are more or less down to hardware… No idea how a wireless adapter could cause this though. What are you using ?

empierre writes

I did put eth0 down, no behavior change.

I did not update to newer kernel for I (used to have) IQ-DAC+ thouth now I have a minidsp 2x4 HD on it.

[ 3.733549] usb 1-1.4: Product: 802.11 n WLAN [ 3.739805] usb 1-1.4: Manufacturer: Ralink [ 3.745823] usb 1-1.4: SerialNumber: 1.0

On Mon, Jun 5, 2017 at 9:50 AM, Jean-Francois Dockes < notifications@github.com > wrote:

> Up or down, it should show in 'ifconfig' output ?
>
> Anything special about your 'jessie' system configuration ? If it's
> vanilla, I think that we are more or less down to hardware... No idea how a
> wireless adapter could cause this though. What are you using ?
>
> —
> You are receiving this because you commented.
> Reply to this email directly, view it on GitHub
> <https://www.lesbonscomptes.com/upmpdcli/github-issues/upmpdcli-html/issue-58.html#issuecomment-306125971 >,
> or mute the thread
> <https://github.com/notifications/unsubscribe-auth/AG8xirYJQzCqLpMcgOtWP6EmBPfi50LLks5sA7NigaJpZM4KaIKu >
> .
>

medoc92 writes

What I find strange is that ifconfig does not list eth0 at all. Can you send the full output of ifconfig -a ?

I think that I’m going to buy a ralink adapter and give it a try. What model/chipset are you using ?

medoc92 writes

No feedback on this issue and issue #108 seems to confirm that this is a configuration issue.