Opened 12 years ago

Closed 12 years ago

#3174 closed defect (worksforme)

Recording no longer exists when on an offline remote backend

Reported by: anonymous Owned by: cpinkham
Priority: minor Milestone: unknown
Component: mythtv Version: head
Severity: medium Keywords: recording slave missing expirer offline
Cc: Ticket locked: no

Description

When a recording is stored on a OFF LINE remote slave backend, and I try to select that recording to watch it will tell me that the recording no longer exists and asked if I would like to delete it.

Mythfrontend should be able to tell when the recording is just on a different host that it can not access and then for should tell us something like that.

Change History (3)

comment:1 Changed 12 years ago by cpinkham

Owner: changed from Isaac Richards to cpinkham

comment:2 Changed 12 years ago by knowledgejunkie@…

Keywords: recording slave missing expirer offline added

In the same vein, the expirer is not aware of the difference between offline and physically missing recordings. For a recent LiveTV recording on a slave backend, the master backend log contains:

2007-03-09 06:04:53.248 Expiring 1070 MBytes for 4046 @ Mon Feb 26 22:00:00 2007 => Ancient Plastic Surgery
2007-03-09 06:04:53.255 ERROR when trying to delete file: myth://192.168.1.30:6543/4046_20070226230033.mpg. File doesn't exist. Database me tadata will not be removed.
2007-03-09 06:04:53.263 mythbackend: Delete Recording: File myth://192.168.1.30:6543/4046_20070226230033.mpg does not exist for chanid 4046 at Mon Feb 26 23:00:33 2007 when trying to delete recording.

If the MBE knows the slave is not connected, and the recording is flagged as on the slave, surely the expirer should not even attempt to expire the recording?

Nick

comment:3 Changed 12 years ago by cpinkham

Resolution: worksforme
Status: newclosed

Closing as 'works for me'. Current mythfrontend doesn't ask or tell you to delete the file, it only states that the file can not be found. If someone wants to submit an enhancement request to make the frontend aware that the slave backend is down and display an appropriate message then a new ticket can be opened.

Note: See TracTickets for help on using tickets.