(Hey Terry, I'm on here too) It turned out to be relatively simple. We have a large, redundant link station handling audio. Most of the time, only 1 machine will be playing - the network feed, switched to all the STL's. But all the machines have a custom script that checks and, if needed, restores the link station connection.
The real trick was: backup the "test" system db. Restore to the networked MySQL server. Settings in rd.conf to point to the MySQL server. Restart and viola: everything works. I was anticipating problems with the db going from one machine to different host names, so I didn't expect the backup/restore to "just work". Glad it did! Now I just have to code the script that merges switching commands from the various hosts, handles the Kramer switching, plus write an app to monitor and switch to the various host send and return audio feeds. Wild ride indeed. Sent from my iPad On Apr 9, 2012, at 11:39 AM, Terry LeTourneau <[email protected]> wrote: > Phil, > > Been meaning to call you but didn't want to overwhelm you with our > incompetence. ;) > > We actually approached it as you recommend (below) over the weekend, and > along with James Harrison's work on installing RD, we seem to be ready to go > LIVE with these machines in the next few weeks. > > Been a wild ride. > > -Terry > > On Mon, Apr 9, 2012 at 11:19 AM, Phil Jennings <[email protected]> > wrote: > How big is your /var/snd? I would use an internal drive on one of the > automation machines (assuming it’s big enough) for /var/snd and use NFS to > share it to the other 3. The same machine would also be your mysql server. > I would then use the Buffalo as a back up drive by setting up a nightly rsync > in cron. My $.02. <wlEmoticon-smile[1].png> > > Phil Jennings > Calvary Radio Network > 219-707-0075 > www.calvaryradionetwork.com > > From: Terry LeTourneau > Sent: Sunday, April 08, 2012 11:26 AM > To: User discussion about the Rivendell Radio Automation System > Subject: Re: [RDD] Replicating Rivendell on 3 machines > > Buffalo Drive=NAS, yes. > > We're using Ubuntu 11.04. Can this be approached the same way as you > describe below? > > -Terry > > On Sun, Apr 8, 2012 at 11:11 AM, James Harrison <[email protected]> > wrote: > Okay. The Buffalo Drive being some form of NAS, I assume? > > I'd just set up the machines using the CentOS RPMs or Tryphon packages for > Debian and have them all backed onto one central PC for hosting your /var/snd > and MySQL DB. Should be pretty trivial to achieve. Then you just set up each > service, generate logs for each and away you go. > Cheers, > James Harrison > > On 08/04/2012 15:59, Terry LeTourneau wrote: >> >> All 4 machines will share a database (via a Buffalo Drive). And each >> machine will be a different FM station, playing out the same format except >> with the top of the hour legal ID's and localized advertisement, etc. >> >> -Terry >> >> On Sun, Apr 8, 2012 at 10:36 AM, James Harrison <[email protected]> >> wrote: >> To clarify, are the 4 machines all going to share a database, with each >> station set up as a specific service? If so, are they going to be in the >> same physical location (or at least same physical network)? >> Cheers, >> James Harrison >> >> On 08/04/2012 15:07, Terry LeTourneau wrote: >>> Hey everyone, >>> >>> Just a quick question to see if anyone knew of the quickest (and yet >>> painless) way to replicate Rivendell on 4 other machines??? We have >>> Rivendell on 1 machine and want to have 4 others built and used for 4 >>> separate stations. Eventually, the 1 machine that is built will function >>> as our server and the others will be LIVE play outs, etc. I have seen the >>> guides on line but thought I'd ask before I start to compile them via the >>> guides. >>> >>> Thoughts? >>> >>> -Terry >>> RenewFM >>> >>> >>> _______________________________________________ >>> Rivendell-dev mailing list >>> [email protected] >>> http://lists.rivendellaudio.org/mailman/listinfo/rivendell-dev >> >> _______________________________________________ >> Rivendell-dev mailing list >> [email protected] >> http://lists.rivendellaudio.org/mailman/listinfo/rivendell-dev >> >> >> >> >> _______________________________________________ >> Rivendell-dev mailing list >> [email protected] >> http://lists.rivendellaudio.org/mailman/listinfo/rivendell-dev > > _______________________________________________ > Rivendell-dev mailing list > [email protected] > http://lists.rivendellaudio.org/mailman/listinfo/rivendell-dev > > > _______________________________________________ > Rivendell-dev mailing list > [email protected] > http://lists.rivendellaudio.org/mailman/listinfo/rivendell-dev > > _______________________________________________ > Rivendell-dev mailing list > [email protected] > http://lists.rivendellaudio.org/mailman/listinfo/rivendell-dev > > > _______________________________________________ > Rivendell-dev mailing list > [email protected] > http://lists.rivendellaudio.org/mailman/listinfo/rivendell-dev
_______________________________________________ Rivendell-dev mailing list [email protected] http://lists.rivendellaudio.org/mailman/listinfo/rivendell-dev
