I love stupid ideas, because they're always the best! I am afraid I am, at the ripe old age of 30, becoming prematurely senile…
Of course, we gained an hour on the morning of November 11. I made no adjustments for this; therefore I presume on that evening the playlist ran short, the Chain-To came up before log had been generated and everything ground to a halt. But after the proper log was started again the next morning, shouldn't everything have gone back to normal? The output of the command is: josephmatthews@Dell-XPS:~$ rdlogmanager -g -s WRSADB -d 1 QTime::setHMS Invalid time 30:00:00.000 QTime::setHMS Invalid time 30:00:00.000 QTime::setHMS Invalid time 48:00:00.000 QTime::setHMS Invalid time 48:00:00.000 QTime::setHMS Invalid time 60:00:00.000 QTime::setHMS Invalid time 60:00:00.000 QTime::setHMS Invalid time 78:00:00.000 QTime::setHMS Invalid time 78:00:00.000 QTime::setHMS Invalid time 90:50:00.000 QTime::setHMS Invalid time 90:50:00.000 QTime::setHMS Invalid time 24:00:00.000 QTime::setHMS Invalid time 24:00:00.000 QTime::setHMS Invalid time 25:00:00.000 QTime::setHMS Invalid time 25:00:00.000 QTime::setHMS Invalid time 27:00:00.000 QTime::setHMS Invalid time 27:00:00.000 QTime::setHMS Invalid time 28:00:00.000 QTime::setHMS Invalid time 28:00:00.000 QTime::setHMS Invalid time 30:00:00.000 QTime::setHMS Invalid time 30:00:00.000 QTime::setHMS Invalid time 31:00:00.000 QTime::setHMS Invalid time 31:00:00.000 QTime::setHMS Invalid time 33:00:00.000 QTime::setHMS Invalid time 33:00:00.000 QTime::setHMS Invalid time 34:00:00.000 QTime::setHMS Invalid time 34:00:00.000 QTime::setHMS Invalid time 36:00:00.000 QTime::setHMS Invalid time 36:00:00.000 QTime::setHMS Invalid time 37:00:00.000 QTime::setHMS Invalid time 37:00:00.000 QTime::setHMS Invalid time 39:00:00.000 QTime::setHMS Invalid time 39:00:00.000 QTime::setHMS Invalid time 40:00:00.000 QTime::setHMS Invalid time 40:00:00.000 QTime::setHMS Invalid time 42:00:00.000 QTime::setHMS Invalid time 42:00:00.000 QTime::setHMS Invalid time 43:00:00.000 QTime::setHMS Invalid time 43:00:00.000 QTime::setHMS Invalid time 45:00:00.000 QTime::setHMS Invalid time 45:00:00.000 QTime::setHMS Invalid time 46:00:00.000 QTime::setHMS Invalid time 46:00:00.000 QTime::setHMS Invalid time 48:00:00.000 QTime::setHMS Invalid time 48:00:00.000 QTime::setHMS Invalid time 49:00:00.000 QTime::setHMS Invalid time 49:00:00.000 QTime::setHMS Invalid time 51:00:00.000 QTime::setHMS Invalid time 51:00:00.000 QTime::setHMS Invalid time 52:00:00.000 QTime::setHMS Invalid time 52:00:00.000 QTime::setHMS Invalid time 54:00:00.000 QTime::setHMS Invalid time 54:00:00.000 QTime::setHMS Invalid time 55:00:00.000 QTime::setHMS Invalid time 55:00:00.000 QTime::setHMS Invalid time 57:00:00.000 QTime::setHMS Invalid time 57:00:00.000 QTime::setHMS Invalid time 58:00:00.000 QTime::setHMS Invalid time 58:00:00.000 QTime::setHMS Invalid time 60:00:00.000 QTime::setHMS Invalid time 60:00:00.000 QTime::setHMS Invalid time 61:00:00.000 QTime::setHMS Invalid time 61:00:00.000 QTime::setHMS Invalid time 63:00:00.000 QTime::setHMS Invalid time 63:00:00.000 QTime::setHMS Invalid time 64:00:00.000 QTime::setHMS Invalid time 64:00:00.000 QTime::setHMS Invalid time 66:00:00.000 QTime::setHMS Invalid time 66:00:00.000 QTime::setHMS Invalid time 67:00:00.000 QTime::setHMS Invalid time 67:00:00.000 QTime::setHMS Invalid time 69:00:00.000 QTime::setHMS Invalid time 69:00:00.000 QTime::setHMS Invalid time 70:00:00.000 QTime::setHMS Invalid time 70:00:00.000 QTime::setHMS Invalid time 72:00:00.000 QTime::setHMS Invalid time 72:00:00.000 QTime::setHMS Invalid time 73:00:00.000 QTime::setHMS Invalid time 73:00:00.000 QTime::setHMS Invalid time 75:00:00.000 QTime::setHMS Invalid time 75:00:00.000 QTime::setHMS Invalid time 76:00:00.000 QTime::setHMS Invalid time 76:00:00.000 QTime::setHMS Invalid time 78:00:00.000 QTime::setHMS Invalid time 78:00:00.000 QTime::setHMS Invalid time 79:00:00.000 QTime::setHMS Invalid time 79:00:00.000 QTime::setHMS Invalid time 81:00:00.000 QTime::setHMS Invalid time 81:00:00.000 QTime::setHMS Invalid time 82:00:00.000 QTime::setHMS Invalid time 82:00:00.000 QTime::setHMS Invalid time 83:00:00.000 That final line is repeated several hundred times before the process exits. RDCatch log shows that proper macro cart is being executed properly at 23:30; it takes about 8.5 minutes to complete. What am I missing? Joey Matthews [email protected] On Nov 23, 2012, at 3:49 AM, "Wayne Merricks" <[email protected]> wrote: > If you get the output of the command it will tell you the time Riv is > generating the log, stupid idea though, have your clocks gone back an hour > recently? > > > -----Original Message----- > From: [email protected] on behalf of Joseph > Matthews > Sent: Fri 23/11/2012 02:07 > To: User discussion about the Rivendell Radio Automation System > Subject: [RDD] Automatic Log Generation > > Hi all! > > I'm having a bit of trouble with RDLogManager generating the wrong day's log. > RDCatch runs a macro cart each night at 23:30 to generate the next day's log: > > RN rdlogmanager -g -s WRSADB -d 1! > > What RDLogManager ends up generating is a log for the second day. For > example, today is 11/22/2012, the current log is 2012_11_22 and the chain-to > at the end of the log is for 2012_11_23. The log generated by RDLogManager is > 2012_11_24. > > I honestly have no idea what I could have changed to cause this to suddenly > start happening. Any thoughts? > > Thanks, > > Joey Matthews > [email protected] > > > > ####################### > Scanned by MailMarshal > ####################### > > ############ > > Attention: > > The information contained in this message is confidential and intended > for the addressee(s) only. If you have received this message in error > or there are any problems, please notify the originator immediately. > The unauthorised use, disclosure, copying or alteration of this message > is strictly forbidden. Christian Vision or any of its subsidiaries will > not be liable for direct, special, indirect or consequential damages > arising from alteration of the contents of this message by a third party > or as a result of any virus being passed on. Please note that we reserve > the right to monitor and read any e-mails sent or received by the > company under the Telecommunications (Lawful Business Practice) > (Interception of Communications) Regulation 2000. Christian Vision is > registered in England as a limited company 2842414 and as a charity > 1031031 > > ############ > <winmail.dat>_______________________________________________ > 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
