Recording rules not honored, 0-byte file created

[drewvs@…]

I have reviewed all open tickets/reports/fixed in master and have not found something similar.

When scheduling a recording through mythweb the recording shows in the upcoming recordings suggesting that the time/day/channel is valid. When the recording starts, it shows in the recorded section with a 0 byte file-size. When the time-slot is done, the file is still a 0-byte blank file.

This also happens when using the on-screen EPG to schedule a time in the future with the record button.

I am able to successfully record a show that is currently playing in a current time-slot--this feature works as expected.

Directory permissions are the same as the user that the backend runs on: mythtv. As stated above, a recording can succeed if the time slot is current.

When a recording fails, I see two entries for the recorded file in mythweb.

Here is an example of a recording that fails:

Apr  6 18:29:00 prime  mythbackend[9548]: I Scheduler scheduler.cpp:1268 (TryAnotherShowing) Moved "Family Guy" on chanid: 1234 from card: 1 to 3 at Sun Apr 6 19:30:00 2014 to avoid LiveTV conflict
Apr  6 19:29:00 prime  mythbackend[9548]: I Scheduler scheduler.cpp:1268 (TryAnotherShowing) Moved "Family Guy" on chanid: 1234 from card: 1 to 3 at Sun Apr 6 19:30:00 2014 to avoid LiveTV conflict
Apr  6 19:30:00 prime  mythbackend[9548]: I CoreContext scheduler.cpp:705 (UpdateRecStatus) Updating status for "Family Guy":"Herpe, the Love Sore" on cardid 3 (Will Record => Recorder Failed)
Apr  6 19:30:00 prime  mythbackend[9548]: I Scheduler scheduler.cpp:2649 (HandleRecordingStatusChange) Tuning recording: "Family Guy":"Herpe, the Love Sore": channel 1234 on cardid 3, sourceid 1

Screenshot is attached.

I have completely wiped the database, re-setup, and ran mythfilldatabase. This behavior has either recently started after an upgrade from .27 base to .27 fixes or from .26 fixes. I am unsure because of a quick-succession upgrade.

[gigem]

0-byte recordings are usually the result of either a temporary recorder failure (happens occasionally) or bad tuning information (always happens). Please ask for help on the mythtv-users mailing list to diagnose whether you have a configuration error or have found a real bug that no one else has seen yet.