[mythtvnz] 0.21 upgrade has me losing recordings!

[Duncan Kennington]

On 22/03/2008, Robin Gilks <g8ecj at gilks.org> wrote:
>
>  > Hi there
>  >
>  > Two days ago I upgraded from 0.20 to 0.21 on my CentOS5 backend and my
>  > FC8 and minimyth frontends (the exact version will be slightly different
>  > - but all 0.21). For the first couple of hours it all looked great, I
>  > watched something and a recording auto-kicked in as expected. Life was
>  > good.
>  >
>  > However, some time after that, the auto-recording function died. It
>  > stopped recording shows it has been set to record for ages. Because of
>  > this, several shows failed to be recorded when they should. And yet at
>  > the same time the playback feature was fine. Last night we watched a
>  > movie recorded a couple of weeks ago just fine - we just didn't notice
>  > it wasn't recording anything new.
>  >
>  > So tonight  we noticed both mythfrontend and mythweb stated we had no
>  > "Recording Schedules" set. Argh! WAF hit 0% - years of settings lost!
>  > End of the world is nigh!
>  >
>  > I checked /var/log/mythtv/mythbackend.log, and the only error I can see
>  > is:
>  >
>  > RemoteFile::openSocket(file data socket): Could not connect to server ""
>  > @ port -1
>  > RemoteFile::openSocket(file data socket): Could not connect to server ""
>  > @ port -1
>  > RingBuffer::RingBuffer(): Failed to open remote file ()
>  >
>  > The weird thing is, I simply restarted mythbackend and all the recording
>  > settings came back! They weren't lost after all - just "misplaced". I'm
>  > still seeing the above errors - but now everything looks fine - so I
>  > don't think they are related. I thought they might be related to the
>  > mysqld database - but that hasn't been restarted since last reboot - so
>  > it's not like it lost access. So the problem is that somehow mythtv
>  > loses it's references to recording schedules and stops recording new
>  > shows - and a restart allows mythtv to relearn them. However, as all
>  > this happened after I rebooted the backend (as I also upgraded the
>  > kernel and ivtv drivers when I upgraded mythtv), I guarantee this will
>  > be happening again unless I get to the bottom of this.
>  >
>  > Any ideas what's going on? The CentOS5 backend is mythtv-0.21-183.el5.
>  > Thanks
>  >
>  > Jason
>
>
> I've a feeling that the mysql version in Centos5 may be a bit too old -
>  check the main mythtv wiki pages for the dependancies - I recall chat on
>  the 'dev' list about other packages not being up to scratch on it.

I agree, it definitely sounds like Myth is losing its connection to
MySQL.  See if there are any errors for mysql in /var/log.  If you
haven't done it recently it might pay to analyze/optimize all the
tables.  And of course take a backup of the database!! :-)