Thank you for your donation!


Problem: Library build problem with my Audiophonics ES09038q2m RaspTouch
#1
Hello to all MoodeUsers,
thanks for the nice piece of software. It is always a pleasure listen to my Audiophonics ES9038q2m, running with Moode.
I am using Moode since 6.2 running perfect. Installation and adding the audiophonics power management was  very easy. The update to 6.3 was a piece of cake. With the upgrade to 6.4 i ran into trouble connecting to my NAS and the power management did not work anymore. So i did a fresh install, installing the power management worked. But the connection to my NAS is still not working. I am not shure if it is a Moode problem, it might be a network related problem.
This is what happens. Installation works normal, listening to Internet Radios is no problem (but sometimes stops). I can find the Moode from other Computers in the Network, acces via Browser is normal. If i create the music source with Configuration Settings i can not mount my NAS connected by Ethernet to my Fritz-Box. Scanning for the Path produces the following: "mbXcli_negprot_smb1_done: No compatible protocol selected by server.". By typing the path manually i have MPD running for a finding the first entry's of my music files on the NAS. Then it stops running, sometimes with the message:"MPD error openMpdSock() failed".


Any help is appreciated!

Maartin

Code:
M O O D E   S T A R T U P   L O G

20191130 203550 worker: -- Start
20191130 203551 worker: Successfully daemonized
20191130 203551 worker: Integrity check (passed)
20191130 203551 worker: Session loaded
20191130 203551 worker: Debug logging (off)
20191130 203551 worker: Device raw: Card0 (DAC) | Card1 () | I2Sdev (Audiophonics ES9028/9038 DAC)
20191130 203551 worker: Device cfg: Name (Audiophonics ES9028/9038 DAC) | Card (0) | MPDdev (0) | Mixer (Digital) | Alsavol: (0)
20191130 203551 worker: ALSA volume set to (0%)
20191130 203551 worker: -- System
20191130 203553 worker: Host name     (moode-unten)
20191130 203553 worker: moOde release (6.4.0 2019-11-24)
20191130 203553 worker: Raspbian OS   (10.2)
20191130 203553 worker: Linux kernel  (4.19.83-v8+ #1277)
20191130 203553 worker: Platform      (Pi-3B+ 1GB v1.3)
20191130 203553 worker: Architecture  (aarch64)
20191130 203553 worker: MPD version   (0.21.16)
20191130 203553 worker: CPU governor  (performance)
20191130 203554 worker: USB boot enabled
20191130 203554 worker: File system expanded
20191130 203554 worker: HDMI port off
20191130 203554 worker: File check (OK)
20191130 203554 worker: -- Network
20191130 203554 worker: eth0 exists
20191130 203554 worker: IP addr (192.168.178.30)
20191130 203555 worker: Netmask (255.255.255.0)
20191130 203555 worker: Gateway (192.168.178.1)
20191130 203555 worker: Pri DNS ()
20191130 203555 worker: Domain  ()
20191130 203555 worker: wlan0 does not exist
20191130 203555 worker: -- Audio
20191130 203555 worker: ALSA outputs unmuted
20191130 203555 worker: ALSA card number (0)
20191130 203555 worker: Audio output (I2S audio device)
20191130 203555 worker: Audio device (Audiophonics ES9028/9038 DAC)
20191130 203555 worker: Audio formats (S16_LE, S32_LE)
20191130 203555 worker: ALSA mixer name (Digital)
20191130 203555 worker: MPD volume control (hardware)
20191130 203555 worker: Hdwr volume controller exists
20191130 203555 worker: Max ALSA volume (100%)
20191130 203555 worker: -- Services
20191130 203555 worker: Reset renderer active state
20191130 203556 worker: MPD conf updated
20191130 203556 worker: MPD started
20191130 203557 worker: MPD accepting connections
20191130 203557 worker: Configure MPD outputs
20191130 203557 worker: MPD output 1 ALSA default (on)
20191130 203557 worker: MPD output 2 ALSA crossfeed (off)
20191130 203557 worker: MPD output 3 ALSA parametric eq (off)
20191130 203557 worker: MPD output 4 ALSA graphic eq (off)
20191130 203557 worker: MPD output 5 ALSA polarity inversion (off)
20191130 203557 worker: MPD output 6 ALSA bluetooth (off)
20191130 203557 worker: MPD output 7 HTTP stream (off)
20191130 203557 worker: MPD crossfade (off)
20191130 203557 worker: Audio source (Local)
20191130 203557 worker: Output device (Local)
20191130 203557 worker: USB auto-mounter (udisks-glue)
20191130 203557 worker: -- Music sources
20191130 203557 worker: USB sources (none attached)
20191130 203558 worker: NAS and UPnP sources (mountall initiated)
20191130 203558 worker: -- Miscellaneous
20191130 203558 worker: Saved MPD vol level (0)
20191130 203558 worker: Preamp volume level (0)
20191130 203558 worker: MPD volume level (54) restored
20191130 203558 worker: ALSA volume level (85%)
20191130 203558 worker: Auto-play (Off)
20191130 203558 worker: LocalUI started
20191130 203558 worker: Maintenance interval (6 hrs)
20191130 203558 worker: Screen saver activation (Never)
20191130 203558 worker: Session permissions (OK)
20191130 203558 worker: Watchdog started
20191130 203558 worker: Ready
20191130 203558 watchdog: INFO Audio output is (closed)
Reply
#2
These lines suggest some sort of network issue.

Code:
20191130 203555 worker: Pri DNS ()
20191130 203555 worker: Domain  ()

In your particular case I would have expected Pro DNS to be 192.168.178.1, same as the Gateway address, and Domain to be populated with a name. Linux stores both these values in /etc/resolve.conf.

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

The issue below suggests possibly a bad SDCard or it could also be related to the issue above where there is no DNS address.

MPD error openMpdSock() failed"

-Tim
Reply
#3
@maartin

In addition to what Tim said about possible network issues, the error message "mbXcli_negprot_smb1_done: No compatible protocol selected by server" implies your NAS won't accept a connection using the SMB1 protocol. 

moOde is set to SMB1 (vers=1.0) by default in the advanced settings at the Music Source panel. Did you notice the small print at the bottom of that panel?

Quote:vers=2.0, 3.0, 3.1 etc may be needed and/or sec=ntlm depending on what the NAS device requires.

You should find out what protocol version(s) your NAS is configured to accept and adjust the settings accordingly.

Regards,
Kent
Reply
#4
Thanks Guys, for your help!  I am going to try your advises asap and report.
So far I set up a new img on a  different SD-card and i did not get any message "MPD error openMpdSock() failed".

I had an eye on the smb1.0, 2.0, 3.0 thing already and will try further with different settings.


I'll keep on!

All the best
Maartin
Reply
#5
Hi Guys,
so far i found that my network problems seem to be left behind. All Computers have access to shares of other Computers in the network.
My trusty Rasptouch does not... That is the message:
sourceMount(): Mount error: (mount error(2): No such file or directory
Refer to the mount.cifs(8) manual page (e.g. man mount.cifs))

Strangely enough is in the Configure/Library Tab > Music Source Field the  NAS marked mounted with a green hook.
Access to I-Net Radio is working fine.

Any Ideas anybody?

All the best
Maartin
Reply
#6
(12-04-2019, 10:30 AM)maartin Wrote: Hi Guys,
so far i found that my network problems seem to be left behind. All Computers have access to shares of other Computers in the network.

What are "all computers"? MS Windows <version>?, OSX <version>? Linux <distro and version>?

Can "all computers" access the shares published by moOde? They should show up in whatever passes on those computers for the old Windows Network Neighborhood screen. From a Linux Mint 18.3 host I see and access moOde shares either from the Network places in the GUI or from the command line (my NAS is that OMV-HC1 at the end of this snippet)

Code:
kreed@t520:~ $ smbtree -bN
    \\MOODELR                moOde SMB Server
        \\MOODELR\IPC$               IPC Service (moOde SMB Server)
        \\MOODELR\MUSIC              USB Storage
        \\MOODELR\SDCard             SDCARD Storage
        \\MOODELR\Radio              RADIO Stations
        \\MOODELR\Playlists          Playlist Directory
        \\MOODELR\NAS                NAS Shares
    \\MOODE4B                moOde SMB Server
        \\MOODE4B\IPC$               IPC Service (moOde SMB Server)
        \\MOODE4B\SDCard             SDCARD Storage
        \\MOODE4B\Radio              RADIO Stations
        \\MOODE4B\Playlists          Playlist Directory
        \\MOODE4B\NAS                NAS Shares
    \\MOODE3A                moOde SMB Server
        \\MOODE3A\IPC$               IPC Service (moOde SMB Server)
        \\MOODE3A\SDCard             SDCARD Storage
        \\MOODE3A\Radio              RADIO Stations
        \\MOODE3A\Playlists          Playlist Directory
        \\MOODE3A\NAS                NAS Shares
    \\OMV-HC1                omv-hc1 server
        \\OMV-HC1\IPC$               IPC Service (omv-hc1 server)
        \\OMV-HC1\Music              
        \\OMV-HC1\Test               
       ...+ lots of other SMB/CIFS servers and shares...


Quote:My trusty Rasptouch does not... That is the message:
sourceMount(): Mount error: (mount error(2): No such file or directory
Refer to the mount.cifs(8) manual page (e.g. man mount.cifs))

Strangely enough is in the Configure/Library Tab > Music Source Field the  NAS marked mounted with a green hook.

These two statements seem contradictory. Are they referring to the same source? AIUI, if you get the green checkmark, then the corresponding source is mounted. What do you see if you invoke mount from the command line? For example, on my moOde 6.4.0 player named moode3a with two SMB shares mounted (OMV-HC1 is my NAS and MOODELR is another moOde player)

Code:
pi@moode3a:~ $ mount|grep mnt
//OMV-HC1/Music on /mnt/NAS/OMV-SMB type cifs (ro,relatime,vers=1.0,cache=strict,username=Guest,uid=0,noforceuid,gid=0,noforcegid,addr=192.168.1.12,soft,unix,posixpaths,serverino,mapposix,acl,rsize=61440,wsize=65536,echo_interval=60,actimeo=1)
//MOODELR/MUSIC on /mnt/NAS/MoodeLRMusic type cifs (ro,relatime,vers=1.0,cache=strict,username=Guest,uid=0,noforceuid,gid=0,noforcegid,addr=192.168.1.198,soft,unix,posixpaths,serverino,mapposix,acl,rsize=61440,wsize=65536,echo_interval=60,actimeo=1)


Quote:Access to I-Net Radio is working fine.

Basically this means you have LAN connectivity, a working router, and a working DNS. Necessary but not sufficient.

Quote:Any Ideas anybody?

You mention in your first post that you're using the NAS function on a Fritz!Box. I checked the Fritz!Box site and found some fragmentary references to SMB protocols regarding one model. It said only SMBv1.0 is supported, yet your first error message suggested it isn't. I still think you need to get information about your specific make, model, and version of its firmware.

Diagnosing CIFS/SMB problems is made difficult by the arcane error messages---kinda like consulting the Oracle at Delphi. If you read the man page for mount.cifs you'll get an idea just how complicated this scheme is.

Have you tried using FTP as the transport protocol instead? I see it mentioned in the Fritz!Box commentary and a number of users have bypassed their Samba problems this way in the past.

Regards,
Kent

PS - I noticed in your earlier post that you are using the 64-bit (aarch64) kernel. Just for fun, how about reverting to the 32-bit (armv7l) kernel just to certain we haven't run into a regression in the underlying Raspbian code?
Reply
#7
Hi Guys, i just did some testing. 

@TheOldPresbyope  I just read your post quickly and try out now the 32bit. Lets see..... still updating library... looks good so far....still running....(Big HD)....yes, it is working!!!

Changing to 32bit Kernel did the trick!

(Had Moode 6.3 running in 64bit, strange. )

Quote:NAS function on a Fritz!Box. I checked the Fritz!Box site and found some fragmentary references to SMB protocols regarding one model. It said only SMBv1.0 is supported

Yes, but there is a Beta running now SMB3.


Quote:What do you see if you invoke mount from the command line?

The Share seems to mount, at least i can see it at /mnt/NAS/ via SSH. I can list all my Folder with ls. All there.


As i know how it is working :-), i will try to switch back to 64bit and see what is happening.

Thanks a lot @TheOldPresbyope, @Tim Curtis 

A pleasure listening with Moode!

AtB
Maartin
Reply
#8
@maartin

Glad you're now able to access your share but I just did the reverse test and learned nothing new. It Just Worked™.

RPi4B - moOde 6.4.0 installed from image - WiFi connection to LAN.

  1. 32-bit kernel: able to scan for and connect to the Music share on my OpenMediaVault NAS (which is configured for SMBv1.0). Built complete MPD database without a problem.
  2. Disconnect share, switch kernels, and reboot.
  3. 64-bit kernel: still able to scan for and connect to the Music share on my OpenMediaVault NAS (still SMBv1.0). Again, built complete MPD database without a problem.
I remain uncertain about the root cause of your issue.

Regards,
Kent
Reply
#9
@maartin

OK, I finally managed to create a test case which behaves in the manner you described.

Scenario:

OpenMediaVault server running on host OMV-HC1 with the following snippet of its directory tree structure:

Code:
/path-to/Music
      ./Music/lots of my music in subdirectories
      ./Music/test
      ./Music/test/a number music test files

I have configured OpenMediaVault to serve the subdirectory /path-to/Music as an SMB/CIFS share with guest privileges using SMBv1.0 protocol. That's what you see in the smbtree output in my previous posts. This share is discovered by the scanning function in moOde's Source Mount panel and reported as Server Path OMV-HC1/Music

It mounts fine in moOde and MPD indexes all its contents (which include the music test files in /path-to/Music/test).

Now, if I try manually to mount the subdirectory /path-to/Music/test as Server Path OMV-HC1/Music/test I get the same error message you got.

Code:
mount error(2): No such file or directory

Not surprising, since I haven't told OpenMediaVault to offer this subdirectory as a SMB/CIFS share. It's accessible to moOde only via the SMB/CIFS share which contains it.

At this point I have two Musical Sources entries in the Library Config panel: OMV-SMB (the friendly name I gave the true share) with a green checkmark and OMB-test (the friendly name I gave the not true share) with a red X.

What had been puzzling me was the mount error number 2 because in all the Samba testing with intentional faults I've done over the past few years I never got that particular error number---6, 13, 15, 95, 115, etc., sure, but not 2. Now I know it's because I never tried to abuse Samba this particular way before!

Regards,
Kent
Reply
#10
@TheOldPresbyope
Too much Samba for me!
I noticed that my Share had been mounted in Library Tab, and the "wheel" started turning.  There had been a few album/artists visible in the Moode-Browser window. But then the "wheel" stopped and it had not been possible to play any of the files from my share....
If i will find the enthusiasm to set up moode again I try to find some more hints how this happened.
Thanks for the support!
AtB
Maartin

PS: After the Library had build and some test listening i changed to 64bit. It is working so far.....
Reply


Forum Jump: