ProppFrexx ONAIR User-Forum

Hi Bernd,

A question about the scheduler. On my test-system I use a script which is scheduled every hour of the day to start at HH:59:52. When I start PFOA for a testsession at let's say 14.15.00, it starts the scheduled program for 13:59:52 and 'fast forwards'.

However, when it's time for the next program scheduled at 14:59:52, in around 50% of the times it's not starting that program. It just continues with the program running at that moment (the 13:59:52 one). In the other 50% of the times it is indeed starting the next scheduled program. Scripts are always the same. All overlays scheduled are fine and played at there appropriate times.

When I look in the logfiles, it tells me that it can't start the program because it's already running :

11-10-2014 14:15:21: Calendar 'F:\ProppFrexx ONAIR.calendar' read-in (last modified: 11-10-2014 14:14:00)
ProgramScheduler: Scheduler started
11-10-2014 14:15:32: Program:NKFM Non Stop (NKFM Standaard), Start:11-10-2014 13:59:52, End:11-10-2014 14:59:52, Started:True
11-10-2014 14:58:36: WARNING: Last-Program 'NKFM Non Stop-NKFM Standaard@2014-10-11T13:59:52' already started (the same program was already started).


when there's no problem (and the next scheduled program starts) it tells me :

11-10-2014 10:55:21: Program:NKFM Non Stop (NKFM Standaard), Start:11-10-2014 9:59:52, End:11-10-2014 10:59:52, Started:True
11-10-2014 10:55:22: WARNING: Last-Program 'NKFM Non Stop-NKFM Standaard@2014-10-11T09:59:52' already started (the same program was already started).
11-10-2014 10:58:39: Program:NKFM Non Stop (NKFM Standaard), Start:11-10-2014 10:59:52, End:11-10-2014 11:59:52, Started:True
11-10-2014 11:32:16: Scheduler stopped

so the warning is the same, but it schedules a next program. When it's not being scheduled I most of the times let PFOA run for another hour and it picks up (starts a next program at the next hour).

Any idea on what might go wrong or what I might do wrong ?

Kind regards,

André

That could be the case.... however it's not shown in the scheduler that way but maybe 'underwater' the calendar file is indeed corrupt
I've send you the file by email.

That looks like you might have multiple 'same' program enties scheduled overlapping in parallel.
Please send me your scheduler calendar file to take a look at.

I just took a look at your calendar file - but this is not corrupted.
And also I can not reproduce the issue here on my side.

When looking again at your log output (errorness case), I see, that the same program is indeed started twice - looking at these 2 lines:
11-10-2014 14:15:32: Program:NKFM Non Stop (NKFM Standaard), Start:11-10-2014 13:59:52, End:11-10-2014 14:59:52, Started:True
11-10-2014 14:58:36: WARNING: Last-Program 'NKFM Non Stop-NKFM Standaard@2014-10-11T13:59:52' already started (the same program was already started).

This is almost impossible, as the @2014-10-11T13:59:52 program was effectively started at 11-10-2014 14:58:36!

This seems to be only possible, if someone changes the system date/time in between.
Are you maybe doing this on your test machine to emulate a later/earlier system time for testing purposes?!

Hi Bernd,

No, it was just running in the background playing music, while we where installing other machines.
I'll delete my scheduling file, recreate te schedule and see if it happens again.

Best regards,

André

After doing some more testing, I was now able to reproduce your issue!
It indeed seems to be a bug in the scheduler lib I am using!
I already submitted a ticket to the developers - waiting for their reply!

Ok, nice to see that there was indeed going something wrong and it wasn't some strange thing happening only at my test-systeem
Hope they come up with a fix !

v3.0.14.19 fixes that issue.