Moode Forum
[PROBLEM] Problem with moOde UPnP renderer - Printable Version

+- Moode Forum (https://moodeaudio.org/forum)
+-- Forum: moOde audio player (https://moodeaudio.org/forum/forumdisplay.php?fid=3)
+--- Forum: Support (https://moodeaudio.org/forum/forumdisplay.php?fid=7)
+--- Thread: [PROBLEM] Problem with moOde UPnP renderer (/showthread.php?tid=3865)

Problem with moOde UPnP renderer - foudebassan - 05-27-2021

Hello,
 
My configuration:
moOde 7.2.1 fresh install
Raspberry Pi4 USB connected with
Cambridge Audio CXA81
moOde UPnP renderer activated
Control point: Bubble UPnP or HiFiCast on Samsung mobile
Ethernet network connection, Pi4 IP=192.168.8.112
Moodeutl file attached
 
My problem:
After Pi4 start-up, moOde UPnP isn’t found neither by Bubble UPnP nor by HiFiCast
If I manually restart moOde UPnP in M menu, Bubble UPnP is at once visible in these 2 control points
 
Facts:
This problem didn’t occur when I was previously on a WIFI network
Here is the last line of upmpdcli, before and after the manual restart of moOde UPnP
Before:
May 24 17:32:06 moode upmpdcli[1004]: :3:libupnpp/upnpplib.cxx:229::LibUPnP: Using IPV4 169.254.206.12 port 49152 IPV6  port 49152
After:
May 24 18:25:02 moode upmpdcli[1128]: :3:libupnpp/upnpplib.cxx:229::LibUPnP: Using IPV4 192.168.8.112 port 49152 IPV6  port 49152
 
What can I do in order to use moOde UPnP directly after start-up?
Thanks in advance.

[attachment=2329]
Code:
20210524 173201 worker: -- Start
20210524 173201 worker: Successfully daemonized
20210524 173202 worker: Integrity check (passed)
20210524 173202 worker: File check (OK)
20210524 173203 worker: Session vacuumed
20210524 173203 worker: Session loaded
20210524 173203 worker: Debug logging (OFF)
20210524 173203 worker: -- Audio debug
20210524 173203 worker: ALSA cards: (0:b1 | 1:Headphones | 2:C20 | 3:empty
20210524 173203 worker: MPD config: (2:CA CXA81 2.0 | mixer:(PCM) | card:2)
20210524 173203 worker: ALSA mixer actual (PCM)
20210524 173203 worker: ALSA PCM volume set to (amixer: Unable to find simple control 'PCM',0)
20210524 173203 worker: -- System
20210524 173204 worker: Host     (moode)
20210524 173204 worker: moOde    (7.2.1 2021-05-06)
20210524 173204 worker: RaspiOS  (10.6)
20210524 173204 worker: Kernel   (5.4.77-v7l+ #1371)
20210524 173204 worker: Platform (Pi-4B 1.4 8GB)
20210524 173204 worker: ARM arch (armv7l, 32-bit kernel)
20210524 173204 worker: MPD ver  (0.22.6_p0x3)
20210524 173204 worker: CPU gov  (ondemand)
20210524 173204 worker: USB boot not available
20210524 173204 worker: File system not expanded yet
20210524 173204 worker: HDMI port off
20210524 173204 worker: -- Network
20210524 173204 worker: eth0 exists
20210524 173204 worker: IP addr (169.254.206.12)
20210524 173204 worker: Netmask (255.255.0.0)
20210524 173204 worker: Gateway (0.0.0.0)
20210524 173204 worker: Pri DNS (192.168.8.1)
20210524 173204 worker: Domain  (None)
20210524 173204 worker: wlan0 does not exist
20210524 173204 worker: -- Audio config
20210524 173204 worker: ALSA card number (2)
20210524 173204 worker: MPD audio output (CA CXA81 2.0)
20210524 173205 worker: Audio formats (S16_LE, S32_LE, SPECIAL)
20210524 173205 worker: ALSA mixer name (PCM)
20210524 173205 worker: MPD volume control (none)
20210524 173205 worker: Hdwr volume controller not detected
20210524 173205 worker: ALSA loopback (Off)
20210524 173205 worker: Reset renderer active flags
20210524 173205 worker: CamillaDSP (off)
20210524 173205 worker: -- MPD startup
20210524 173205 worker: MPD started
20210524 173205 worker: MPD accepting connections
20210524 173205 worker: MPD output 1 ALSA Default (on)
20210524 173205 worker: MPD output 2 ALSA Bluetooth (off)
20210524 173205 worker: MPD output 3 HTTP Server (off)
20210524 173205 worker: MPD crossfade (off)
20210524 173206 worker: MPD ignore CUE files (yes)
20210524 173206 worker: -- Feature availability
20210524 173206 worker: Source select (available)
20210524 173206 worker: Source select (source: MPD)
20210524 173206 worker: Source select (output: CA CXA81 2.0)
20210524 173206 worker: Bluetooth (available)
20210524 173206 worker: Airplay renderer (available)
20210524 173206 worker: Spotify renderer (available)
20210524 173206 worker: Squeezelite (available)
20210524 173206 worker: RoonBridge renderer (not installed)
20210524 173206 worker: UPnP renderer (available: started)
20210524 173206 worker: DLNA server (available: started)
20210524 173206 worker: UPnP browser (available)
20210524 173206 worker: GPIO button handler (available)
20210524 173206 worker: Stream recorder (n/a)
20210524 173206 worker: -- Music sources
20210524 173206 worker: USB source (FILMS_1)
20210524 173206 worker: USB source (FILMS_2)
20210524 173206 worker: USB source (SERIES)
20210524 173206 worker: NAS and UPnP sources (none configured)
20210524 173206 worker: -- Other
20210524 173206 worker: USB volume knob (Off)
20210524 173206 worker: USB auto-mounter (udisks-glue)
20210524 173206 worker: LED0 (On)
20210524 173206 worker: LED1 (On)
20210524 173206 worker: Saved MPD vol level (0)
20210524 173206 worker: Preamp volume level (0)
20210524 173206 worker: MPD volume level (0) restored
20210524 173206 worker: ALSA volume level (None)
20210524 173206 worker: Auto-play (Off)
20210524 173206 worker: Maintenance interval (3 hours)
20210524 173206 worker: Screen saver activation (Never)
20210524 173206 worker: Session permissions (OK)
20210524 173206 worker: Watchdog started
20210524 173206 worker: Ready


RE: Problem with moOde UPnP renderer - Tim Curtis - 05-27-2021

I put your log in a code box for readability.

RE: Problem with moOde UPnP renderer - foudebassan - 05-27-2021

(05-27-2021, 11:52 AM)Tim Curtis Wrote: I put your log in a code box for readability.

Thanks Tim.

I get these two lines of upmpdcli service with the command:
sudo systemctl status upmpdcli
It seems that upmpdcli starts with this wrong adress 169.254.206.12, which is corrected by the right IP given by the router's DHCP when I manually restart upmpdcli.

I am not an expert, have you some idea how I can correct this?

Regards.
Alain

RE: Problem with moOde UPnP renderer - TheOldPresbyope - 05-27-2021

(05-27-2021, 01:36 PM)foudebassan Wrote:
(05-27-2021, 11:52 AM)Tim Curtis Wrote: I put your log in a code box for readability.

Thanks Tim.

I get these two lines of upmpdcli service with the command:
sudo systemctl status upmpdcli
It seems that upmpdcli starts with this wrong adress 169.254.206.12, which is corrected by the right IP given by the router's DHCP when I manually restart upmpdcli.

I am not an expert, have you some idea how I can correct this?

Regards.
Alain

But your log file says

Code:
20210524 173204 worker: -- Network
20210524 173204 worker: eth0 exists
20210524 173204 worker: IP addr (169.254.206.12)
20210524 173204 worker: Netmask (255.255.0.0)
20210524 173204 worker: Gateway (0.0.0.0)
20210524 173204 worker: Pri DNS (192.168.8.1)
20210524 173204 worker: Domain  (None)

Sorry no time here to diagnose but several entries here seem screwy.

Regards,
Kent

RE: Problem with moOde UPnP renderer - Tim Curtis - 05-27-2021

Yes, something in the network is misconfigured. The log lines below shows several issues.

1. An Automatic Private IP address (APIPA) is being assigned to the Pi. This would happen for example if the Pi did not receive an IP address from the Router's DHCP server.
2. No Gateway address
3. Pri DNS with .8 subnet is not typically what residential Router DHCP would assign

Code:
20210524 173204 worker: eth0 exists
20210524 173204 worker: IP addr (169.254.206.12)
20210524 173204 worker: Netmask (255.255.0.0)
20210524 173204 worker: Gateway (0.0.0.0)
20210524 173204 worker: Pri DNS (192.168.8.1)
20210524 173204 worker: Domain  (None)
20210524 173204 worker: wlan0 does not exist

@foudebassan is this a residential network with a conventional Router?

RE: Problem with moOde UPnP renderer - foudebassan - 05-27-2021

@Tim Curtis

Yes, it's a Huawei conventional residential router
All others devices on the network work correctly with its DHCP

When I launch
ip route |grep default
default via 192.168.8.1 dev eth0 proto dhcp src 192.168.8.112 metric 202
The router address 192.168.8.1 and Raspberry address 192.168.8.112 are both correct

But at the same time:
sudo systemctl status upmpdcli
● upmpdcli.service - UPnP Renderer front-end to MPD
Loaded: loaded (/lib/systemd/system/upmpdcli.service; disabled; vendor preset: enabled)
Active: active (running) since Wed 2021-05-26 19:11:31 CEST; 22h ago
Main PID: 850 (upmpdcli)
Tasks: 10 (limit: 4915)
CGroup: /system.slice/upmpdcli.service
└─850 /usr/bin/upmpdcli -c /etc/upmpdcli.conf
May 26 19:11:31 moode upmpdcli[850]: :3:libupnpp/upnpplib.cxx:229::LibUPnP: Using IPV4 169.254.206.12 port 49152 IPV6 port 49152

So where moode upmpdcli is taking this address?

Regards,
Alain

RE: Problem with moOde UPnP renderer - Tim Curtis - 05-27-2021

The IP addresse block for eth0 in the Moode startup log is not correct. They come from Linux networking subsystem.The moOde startup daemon, worker.php, is launched from /etc/rc.local script which is run after Linux completes its startup.

It's not obvious to me why valid IP addresses are not present during moOde startup.

RE: Problem with moOde UPnP renderer - foudebassan - 05-28-2021

Hello Tim,

I haven't enough knowledge to dig further into the "check ETH0" lines of worker.php in order to understand why it doesn't collect the valid adress, yet it's there!
Off chance, I have upgraded Raspi OS from 10.6 to 10.9: no improvment.

Regards,
Alain

RE: Problem with moOde UPnP renderer - foudebassan - 05-29-2021

In order to avoid this UPnP renderer manual restart, the simple workaround is to set a fix IP in moOde configuration.