[mythtv-users] Hmmmm

[Brian Maupin]

On Fri, Jul 2, 2010 at 12:18 PM, Jason Ward <jasonfward at gmail.com> wrote:
>
>
> On 2 July 2010 14:59, Jason Ward <jasonfward at gmail.com> wrote:
>>
>> 3      36327      mythbackend      4      0      2010-07-02 14:45:50
>> MythLivingroom      Delete Recording      File
>> /var/lib/mythtv/livetv/1006_20100618220723.mpg for chanid 1006 at Fri Jun 18
>> 22:07:23 2010 could not be deleted.
>> 4     36326     mythbackend     4     0     2010-07-02 14:45:42
>> MythLivingroom     Delete Recording     File
>> /var/lib/mythtv/livetv/1007_20100618210000.mpg for chanid 1007 at Fri Jun 18
>> 21:00:00 2010 could not be deleted.
>> 5     36325     mythbackend     4     0     2010-07-02 14:45:39
>> MythLivingroom     Delete Recording     File
>> /var/lib/mythtv/livetv/1007_20100618200000.mpg for chanid 1007 at Fri Jun 18
>> 20:00:00 2010 could not be deleted.
>> 6     36324     mythbackend     4     0     2010-07-02 14:45:36
>> MythLivingroom     Delete Recording     File
>> /var/lib/mythtv/livetv/1002_20100618190947.mpg for chanid 1002 at Fri Jun 18
>> 19:09:47 2010 could not be deleted.
>> 7     36323     mythbackend     4     0     2010-07-02 14:45:32
>> MythLivingroom     Delete Recording     File
>> /var/lib/mythtv/livetv/1007_20100618192202.mpg for chanid 1007 at Fri Jun 18
>> 19:22:02 2010 could not be deleted.
>>
> Anyone able to tell me how I cure the above? i.e. how I make it so that
> MythTV can delete the files again and all future files?
>
> _______________________________________________
> mythtv-users mailing list
> mythtv-users at mythtv.org
> http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
>
>

Check the output of these commands

ls -l /var/lib/mythtv/livetv/1006_20100618220723.mpg

ps aux | grep [m]ythbackend

Does the user that mythbackend is running as have the correct
permissions on the livetv/recordings folder/files?  It kind of sounds
like permission issues on a folder if you can't delete and have blank
recordings (can't write).  Maybe one of the updates changed the
startup script or the startup script settings so it is running as a
different user than it used to.

--

To check what may be the problem with your frontends you should run
the mythfrontend from a console.  'tee' the output to a text file to
make it easier to see what the problem is.

mythtfrontend | tee felog.txt

Look in that console or felog.txt and see if the backend it is trying
to connect to has the wrong ip address or if there are MySQL
permission issues or something else.  mythfrontend -v [some category]
will give you more detailed messages, mythfrontend -v help will show
your options.

If you have frontends that used to be able to connect and now can't
I'd guess it is something to do with IP addresses/DHCP.  If your
backend IP address changes then the other frontends maybe trying to
connect to that old IP address.  If this is the problem give your
backend a static ip and update that information on the frontends.
MySQL permissions can be based on host, like mythtv at 192.168.1.100,
mythtv at 192.168.1.102, etc.  So if you MySQL permissions are configured
that way and a frontend gets a new IP that doesn't have access to the
MySQL server it won't be able to connect.  Giving your frontends
static ip's probably wouldn't be a bad idea either.  You could also
just give the user mythtv from any host access to the mythconverg
table and that should allow frontends with DHCP assigned ip addresses
to be able to connect.

---

One other thing you may want to check is dmesg or smartctl to see if
your drives are having any issues, probably not if mythbackend is the
only thing affected.