Mailing List Archive

OLD Scheduled recordings disappearing problem...
Hoping someone can clue me in on this.
Background, I recently changed the OS of my primary machine from
CentOS-7.x to Linux Mint 20.3 (based on Ubuntu 20.4 LTS)
and hence I am pulling MyhTV from different repo's.

To the point, did the move, have managed to keep old recordings and
Database etc. All looked good. It was supposed
to record last night...it didn't..I looked and the schedules were there
but all the upcoming recordings were gone. I found
the suspect lines "Scheduler mythdbcon.cpp:874 (prepare) Driver error
was [2/4031]:#012QMYSQL3: Unable to prepare statement#012Database error
was:#012The client was disconnected by the server because of
inactivity. See wait_timeout and interactive_timeout for configuring
this behavior." in the logs...This appears to be an OLD problem that
was solved in June of 2021...See Forum link:
https://forum.mythtv.org/viewtopic.php?f=36&t=4453&start=60


I am running : "31.0+fixes.20200323.9579662cdc-0ubuntu1"

Did the Ubuntu repo's never pick up the fix, or has this OLD issue come
back ?


Jim
Re: OLD Scheduled recordings disappearing problem... [ In reply to ]
On Wed, 19 Jan 2022 08:49:30 -0500, you wrote:

>Hoping someone can clue me in on this.
>Background, I recently changed the OS of my primary machine from
>CentOS-7.x to Linux Mint 20.3 (based on Ubuntu 20.4 LTS)
>and hence I am pulling MyhTV from different repo's.
>
>To the point, did the move, have managed to keep old recordings and
>Database etc. All looked good. It was supposed
>to record last night...it didn't..I looked and the schedules were there
>but all the upcoming recordings were gone. I found
>the suspect lines "Scheduler mythdbcon.cpp:874 (prepare) Driver error
>was [2/4031]:#012QMYSQL3: Unable to prepare statement#012Database error
>was:#012The client was disconnected by the server because of
>inactivity. See wait_timeout and interactive_timeout for configuring
>this behavior." in the logs...This appears to be an OLD problem that
>was solved in June of 2021...See Forum link:
>https://forum.mythtv.org/viewtopic.php?f=36&t=4453&start=60
>
>
>I am running : "31.0+fixes.20200323.9579662cdc-0ubuntu1"
>
>Did the Ubuntu repo's never pick up the fix, or has this OLD issue come
>back ?
>
>
>Jim

You are using an old version of v31+fixes there - "20200323". The
current version is v31.0+fixes.202201182122.23738a7074~ubuntu20.04.1
(2022 as opposed to 2020). Have you installed the Mythbuntu
repository that the "+fixes" versions come from? Your version is old
enough for it to be the one that comes from the main Ubuntu
repositories. They seem to pick up the current "+fixes" version
whenever they do a point release, so the have the "+fixes" bit in the
version name, but do not actually get updated again until the next
point release.
_______________________________________________
mythtv-users mailing list
mythtv-users@mythtv.org
http://lists.mythtv.org/mailman/listinfo/mythtv-users
http://wiki.mythtv.org/Mailing_List_etiquette
MythTV Forums: https://forum.mythtv.org
Re: OLD Scheduled recordings disappearing problem... [ In reply to ]
On Thu, 2022-01-20 at 03:44 +1300, Stephen Worthington wrote:
> On Wed, 19 Jan 2022 08:49:30 -0500, you wrote:
>
> > Hoping someone can clue me in on this.
> > Background, I recently changed the OS of my primary machine from
> > CentOS-7.x to Linux Mint 20.3 (based on Ubuntu 20.4 LTS)
> > and hence I am pulling MyhTV from different repo's.
> >
> > To the point, did the move, have managed to keep old recordings and
> > Database etc. All looked good. It was supposed
> > to record last night...it didn't..I looked and the schedules were
> > there
> > but all the upcoming recordings were gone. I found
> > the suspect lines "Scheduler mythdbcon.cpp:874 (prepare) Driver
> > error
> > was [2/4031]:#012QMYSQL3: Unable to prepare statement#012Database
> > error
> > was:#012The client was disconnected by the server because of
> > inactivity. See wait_timeout and interactive_timeout for
> > configuring
> > this behavior." in the logs...This appears to be an OLD problem
> > that
> > was solved in June of 2021...See Forum link:
> > https://forum.mythtv.org/viewtopic.php?f=36&t=4453&start=60
> >
> >
> > I am running : "31.0+fixes.20200323.9579662cdc-0ubuntu1"
> >
> > Did the Ubuntu repo's never pick up the fix, or has this OLD issue
> > come
> > back ?
> >
> >
> > Jim
>
> You are using an old version of v31+fixes there - "20200323". The
> current version is v31.0+fixes.202201182122.23738a7074~ubuntu20.04.1
> (2022 as opposed to 2020). Have you installed the Mythbuntu
> repository that the "+fixes" versions come from? Your version is old
> enough for it to be the one that comes from the main Ubuntu
> repositories. They seem to pick up the current "+fixes" version
> whenever they do a point release, so the have the "+fixes" bit in the
> version name, but do not actually get updated again until the next
> point release.
> _______________________________________________
>
Stephen, You are correct, I was just using the Main Ubuntu repo,
switching repo's now.

Thank you

Jim

_______________________________________________
mythtv-users mailing list
mythtv-users@mythtv.org
http://lists.mythtv.org/mailman/listinfo/mythtv-users
http://wiki.mythtv.org/Mailing_List_etiquette
MythTV Forums: https://forum.mythtv.org