Re: [RDD] Setup Advice
Are you referring to the "aman" feature that is supposed to handle replication between two servers? (https://github.com/ElvishArtisan/aman/blob/master/README) Is it no longer recommended? Mark Murdock KAMB -Original Message- From: rivendell-dev-boun...@lists.rivendellaudio.org On Behalf Of Cowboy Sent: Tuesday, October 8, 2019 10:27 AM To: Rivendell-Dev Subject: Re: [RDD] Setup Advice On Tue, 8 Oct 2019 11:51:07 -0500 Tom Van Gorkom wrote: > My experience with the DB replication is that if he reboots one of > them, it will stop replicating until re-synced Thank you for that !! We had a "main" server fail a month or two ago, and then discovered that "replication" was at least 14 months out of date ! Methinks you just explained how that happened. -- Cowboy ___ 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
Re: [RDD] Setup Advice
On Tue, 8 Oct 2019 11:51:07 -0500 Tom Van Gorkom wrote: > My experience with the DB replication is > that if he reboots one of them, it will stop replicating until re-synced Thank you for that !! We had a "main" server fail a month or two ago, and then discovered that "replication" was at least 14 months out of date ! Methinks you just explained how that happened. -- Cowboy ___ Rivendell-dev mailing list Rivendell-dev@lists.rivendellaudio.org http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev
Re: [RDD] Setup Advice
I wrote two custom scripts, rsa.pl and rsl.pl, to synchronize audio cuts and daily logs from one RD stand-alone system to another. They do not synchronize the rest of the database, but they do insure that a log produced on one system will run on the other. It is possible to use these scripts bi-directionally, i.e. changes to A propagate to B and changes to B propagate to A; however, cart and log deletions do not propagate. Additions and changes will propagate, but deletions cannot, because if they did, it would be impossible to tell the difference between a deletion from one system and an addition to the other. This is a feature that I wish were included in Rivendell itself. Just the other day it saved one of my stations when the sound card in the RD system in the on-air studio went west. We switched to the backup RD system at the transmitter site, which is on the air right now with identical content pending the arrival of the replacement sound card. I can send you copies of these scripts if you think they will be useful. They will not work on RD 3.x, which I am told has a completely different database structure. Rob -- Сквозь грозы сияло нам солнце свободы И Linus великий нам путь озарил; Нас вырастил Stallman на верность народу, На труд и на подвиги нас вдохновил. On Tue, 8 Oct 2019, Tom Van Gorkom wrote: I'm preparing two CentOS 7 Riv 2.19 machines for an LPFM. The owner would like a main airplay and a production machine that syncs with the airplay. I'm looking for good options that he could easily manage since he's not a Linux person. The options I think of are to make one a server and the other a client, or make them both stand-alones that have a scripted audio sync and DB replicator between them. My experience with the DB replication is that if he reboots one of them, it will stop replicating until re-synced which is going to be beyond his ability. I have not played with replication on MariaDB. Perhaps there is a way to automate this that I don't know about. Other suggestions to make this simple and somewhat foolproof? Thanks, Tom Van Gorkom Radio Esperanza Engineering, KRIO AM/FM, KOIR FM Office: 956-380-8150 Cell: 865-803-7427 www.radioesperanza.com Director of Media Rio Grande Bible Ministries 4300 S US Hwy 281 Edinburg, TX 78539 www.riogrande.edu ___ Rivendell-dev mailing list Rivendell-dev@lists.rivendellaudio.org http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev
[RDD] Setup Advice
I'm preparing two CentOS 7 Riv 2.19 machines for an LPFM. The owner would like a main airplay and a production machine that syncs with the airplay. I'm looking for good options that he could easily manage since he's not a Linux person. The options I think of are to make one a server and the other a client, or make them both stand-alones that have a scripted audio sync and DB replicator between them. My experience with the DB replication is that if he reboots one of them, it will stop replicating until re-synced which is going to be beyond his ability. I have not played with replication on MariaDB. Perhaps there is a way to automate this that I don't know about. Other suggestions to make this simple and somewhat foolproof? Thanks, Tom Van Gorkom Radio Esperanza Engineering, KRIO AM/FM, KOIR FM Office: 956-380-8150 Cell: 865-803-7427 www.radioesperanza.com Director of Media Rio Grande Bible Ministries 4300 S US Hwy 281 Edinburg, TX 78539 www.riogrande.edu ___ Rivendell-dev mailing list Rivendell-dev@lists.rivendellaudio.org http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev