Hi Andy, Thanks for pointing me to that post. I'll give your script a go, would certainly save a heck of a lot of hassle.
As per my previous email I did do a database repair so will have to wait and see if it fixes the issue. Cheers, Lee -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Andy Brown Sent: Thursday, 10 October 2013 9:10 PM To: [email protected] Subject: Re: [RDD] RDAirplay quitting again Hi Lee, I feel your pain, we've had similar, but to work around it we run rivendell in a constant script so at least it starts back up where it left off. See my posting at: http://caspian.paravelsystems.com/pipermail/rivendell-dev/2013-September/019 121.html Which should point you in the right direction to run it under a script to keep it going. On 09/10/13 13:54, Lee Baker wrote: > Hi Rick I have rd running on dell pe 2650s, 3gb ram and dual 2.5ghz > cpu with redundant ups on both power supplies so power issues are not a problem. > > Although have had past problems whereby power has gone out for > extended time and ups have run out and shut everything off. But > otherwise the environment is solid. > > Running latest 2.5.1 of rd on ubuntu 12.2 > > Mysql version is 5.1.69 > > Rd db is lattest upon upgrade to 2.5.1 > > Might try a repair of the database and see if it makes a difference. > Have had past issues with a corrupt db. > > Will report back. > > once I worked at a location with poor power conditions, power > fluctuations caused damage to data integrity in the database which > caused random effects, it took us some time to figure this out and in > the end we set up a ups, reparing the database could also solve a > problem if you live on such a location > > drew Roberts schreef op 9-10-2013 14:34: > >> On Wednesday 09 October 2013 07:35:14 Rick wrote: >> >>> A system NEVER acts randomly unless the RND statement used in a >>> lookup in the database generates an eof() situation in certain situations. >>> >> If only. On standard setups, the sound card order can change on bootup. >> Close >> enough to a random event to cause trouble even if not a strictly >> random event. (I am not saying there are no fixes, just that the >> fixes, if available, need to be made in order to avoid the problem.) >> >> all the best, >> >> drew >> ______________________________**_________________ >> Rivendell-dev mailing list >> Rivendell-dev@lists.**rivendellaudio.org<[email protected] >> laudio.org> >> http://caspian.paravelsystems.**com/mailman/listinfo/**rivendell-dev< >> http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev> >> >> > ______________________________**_________________ > Rivendell-dev mailing list > Rivendell-dev@lists.**rivendellaudio.org<[email protected] > audio.org> > http://caspian.paravelsystems.**com/mailman/listinfo/**rivendell-dev<h > ttp://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev> > > > > _______________________________________________ > Rivendell-dev mailing list > [email protected] > http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev > -- Andy e: andy @ thebmwz3.co.uk w: http://www.thebmwz3.co.uk g: https://github.com/andyb2000/ _______________________________________________ Rivendell-dev mailing list [email protected] http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev _______________________________________________ Rivendell-dev mailing list [email protected] http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev
