I'm creating a how-to guide of setting up Rivendell with the appliance disk, but I believe that it needs to be easier to setup as well for people like me who knows a lot about windows networking and doing a hard transition into Linux/CentOS and people like you, Tom, who forgets some steps without knowing. When I get done with this how-to guide, I will re-install my audio system and follow it step by step and if it works the way that I had it, then I will release it to the public for them so that they can do it an easy way, but it's not intended for people to get lazy, it's for people who want to get into Rivendell and don't know anything about Linux and they can go ahead and set it up quickly and run with it without trouble.
On 7/18/16, Tom Van Gorkom <tomvangor...@gmail.com> wrote: > If it would help and I can get to it, I need to update our in-house setup > instructions for servers and clients, starting with the appliance > installation, and would be willing to make a more generic version available > to others. I am not an expert either but have figured out how to do it with > the help of others. Yes, I forgot some steps in my email and did not give > enough detail. Sorry about that. > > Tom Van Gorkom > Radio Esperanza Engineering, KRIO AM/FM, KOIR FM > Office: 956-380-8150 > Cell: 865-803-7427 > > Rio Grande Bible Institute > 4300 S US Hwy 281 > Edinburg, TX 78539 > > On Mon, Jul 18, 2016 at 5:48 AM, Wayne Merricks < > waynemerri...@thevoiceasia.com> wrote: > >> Hi, >> >> Rivendell is really simple, all you're doing is sharing mysql access and >> a >> directory full of audio. >> >> Before you dive too deep, make sure every machine works with the sound >> card as you'd expect. I find it easier to set every one up standalone >> (mysql, apache etc) but that is just my preference for how we do things >> here. >> >> On each machine, check if you can ping: >> ping rdserver >> ping rdairone >> ping rdprodone >> ping rdprodtwo >> >> Depending on how your network is setup, you probably won't be able to >> ping. From here you have three options. You should have already set >> every >> machine to a static IP address. If you haven't do that first. You can >> then either use the IP addresses directly, add the DNS names to your >> DNS/DHCP server or add them locally to the machines via /etc/hosts. >> >> Lets assume your network is a standard class C (192.168.x.y) and most >> likely 192.168.1.x. Check with your network/IT guy if you have one. >> >> Make the machines static like this: >> >> rdserver: 192.168.1.210 >> rdairone: 192.168.1.211 >> rdprodone: 192.168.1.221 >> rdprodtwo: 192.168.1.222 >> >> Then check you can ping each address from each machine. >> >> Next up check MySQL is accessible from each machine. >> >> mysql -u rduser -pletmein -h 192.168.1.210 >> >> If you get an error about not connecting it is probably because mysql >> isn't set to allow connections from other machines. >> >> sudo nano /etc/mysql/my.cnf (I'm not sure where this file is in CentOS) >> >> Find the line bind-address = 127.0.0.1 (Ctrl+W to find) >> >> Change it to: bind-address = 0.0.0.0 >> >> Save and quit (Ctrl+X) >> >> Restart mysql: >> >> sudo service mysqld restart (might be service mysql restart) >> >> Check MySQL works again, if you get access denied for rduser log in as >> root on the server: >> >> mysql -u root -p >> >> It will ask for your root MySQL password, you should have been asked to >> make this when you installed. >> >> Once in add access for rduser from any host: >> >> create user 'rduser'@'%' identified by 'letmein'; >> grant all on Rivendell.* to 'rduser'@'%'; >> flush privileges; >> quit; >> >> Now check MySQL again. >> >> Assuming MySQL is now working we can edit rd.conf to point to the server >> on each machine. >> >> sudo nano /etc/rd.conf >> >> Change Hostname=rdserver to Hostname=192.168.1.210 >> >> If your pinging by name works you can use rdserver instead. >> >> Restart the Rivendell daemons and try to load up rdadmin. In there add a >> host for each machine you have, use the host name of the machine and the >> static IP address you set. >> >> You will have to restart the daemons once more when you've added the >> hosts >> so that the daemons update their sound card information. >> >> Now load up something like rdlibrary and see if you can see the test >> tone. You won't be able to play it yet as the audio is probably only on >> the server machine (if you set up standalone it will work as the local >> audio copy will be there). >> >> Finally with that working, we can move on to getting the audio shared. >> >> I'm hoping that the appliance already comes with nfs-kernel-server >> (Debian >> name) so all we have to do is edit the exports file: >> >> sudo nano /etc/exports >> >> Add the line: >> >> /var/snd 192.168.1.0/255.255.255.0(rw,sync,all_squash,subtree_check) >> >> This shares it to all computers on the 192.168.1.x network. >> >> Then push the changes: >> >> sudo exportfs -r -v >> >> Now we have to mount this directory on every machine (except the server >> because it already has it). >> >> On one of the clients test it like this: >> >> sudo mount -t nfs 192.168.1.210:/var/snd /var/snd >> >> Now you will be playing audio from the server instead of locally. >> >> To make this a permanent change: >> >> sudo nano /etc/fstab >> >> Add the line: >> >> 192.168.1.210:/var/snd /var/snd_server nfs >> rsize=32768,wsize=32768,timeo=14,intr >> >> This might make your bootups longer as sometimes it tries to mount before >> the network is ready. I sometimes just use startup scripts to do this >> instead but try it and see. >> >> >> On 18/07/16 06:15, Ryan Kin wrote: >> >>> I even changed my name back to localhost >>> [root@rdserv rd]# nano /etc/rd.conf >>> [root@rdserv rd]# service rivendell restart >>> Starting Rivendell system daemons [ OK ] >>> [root@rdserv rd]# >>> Why am I having MySQL problems now? lol >>> >>> On 7/18/16, Ryan Kin <k1n9h...@gmail.com> wrote: >>> >>>> I changed my name on my hostname to the IP address and rdserv and will >>>> show >>>> me >>>> [root@rdserv rd]# service rivendell restart >>>> Stopping Rivendell system daemons [ OK ] >>>> ripcd: Couldn't open mySQL connection! >>>> ERROR rdcatchd aborting - Couldn't open mySQL connection!Starting >>>> Rivendell system daemons >>>> [FAILED] >>>> >>>> >>>> >>>> On 7/17/16, Tom Van Gorkom <tomvangor...@gmail.com> wrote: >>>> >>>>> Not to jump into the middle of this discussion but for what it's >>>>> worth, >>>>> you >>>>> will need to change 3 things in rd.conf to get it working. >>>>> >>>>> If you have not changed the user names that came with the install, >>>>> then >>>>> make the following changes: >>>>> >>>>> [Identity] >>>>> ; These entries are used to define the system user and group that will >>>>> ; own the audio files. >>>>> AudioOwner=rd >>>>> AudioGroup=users >>>>> >>>>> Then point the client to your server: >>>>> >>>>> [mySQL] >>>>> ; The connection parameters for the MySQL server. >>>>> Hostname=rdserver (the name you gave to your server or the IP address >>>>> works also) >>>>> Loginname=rduser >>>>> Password=letmein >>>>> Database=Rivendell >>>>> Driver=QMYSQL3 >>>>> >>>>> We disable mySQL on the clients. Also make sure that you add all of >>>>> your >>>>> hosts to the hosts file with their IP addresses on all machines. >>>>> >>>>> You need to make sure you give all the correct permissions on the >>>>> server >>>>> mySQL - I assume you found directions for doing that from what you >>>>> said >>>>> earlier. >>>>> >>>>> Be sure to create an exportfs for the shared folders if you have some >>>>> such >>>>> as rd_xfer and export it on the server, and then add the shared >>>>> file(s) >>>>> on >>>>> your fstab list on each client and mount them. >>>>> >>>>> That's what I remember without being where I can look at my notes. >>>>> Hope >>>>> it >>>>> helps. >>>>> >>>>> Tom Van Gorkom >>>>> Radio Esperanza Engineering, KRIO AM/FM, KOIR FM >>>>> Office: 956-380-8150 >>>>> Cell: 865-803-7427 >>>>> >>>>> Rio Grande Bible Institute >>>>> 4300 S US Hwy 281 >>>>> Edinburg, TX 78539 >>>>> >>>>> On Sun, Jul 17, 2016 at 6:08 AM, Ryan Kin <k1n9h...@gmail.com> wrote: >>>>> >>>>> Hey Wayne, this is my rd.conf folder >>>>>> >>>>>> >>>>>> ; rd.conf >>>>>> ; >>>>>> ; This is the default configuration file for Rivendell >>>>>> ; >>>>>> ; by Fred Gleason <fr...@paravelsystems.com> >>>>>> ; >>>>>> >>>>>> [Identity] >>>>>> ; These entries are used to define the system user and group that >>>>>> will >>>>>> ; own the audio files. >>>>>> AudioOwner=rivendell >>>>>> AudioGroup=rivendell >>>>>> >>>>>> ; This password is used by the various Rivendell modules to log into >>>>>> ; Rivendell system services [caed(8), ripcd(8), rdcatchd(8)]. >>>>>> Password=letmein >>>>>> >>>>>> ; This entry is what will appear in RDSelect's list for this >>>>>> configuration. >>>>>> Label=Default (Local) >>>>>> >>>>>> [mySQL] >>>>>> ; The connection parameters for the MySQL server. >>>>>> Hostname=localhost >>>>>> Loginname=rduser >>>>>> Password=letmein >>>>>> Database=Rivendell >>>>>> Driver=QMYSQL3 >>>>>> >>>>>> [AudioStore] >>>>>> MountSource= >>>>>> MountType= >>>>>> MountOptions=defaults >>>>>> CaeHostname= >>>>>> XportHostname= >>>>>> >>>>>> [Logs] >>>>>> ; Set the method to be used for logging. Possible values are: >>>>>> ; Syslog = Use the syslog facility. >>>>>> ; File = Log directly to a file. See also the 'LogDirectory=' >>>>>> ; and 'LogPattern=' parameters below. >>>>>> ; None = Don't generate logs at all. >>>>>> Facility=Syslog >>>>>> >>>>>> ; The directory to write logs to. Used only if the 'Facility=' >>>>>> ; parameter is set to 'File'. >>>>>> LogDirectory=/home/rd/rdlogs >>>>>> >>>>>> ; The directory to to put core files in in the event of a daemon >>>>>> ; crash. For this to work, you must also configure your environment >>>>>> ; to allow the generation of core dumps (e.g. 'ulimit -c unlimited'). >>>>>> CoreDumpDirectory=/home/rd/rdlogs >>>>>> >>>>>> ; The name of the file to send logs to. The following wildcards can >>>>>> ; be used: >>>>>> ; %d - The day of the month (01 - 31) >>>>>> ; %h - The hour (00 - 23) >>>>>> ; %M - The month (01 - 12) >>>>>> ; %m - The minute (00 - 59) >>>>>> ; %n - The name of the originating module --e.g. 'rdairplay', >>>>>> 'caed'. >>>>>> ; %s - The second (00 - 60) >>>>>> ; %Y - The four digit year >>>>>> ; This parameter is used only if the 'Facility=' parameter is set to >>>>>> ; 'File'. >>>>>> LogPattern=%n-%Y%M%d.log >>>>>> >>>>>> ; Log upload/download debug data. You generally want to enable this >>>>>> only >>>>>> ; when debugging a specific upload/download problem, as *lots* of >>>>>> data >>>>>> ; can be generated. Valid arguments are 'Yes' or 'No'. >>>>>> LogXloadDebugData=No >>>>>> >>>>>> [Alsa] >>>>>> ; ALSA Parameters >>>>>> ; (It should seldom be necessary to tweak these) >>>>>> PeriodQuantity=4 >>>>>> PeriodSize=1024 >>>>>> ChannelsPerPcm=-1 >>>>>> >>>>>> ; [SoftKeys] >>>>>> ; >>>>>> ; This section can be used to program the RDSoftKeys applet, or you >>>>>> ; can use the --map-file=<filename> switch to configure multiple soft >>>>>> ; key setups on the same host. >>>>>> ; >>>>>> ; Columns=10 >>>>>> ; >>>>>> ; Command1=hithlum.srlabs.loc:GO 3 1 1 0! >>>>>> ; Legend1=Telos 1 ON >>>>>> ; Color1=red >>>>>> ; >>>>>> ; Command2=hithlum.srlabs.loc:GO 3 2 1 0! >>>>>> ; Legend2=Telos 2 ON >>>>>> ; Color2=red >>>>>> ; >>>>>> >>>>>> [Tuning] >>>>>> ; This section defines the realtime parameters used when running >>>>>> ; audio components. Normally, these are useful only for debugging. >>>>>> UseRealtime=Yes >>>>>> RealtimePriority=9 >>>>>> >>>>>> [Format] >>>>>> ; This value is used when testing and developing new features in the >>>>>> ; audio drivers. It should never be altered on a production system. >>>>>> Channels=2 >>>>>> >>>>>> [Hacks] >>>>>> ; If you are getting no output level meter indications with an older >>>>>> ; ASI card (such as the ASI4215, ASI4113 or ASI4111), try >>>>>> uncommenting >>>>>> ; the following line: >>>>>> ; UseStreamMeters=Yes >>>>>> >>>>>> ; Completely disable maintenance checks on this host. >>>>>> ; DisableMaintChecks=Yes >>>>>> >>>>>> ; >>>>>> ; Log Generation (old method, deprecated) >>>>>> ; >>>>>> ; These sections are here strictly for backward compatibility. See >>>>>> ; the [Logs] section for a much more powerful way to configure >>>>>> ; logging. >>>>>> ; >>>>>> ; [RDAirPlay] >>>>>> ; Logfile=/home/rd/rdairplay.log >>>>>> ; >>>>>> ; [RDCatchd] >>>>>> ; Logfile=/home/rd/rdcatchd.log >>>>>> ; >>>>>> ; [Ripcd] >>>>>> ; Logfile=/home/rd/ripcd.log >>>>>> ; >>>>>> ; [Caed] >>>>>> ; Logfile=/home/rd/caed.log >>>>>> ; EnableMixerLogging=No >>>>>> >>>>>> On 7/16/16, Wayne Merricks <waynemerri...@thevoiceasia.com> wrote: >>>>>> >>>>>>> Assuming your networking is actually working and you've assigned IP >>>>>>> addresses statically (or reserved DHCP leases) all you have to do is >>>>>>> edit /etc/rd.conf to point to rdserver on every machine for the >>>>>>> MySQL >>>>>>> database. >>>>>>> >>>>>>> You then NFS share the server's /var/snd and mount it locally on >>>>>>> every >>>>>>> machine also to /var/snd. >>>>>>> >>>>>>> Then load up rdadmin and add a new host for each one of your >>>>>>> machines. >>>>>>> Then either restart the daemons or restart each client and you're >>>>>>> (in >>>>>>> theory) done. >>>>>>> >>>>>>> On 2016-07-16 00:08, Ryan Kin wrote: >>>>>>> >>>>>>>> I just installed 1 server and 3 clients on my network. >>>>>>>> On my rdserv, I used the 2 drives 0 spare option >>>>>>>> and on my other 3 computers I used the 2nd option, the networking >>>>>>>> option >>>>>>>> How can I get my 3 PC's to network with my server easily? >>>>>>>> I tried to follow the instructions on the wikipedia website and on >>>>>>>> the >>>>>>>> form here, and I get spun around, and little do I know, my >>>>>>>> computers >>>>>>>> wont network together or anything. >>>>>>>> Anyways, without getting me confused, what do I do with setting up >>>>>>>> 1 >>>>>>>> server and 3 clients >>>>>>>> The names are as follows on my network.... rdserver, rdairone, >>>>>>>> rdprodone, rdprodtwo. >>>>>>>> Thank you!!! >>>>>>>> _______________________________________________ >>>>>>>> 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 >>>>>>> >>>>>>> _______________________________________________ >>>>>> 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 >> > _______________________________________________ Rivendell-dev mailing list Rivendell-dev@lists.rivendellaudio.org http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev
