[PROBLEM] Ethernet works fine playing music, Wi-Fi doesn't

[Joseph.Barrow]

So here's a problem that I'm scratching my head over. I have a fresh-install 8.3.7 64-bit moOde on a Raspberry Pi 3B+ that apparently gets cranky and cannot handle Wi-Fi well after the new install. I installed it over Ethernet and that works in all respects. Sound over a HiFi HAT, network, LCD display over DSI, NFS share to my media server - everything. Plays all day, after first refreshing the library.

The problem is that I don't want an Ethernet connection, but Wi-Fi. In the past for older installs, it has worked exactly as I've mentioned for Ethernet. Plays all day. I just don't want a tether that I'll trip over in between. I can trip over air - I don't need help. I've already found that out.

Over Wi-Fi, I can SSH into the Pi all day long and do stuff as required. The web interface comes up beautifully. But I immediately get an MPD error: "Failed to decode SuchandSuch.mp3; Failed to open 'SuchAndSuch.mp3': No such file or directory."

Well, I figured that, as the NFS mount went down when I unplugged the Ethernet. So, I SSH into my media server and issue a "sudo exportfs -ra" as a matter of course and it's accepted. Going into 'Music Sources' in the web interface and clicking re-mount does nothing. Also, restarting MPD does nothing. Reboot does nothing.

Plugging in the Ethernet cable makes everything suddenly work again. Plays all day long. Unplugging it - everything stops.

I have network addresses for both Ethernet and Wi-Fi, which I know from "ip address" and the fact that I can SSH into both.

Any ideas? I've cast about and came up dry. I've included the moodeutl below. What other information is needed?

Code:

> $ moodeutl -l

20231221 122542 worker: --
20231221 122542 worker: -- Start moOde 8 series
20231221 122542 worker: --
20231221 122542 worker: Successfully daemonized
20231221 122542 worker: Wait for Linux startup...
20231221 122555 worker: Linux startup complete
20231221 122555 worker: Boot config backed up
20231221 122557 worker: Session loaded
20231221 122600 worker: Package holds applied
20231221 122601 worker: File check complete
20231221 122601 worker: Debug logging off
20231221 122601 worker: Reduced logging off
20231221 122601 worker: --
20231221 122601 worker: -- Audio debug
20231221 122601 worker: --
20231221 122601 worker: ALSA cards:  0:BossDAC | 1:empty | 2:empty | 3:empty
20231221 122601 worker: MPD config:  0:Allo Boss DAC | mixer:Digital | cardnum:0
20231221 122601 worker: Mixer name:  [Digital]
20231221 122601 worker: Hdwr volume: set to 0%
20231221 122601 worker: --
20231221 122601 worker: -- System
20231221 122601 worker: --
20231221 122604 worker: Host:     wireless
20231221 122604 worker: Model:    Pi-3B+ 1.3 1GB
20231221 122604 worker: moOde:    8.3.7 2023-12-07
20231221 122604 worker: RaspiOS:  11.8 Bullseye 64-bit
20231221 122604 worker: Kernel:   6.1.21 64-bit
20231221 122604 worker: MPD ver:  0.23.14
20231221 122604 worker: CPU gov:  ondemand
20231221 122604 worker: Userid:   joe
20231221 122604 worker: Homedir:  /home/joe
20231221 122604 worker: Timezone: America/Chicago
20231221 122604 worker: Keyboard: us
20231221 122604 worker: USB boot: enabled
20231221 122604 worker: File sys: expanded
20231221 122604 worker: HDMI out: off
20231221 122604 worker: Sys LED0: on
20231221 122604 worker: Sys LED1: on
20231221 122604 worker: --
20231221 122604 worker: -- Network
20231221 122604 worker: --
20231221 122604 worker: Eth: adapter does not exist
20231221 122604 worker: Wlan: adapter exists
20231221 122604 worker: Wlan: country US
20231221 122604 worker: Wlan: SSID    NOKIA-1DB1
20231221 122604 worker: Wlan: other   none
20231221 122604 worker: Wlan: router  off
20231221 122604 worker: Wlan: timeout up to 90 secs
20231221 122604 worker: Wlan: connect to NOKIA-1DB1
20231221 122605 worker: Wlan: sleep   disabled
20231221 122605 worker: Wlan: method  dhcp
20231221 122605 worker: Wlan: address 192.168.18.19
20231221 122605 worker: Wlan: netmask 255.255.255.0
20231221 122605 worker: Wlan: gateway 192.168.18.1
20231221 122605 worker: Wlan: pri DNS 192.168.18.1
20231221 122605 worker: Wlan: domain
20231221 122605 worker: --
20231221 122605 worker: -- Software update
20231221 122605 worker: --
20231221 122605 worker: Automatic check: on
20231221 122605 worker: Checking for available update...
20231221 122605 worker: Software is up to date
20231221 122605 worker: --
20231221 122605 worker: -- File sharing
20231221 122605 worker: --
20231221 122605 worker: SMB file sharing:  off
20231221 122605 worker: NFS file sharing:  off
20231221 122605 worker: DLNA file sharing: on
20231221 122605 worker: --
20231221 122605 worker: -- Audio config
20231221 122605 worker: --
20231221 122606 worker: MPD config:    updated
20231221 122606 worker: Audio device:  Allo Boss DAC
20231221 122606 worker: Formats:       S16_LE, S24_LE, S32_LE
20231221 122606 worker: Mixer type     Software
20231221 122606 worker: Mixer name     Digital
20231221 122606 worker: Hdwr volume:   controller detected
20231221 122606 worker: ALSA max vol:  100%
20231221 122606 worker: ALSA card:     0
20231221 122606 worker: ALSA mode:     Default
20231221 122606 worker: ALSA loopback: off
20231221 122606 worker: CamillaDSP:    off
20231221 122606 worker: Renderers:     active flags reset
20231221 122606 worker: --
20231221 122606 worker: -- MPD startup
20231221 122606 worker: --
20231221 122608 worker: MPD service:        started
20231221 122608 worker: MPD port 6600:      accepting connections
20231221 122608 worker: MPD ALSA Default:   on
20231221 122608 worker: MPD ALSA Bluetooth: off
20231221 122608 worker: MPD HTTP Server:    off
20231221 122608 worker: MPD crossfade:      off
20231221 122608 worker: MPD ignore CUE:     yes
20231221 122608 worker: MPD CDSP volsync:   off
20231221 122608 worker: MPD CDSP volrange:  60 dB
20231221 122608 worker: --
20231221 122608 worker: -- Music sources
20231221 122608 worker: --
20231221 122608 worker: USB auto-mount: udisks-glue
20231221 122608 worker: USB drives:     no drives found
20231221 122608 worker: NAS source:     TheTome
20231221 122608 worker: NAS mount:      mount all submitted
20231221 122608 worker: --
20231221 122608 worker: -- Feature availability
20231221 122608 worker: --
20231221 122608 worker: Input select:    available, src MPD, out Allo Boss DAC
20231221 122608 worker: Bluetooth:       available, ALSA mode Default
20231221 122608 worker: AirPlay:         available
20231221 122608 worker: Spotify Connect: available
20231221 122608 worker: Squeezelite:     available
20231221 122608 worker: RoonBridge:      not installed
20231221 122608 worker: Multiroom:       available
20231221 122608 worker: UPnP client:     available
20231221 122608 worker: GPIO buttons:    available
20231221 122608 worker: Stream recorder: n/a
20231221 122608 worker: HTTPS-Only mode: n/a
20231221 122608 worker: --
20231221 122608 worker: -- Volume levels
20231221 122608 worker: --
20231221 122608 worker: Volume knob:      51
20231221 122608 worker: Saved MPD volume: 0
20231221 122608 worker: Saved SRC volume: 0
20231221 122609 worker: Hdwr volume:      100%
20231221 122609 worker: --
20231221 122609 worker: -- Peripherals
20231221 122609 worker: --
20231221 122622 worker: Local display:   off
20231221 122622 worker: On-screen kbd:   off
20231221 122622 worker: Rotary encoder:  off
20231221 122622 worker: USB volume knob: off
20231221 122622 worker: LCD updater:     on
20231221 122622 worker: --
20231221 122622 worker: -- Miscellaneous
20231221 122622 worker: --
20231221 122622 worker: Auto-CoverView:    off
20231221 122622 worker: CoverView timeout: Never
20231221 122622 worker: Auto-shuffle:      off
20231221 122622 worker: Auto-play:         on, via playid 1
20231221 122622 worker: Web SSH server:    off
20231221 122622 worker: Maintenance task:  360 mins
20231221 122622 worker: Current view:      reset to Playback
20231221 122623 worker: Session check:     ok
20231221 122623 worker: --
20231221 122623 worker: -- Startup complete
20231221 122623 worker: --
20231221 122623 worker: Mount monitor:    started
20231221 122623 worker: MPD monitor:      off
20231221 122623 worker: Watchdog monitor: started
20231221 122623 worker: Responsiveness:   Default
20231221 122623 worker: Ready

[Tim Curtis]

Leave WiFi as configured, reboot and then look at the status for the NFS share you are mounting.

Code:

mount | grep nfs4

Example from one of my systems that mounts an NFS share hosted on another Pi.

Code:

pi@moode:~ $ mount | grep nfs4
192.168.1.199:/media/VFAT128/FLAC on /mnt/NAS/TRX-NFS-FLAC type nfs4 (ro,relatime,vers=4.2,rsize=131072,wsize=131072,namlen=255,soft,proto=tcp,timeo=10,retrans=1,sec=sys,clientaddr=192.168.1.121,local_lock=none,addr=192.168.1.199)

[Joseph.Barrow]

Leave WiFi as configured, reboot and then look at the status for the NFS share you are mounting.

Code:

mount | grep nfs4

Example from one of my systems that mounts an NFS share hosted on another Pi.

Code:

pi@moode:~ $ mount | grep nfs4
192.168.1.199:/media/VFAT128/FLAC on /mnt/NAS/TRX-NFS-FLAC type nfs4 (ro,relatime,vers=4.2,rsize=131072,wsize=131072,namlen=255,soft,proto=tcp,timeo=10,retrans=1,sec=sys,clientaddr=192.168.1.121,local_lock=none,addr=192.168.1.199)

Before reboot, with Ethernet:

Code:

joe@wireless:~ $ mount | grep nfs4
192.168.18.16:/media/depot/audio/audio on /mnt/NAS/TheTome type nfs4 (ro,relatime,vers=4.2,rsize=1048576,wsize=1048576,namlen=255,soft,proto=tcp,timeo=10,retrans=1,sec=sys,clientaddr=192.168.18.30,local_lock=none,addr=192.168.18.16)

After reboot, without Ethernet:

Nothing.

After reboot, with Ethernet:

Code:

joe@wireless:~ $ sudo mount | grep nfs4
192.168.18.16:/media/depot/audio/audio on /mnt/NAS/TheTome type nfs4 (ro,relatime,vers=4.2,rsize=1048576,wsize=1048576,namlen=255,soft,proto=tcp,timeo=10,retrans=1,sec=sys,clientaddr=192.168.18.30,local_lock=none,addr=192.168.18.16)

I'm not proficient with NFS aside from looking up stuff to set it up, so I don't know what differences I'd be looking for. But... it seems to me that the 'clientaddr' needs to point to my Wi-Fi address, not my Ethernet address. Granted, with just Wi-Fi, it's not mounting anything at all, and a 'mount -a' isn't doing anything... and I've just remembered that I don't have any NFS mounts in the new fstab that I might have had in the old one. Still... it mounted with an Ethernet connection and ignored Wi-Fi.

 If I'm right, then how do I fix it?

And congratulations for 10 years, while I'm thinking about it!

[Tim Curtis]

Leave WiFi as configured, reboot and then look at the status for the NFS share you are mounting.

Code:

mount | grep nfs4

Example from one of my systems that mounts an NFS share hosted on another Pi.

Code:

pi@moode:~ $ mount | grep nfs4
192.168.1.199:/media/VFAT128/FLAC on /mnt/NAS/TRX-NFS-FLAC type nfs4 (ro,relatime,vers=4.2,rsize=131072,wsize=131072,namlen=255,soft,proto=tcp,timeo=10,retrans=1,sec=sys,clientaddr=192.168.1.121,local_lock=none,addr=192.168.1.199)

Before reboot, with Ethernet:

Code:

joe@wireless:~ $ mount | grep nfs4
192.168.18.16:/media/depot/audio/audio on /mnt/NAS/TheTome type nfs4 (ro,relatime,vers=4.2,rsize=1048576,wsize=1048576,namlen=255,soft,proto=tcp,timeo=10,retrans=1,sec=sys,clientaddr=192.168.18.30,local_lock=none,addr=192.168.18.16)

After reboot, without Ethernet:

Nothing.

After reboot, with Ethernet:

Code:

joe@wireless:~ $ sudo mount | grep nfs4
192.168.18.16:/media/depot/audio/audio on /mnt/NAS/TheTome type nfs4 (ro,relatime,vers=4.2,rsize=1048576,wsize=1048576,namlen=255,soft,proto=tcp,timeo=10,retrans=1,sec=sys,clientaddr=192.168.18.30,local_lock=none,addr=192.168.18.16)

I'm not proficient with NFS aside from looking up stuff to set it up, so I don't know what differences I'd be looking for. But... it seems to me that the 'clientaddr' needs to point to my Wi-Fi address, not my Ethernet address. Granted, with just Wi-Fi, it's not mounting anything at all, and a 'mount -a' isn't doing anything... and I've just remembered that I don't have any NFS mounts in the new fstab that I might have had in the old one. Still... it mounted with an Ethernet connection and ignored Wi-Fi.

 If I'm right, then how do I fix it?

And congratulations for 10 years, while I'm thinking about it!

It sounds like an NFS server config issue.

Maybe configure your server so that the exports can be accessed by the entire subnet or alternatively by a list of specific  IP addresses. The NFS server options should also include "no_root_squash"

Below is the help for moOde's built in NFS server for reference.
   

[Joseph.Barrow]

[quote pid='50572' dateline='1703191579']
It sounds like an NFS server config issue.

Maybe configure your server so that the exports can be accessed by the entire subnet or alternatively by a list of specific  IP addresses. The NFS server options should also include "no_root_squash"

Below is the help for moOde's built in NFS server for reference.

[/quote]


Okay, I'll look into that. Could be!

May be a while - as some other real-life things are upcoming tomorrow and it may be a while. For this issue, I've been taking notes.

If not working after that, I'll post either here or in a new message.

[Joseph.Barrow]

Quick reply - Added "no_root_squash" and exported the share again, unplugged the Ethernet, then rebooted. After reboot, the Wi-Fi connection was working and the music was playing.

Thanks!

[Tim Curtis]

Quick reply - Added "no_root_squash" and exported the share again, unplugged the Ethernet, then rebooted. After reboot, the Wi-Fi connection was working and the music was playing.

Thanks!

Nice :-)

When convenient, edit your post #1 you can change the Thread to "solved".

[TheOldPresbyope]

Since you got it working, this is just a sidebar observation.

Both of your "mount|grep nfs" outputs show the "clientaddr=..." option is set in the mount.

I don't see that option set when mounting some nfs shares and do with others. Here, for example, is the comparable output on one of my moOde 8.3.7 players

Code:

pi@moode837:/etc $ mount|grep nfs
10.0.0.2:/export/Test on /mnt/NAS/omv-nfs type nfs (ro,relatime,vers=3,rsize=131072,wsize=131072,namlen=255,soft,nolock,proto=tcp,timeo=10,retrans=1,sec=sys,mountaddr=10.0.0.2,mountvers=3,mountport=60426,mountproto=udp,local_lock=all,addr=10.0.0.2)
10.0.0.19:/media/KAR01 on /mnt/NAS/sunroom-nfs type nfs4 (ro,relatime,vers=4.2,rsize=65536,wsize=65536,namlen=255,soft,proto=tcp,timeo=10,retrans=1,sec=sys,clientaddr=10.0.0.5,local_lock=none,addr=10.0.0.19)
10.0.0.147:/srv on /mnt/NAS/xenon-nfs type nfs (ro,relatime,vers=3,rsize=1048576,wsize=1048576,namlen=255,soft,nolock,proto=tcp,timeo=10,retrans=1,sec=sys,mountaddr=10.0.0.147,mountvers=3,mountport=44826,mountproto=udp,local_lock=all,addr=10.0.0.147)

In this case, host 10.0.0.2 is an OpenMediaVault NAS running in Armbian on a Odroid HC1. Host 10.0.0.19 is another moOde 8.3.7 player. Host 10.0.0.147 is a Linux Mint server. Only the share from the moOde NFS server has clientaddr= in the mount options.

Curious. May take some digging to find out what server setting(s) is causing the difference.

ETA - Yeah, it might be a NFSv4 thing but AFAIK it doesn't need to be specified in most cases, so I'm not sure why it is here.

Regards,
Kent