Mailing List Archive

On 27/10/2021 04:24, Fred Squires wrote:
> I'm not getting any new recordings today and found that I have no
> upcoming recordings listed.
> I'm also unable to schedule new recordings. If I try in MythWeb it
> simply refreshes the page as if I selected no settings.
> My current recordings still exist and play back properly. I have
> listings, recording schedules and tuners. I can play live TV. I'm
> currently running Ubuntu 20.04.3 LTS and MythTV
> v31.0+fixes.202108081239.5da2523154~ubuntu20.04.1
>
> I've restored my database to the backup from the last 2 days which did
> not help.
>
> I noticed that another person posted a similar problem today. I
> installed updates today including a "Ubuntu base" update, so maybe
> something is wrong there.
>
> I see the following error in the mythbackend log:
> Oct 26 23:05:08 mainbe mythbackend: mythbackend[9515]: E Scheduler
> mythdb.cpp:181 (DBError) DB Error (AddNewRecords):#012Query
> was:#012SELECT     c.chanid, c.sourceid,           p.starttime,      
>     p.endtime,  p.title,              p.subtitle,          
>  p.description,  c.channum,            c.callsign, c.name
> <http://c.name>,       oldrecduplicate,      p.category,
>  sched_temp_record.recpriority, sched_temp_record.dupin, recduplicate,
>          findduplicate,  sched_temp_record.type,      
>  sched_temp_record.recordid,   p.starttime - INTERVAL
> sched_temp_record.startoffset minute AS recstartts,     p.endtime +
> INTERVAL sched_temp_record.endoffset     minute AS recendts,          
>                         p.previouslyshown, sched_temp_record.recgroup,
> sched_temp_record.dupmethod,  c.commmethod,        
>  capturecard.cardid, 0,  p.seriesid,          p.programid,
> sched_temp_record.inetref,    p.category_type, p.airdate,        
> p.stars,             p.originalairdate, sched_temp_record.inactive,
> sched_temp_record.parentid, recordmatch.findid,    
> sched_temp_record.playgroup, oldrecstatus.recstatus,    
> oldrecstatus.reactivate, p.videoprop+0,         p.subtitletypes+0,
> p.audioprop+0, sched_temp_record.storagegroup,    
> capturecard.hostname, recordmatch.oldrecstatus, NULL,    
> oldrecstatus.future, capturecard.schedorder,    
> p.syndicatedepisodenumber, p.partnumber, p.parttotal,     c.mplexid,
> capturecard.displayname,             p.season, p.episode,
> p.totalepisodes, c.recpriority + capturecard.recpriority +
> (capturecard.cardid = sched_temp_record.prefinput) * 2 + (p.hdtv > 0
> OR FIND_IN_SET('HDTV', p.videoprop) > 0) * 1 AS powerpriority FROM
> recordmatch INNER JOIN sched_temp_record ON (recordmatch.recordid =
> sched_temp_record.recordid) INNER JOIN program AS p ON (
> recordmatch.chanid    = p.chanid    AND      recordmatch.starttime =
> p.starttime AND  recordmatch.manualid  = p.manualid ) INNER JOIN
> channel AS c O
>
> Does anyone have any thoughts?
> Thanks!
>
> _______________________________________________
> 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

I see mysql client changed on the 25 th you could try reverting it
libmysqlclient21:amd64 (8.0.26-0ubuntu0.20.04.3, 8.0.27-0ubuntu0.20.04.1),

On Wed, Oct 27, 2021 at 4:51 AM John <jksjdevelop@gmail.com> wrote:

> On 27/10/2021 04:24, Fred Squires wrote:
>
> I'm not getting any new recordings today and found that I have no upcoming
> recordings listed.
> I'm also unable to schedule new recordings. If I try in MythWeb it simply
> refreshes the page as if I selected no settings.
> My current recordings still exist and play back properly. I have listings,
> recording schedules and tuners. I can play live TV. I'm currently running
> Ubuntu 20.04.3 LTS and MythTV
> v31.0+fixes.202108081239.5da2523154~ubuntu20.04.1
>
> I've restored my database to the backup from the last 2 days which did not
> help.
>
> I noticed that another person posted a similar problem today. I installed
> updates today including a "Ubuntu base" update, so maybe something is wrong
> there.
>
> I see the following error in the mythbackend log:
> Oct 26 23:05:08 mainbe mythbackend: mythbackend[9515]: E Scheduler
> mythdb.cpp:181 (DBError) DB Error (AddNewRecords):#012Query was:#012SELECT
> c.chanid, c.sourceid, p.starttime,
> p.endtime, p.title, p.subtitle,
> p.description, c.channum, c.callsign, c.name,
> oldrecduplicate, p.category,
> sched_temp_record.recpriority, sched_temp_record.dupin, recduplicate,
> findduplicate, sched_temp_record.type,
> sched_temp_record.recordid, p.starttime - INTERVAL
> sched_temp_record.startoffset minute AS recstartts, p.endtime +
> INTERVAL sched_temp_record.endoffset minute AS recendts,
> p.previouslyshown,
> sched_temp_record.recgroup, sched_temp_record.dupmethod, c.commmethod,
> capturecard.cardid, 0, p.seriesid,
> p.programid, sched_temp_record.inetref, p.category_type,
> p.airdate, p.stars, p.originalairdate,
> sched_temp_record.inactive, sched_temp_record.parentid,
> recordmatch.findid, sched_temp_record.playgroup,
> oldrecstatus.recstatus, oldrecstatus.reactivate, p.videoprop+0,
> p.subtitletypes+0, p.audioprop+0, sched_temp_record.storagegroup,
> capturecard.hostname, recordmatch.oldrecstatus, NULL,
> oldrecstatus.future, capturecard.schedorder, p.syndicatedepisodenumber,
> p.partnumber, p.parttotal, c.mplexid, capturecard.displayname,
> p.season, p.episode, p.totalepisodes, c.recpriority +
> capturecard.recpriority + (capturecard.cardid =
> sched_temp_record.prefinput) * 2 + (p.hdtv > 0 OR FIND_IN_SET('HDTV',
> p.videoprop) > 0) * 1 AS powerpriority FROM recordmatch INNER JOIN
> sched_temp_record ON (recordmatch.recordid = sched_temp_record.recordid)
> INNER JOIN program AS p ON ( recordmatch.chanid = p.chanid AND
> recordmatch.starttime = p.starttime AND recordmatch.manualid =
> p.manualid ) INNER JOIN channel AS c O
>
> Does anyone have any thoughts?
> Thanks!
>
> _______________________________________________
> mythtv-users mailing listmythtv-users@mythtv.orghttp://lists.mythtv.org/mailman/listinfo/mythtv-usershttp://wiki.mythtv.org/Mailing_List_etiquette
> MythTV Forums: https://forum.mythtv.org
>
> I see mysql client changed on the 25 th you could try reverting it
> libmysqlclient21:amd64 (8.0.26-0ubuntu0.20.04.3, 8.0.27-0ubuntu0.20.04.1),
> _______________________________________________
> 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


Thanks!
I downgraded that from 8.0.27 to 8.019, but that didn't help. I'm going to
try downgrading the rest of the packages that were upgraded yesterday
before trying anything more drastic.
Here are the packages that upgraded yesterday:

Start-Date: 2021-10-26 06:04:32
Commandline: /usr/bin/unattended-upgrade
Upgrade: libmysqlclient21:amd64 (8.0.26-0ubuntu0.20.04.3,
8.0.27-0ubuntu0.20.04.
1)
End-Date: 2021-10-26 06:04:34

Start-Date: 2021-10-26 06:04:39
Commandline: /usr/bin/unattended-upgrade
Upgrade: binutils:amd64 (2.34-6ubuntu1.1, 2.34-6ubuntu1.3),
binutils-x86-64-linu
x-gnu:amd64 (2.34-6ubuntu1.1, 2.34-6ubuntu1.3), binutils-common:amd64
(2.34-6ubu
ntu1.1, 2.34-6ubuntu1.3), libbinutils:amd64 (2.34-6ubuntu1.1,
2.34-6ubuntu1.3),
libctf0:amd64 (2.34-6ubuntu1.1, 2.34-6ubuntu1.3)
End-Date: 2021-10-26 06:04:42

Start-Date: 2021-10-26 06:04:47
Commandline: /usr/bin/unattended-upgrade
Upgrade: mysql-client-8.0:amd64 (8.0.26-0ubuntu0.20.04.3,
8.0.27-0ubuntu0.20.04.
1), mysql-server-8.0:amd64 (8.0.26-0ubuntu0.20.04.3,
8.0.27-0ubuntu0.20.04.1), m
ysql-server-core-8.0:amd64 (8.0.26-0ubuntu0.20.04.3,
8.0.27-0ubuntu0.20.04.1)
End-Date: 2021-10-26 06:05:34

Start-Date: 2021-10-26 06:05:39
Commandline: /usr/bin/unattended-upgrade
Upgrade: python3-apport:amd64 (2.20.11-0ubuntu27.20, 2.20.11-0ubuntu27.21)
End-Date: 2021-10-26 06:05:41

Start-Date: 2021-10-26 06:05:46
Commandline: /usr/bin/unattended-upgrade
Upgrade: python3-problem-report:amd64 (2.20.11-0ubuntu27.20,
2.20.11-0ubuntu27.2
1)
End-Date: 2021-10-26 06:05:47

Start-Date: 2021-10-26 06:05:51
Commandline: /usr/bin/unattended-upgrade
Upgrade: apport-gtk:amd64 (2.20.11-0ubuntu27.20, 2.20.11-0ubuntu27.21)
End-Date: 2021-10-26 06:05:52

Start-Date: 2021-10-26 06:05:57
Commandline: /usr/bin/unattended-upgrade
Upgrade: mysql-client-core-8.0:amd64 (8.0.26-0ubuntu0.20.04.3,
8.0.27-0ubuntu0.2
0.04.1)
End-Date: 2021-10-26 06:06:02

Start-Date: 2021-10-26 06:06:07
Commandline: /usr/bin/unattended-upgrade
Upgrade: apport:amd64 (2.20.11-0ubuntu27.20, 2.20.11-0ubuntu27.21)
End-Date: 2021-10-26 06:06:13

Start-Date: 2021-10-26 06:06:18
Commandline: /usr/bin/unattended-upgrade
Upgrade: libctf-nobfd0:amd64 (2.34-6ubuntu1.1, 2.34-6ubuntu1.3)
End-Date: 2021-10-26 06:06:18

Start-Date: 2021-10-26 21:53:20
Commandline: aptdaemon role='role-commit-packages' sender=':1.16976'
Upgrade: netplan.io:amd64 (0.103-0ubuntu5~20.04.1, 0.103-0ubuntu5~20.04.2),
brave-browser:amd64 (1.30.89, 1.31.87), alsa-ucm-conf:amd64
(1.2.2-1ubuntu0.10, 1.2.2-1ubuntu0.11), libpulsedsp:amd64
(1:13.99.1-1ubuntu3.11, 1:13.99.1-1ubuntu3.12), pulseaudio:amd64
(1:13.99.1-1ubuntu3.11, 1:13.99.1-1ubuntu3.12), libpulse0:amd64
(1:13.99.1-1ubuntu3.11, 1:13.99.1-1ubuntu3.12),
libpulse-mainloop-glib0:amd64 (1:13.99.1-1ubuntu3.11,
1:13.99.1-1ubuntu3.12), libnetplan0:amd64 (0.103-0ubuntu5~20.04.1,
0.103-0ubuntu5~20.04.2), pulseaudio-module-bluetooth:amd64
(1:13.99.1-1ubuntu3.11, 1:13.99.1-1ubuntu3.12), pulseaudio-utils:amd64
(1:13.99.1-1ubuntu3.11, 1:13.99.1-1ubuntu3.12)
End-Date: 2021-10-26 21:53:42

On 10/26/21 10:24 PM, Fred Squires wrote:
> I'm not getting any new recordings today and found that I have no upcoming recordings listed.
> I'm also unable to schedule new recordings. If I try in MythWeb it simply refreshes the page as if I selected no settings.
> My current recordings still exist and play back properly. I have listings, recording schedules and tuners. I can play live TV. I'm currently
> running Ubuntu 20.04.3 LTS and MythTV v31.0+fixes.202108081239.5da2523154~ubuntu20.04.1
>
> I've restored my database to the backup from the last 2 days which did not help.
>
> I noticed that another person posted a similar problem today. I installed updates today including a "Ubuntu base" update, so maybe something is
> wrong there.
>
> I see the following error in the mythbackend log:
> Oct 26 23:05:08 mainbe mythbackend: mythbackend[9515]: E Scheduler mythdb.cpp:181 (DBError) DB Error (AddNewRecords):#012Query was:#012SELECT  
>   c.chanid,         c.sourceid,           p.starttime,           p.endtime,        p.title,              p.subtitle,            p.description,  
>  c.channum,            c.callsign,            c.name <http://c.name>,           oldrecduplicate,      p.category,          
>  sched_temp_record.recpriority, sched_temp_record.dupin,   recduplicate,          findduplicate,    sched_temp_record.type,      
>  sched_temp_record.recordid,     p.starttime - INTERVAL sched_temp_record.startoffset     minute AS recstartts,     p.endtime + INTERVAL
> sched_temp_record.endoffset     minute AS recendts,                                             p.previouslyshown,    
> sched_temp_record.recgroup, sched_temp_record.dupmethod,  c.commmethod,          capturecard.cardid, 0,                  p.seriesid,        
>  p.programid,       sched_temp_record.inetref,    p.category_type,       p.airdate,         p.stars,             p.originalairdate,    
> sched_temp_record.inactive, sched_temp_record.parentid,   recordmatch.findid,     sched_temp_record.playgroup, oldrecstatus.recstatus,    
> oldrecstatus.reactivate, p.videoprop+0,         p.subtitletypes+0, p.audioprop+0,   sched_temp_record.storagegroup,     capturecard.hostname,
> recordmatch.oldrecstatus, NULL,     oldrecstatus.future, capturecard.schedorder,     p.syndicatedepisodenumber, p.partnumber, p.parttotal,    
> c.mplexid, capturecard.displayname,             p.season, p.episode, p.totalepisodes, c.recpriority + capturecard.recpriority +
> (capturecard.cardid = sched_temp_record.prefinput) * 2 + (p.hdtv > 0 OR FIND_IN_SET('HDTV', p.videoprop) > 0) * 1 AS powerpriority FROM
> recordmatch INNER JOIN sched_temp_record ON (recordmatch.recordid = sched_temp_record.recordid) INNER JOIN program AS p ON ( recordmatch.chanid
>    = p.chanid    AND      recordmatch.starttime = p.starttime AND      recordmatch.manualid  = p.manualid ) INNER JOIN channel AS c O
>
> Does anyone have any thoughts?

Please see: https://forum.mythtv.org/viewtopic.php?f=36&t=4628

--
Bill
_______________________________________________
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

On Thu, Oct 28, 2021 at 1:34 AM Bill Meek <keemllib@gmail.com> wrote:

>
> Please see: https://forum.mythtv.org/viewtopic.php?f=36&t=4628
>


So, once again, Oracle made a "breaking change" in
a patch level release (which is NOT supposed to happen
in a well run organization).

I guess that is why it is necessary for Oracle to pay
Canonical to push MySQL as the default, for anyone
with a clue would have moved to MariaDB by now.
_______________________________________________
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

On 10/29/21 8:35 AM, Gary Buhrmaster wrote:
> On Thu, Oct 28, 2021 at 1:34 AM Bill Meek <keemllib@gmail.com> wrote:
>
>> Please see: https://forum.mythtv.org/viewtopic.php?f=36&t=4628
>>
>
> So, once again, Oracle made a "breaking change" in
> a patch level release (which is NOT supposed to happen
> in a well run organization).
>
> I guess that is why it is necessary for Oracle to pay
> Canonical to push MySQL as the default, for anyone
> with a clue would have moved to MariaDB by now.

So if your were building an *buntu based Mythtv combo FE/BE and wanted
MariaDB instead of the default, how would your proceed?

I assume you could install MariaDB prior to installing MythTV?

Do you know which MariaDB packages would be needed?

Jim A


_______________________________________________
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

On 29/10/2021 14:35, Jim Abernathy wrote:
>
> On 10/29/21 8:35 AM, Gary Buhrmaster wrote:
>> On Thu, Oct 28, 2021 at 1:34 AM Bill Meek <keemllib@gmail.com> wrote:
>>
>>> Please see: https://forum.mythtv.org/viewtopic.php?f=36&t=4628
>>>
>>
>> So, once again, Oracle made a "breaking change" in
>> a patch level release (which is NOT supposed to happen
>> in a well run organization).
>>
>> I guess that is why it is necessary for Oracle to pay
>> Canonical to push MySQL as the default, for anyone
>> with a clue would have moved to MariaDB by now.
>
> So if your were building an *buntu based Mythtv combo FE/BE and wanted
> MariaDB instead of the default, how would your proceed?
>
> I assume you could install MariaDB prior to installing MythTV?
>
> Do you know which MariaDB packages would be needed?
>
> Jim A
>

The mariadb-server virtual package will get you the latest MariaDB
server package which is what the Ubuntu mythbackend package depends on.


There is also mariadb-client virtual package which the frontend depends on.


Paul H.

_______________________________________________
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

On Fri, Oct 29, 2021 at 12:46 PM Paul Harrison <mythtv@mythqml.net> wrote:

>
> On 29/10/2021 14:35, Jim Abernathy wrote:
> >
> > On 10/29/21 8:35 AM, Gary Buhrmaster wrote:
> >> On Thu, Oct 28, 2021 at 1:34 AM Bill Meek <keemllib@gmail.com> wrote:
> >>
> >>> Please see: https://forum.mythtv.org/viewtopic.php?f=36&t=4628
> >>>
> >>
> >> So, once again, Oracle made a "breaking change" in
> >> a patch level release (which is NOT supposed to happen
> >> in a well run organization).
> >>
> >> I guess that is why it is necessary for Oracle to pay
> >> Canonical to push MySQL as the default, for anyone
> >> with a clue would have moved to MariaDB by now.
> >
> > So if your were building an *buntu based Mythtv combo FE/BE and wanted
> > MariaDB instead of the default, how would your proceed?
> >
> > I assume you could install MariaDB prior to installing MythTV?
> >
> > Do you know which MariaDB packages would be needed?
> >
> > Jim A
> >
>
> The mariadb-server virtual package will get you the latest MariaDB
> server package which is what the Ubuntu mythbackend package depends on.
>
>
> There is also mariadb-client virtual package which the frontend depends on.
>
>
> Paul H.
>

Thanks, I did a fresh install of Linux Mint 20 on a system to test Secure
Boot and while I was at it I installed mariadb-server and mariadb-client.
Then I installed v32 mythtv via the ppa and it's working fine. Not sure
how to tell if I'm using mariadb. Maybe I don't care because it's working.

Jim A

On 10/29/21 4:12 PM, James Abernathy wrote:
> Not sure how to tell if I'm using mariadb. Maybe I don't care because it's working.

mysql --version should help.

--
Bill
_______________________________________________
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

On Fri, Oct 29, 2021 at 5:39 PM Bill Meek <keemllib@gmail.com> wrote:

> On 10/29/21 4:12 PM, James Abernathy wrote:
> > Not sure how to tell if I'm using mariadb. Maybe I don't care because
> it's working.
>
> mysql --version should help.
>
> --
> Bill
>

mysql Ver 15.1 Distrib 10.3.31-MariaDB, for debian-linux-gnu (x86_64)
using readline 5.2

Yes, it's working.

Thanks, Jim A