That's why you shouldn't have a timed log roll over event on any system, especially if they occur at the same time each day. You should make a timed event before the chain to, and have something play for say 30 seconds after that (a promo or something) before manually moving on to a 'segue' chain-to event rather than timed. That gives the system time enough to load the next log, and no room for jumping over another log by accident.

You'd be surprised how many people I've seen schedule a timed event as a log roll over, not a good idea.

Cheers,
Gavin.


On 2011-12-28 07:14, Benjamin D. Fillmore wrote:
I had a problem with Chain-to for a while....

Basically it would hit the event before midnight, load the next day's log, and then at midnight, it would jump to the next chain-to event (effectively skipping 2 days in one night). The solution was simply to add more music events prior the the Chain-To (timed event). That forced more items into the log, and the extras were then skipped at midnight.




On 12/27/2011 1:08 PM, Nathan Steele wrote:
This is the syslog around midnight:

Dec 26 23:51:38 rdoa rdairplay: finished event: Line: 599 Cart: 102190 Cut: 1 Card: 0 Stream: 1 Port: 0
Dec 26 23:52:29 rdoa ntpd[2353]: synchronized to LOCAL(0), stratum 10
Dec 26 23:52:44 rdoa ntpd[2353]: synchronized to 70.86.250.6, stratum 2
Dec 26 23:53:32 rdoa ntpd[2353]: synchronized to LOCAL(0), stratum 10
Dec 26 23:54:35 rdoa ntpd[2353]: synchronized to 70.86.250.6, stratum 2
Dec 26 23:55:20 rdoa rdairplay: started audio cart: Line: 602 Cart: 101929 Cut: 1 Pos: 0 Card: 0 Stream: 0 Port: 0 Dec 26 23:55:23 rdoa rdairplay: finished event: Line: 601 Cart: 101988 Cut: 1 Card: 0 Stream: 2 Port: 0
Dec 26 23:55:41 rdoa ntpd[2353]: synchronized to LOCAL(0), stratum 10
Dec 26 23:56:35 rdoa ntpd[2353]: synchronized to 70.86.250.6, stratum 2
Dec 26 23:56:39 rdoa ripcd: ran local maintenance routines
Dec 26 23:56:39 rdoa ripcd: Database connection failed : lock tables VERSION write
Dec 26 23:56:39 rdoa ripcd: Database connection restored.
Dec 26 23:56:47 rdoa ntpd[2353]: synchronized to LOCAL(0), stratum 10
Dec 26 23:57:51 rdoa ntpd[2353]: synchronized to 70.86.250.6, stratum 2
Dec 26 23:58:29 rdoa rdairplay: Database connection failed : select TRANS_TYPE from 2011_12_28_LOG where COUNT=0
Dec 26 23:58:29 rdoa rdairplay: Database connection restored.
Dec 26 23:58:29 rdoa rdairplay: chained to log: Line: 603 Log: 2011_12_28

Dec 26 23:58:29 rdoa ripcd: received rml: 'LL 1 2011_12_28 -2!' from 10.100.1.114

Dec 26 23:58:32 rdoa rdairplay: finished event: Line: 602 Cart: 101929 Cut: 1 Card: 0 Stream: 0 Port: 0
Dec 26 23:58:54 rdoa ntpd[2353]: synchronized to LOCAL(0), stratum 10
Dec 26 23:59:57 rdoa ntpd[2353]: synchronized to 70.86.250.6, stratum 2
Dec 27 00:01:01 rdoa ntpd[2353]: synchronized to LOCAL(0), stratum 10
Dec 27 00:02:04 rdoa ntpd[2353]: synchronized to 70.86.250.6, stratum 2
Dec 27 00:03:10 rdoa ntpd[2353]: synchronized to LOCAL(0), stratum 10
Dec 27 00:04:16 rdoa ntpd[2353]: synchronized to 70.86.250.6, stratum 2
Dec 27 00:05:20 rdoa ntpd[2353]: synchronized to LOCAL(0), stratum 10

Looks like it tried to load tomorrows log, which does not exist.....but why?

Also, is that ntp stuff looking normal? Why is it syncing local and then remote?

Thanks,
Nathan
Nathaniel C. Steele
Assistant Chief Engineer/Technical Director
WTRM-FM / TheCrossFM

On 12/27/2011 10:36 AM, Fred Gleason wrote:
On Dec 27, 2011, at 09:39 23, Nathan Steele wrote:

Came in this morning to RDAirply sitting Idle again.
So what does syslog say happened?

Cheers!


|-------------------------------------------------------------------------|
| Frederick F. Gleason, Jr. |               Chief Developer               |
|                           |               Paravel Systems               |
|-------------------------------------------------------------------------|
|          A room without books is like a body without a soul.            |
|                                         -- Cicero                       |
|-------------------------------------------------------------------------|

_______________________________________________
Rivendell-dev mailing list
Rivendell-dev@lists.rivendellaudio.org
http://lists.rivendellaudio.org/mailman/listinfo/rivendell-dev




_______________________________________________
Rivendell-dev mailing list
Rivendell-dev@lists.rivendellaudio.org
http://lists.rivendellaudio.org/mailman/listinfo/rivendell-dev


_______________________________________________
Rivendell-dev mailing list
Rivendell-dev@lists.rivendellaudio.org
http://lists.rivendellaudio.org/mailman/listinfo/rivendell-dev
_______________________________________________
Rivendell-dev mailing list
Rivendell-dev@lists.rivendellaudio.org
http://lists.rivendellaudio.org/mailman/listinfo/rivendell-dev

Reply via email to