I have been trying to track down why the playback is stopping. When I saw the 24 hour bug I applied the update but then an hour later playback stopped between playlists. The next item was available and I could play it in the library. The Now Playing interface showed the item playing and strangely the on air light was still lit.
See attached logs. The problem happened after 22:00:34 when the next event was scheduled.
After restarting airtime-playout, it resumes playing according to the clock.
As soon as this wanring message occurs Liquidsoap moves on to the next file which leads me to believe that the files had a size of 0 bytes. Can you go look into /var/tmp/airtime/pypo/cache/scheduler/2012-03-10-03-00-34 and see if this is the case? (Hurry before the cache gets cleared, it happens for anything older than 24 hours)
I just saw this now so I hope it's still relevant. I did see those messages in the log and the broken pipe ones. I wondered what that was about. I did check the files before and after the glitch in the schedule and they were present in the library but not sure about the cache.
I have spot checked today and the stream is still playing including a repeated playlist with the files that failed last night. I wonder if it just hadn't applied the 2.0.2 update until after I restarted airtime-playout?
Ok every file shows that it has only 357 bytes. If you open them as text files you will probably see some Apache server errors.
Was your apache server down or misconfigured before?
You can recreate this cache by deleting everything in /var/tmp/airtime/pypo/cache/scheduler and restarting pypo (sudo service airtime-playout restart).
Alternatively, you can also try deleting everything in /var/tmp/airtime/pypo/cache/scheduler and then create a temporary show which always causes pypo to recheck its cache (you can delete this show after)
It never crossed my mind those files had human readable data in them.
Apache wasn't touched to my knowledge but since the restart of airtime-playout it hasn't hasn't stopped. So perhaps something "crossed-over" in the upgrade or the bug had already tripped when I upgraded. I really can't say at this point.
In 2.1 we've made it so that files are copied instead of downloaded through a browser if Pypo is on the same host as the media library. File integrity checks are also done so that this problem should never occur again.