[SOLVED] RPi3A+ Network instability.

[the_bertrum]

OK, I give up.

Fresh burn with @eaDir in the mpdignore and SMB library configured. = Successful scan.
Fresh burn with no mpdignore and SMB library configured = Freeze. - so far so good
Fresh burn with no mpdignore and NFS library configured = Successful scan.
Fresh burn with @eaDir in the mpdignore and NFS library configured = Freeze - What?
Fresh burn with @eaDir in the mpdignore and SMB library configured (again)= Freeze.

I must have run 20 combinations today and while NFS and ignoring the eaDirs seems to be more likely to complete, it isn't ever certain.
I did manage to get a moodeutl -m reading as a freeze happened and the cpu was heading north with the last reported value at 98%. Tried to run TOP for a few scans to see what process might be to blame, but it never managed to capture stats just before the freeze.

I really thought I had it this time.

[Tim Curtis]

Interesting. If the CPU gets pegged it would explain the unresponsiveness of the system.

The components involved in a Library update are:

MPD
/var/www/util/list-songfiles.sh
/var/www/util/thumb-gen.php

The list-songfiles.sh command is run by thumb-get.php and it pipes it to sort. Since sorting can be resource intensive I'd try running the command stand alone and monitor it with htop in a second SSH term.

Code:

# Default is from the Prefs setting COVER ART > Audio formats

sudo /var/www/util/list-songfiles.sh Default | sort

[TheOldPresbyope]

A quick search of the InterWeb™ reveals that folks have been complaining about these @eaDir directories in the Synology Community for at least a decade. Here's an expletive-punctuated example: https://community.synology.com/enu/forum/17/post/70878

I hate to indulge in Shadenfreude but boy am I glad I don't have a Synology NAS under the desk. I admit I was tempted more than once 'cuz my DIY NASes look ugly and lack bells and whistles (the "it's so easy a caveman can do it" interface) but they are easy to understand/configure/modify.

Still, there's lots of Synology users out there so finding a way to inoculate moOde would help cut down on the support traffic. Good hunting.

Regards,
Kent

[the_bertrum]

Interesting. If the CPU gets pegged it would explain the unresponsiveness of the system.

The components involved in a Library update are:

MPD
/var/www/util/list-songfiles.sh
/var/www/util/thumb-gen.php

The list-songfiles.sh command is run by thumb-get.php and it pipes it to sort. Since sorting can be resource intensive I'd try running the command stand alone and monitor it with htop in a second SSH term.

Code:

# Default is from the Prefs setting COVER ART > Audio formats

sudo /var/www/util/list-songfiles.sh Default | sort

Thanks Tim, something else to try.  It would be nice to work this out.  I'll run these tests shortly.

[zandman]

I did have similar issues with my Pi3A+, but only on 9.0.1. You are not alone :-)
It starts up fine from a fresh SD image, but after changing some essential settings the interface freezes. I believe it happens after I add my NAS tot the library
No issues on 8.3.9

Today my Pi didn't even startup anymore, it doesn't read the SD card. So maybe my issues were (partially) due to a failing SD slot.

New Pi5 is on the way

What NAS are you using @zandman?

Sorry for the late response. My NAS is a QNAP TS 464. No issues with the Pi5. My 3A+ officially died, so can't test anymore

[the_bertrum]

A quick search of the InterWeb™ reveals that folks have been complaining about these @eaDir directories in the Synology Community for at least a decade. Here's an expletive-punctuated example: https://community.synology.com/enu/forum/17/post/70878

I hate to indulge in Shadenfreude but boy am I glad I don't have a Synology NAS under the desk. I admit I was tempted more than once 'cuz my DIY NASes look ugly and lack bells and whistles (the "it's so easy a caveman can do it" interface) but they are easy to understand/configure/modify.

Still, there's lots of Synology users out there so finding a way to inoculate moOde would help cut down on the support traffic. Good hunting.

Regards,
Kent

But is it sooo pretty Kent.  All shiny and white and monolithic.

The easy to use features are great as far as they go, it's nice to be able to connect from anywhere with reasonable out of the box security, but the software has clearly been designed by people who make storage solutions rather than by people who use them.  It can be a faff to configure anything vaguely advanced as well, three screens in different sections to tie NFS together so it works for example.
In short, not perfect, but not rubbish enough to justify changing it either.

[TheOldPresbyope]

@the_bertrum 

But is it sooo pretty Kent.  All shiny and white and monolithic.

I get that. My partner would love to see more shiny and white and monolithic and fewer open boards, rats nests of cables and power packs. Still, she gets a resident IT support staffer (her "nerd boy"!) who is available 24/7 to deal with the inevitable Microsoft/Apple/Google issues. We've been together a decade so I guess she still figures the tradeoff is worth it.

Regards,
Kent

[the_bertrum]

Interesting. If the CPU gets pegged it would explain the unresponsiveness of the system.

The components involved in a Library update are:

MPD
/var/www/util/list-songfiles.sh
/var/www/util/thumb-gen.php

The list-songfiles.sh command is run by thumb-get.php and it pipes it to sort. Since sorting can be resource intensive I'd try running the command stand alone and monitor it with htop in a second SSH term.

Code:

# Default is from the Prefs setting COVER ART > Audio formats

sudo /var/www/util/list-songfiles.sh Default | sort

Well, it certainly isn't that command that hangs.  The whole thing run in about 5 seconds.  The initial "find" part gets permission denied errors on the eaDir folders, then the "file" part runs so fast that the console becomes a blur as the output whirls past.
Snippet here:

Code:

find: '/mnt/NAS/Claudia/Will Young/Friday\'s Child/@eaDir/06 Dance The Night Away.m4a': Permission denied
find: '/mnt/NAS/Claudia/Will Young/Friday\'s Child/@eaDir/09 Going My Way.m4a': Permission denied
find: '/mnt/NAS/Claudia/Will Young/Friday\'s Child/@eaDir/04 Leave Right Now.m4a': Permission denied
find: '/mnt/NAS/Claudia/Will Young/Friday\'s Child/@eaDir/02 Your Game.m4a': Permission denied
file: NAS/Claudia/'Til Tuesday/Everything's Different Now/01 Everything’s Different Now.m4a
file: NAS/Claudia/'Til Tuesday/Everything's Different Now/02 Rip in Heaven.m4a
file: NAS/Claudia/'Til Tuesday/Everything's Different Now/03 Why Must I.m4a
file: NAS/Claudia/'Til Tuesday/Everything's Different Now/04 ‘J’ for Jules.m4a

[the_bertrum]

Running a full update with htop running to see what happens.  Attached a screenshot taken from the frozen system.  Top window is the mpd log, the track being scanned is irrelevant, it doesn't fail on the same track each time.  The top process is nmap, that's interesting given the network oddness that goes with the freeze (network operations never timing out or failing , but also never completing either).
   

[the_bertrum]

Dunno if this helps.  My Router interface says that the "testbed player" it there, on ip 192.168.1.73.

Code:

robert@Lyssa:~$ ping testbed.local
ping: testbed.local: Name or service not known
robert@Lyssa:~$ ping 192.168.1.73
PING 192.168.1.73 (192.168.1.73) 56(84) bytes of data.
64 bytes from 192.168.1.73: icmp_seq=1 ttl=64 time=76.6 ms
64 bytes from 192.168.1.73: icmp_seq=2 ttl=64 time=97.6 ms
64 bytes from 192.168.1.73: icmp_seq=3 ttl=64 time=121 ms
^C
--- 192.168.1.73 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2003ms
rtt min/avg/max/mdev = 76.555/98.439/121.147/18.213 ms
robert@Lyssa:~$ avahi-browse -k -a
+ wlp1s0 IPv4 0006786CD796@dionysus                         _raop._tcp           local
+ wlp1s0 IPv4 0006786cd796dionysus                          _spotify-connect._tcp local
+ wlp1s0 IPv4 dionysus                                      _heos-audio._tcp     local
+ wlp1s0 IPv4 master                                        _omsg._tcp           local
+ wlp1s0 IPv4 apollo                                        _device-info._tcp    local
+ wlp1s0 IPv4 Claudia                                       _device-info._tcp    local
+ wlp1s0 IPv4 orpheus                                       _device-info._tcp    local
+ wlp1s0 IPv4 apollo                                        _smb._tcp            local
+ wlp1s0 IPv4 Claudia                                       _smb._tcp            local
+ wlp1s0 IPv4 orpheus                                       _smb._tcp            local
+ wlp1s0 IPv4 dionysus                                      _http._tcp           local
+ wlp1s0 IPv4 moOde audio player: apollo                    _http._tcp           local
+ wlp1s0 IPv4 myrouter                                      _http._tcp           local
+ wlp1s0 IPv4 moOde audio player: orpheus                   _http._tcp           local
+ wlp1s0 IPv4 apollo                                        _udisks-ssh._tcp     local
+ wlp1s0 IPv4 orpheus                                       _udisks-ssh._tcp     local
+ wlp1s0 IPv4 Fabrizzio                                     _airplay._tcp        local
+ wlp1s0 IPv4 dionysus                                      _airplay._tcp        local
+ wlp1s0 IPv4 Apollo                                        _spotify-connect._tcp local
^CGot SIGINT, quitting.
robert@Lyssa:~$

ssh to ip just hangs, ssh to host name isn't resolved.  My router knows it's there though, and knows it's name.

Code:

robert@Lyssa:~$ ssh master@192.168.1.73
^C
robert@Lyssa:~$ ssh master@testbed.local
ssh: Could not resolve hostname testbed.local: Name or service not known