({ (1w or 2w or 3w or 4w or 5w) and 10h01-12h30}, schedule_replica),
({ (1w) and 12h31-23h59}, schedule_lun),
({ (2w) and 12h31-23h59}, schedule_mar),
({ (3w) and 12h31-23h59}, schedule_mer),
({ (4w) and 12h31-23h59}, schedule_gio),
({ (5w) and 12h31-23h59}, schedule_ven),
])
])
default=mksafe(default)
Now, everything goes smoothly, with files being played correctly as of their requested distribution etc. I must add that, at 15:00 hours, Airtime stream kicks in and plays the radio program from its scheduler, and, as soon as it finishes, liquidsoap regains control and goes on with the above.
Now, the problem is that in the morning (each morning and this as well; i'm writing at 9.30 am italian time) no sound is audible.
From the logs everything (as i can see) is running normally, files are fetched from the directories to be played, pypo (from pypo.log) blocks until Airtime show starts and no error whatsoever.
Only a sudo service airtime-playout restart helps, with the audio immediately resuming and going fine. Well, until the next morning :(
What could cause something like that?
I'm running airtime 2.1.3 on Ubuntu 12.04.1 LTS over VPS.
at 15:00 hours Airtime kicked in and played everything by the book (as expected). As soon as it finished, gave back control to liquidsoap, that RESUMED WORKING correctly, thus playing the scheduled playlists and keeping being audible (as it is now)
What can cause the playout to get stuck but can be resumed by: