![]() |
Upcoming moOde 8.2.1 release - 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: Upcoming moOde 8.2.1 release (/showthread.php?tid=5082) |
Upcoming moOde 8.2.1 release - Tim Curtis - 09-20-2022 Here are WIP release notes for upcoming 8.2.1 release (Q3 or Q4). This release provides some minor updates and a few bug fixes :-) Code: ################################################################################ RE: Upcoming moOde 8.2.1 release - Tim Curtis - 09-28-2022 Here are latest WIP release notes. A mount monitoring option has been added to the File sharing feature. This replaces the basic mount monitor function in worker.php This is a dedicated daemon that automatically attempts to re-mount a Music source if it's mount point becomes unreachable. It supports both SMB and NFS mounts. We are also looking at including the Airplay 2 capable version of shairport-sync if testing goes well. Code: ################################################################################ RE: Upcoming moOde 8.2.1 release - suzywong - 09-28-2022 A mount monitoring option has been added to the File sharing feature. This replaces the basic mount monitor function in worker.php This is a dedicated daemon that automatically attempts to re-mount a Music source if it's mount point becomes unreachable. It supports both SMB and NFS mounts. That would be very useful, and for me timely! ![]() For sure, it's not been a critical issue, and a manual remount has got it back up, but in both cases I was left with an empty database, and had to do a "database update" to restore the library (is there a quicker way?), which obviously takes a bit of time but does however provide an opportunity to wander off the kitchen, make coffee, and stroke the kitties! ![]() So t'would be nice to have an auto re-mount. Would (could) you auto trigger a database update as well? RE: Upcoming moOde 8.2.1 release - Tim Curtis - 09-28-2022 lol, your cats trained you well ;-) First I'd like to see how the improved mount monitor works in the field. It does the basics for example "is the host pingable" then if so "can the mount point be reached". The last one is where you can end up in the deep end of the pool with the Alligators :-0 RE: Upcoming moOde 8.2.1 release - suzywong - 09-29-2022 Fifteen years of Burmese cats has left us “on our knees” ![]() Hear what you say, especially “it’s difficult to think straight when you are up to your a$$ in alligators” RE: Upcoming moOde 8.2.1 release - romain - 09-30-2022 (09-28-2022, 04:52 PM)Tim Curtis Wrote: Here are latest WIP release notes.Hello @Tim Curtis , nice to see a feature that I posted a while ago here: https://moodeaudio.org/forum/showthread.php?tid=2344 The systemd service checks the availability of all sources, be it network (NFS, SMB, UPnP) or local (USB) sources, every 15 seconds and combines the auto re-mount function with leds. I still use it with moOde 8.2.0, see files attached. RE: Upcoming moOde 8.2.1 release - Tim Curtis - 09-30-2022 its a super nice script but the command (mountpoint) which is used in the script to check mount points will wait indefinitely if a mount point is an NFS mount and the NFS server service on the NAS has been turned off, is hung or has crashed. In this scenario the script will not continue checking mount points until the NFS server service comes back up on the NAS :-0 The approach I took in mountmon.php to check for NFS service availability is to probe port 2049. If this port is not open the script simply logs a warning and avoids checking the mount point which could result in an indefinite wait. Code: while (true) { Here's some log output Code: pi@moode:~ $ tail -f /var/log/mountmon.log Also, a user posted an issue to our Git repo about a mount checking service built into systemd called Automount. I haven't tested it but apparently it depends on having the mounts in fstab. This would involve a rip and replace of how mounts are done in moOde and so its not something that has a high priority particularly if the basic mountmon daemon does a decent job. RE: Upcoming moOde 8.2.1 release - romain - 09-30-2022 (09-30-2022, 12:56 PM)Tim Curtis Wrote: its a super nice script but the command (mountpoint) which is used in the script to check mount points will wait indefinitely if a mount point is an NFS mount and the NFS server service on the NAS has been turned off, is hung or has crashed. In this scenario the script will not continue checking mount points until the NFS server service comes back up on the NAS :-0Tim, in my initial post, I had already raised the NFS problem, it's because NFS mounts are hard mounted by default. To avoid the script waiting indefinitely for NFS mounts or server to be back online, the solution is simply to use the soft mount option instead of the hard one. The following NFS mount options work like a charm for me : soft,timeo=10,retrans=1,ro,nolock RE: Upcoming moOde 8.2.1 release - Tim Curtis - 09-30-2022 Interesting. Similar to what is described in the article below? https://kb.netapp.com/Advice_and_Troubleshooting/Data_Storage_Software/ONTAP_OS/What_are_the_differences_between_hard_mount_and_soft_mount I'll run some tests this weekend :-) RE: Upcoming moOde 8.2.1 release - romain - 09-30-2022 (09-30-2022, 01:17 PM)Tim Curtis Wrote: Interesting. Similar to what is described in the article below? Exactly. IMHO, NFS soft mount is much more adapted than the hard one for a read only usage scenario as it is supposed to be the case with moOde. Moreover, if I've well understood your approach, checking that the NFS server is online is not exactly the same thing as checking if NFS shares are online because testing the server port doesn't guarantee that NFS exports are available. |