I just ran that. It found a bunch of orphaned tables and fixed some incorrect audio lengths.
One interesting thing. There's a table that rddbcheck can't seem to get rid of. I did track one issue down to user error. I'll have to go through the system an check up on other things. I've also updated all systems to 2.17.0. Thanks for the rddbcheck tip! James Greenlee WZXI 1280 AM 95.5 FM From: "Stan Fotinos" <[email protected]> To: "Rivendell-Dev" <[email protected]> Sent: Sunday, October 15, 2017 1:43:02 PM Subject: Re: [RDD] Cart/Cut audio management (Or...Rivendell has lost its %&$* mind) Hi James Have you tried running rddbcheck to test the database? Thanks Stan On 15/10/2017 9:18 pm, James Greenlee wrote: For the past week our Rivendell system has gone kind of crazy. Our biggest problem stems from a "weather" cart. First off, we built the Rivendell system per the new build process, and it is currently running 2.16.0. We have a server system with a couple of workstations. We refresh the Weather cart daily, importing updated weather into the cart as a new cut, setting the date that the cut is valid for, and most often deleting an older cut. On Monday, we'll import a cut for Tuesday, set it to expire at the end of Tuesday, and delete the Sunday cut from the cart. This seems pretty logical and has been working for us. Last week the Rivendell system started doing weird things with the Weather cart. It stopped playing the newly added cut, instead playing the previous days cut. Then it stopped playing weather altogether. The "event" in the clock is there, the cart is listed in the Log, but nothing ever runs, even though the play counter of the cut increments. Today it decided to play a weather cut that had been deleted a week ago. My only guess with that is when you delete audio from a cut, it doesn't get removed from the database (which is somewhat counter-intuitive)? On other cart/cut madness... We have an obligation to run spots for a content provider. Every week we load the new spots for the upcoming week as cuts in this clients cart. We update the valid Air Date/Time information for the cuts (setting older cuts to expire, newer cuts to be valid in the future) and move on with other tasks. Yesterday (10/14), we updated the cart/cuts around 3p ET. The expiration date/time for the retiring cuts was set to 10/15 at 23:59), but after we made that update, those cuts stopped playing for the rest of the day. What's going on here? My guess is we've either hit a bug, have a corrupted database, or we're working with the Rivendell system in a way that it's unhappy with. Thanks, James Greenlee WZXI 1280 AM 95.5 FM _______________________________________________ Rivendell-dev mailing list [ mailto:[email protected] | [email protected] ] [ http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev | http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev ] _______________________________________________ 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
