Well Phil, I have gone down a rabbit hole looking into this and may have hosed one of my PIs which is a pain as I had not made proper notes on its config for another purpose yet... ~;-) Live and learn.
I think the issue may be Pi and nfs related. I would not do more than I suggest in trying to run this down unless you really know what you are doing or are getting advice from someone who really knows what they are doing. I just did something that I do not know how to reverse. It involved deleting a symbolic link to /dev/null... (Just checked, I may have got it back.) OK. Here goes: I found something that advised me to put something like this in my /etc/fstab: 192.168.86.150:/var/snd /var/snd nfs noatime,x-systemd.automount,x-systemd.device-timeout=5 0 2 On account of the pi using systemd. I did that but it did not seem to help. Perhaps I was not patient enough. I saw something that advised doing this: sudo update-rc.d nfs-common enable And something that advised this: sudo raspi-config then select Wait for network at boot/Yes None of this seemed to work. Perhaps I was not being patient enough at each step. If you try this, I suggest you reboot between each change and give it about 5 minutes to see if /var/snd gets mounted. I finally put this in a script that gets run from ~/.config/autostart/afterairplay.desktop sudo mount.nfs 192.168.86.150:/var/snd /var/snd after a reboot, even that did not seem to work... However... after a good while... /var/snd got mounted... Hence my thought to wait longer than you think necessary after the reboot after each change listed. On Sun, Mar 8, 2020 at 11:18 PM Phil Biehl <fylbe...@gmail.com> wrote: > Drew, > > I’ve made the changes you suggested but things seem to be the same: I can > manually sudo mount to /var/snd and I do see files in it. However, as > before, after having modified the /etc/fstab file I do not see these mounts > unless I manually mount them. I’ve opened up permissions (chmod 777) for > /var and /var/snd with no effect on the problem. > > > > Is there a log file I can look at to look for errors during boot? > Other than the normal system logs, I do not know. > What information can I send you to help diagnose this. I can’t imagine > this is a unique problem. > What I intend to do at some point is follow the instructions here: http://static.paravelsystems.com/rivendell-install-rd3/rivendell-install-rhel7.html With 3 different "machines". When I get to the proper point, I intend to do one of each: /root/install_rivendell.sh --standalone /root/install_rivendell.sh --server /root/install_rivendell.sh --client and see what I can learn from that about how the folks at Paravel want this to go down. all the best, drew > > Phil > > > > *From:* drew Roberts [mailto:zotz...@gmail.com] > *Sent:* Sunday, March 08, 2020 3:53 PM > *To:* Phil Biehl > *Cc:* Mike Carroll; User discussion about the Rivendell Radio Automation > System > *Subject:* Re: [RDD] Riv with a NAS > > > > OK Phil, > > > > I have something that should get you closer although there may still be > more to sort out. > > > > On the rivendell server (which in your case would be the NFS server / NAS) > > [rd@rdserv2 ~]$ cat /etc/exports > /var/nfs 192.168.86.86(rw,sync,no_subtree_check) > /var/snd 192.168.86.1/24(rw,no_root_squash,async) > /var/vid 192.168.86.1/24(rw,no_root_squash,async) > > > > make your /etc/exports match the /var/snd line with appropriate changes to > match your subnet. > > > > sudo exportfs -a > > > > On the Pi: > > > > sudo mkdir /var/snd > > sudo mount.nfs 192.168.86.150:/var/snd /var/snd > > > > 192.168.86.150 is the IP for the Riv server / NFS server / NAS. > > > > I was not careful as to user and group ownership for /var/snd so that may > still need to be sorted to get everything working right. However: > > > > pi@remobpi:~ $ ls /var/snd/000001* > /var/snd/000001_001.wav > > > > pi@remobpi:~ $ ls -lah /var/snd/000001* > -rw-rw-r-- 1 150 150 5.6M Jul 20 2017 /var/snd/000001_001.wav > > > > Yup, looks like something needs to be done with user/group permissions. > > > > all the best, > > > > drew > > > > On Sun, Mar 8, 2020 at 4:16 PM Phil Biehl <fylbe...@gmail.com> wrote: > > Thanks Mike, > > I have already done most of what you describe and appreciate it very much. > What I’m confused about is what and where to place the new library location > reference in the /etc/rd.conf file. I see no sign of an entry that points > to the /var/snd directory that I can modify. > > > > Also, I’ve tried mounting my NAS directory to /var/snd but have had no > success with it as the mount point, /var/snd, has no files showing. I > suspect it’s a Raspberry Pi Raspian permissions issue but I have not been > able to figure out have to fix this even though the mount is successful. > > > > > > Phil > > > > > > On Mar 7, 2020, at 8:04 PM, Mike Carroll <druidl...@gmail.com> wrote: > > > > Hi, Phil. > > > > You're correct, it's "rd.conf". (I work in three different operating > systems in my day job, plus Rivendell/CentOS, and I forgot which one I was > talking about. <smile>) > > > > I'm not much of a Linux guy, but here's what I've done as an experiment. > I'm counting on the more experienced folks on the list to point out errors > and flaws. This is using Win10, standard Rivendell 3 on CentOS, running on > VMWare under Win10, and a pretty old consumer-grade Netgear ReadyNAS, at > address 192.168.86.30. > > 1. Use the Netgear web interface to create a shared folder in the > NAS. I used the name "rivendell". Ensure the folder is marked public. > 2. By default, the only way to access a new ReadyNAS shared folder is > by using Windows file services (Netgear calls this "CIFS"). Use the web > interface to also activate these services for the "rivendell" folder: > > > 1. "NFS". Ensure the "Default Access" is set to "Read/write". My NAS > is on a UPS, so I've disabled "Sync mode". > 2. "HTTP/S". Ensure the Default Access is set to something other > than "Disabled". I used "Read-only". > > > 1. I could now see the shared folder in a web browser, at > 192.168.86.30/rivendell, on both Windows and CentOS. > > On the Rivendell/CentOS machine, you can access the NFS share by issuing > these commands as root: > > 1. Create a /var/rivendell directory. Don't put anything in it - this > is used as a target for a mount. mkdir /var/rivendell > 2. Make the NAS shared folder available to CentOS: mount -t nfs > 192.168.86.30:/rivendell /var/rivendell/ > > At this point you can work with /var/rivendell as if it were any other > directory - except that it's on the NAS. For example, you could update the > rd.conf audio store settings to point to /var/rivendell instead of > /var/snd > > > > The /var/rivendell directory on your local drive is hidden. If you unmount > ("umount") the /var/rivendell remote directory, the local one will > re-appear. > > > > There are issues with Rivendell file and directory permissions, and you > definitely want to update the /etc/fstab file so the NAS share gets mounted > at boot time. I leave those as an exercise for someone more experienced > than me. > > > > Mike > > > > On Sat, Mar 7, 2020 at 12:03 PM Phil Biehl <fylbe...@gmail.com> wrote: > > Hello Mike, > > I saw your post below on how to specify a different sound directory from > the default /var/snd but upon looking int ot I don’t quite see what you > mean. First you said the file to do this is /etc/rd.config. I suspect you > meant etc/rd.conf? Once in that file I see the [AudioStore] section but I > do not see any mention of /var/snd. How does one make Riv look for a NAS > mounted folder? > > > > Thanks very much, > > Phil > > > > > > *From:* rivendell-dev-boun...@lists.rivendellaudio.org [mailto: > rivendell-dev-boun...@lists.rivendellaudio.org] *On Behalf Of *Mike > Carroll > *Sent:* Wednesday, March 04, 2020 6:51 PM > *To:* Frank Christel > *Cc:* User discussion about the Rivendell Radio Automation System > *Subject:* Re: [RDD] Riv with a NAS > > > > You specify the location of both the sound directory and the SQL server > address in /etc/rd.config. Note that the directory can be named anything, > but is traditionally called /var/snd. > > > > I haven't put a Rivendell library on a NAS. But our music server at home, > running on Raspberry Pi Raspbian, has an NFS mount to our consumer-grade > NAS. I had to activate the NFS service in the NAS, but after that it was > just a normal mount from the Pi. So I expect something similar would need > to be done for your NAS. > > > > Mike > > > > On Wed, Mar 4, 2020 at 5:06 PM Frank Christel <fjchris...@gmail.com> > wrote: > > Actually, my interest in using a NAS is just curiosity at this point. > > My immediate goal is in learning how to move the Rivendell audio storage > location to a different hard drive on the same machine. I haven’t yet > located where in RDAdmin(?) to modify the audio and database default > location of "(directory) /var/snd". > > Thanks, > > Frank > > ______________ > > On 3/4/2020, at 3:37 PM, drew Roberts <zotz...@gmail.com> wrote: > > Which NAS do you want to use. Do you have a link to the docs for that NAS? > > _______________________________________________ > Rivendell-dev mailing list > Rivendell-dev@lists.rivendellaudio.org > http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev > > _______________________________________________ > Rivendell-dev mailing list > Rivendell-dev@lists.rivendellaudio.org > http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev > > > > > -- > > Enjoy the *Paradise Island Cam* playing > > *Bahamian Or Nuttin* - https://www.paradiseislandcam.com/ > -- Enjoy the *Paradise Island Cam* playing *Bahamian Or Nuttin* - https://www.paradiseislandcam.com/
_______________________________________________ Rivendell-dev mailing list Rivendell-dev@lists.rivendellaudio.org http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev
