[mythtv-users] recording problems with recent 'fixes' build

Udo van den Heuvel udovdh at xs4all.nl
Fri Dec 19 19:40:13 UTC 2008


Udo van den Heuvel wrote:
> I noticed that mythbackend stops recording although there is program 
> data for a few days into the future and although I have three searches 
> active to record everything on three channels 24/7.

The searches look like:

channel.callsign = "NL1" AND program.starttime < DATE_ADD( NOW( ) , 
INTERVAL 8 HOUR )

(also one for NL2 and NL3)

> The logs show this:
> 
> (...)
> 2008-12-19 07:05:02.034 MainServer::HandleAnnounce Playback
> 2008-12-19 07:05:02.035 adding: localhost as a client (events: 0)
> 2008-12-19 07:05:02.037 MainServer::HandleAnnounce Monitor
> 2008-12-19 07:05:02.038 adding: localhost as a client (events: 1)
> 2008-12-19 11:05:01.653 MainServer::HandleAnnounce Playback
> 2008-12-19 11:05:01.654 adding: localhost as a client (events: 0)
> 2008-12-19 11:05:01.656 MainServer::HandleAnnounce Monitor
> 2008-12-19 11:05:01.657 adding: localhost as a client (events: 1)
> 2008-12-19 15:05:02.299 MainServer::HandleAnnounce Playback
> 2008-12-19 15:05:02.300 adding: localhost as a client (events: 0)
> 2008-12-19 15:05:02.302 MainServer::HandleAnnounce Monitor
> 2008-12-19 15:05:02.303 adding: localhost as a client (events: 1)

These are the times a reschedule via cron is initiated.
But it doesn't look like a manual reschedule:

2008-12-18 19:05:01.650 adding: localhost as a client (events: 1)
2008-12-18 19:05:01.655 Reschedule requested for id -1.

The cron reschedule did work in the past.
Did anything change here?

Udo


More information about the mythtv-users mailing list