Official moOde 7.6.0 support thread

[Tim Curtis]

Hi,

Post all bug reports and questions concerning moOde 7.6.0 or the in-place update from 7.5.0 to 7.6.0

Please paste log output, scripts, etc in code boxes for readability.

-Tim

Tim, am having issues re-mounting my NAS.  Used to work seamlessly, now for some reason on 2 of the players it continuously fails to remount.  One is working as before - all have same settings for the NAS?

Are there any tricks I am missing.
Using the default settings for mount flags: ro,dir_mode=0777,file_mode=0777
Synology NAS, works fine on the 3B+, not on the zero or the 1B

If it used to work but now doesn't and there were no changes to moOde software or OS then it would suggest something external for example network, NAS, Router, other hardware etc.

Try rebooting the Router, NAS or other network devices.

[TheOldPresbyope]

@Britracer

And I had a nagging suspicion there was work done to improve the SMB mounting process in moOde. Sure enough, in the relnotes.txt file I find that as part of the moOde 7.1.0 release last March

Code:

- UPD: Automatically detect SMB protocol version

so it's even less likely my second point is relevant.

Regards,
Kent

[Britracer]

Hi,

Post all bug reports and questions concerning moOde 7.6.0 or the in-place update from 7.5.0 to 7.6.0

Please paste log output, scripts, etc in code boxes for readability.

-Tim

Tim, am having issues re-mounting my NAS.  Used to work seamlessly, now for some reason on 2 of the players it continuously fails to remount.  One is working as before - all have same settings for the NAS?

Are there any tricks I am missing.
Using the default settings for mount flags: ro,dir_mode=0777,file_mode=0777
Synology NAS, works fine on the 3B+, not on the zero or the 1B

If it used to work but now doesn't and there were no changes to moOde software or OS then it would suggest something external for example network, NAS, Router, other hardware etc.

Try rebooting the Router, NAS or other network devices.

Tim, everything was Ok until I did the in situ update to 7.6.0  All are currently at 7.6.0  Am now doing the update to 7.6.1.
I have also set the 2 that were not re-mounting up with static IP to see if that makes a difference.
let's see.

[TheOldPresbyope]

@Britracer

I took a little time to try to replicate your problem.

My test:

Synology DSM6.1 running on a virtual machine. SMB advanced settings: SMB2 minimum, SMB3 maximum. Publishes a Music directory with guest read-only privileges. Connected to LAN wirelessly.

RPi Zero W (the original, not the Zero 2 W) running a fresh copy of moOde 7.6.1. Default settings except for renaming the host, expanding the root file system, and setting up networking. Connected to LAN wirelessly.

Created a new music source in moOde using the Synology host/share path and guest user-id and keeping the default advanced settings, including mount flags.

• this source mounted (green checkmark) and scanned properly (tracks appear in Library listings). The Linux mount command shows the server and client settled on SMB3.1.1 during the mounting process, which tells me moOde's improved protocol negotiation works.
  
• executed the "Re-mount music sources" command in Library Sources screen. The source re-mounted cleanly.
  
• shut down and and powered off the moOde player; powered on again; this source again mounted cleanly during startup.
  

I'm not seeing anything which would help me diagnose your problem. All the moOde players I'm running on various model Pis are behaving as I expect with the various SMB and FTP NFS music servers I test with.

I suppose I could step through the combinations of SMB protocol possible in DSM (SMB1, SMB2, SMB3, SMB1+SMB2, SMB2+SMB3, SMB1 thru SMB3) but not without some provocation 

Regards,
Kent

[Britracer]

@Britracer

I took a little time to try to replicate your problem.

My test:

Synology DSM6.1 running on a virtual machine. SMB advanced settings: SMB2 minimum, SMB3 maximum. Publishes a Music directory with guest read-only privileges. Connected to LAN wirelessly.

RPi Zero W (the original, not the Zero 2 W) running a fresh copy of moOde 7.6.1. Default settings except for renaming the host, expanding the root file system, and setting up networking. Connected to LAN wirelessly.

Created a new music source in moOde using the Synology host/share path and guest user-id and keeping the default advanced settings, including mount flags.

• this source mounted (green checkmark) and scanned properly (tracks appear in Library listings). The Linux mount command shows the server and client settled on SMB3.1.1 during the mounting process, which tells me moOde's improved protocol negotiation works.
  
• executed the "Re-mount music sources" command in Library Sources screen. The source re-mounted cleanly.
  
• shut down and and powered off the moOde player; powered on again; this source again mounted cleanly during startup.
  

I'm not seeing anything which would help me diagnose your problem. All the moOde players I'm running on various model Pis are behaving as I expect with the various SMB and FTP NFS music servers I test with.

I suppose I could step through the combinations of SMB protocol possible in DSM (SMB1, SMB2, SMB3, SMB1+SMB2, SMB2+SMB3, SMB1 thru SMB3) but not without some provocation 

Regards,
Kent

Kent,
really appreciate you doing that test.  I leave my players on permanently so that I don't have to power up when I want to use them.
After a day or several the mount is lost.

Just happened on my 3b+ player

here is the log
20211230 162558 worker: -- Start
20211230 162558 worker: Successfully daemonized
20211230 162600 worker: Integrity check (passed)
20211230 162601 worker: File check (OK)
20211230 162602 worker: Session vacuumed
20211230 162602 worker: Session loaded
20211230 162602 worker: Debug logging (OFF)
20211230 162602 worker: -- Audio debug
20211230 162602 worker: ALSA cards: (0ndrpihifiberry | 1:empty | 2:empty | 3:empty
20211230 162602 worker: MPD config: (0:HIFI DAC+ | mixerDigital) | card:0)
20211230 162602 worker: ALSA mixer actual (Digital)
20211230 162602 worker: ALSA Digital volume set to (0%)
20211230 162602 worker: -- System
20211230 162609 worker: Host     (AuraTU50)
20211230 162609 worker: moOde    (7.6.1 2021-12-17)
20211230 162609 worker: RaspiOS  (10.6)
20211230 162609 worker: Kernel   (5.4.77-v7+ #1371)
20211230 162609 worker: Platform (Pi-3B 1.2 1GB)
20211230 162609 worker: ARM arch (armv7l, 32-bit kernel)
20211230 162609 worker: MPD ver  (0.23.4_p0x3)
20211230 162609 worker: CPU gov  (performance)
20211230 162609 worker: USB boot not enabled yet
20211230 162610 worker: File system expanded
20211230 162610 worker: HDMI port off
20211230 162610 worker: -- Network
20211230 162610 worker: IP address check timeout (90 secs)
20211230 162611 worker: eth0 adapter exists
20211230 162611 worker: eth0 IP address check (No)
20211230 162611 worker: IP addr (192.168.3.240)
20211230 162611 worker: Netmask (255.255.255.0)
20211230 162611 worker: Gateway (192.168.3.1)
20211230 162612 worker: Pri DNS (8.8.8.8)
20211230 162612 worker: Domain  (192.168.3.1)
20211230 162612 worker: wlan0 adapter exists
20211230 162612 worker: wifi country (CA)
20211230 162612 worker: wlan0 trying SSID (SynologySmartConnect)
20211230 162612 worker: IP addr (192.168.3.101)
20211230 162612 worker: Netmask (255.255.255.0)
20211230 162612 worker: Gateway (192.168.3.1)
20211230 162612 worker: Pri DNS (8.8.8.8)
20211230 162612 worker: Domain  (192.168.3.1)
20211230 162612 worker: Pi integrated wlan0 power save disabled
20211230 162612 worker: -- Audio config
20211230 162612 worker: MPD conf updated
20211230 162612 worker: ALSA card number (0)
20211230 162612 worker: MPD audio output (HIFI DAC+)
20211230 162613 worker: Audio formats (S16_LE, S24_LE, S32_LE)
20211230 162613 worker: ALSA mixer name (Digital)
20211230 162613 worker: MPD mixer type (software)
20211230 162613 worker: Hdwr volume controller exists
20211230 162613 worker: Max ALSA volume (100%)
20211230 162613 worker: ALSA output mode (Direct: hw)
20211230 162613 worker: ALSA loopback (Off)
20211230 162613 worker: Reset renderer active flags
20211230 162613 worker: CamillaDSP (off)
20211230 162613 worker: -- MPD startup
20211230 162613 worker: MPD started
20211230 162614 worker: MPD accepting connections
20211230 162614 worker: MPD output 1 ALSA Default (on)
20211230 162614 worker: MPD output 2 ALSA Bluetooth (off)
20211230 162614 worker: MPD output 3 HTTP Server (off)
20211230 162614 worker: MPD crossfade (3 secs)
20211230 162614 worker: MPD ignore CUE files (no)
20211230 162614 worker: -- Feature availability
20211230 162614 worker: Source select (available)
20211230 162614 worker: Source select (source: MPD)
20211230 162614 worker: Source select (output: HIFI DAC+)
20211230 162632 worker: Bluetooth (available: started)
20211230 162632 worker: Airplay renderer (available: started)
20211230 162632 worker: Spotify renderer (available)
20211230 162632 worker: Squeezelite (available)
20211230 162632 worker: RoonBridge renderer (not installed)
20211230 162632 worker: Multiroom sender (available)
20211230 162632 worker: Multiroom receiver (available)
20211230 162632 worker: UPnP renderer (available)
20211230 162632 worker: DLNA server (available)
20211230 162632 worker: UPnP browser (available)
20211230 162632 worker: GPIO button handler (available)
20211230 162632 worker: Stream recorder (n/a)
20211230 162632 worker: -- Music sources
20211230 162633 worker: USB sources (none attached)
20211230 162633 worker: NAS and UPnP sources (mountall initiated)
20211230 162633 worker: -- Other
20211230 162633 worker: USB volume knob (Off)
20211230 162634 worker: LCD updater engine started
20211230 162634 worker: Shellinabox SSH started
20211230 162634 worker: USB auto-mounter (udisks-glue)
20211230 162634 worker: LED0 (On)
20211230 162634 worker: LED1 (On)
20211230 162634 worker: Saved MPD vol level (0)
20211230 162634 worker: Preamp volume level (0)
20211230 162634 worker: MPD volume level (40) restored
20211230 162634 worker: ALSA Digital volume (100%)
20211230 162634 worker: Auto-play (Off)
20211230 162634 worker: Maintenance interval (3 hours)
20211230 162634 worker: Screen saver activation (Never)
20211230 162634 worker: Session permissions (OK)
20211230 162635 worker: Watchdog started
20211230 162635 worker: Ready
20211230 180843 watchdog: Info: Reducing PHP fpm worker pool
20211230 181506 sourceMount(): Mount error: (mount error(2): No such file or directory
Refer to the mount.cifs(8) manual page (e.g. man mount.cifs))
20211230 181659 sourceMount(): Mount error: (mount error(2): No such file or directory
Refer to the mount.cifs(8) manual page (e.g. man mount.cifs))
20211230 182029 sourceMount(): Mount error: (mount error(2): No such file or directory
Refer to the mount.cifs(8) manual page (e.g. man mount.cifs))

[Tim Curtis]

The network section shows some oddness including having both Ethernet and WLAN interfaces active (only one is needed) and an external Primary DNS.

Code:

20211230 162610 worker: -- Network
20211230 162610 worker: IP address check timeout (90 secs)
20211230 162611 worker: eth0 adapter exists
20211230 162611 worker: eth0 IP address check (No)
20211230 162611 worker: IP addr (192.168.3.240)
20211230 162611 worker: Netmask (255.255.255.0)
20211230 162611 worker: Gateway (192.168.3.1)
20211230 162612 worker: Pri DNS (8.8.8.8)
20211230 162612 worker: Domain  (192.168.3.1)
20211230 162612 worker: wlan0 adapter exists
20211230 162612 worker: wifi country (CA)
20211230 162612 worker: wlan0 trying SSID (SynologySmartConnect)
20211230 162612 worker: IP addr (192.168.3.101)
20211230 162612 worker: Netmask (255.255.255.0)
20211230 162612 worker: Gateway (192.168.3.1)
20211230 162612 worker: Pri DNS (8.8.8.8)
20211230 162612 worker: Domain  (192.168.3.1)

Try with just a single network interface and primary DNS set to the Router LAN interface which in your case would be 192.168.3.1. I'm assuming you are using a typical residential Router that proxies DNS.

[Britracer]

The network section shows some oddness including having both Ethernet and WLAN interfaces active (only one is needed) and an external Primary DNS.

Code:

20211230 162610 worker: -- Network
20211230 162610 worker: IP address check timeout (90 secs)
20211230 162611 worker: eth0 adapter exists
20211230 162611 worker: eth0 IP address check (No)
20211230 162611 worker: IP addr (192.168.3.240)
20211230 162611 worker: Netmask (255.255.255.0)
20211230 162611 worker: Gateway (192.168.3.1)
20211230 162612 worker: Pri DNS (8.8.8.8)
20211230 162612 worker: Domain  (192.168.3.1)
20211230 162612 worker: wlan0 adapter exists
20211230 162612 worker: wifi country (CA)
20211230 162612 worker: wlan0 trying SSID (SynologySmartConnect)
20211230 162612 worker: IP addr (192.168.3.101)
20211230 162612 worker: Netmask (255.255.255.0)
20211230 162612 worker: Gateway (192.168.3.1)
20211230 162612 worker: Pri DNS (8.8.8.8)
20211230 162612 worker: Domain  (192.168.3.1)

Try with just a single network interface and primary DNS set to the Router LAN interface which in your case would be 192.168.3.1. I'm assuming you are using a typical residential Router that proxies DNS.

Tim, I don't know why the log shows the primary DNS as 8.8.8.8, this is set as secondary DNS in the network config (both wired and wireless).  I can disable the wireless connection and see if it makes a difference.  The other 2 players are only wireless, so not there issue there.


[img]blob:https://moodeaudio.org/57e2fa91-cd87-4da7-ba0b-40c80cf5f29e[/img]

[Tim Curtis]

Prolly due to the command used by moOde to parse out the DNS address. It gets the address from the 3rd line in the /etc/resolv.conf file. Maybe when there are both primary and secondary addresses in resolve.conf the secondary address is in the 3rd line. 

See below.

Code:

pi@rp1:~ $ cat /etc/resolv.conf
# Generated by resolvconf
domain home
nameserver 192.168.1.1

pi@rp1:~ $ cat /etc/resolv.conf | awk 'NR==3 {print $2}'
192.168.1.1
pi@rp1:~ $

[fdealexa]

Hi all,
Have you tried to search the NAS by using IPaddress instead of the name (//192.168.3.x)?
Best regards,
Francesco

[TheOldPresbyope]

@Britracer

I took a little time to try to replicate your problem.

...blah, blah, blah...

Kent,
really appreciate you doing that test.  I leave my players on permanently so that I don't have to power up when I want to use them.
After a day or several the mount is lost.
...

Okay. Your original post led me to believe it was a re-mount problem so that's what I tried to replicate in various ways.

Not sure why the mount would be dropped in normal operation but the cause would seem to be external to moOde/moOdeOS. The SSID SynologySmartConnect in your last log suggests you're using a Synology router product. I don't know what goes on under its covers but I get nervous when I see words like "smart" and "Inteligent" in marketing literature.

There's no primary/secondary nameserver setup available in moOde's Network Config screen. Your moOde player gets the gateway and nameserver information from whatever DHCP server is running on your LAN. I assume this means the SynologySmartConnect.

Francesco's suggestion to try using the NAS's IP address instead of domain name is a good one.

Good luck.

Regards,
Kent