Mailing List Archive

On Wed, Oct 11, 2023 at 7:22?AM James Abernathy <jfabernathy@gmail.com>
wrote:

> I have my mythconverg backup script running daily and after yesterday's
> update to master it didn't run this morning at 5:40 as it should. I know
> because I didn't get the email it usually sends to one of my gmail
> accounts.
>
> I checked the systemctl status and this is what I saw:
>
> Oct 11 05:40:02 kubuntu-closet systemd[1]: Starting Backup MythTV Database
> 'mythconverg'...
> Oct 11 05:40:02 kubuntu-closet mythtv-database-backup.sh[319303]: Database
> schema 1379 not supported.
> Oct 11 05:40:02 kubuntu-closet mythtv-database-backup.sh[319303]: Bindings
> support schema version 1378
> Oct 11 05:40:02 kubuntu-closet systemd[1]: mythtv-database-backup.service:
> Main process exited, code=exited, status=1/FAILURE
> Oct 11 05:40:02 kubuntu-closet systemd[1]: mythtv-database-backup.service:
> Failed with result 'exit-code'.
> Oct 11 05:40:02 kubuntu-closet systemd[1]: Failed to start Backup MythTV
> Database 'mythconverg'.
>
>
> Not sure why it's talking about schema 1379??
>
> Jim A
>

BTW, the complete script that systemd runs to backup is below:
#!/bin/sh
# /etc/cron.weekly/mythtv-database script - check and backup mythconverg
tables
# Copyright 2005/12/02 2006/10/08 Paul Andreassen
# 2010 Mario Limonciello

set -e -u

DBNAME="mythconverg"
USER="mythtv"
OPT_MYTHDB='/usr/share/doc/mythtv-backend/contrib/maintenance/
optimize_mythdb.pl'

/usr/bin/mysqlcheck -s $DBNAME

BKUP_LOG=/tmp/backup-mythconverg.log

export MYTHCONFDIR=/home/mythtv/.mythtv/

${OPT_MYTHDB} | grep -v "^Analyzed:" 2>&1 > $BKUP_LOG

sudo --preserve-env --user=$USER /usr/share/mythtv/mythconverg_backup.pl \
--rotate=5 --verbose 2>&1 >> $BKUP_LOG

if [ $? -eq 0 ]; then
MSG="kubuntu-closet $DBNAME Checked and Backed Up, RC=$?"
else
MSG="kubuntu-closet $DBNAME Back Up Failed, RC=$?"
fi

cd /data/mythtv/db_backups/
ls -l --directory --block-size=K * | tail -10 >> $BKUP_LOG

mail -s "$MSG" my.email@gmail.com < $BKUP_LOG

--------------------------

The actual error I get when it's run from the console is:

Database schema 1379 not supported.
Bindings support schema version 1378

Jim A

On 11/10/2023 12:42, James Abernathy wrote:
>
>
> On Wed, Oct 11, 2023 at 7:22?AM James Abernathy <jfabernathy@gmail.com
> <mailto:jfabernathy@gmail.com>> wrote:
>
> I have my mythconverg backup script running daily and after
> yesterday's update to master it didn't run this morning at 5:40 as
> it should.  I know because I didn't get the email it usually sends
> to one of my gmail accounts.
>
> I checked the systemctl status and this is what I saw:
>
> Oct 11 05:40:02 kubuntu-closet systemd[1]: Starting Backup MythTV
> Database 'mythconverg'...
> Oct 11 05:40:02 kubuntu-closet mythtv-database-backup.sh[319303]:
> Database schema 1379 not supported.
> Oct 11 05:40:02 kubuntu-closet mythtv-database-backup.sh[319303]:
> Bindings support schema version 1378
> Oct 11 05:40:02 kubuntu-closet systemd[1]:
> mythtv-database-backup.service: Main process exited, code=exited,
> status=1/FAILURE
> Oct 11 05:40:02 kubuntu-closet systemd[1]:
> mythtv-database-backup.service: Failed with result 'exit-code'.
> Oct 11 05:40:02 kubuntu-closet systemd[1]: Failed to start Backup
> MythTV Database 'mythconverg'.
>
>
> Not sure why it's talking about schema 1379??
>
> Jim A
>
>
> BTW, the complete script that systemd runs to backup is below:
> #!/bin/sh
> # /etc/cron.weekly/mythtv-database script - check and backup mythconverg
> tables
> # Copyright 2005/12/02 2006/10/08 Paul Andreassen
> #                      2010 Mario Limonciello
>
> set -e -u
>
> DBNAME="mythconverg"
> USER="mythtv"
> OPT_MYTHDB='/usr/share/doc/mythtv-backend/contrib/maintenance/optimize_mythdb.pl <http://optimize_mythdb.pl>'
>
> /usr/bin/mysqlcheck -s $DBNAME
>
> BKUP_LOG=/tmp/backup-mythconverg.log
>
> export MYTHCONFDIR=/home/mythtv/.mythtv/
>
> ${OPT_MYTHDB} | grep -v "^Analyzed:" 2>&1 > $BKUP_LOG
>
> sudo --preserve-env --user=$USER /usr/share/mythtv/mythconverg_backup.pl
> <http://mythconverg_backup.pl> \
>     --rotate=5 --verbose 2>&1 >> $BKUP_LOG
>
> if [ $? -eq 0 ]; then
>     MSG="kubuntu-closet $DBNAME Checked and Backed Up, RC=$?"
> else
>     MSG="kubuntu-closet $DBNAME Back Up Failed, RC=$?"
> fi
>
> cd /data/mythtv/db_backups/
> ls -l --directory --block-size=K * | tail -10 >> $BKUP_LOG
>
> mail -s "$MSG" my.email@gmail.com <mailto:my.email@gmail.com> < $BKUP_LOG
>
>  --------------------------
>
> The actual error I get when it's run from the console is:
>
> Database schema 1379 not supported.
> Bindings support schema version 1378
>
> Jim A
>
chema 1379 came with yesterday's commit for gallery images.


https://github.com/MythTV/mythtv/commit/5825b36c97ec742f908845ccd11eee40040c0529

ISTR that these updates used to get a bigger flag. Nowadays they just
happen...

_______________________________________________
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 Wed, Oct 11, 2023 at 7:51?AM John Pilkington <johnpilk222@gmail.com>
wrote:

> On 11/10/2023 12:42, James Abernathy wrote:
> >
> >
> > On Wed, Oct 11, 2023 at 7:22?AM James Abernathy <jfabernathy@gmail.com
> > <mailto:jfabernathy@gmail.com>> wrote:
> >
> > I have my mythconverg backup script running daily and after
> > yesterday's update to master it didn't run this morning at 5:40 as
> > it should. I know because I didn't get the email it usually sends
> > to one of my gmail accounts.
> >
> > I checked the systemctl status and this is what I saw:
> >
> > Oct 11 05:40:02 kubuntu-closet systemd[1]: Starting Backup MythTV
> > Database 'mythconverg'...
> > Oct 11 05:40:02 kubuntu-closet mythtv-database-backup.sh[319303]:
> > Database schema 1379 not supported.
> > Oct 11 05:40:02 kubuntu-closet mythtv-database-backup.sh[319303]:
> > Bindings support schema version 1378
> > Oct 11 05:40:02 kubuntu-closet systemd[1]:
> > mythtv-database-backup.service: Main process exited, code=exited,
> > status=1/FAILURE
> > Oct 11 05:40:02 kubuntu-closet systemd[1]:
> > mythtv-database-backup.service: Failed with result 'exit-code'.
> > Oct 11 05:40:02 kubuntu-closet systemd[1]: Failed to start Backup
> > MythTV Database 'mythconverg'.
> >
> >
> > Not sure why it's talking about schema 1379??
> >
> > Jim A
> >
> >
> > BTW, the complete script that systemd runs to backup is below:
> > #!/bin/sh
> > # /etc/cron.weekly/mythtv-database script - check and backup mythconverg
> > tables
> > # Copyright 2005/12/02 2006/10/08 Paul Andreassen
> > # 2010 Mario Limonciello
> >
> > set -e -u
> >
> > DBNAME="mythconverg"
> > USER="mythtv"
> > OPT_MYTHDB='/usr/share/doc/mythtv-backend/contrib/maintenance/
> optimize_mythdb.pl <http://optimize_mythdb.pl>'
> >
> > /usr/bin/mysqlcheck -s $DBNAME
> >
> > BKUP_LOG=/tmp/backup-mythconverg.log
> >
> > export MYTHCONFDIR=/home/mythtv/.mythtv/
> >
> > ${OPT_MYTHDB} | grep -v "^Analyzed:" 2>&1 > $BKUP_LOG
> >
> > sudo --preserve-env --user=$USER /usr/share/mythtv/mythconverg_backup.pl
> > <http://mythconverg_backup.pl> \
> > --rotate=5 --verbose 2>&1 >> $BKUP_LOG
> >
> > if [ $? -eq 0 ]; then
> > MSG="kubuntu-closet $DBNAME Checked and Backed Up, RC=$?"
> > else
> > MSG="kubuntu-closet $DBNAME Back Up Failed, RC=$?"
> > fi
> >
> > cd /data/mythtv/db_backups/
> > ls -l --directory --block-size=K * | tail -10 >> $BKUP_LOG
> >
> > mail -s "$MSG" my.email@gmail.com <mailto:my.email@gmail.com> <
> $BKUP_LOG
> >
> > --------------------------
> >
> > The actual error I get when it's run from the console is:
> >
> > Database schema 1379 not supported.
> > Bindings support schema version 1378
> >
> > Jim A
> >
> chema 1379 came with yesterday's commit for gallery images.
>
>
>
> https://github.com/MythTV/mythtv/commit/5825b36c97ec742f908845ccd11eee40040c0529
>
> ISTR that these updates used to get a bigger flag. Nowadays they just
> happen...
>
>
It seems that normal TV program recording and playback still works fine, so
I'll wait for things to just clear up.

Jim A

On Wed, 2023-10-11 at 07:58 -0400, James Abernathy wrote:
>
>
> On Wed, Oct 11, 2023 at 7:51?AM John Pilkington
> <johnpilk222@gmail.com> wrote:
> > On 11/10/2023 12:42, James Abernathy wrote:
> > >
> > >
> > > On Wed, Oct 11, 2023 at 7:22?AM James Abernathy
> > > <jfabernathy@gmail.com
> > > <mailto:jfabernathy@gmail.com>> wrote:
> > >
> > >      I have my mythconverg backup script running daily and after
> > >      yesterday's update to master it didn't run this morning at
> > > 5:40 as
> > >      it should.  I know because I didn't get the email it usually
> > > sends
> > >      to one of my gmail accounts.
> > >
> > >      I checked the systemctl status and this is what I saw:
> > >
> > >      Oct 11 05:40:02 kubuntu-closet systemd[1]: Starting Backup
> > > MythTV
> > >      Database 'mythconverg'...
> > >      Oct 11 05:40:02 kubuntu-closet mythtv-database-
> > > backup.sh[319303]:
> > >      Database schema 1379 not supported.
> > >      Oct 11 05:40:02 kubuntu-closet mythtv-database-
> > > backup.sh[319303]:
> > >      Bindings support schema version 1378
> > >      Oct 11 05:40:02 kubuntu-closet systemd[1]:
> > >      mythtv-database-backup.service: Main process exited,
> > > code=exited,
> > >      status=1/FAILURE
> > >      Oct 11 05:40:02 kubuntu-closet systemd[1]:
> > >      mythtv-database-backup.service: Failed with result 'exit-
> > > code'.
> > >      Oct 11 05:40:02 kubuntu-closet systemd[1]: Failed to start
> > > Backup
> > >      MythTV Database 'mythconverg'.
> > >
> > >
> > >      Not sure why it's talking about schema 1379??
> > >
> > >      Jim A
> > >
> > >
> > > BTW, the complete script that systemd runs to backup is below:
> > > #!/bin/sh
> > > # /etc/cron.weekly/mythtv-database script - check and backup
> > > mythconverg
> > > tables
> > > # Copyright 2005/12/02 2006/10/08 Paul Andreassen
> > > #                      2010 Mario Limonciello
> > >
> > > set -e -u
> > >
> > > DBNAME="mythconverg"
> > > USER="mythtv"
> > > OPT_MYTHDB='/usr/share/doc/mythtv-
> > > backend/contrib/maintenance/optimize_mythdb.pl
> > > <http://optimize_mythdb.pl>'
> > >
> > > /usr/bin/mysqlcheck -s $DBNAME
> > >
> > > BKUP_LOG=/tmp/backup-mythconverg.log
> > >
> > > export MYTHCONFDIR=/home/mythtv/.mythtv/
> > >
> > > ${OPT_MYTHDB} | grep -v "^Analyzed:" 2>&1 > $BKUP_LOG
> > >
> > > sudo --preserve-env --user=$USER
> > > /usr/share/mythtv/mythconverg_backup.pl
> > > <http://mythconverg_backup.pl> \
> > >       --rotate=5 --verbose 2>&1 >> $BKUP_LOG
> > >
> > > if [ $? -eq 0 ]; then
> > >       MSG="kubuntu-closet $DBNAME Checked and Backed Up, RC=$?"
> > > else
> > >       MSG="kubuntu-closet $DBNAME Back Up Failed, RC=$?"
> > > fi
> > >
> > > cd /data/mythtv/db_backups/
> > > ls -l --directory --block-size=K * | tail -10 >> $BKUP_LOG
> > >
> > > mail -s "$MSG" my.email@gmail.com <mailto:my.email@gmail.com> <
> > > $BKUP_LOG
> > >
> > >    --------------------------
> > >
> > > The actual error I get when it's run from the console is:
> > >
> > > Database schema 1379 not supported.
> > > Bindings support schema version 1378
> > >
> > > Jim A
> > >
> > chema 1379 came with yesterday's commit for gallery images.
> >
> >
> > https://github.com/MythTV/mythtv/commit/5825b36c97ec742f908845ccd11eee40040c0529
> >
> > ISTR that these updates used to get a bigger flag.  Nowadays they
> > just
> > happen...
> >
> >
>
>
> It seems that normal TV program recording and playback still works
> fine, so I'll  wait for things to just clear up. 

Did your MythTV perl bindings get updated at the same time your backend
was updated? They should both use schema 1379. What's the output of:

grep SCHEMA $(find /usr -name MythTV.pm 2>/dev/null) | head -1

I was able to run a database backup on my production system (schema
1379) without a problem.

David

_______________________________________________
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 Wed, Oct 11, 2023 at 8:42?AM David Hampton via mythtv-users <
mythtv-users@mythtv.org> wrote:

> On Wed, 2023-10-11 at 07:58 -0400, James Abernathy wrote:
> >
> >
> > On Wed, Oct 11, 2023 at 7:51?AM John Pilkington
> > <johnpilk222@gmail.com> wrote:
> > > On 11/10/2023 12:42, James Abernathy wrote:
> > > >
> > > >
> > > > On Wed, Oct 11, 2023 at 7:22?AM James Abernathy
> > > > <jfabernathy@gmail.com
> > > > <mailto:jfabernathy@gmail.com>> wrote:
> > > >
> > > > I have my mythconverg backup script running daily and after
> > > > yesterday's update to master it didn't run this morning at
> > > > 5:40 as
> > > > it should. I know because I didn't get the email it usually
> > > > sends
> > > > to one of my gmail accounts.
> > > >
> > > > I checked the systemctl status and this is what I saw:
> > > >
> > > > Oct 11 05:40:02 kubuntu-closet systemd[1]: Starting Backup
> > > > MythTV
> > > > Database 'mythconverg'...
> > > > Oct 11 05:40:02 kubuntu-closet mythtv-database-
> > > > backup.sh[319303]:
> > > > Database schema 1379 not supported.
> > > > Oct 11 05:40:02 kubuntu-closet mythtv-database-
> > > > backup.sh[319303]:
> > > > Bindings support schema version 1378
> > > > Oct 11 05:40:02 kubuntu-closet systemd[1]:
> > > > mythtv-database-backup.service: Main process exited,
> > > > code=exited,
> > > > status=1/FAILURE
> > > > Oct 11 05:40:02 kubuntu-closet systemd[1]:
> > > > mythtv-database-backup.service: Failed with result 'exit-
> > > > code'.
> > > > Oct 11 05:40:02 kubuntu-closet systemd[1]: Failed to start
> > > > Backup
> > > > MythTV Database 'mythconverg'.
> > > >
> > > >
> > > > Not sure why it's talking about schema 1379??
> > > >
> > > > Jim A
> > > >
> > > >
> > > > BTW, the complete script that systemd runs to backup is below:
> > > > #!/bin/sh
> > > > # /etc/cron.weekly/mythtv-database script - check and backup
> > > > mythconverg
> > > > tables
> > > > # Copyright 2005/12/02 2006/10/08 Paul Andreassen
> > > > # 2010 Mario Limonciello
> > > >
> > > > set -e -u
> > > >
> > > > DBNAME="mythconverg"
> > > > USER="mythtv"
> > > > OPT_MYTHDB='/usr/share/doc/mythtv-
> > > > backend/contrib/maintenance/optimize_mythdb.pl
> > > > <http://optimize_mythdb.pl>'
> > > >
> > > > /usr/bin/mysqlcheck -s $DBNAME
> > > >
> > > > BKUP_LOG=/tmp/backup-mythconverg.log
> > > >
> > > > export MYTHCONFDIR=/home/mythtv/.mythtv/
> > > >
> > > > ${OPT_MYTHDB} | grep -v "^Analyzed:" 2>&1 > $BKUP_LOG
> > > >
> > > > sudo --preserve-env --user=$USER
> > > > /usr/share/mythtv/mythconverg_backup.pl
> > > > <http://mythconverg_backup.pl> \
> > > > --rotate=5 --verbose 2>&1 >> $BKUP_LOG
> > > >
> > > > if [ $? -eq 0 ]; then
> > > > MSG="kubuntu-closet $DBNAME Checked and Backed Up, RC=$?"
> > > > else
> > > > MSG="kubuntu-closet $DBNAME Back Up Failed, RC=$?"
> > > > fi
> > > >
> > > > cd /data/mythtv/db_backups/
> > > > ls -l --directory --block-size=K * | tail -10 >> $BKUP_LOG
> > > >
> > > > mail -s "$MSG" my.email@gmail.com <mailto:my.email@gmail.com> <
> > > > $BKUP_LOG
> > > >
> > > > --------------------------
> > > >
> > > > The actual error I get when it's run from the console is:
> > > >
> > > > Database schema 1379 not supported.
> > > > Bindings support schema version 1378
> > > >
> > > > Jim A
> > > >
> > > chema 1379 came with yesterday's commit for gallery images.
> > >
> > >
> > >
> https://github.com/MythTV/mythtv/commit/5825b36c97ec742f908845ccd11eee40040c0529
> > >
> > > ISTR that these updates used to get a bigger flag. Nowadays they
> > > just
> > > happen...
> > >
> > >
> >
> >
> > It seems that normal TV program recording and playback still works
> > fine, so I'll wait for things to just clear up.
>
> Did your MythTV perl bindings get updated at the same time your backend
> was updated? They should both use schema 1379. What's the output of:
>
> grep SCHEMA $(find /usr -name MythTV.pm 2>/dev/null) | head -1
>
> I was able to run a database backup on my production system (schema
> 1379) without a problem.
>
> David
>
>
jim@kubuntu-closet:~$ grep SCHEMA $(find /usr -name MythTV.pm 2>/dev/null)
| head -1
/usr/local/share/perl/5.34.0/MythTV.pm: our $SCHEMA_VERSION = "1378";
jim@kubuntu-closet:~$


Jim A

On Wed, Oct 11, 2023 at 8:55?AM James Abernathy <jfabernathy@gmail.com>
wrote:

>
>
> On Wed, Oct 11, 2023 at 8:42?AM David Hampton via mythtv-users <
> mythtv-users@mythtv.org> wrote:
>
>> On Wed, 2023-10-11 at 07:58 -0400, James Abernathy wrote:
>> >
>> >
>> > On Wed, Oct 11, 2023 at 7:51?AM John Pilkington
>> > <johnpilk222@gmail.com> wrote:
>> > > On 11/10/2023 12:42, James Abernathy wrote:
>> > > >
>> > > >
>> > > > On Wed, Oct 11, 2023 at 7:22?AM James Abernathy
>> > > > <jfabernathy@gmail.com
>> > > > <mailto:jfabernathy@gmail.com>> wrote:
>> > > >
>> > > > I have my mythconverg backup script running daily and after
>> > > > yesterday's update to master it didn't run this morning at
>> > > > 5:40 as
>> > > > it should. I know because I didn't get the email it usually
>> > > > sends
>> > > > to one of my gmail accounts.
>> > > >
>> > > > I checked the systemctl status and this is what I saw:
>> > > >
>> > > > Oct 11 05:40:02 kubuntu-closet systemd[1]: Starting Backup
>> > > > MythTV
>> > > > Database 'mythconverg'...
>> > > > Oct 11 05:40:02 kubuntu-closet mythtv-database-
>> > > > backup.sh[319303]:
>> > > > Database schema 1379 not supported.
>> > > > Oct 11 05:40:02 kubuntu-closet mythtv-database-
>> > > > backup.sh[319303]:
>> > > > Bindings support schema version 1378
>> > > > Oct 11 05:40:02 kubuntu-closet systemd[1]:
>> > > > mythtv-database-backup.service: Main process exited,
>> > > > code=exited,
>> > > > status=1/FAILURE
>> > > > Oct 11 05:40:02 kubuntu-closet systemd[1]:
>> > > > mythtv-database-backup.service: Failed with result 'exit-
>> > > > code'.
>> > > > Oct 11 05:40:02 kubuntu-closet systemd[1]: Failed to start
>> > > > Backup
>> > > > MythTV Database 'mythconverg'.
>> > > >
>> > > >
>> > > > Not sure why it's talking about schema 1379??
>> > > >
>> > > > Jim A
>> > > >
>> > > >
>> > > > BTW, the complete script that systemd runs to backup is below:
>> > > > #!/bin/sh
>> > > > # /etc/cron.weekly/mythtv-database script - check and backup
>> > > > mythconverg
>> > > > tables
>> > > > # Copyright 2005/12/02 2006/10/08 Paul Andreassen
>> > > > # 2010 Mario Limonciello
>> > > >
>> > > > set -e -u
>> > > >
>> > > > DBNAME="mythconverg"
>> > > > USER="mythtv"
>> > > > OPT_MYTHDB='/usr/share/doc/mythtv-
>> > > > backend/contrib/maintenance/optimize_mythdb.pl
>> > > > <http://optimize_mythdb.pl>'
>> > > >
>> > > > /usr/bin/mysqlcheck -s $DBNAME
>> > > >
>> > > > BKUP_LOG=/tmp/backup-mythconverg.log
>> > > >
>> > > > export MYTHCONFDIR=/home/mythtv/.mythtv/
>> > > >
>> > > > ${OPT_MYTHDB} | grep -v "^Analyzed:" 2>&1 > $BKUP_LOG
>> > > >
>> > > > sudo --preserve-env --user=$USER
>> > > > /usr/share/mythtv/mythconverg_backup.pl
>> > > > <http://mythconverg_backup.pl> \
>> > > > --rotate=5 --verbose 2>&1 >> $BKUP_LOG
>> > > >
>> > > > if [ $? -eq 0 ]; then
>> > > > MSG="kubuntu-closet $DBNAME Checked and Backed Up, RC=$?"
>> > > > else
>> > > > MSG="kubuntu-closet $DBNAME Back Up Failed, RC=$?"
>> > > > fi
>> > > >
>> > > > cd /data/mythtv/db_backups/
>> > > > ls -l --directory --block-size=K * | tail -10 >> $BKUP_LOG
>> > > >
>> > > > mail -s "$MSG" my.email@gmail.com <mailto:my.email@gmail.com> <
>> > > > $BKUP_LOG
>> > > >
>> > > > --------------------------
>> > > >
>> > > > The actual error I get when it's run from the console is:
>> > > >
>> > > > Database schema 1379 not supported.
>> > > > Bindings support schema version 1378
>> > > >
>> > > > Jim A
>> > > >
>> > > chema 1379 came with yesterday's commit for gallery images.
>> > >
>> > >
>> > >
>> https://github.com/MythTV/mythtv/commit/5825b36c97ec742f908845ccd11eee40040c0529
>> > >
>> > > ISTR that these updates used to get a bigger flag. Nowadays they
>> > > just
>> > > happen...
>> > >
>> > >
>> >
>> >
>> > It seems that normal TV program recording and playback still works
>> > fine, so I'll wait for things to just clear up.
>>
>> Did your MythTV perl bindings get updated at the same time your backend
>> was updated? They should both use schema 1379. What's the output of:
>>
>> grep SCHEMA $(find /usr -name MythTV.pm 2>/dev/null) | head -1
>>
>> I was able to run a database backup on my production system (schema
>> 1379) without a problem.
>>
>> David
>>
>>
> jim@kubuntu-closet:~$ grep SCHEMA $(find /usr -name MythTV.pm
> 2>/dev/null) | head -1
> /usr/local/share/perl/5.34.0/MythTV.pm: our $SCHEMA_VERSION = "1378";
> jim@kubuntu-closet:~$
>
>
> Jim A
>
>
FYI, I tried this on a Debian 12 build and it showed
jim@debian-mythtv:~$ grep SCHEMA $(find /usr -name MythTV.pm
2>/dev/null) | head -1
/usr/share/perl5/MythTV.pm: our $SCHEMA_VERSION = "1379";

The previous run was on a Ubuntu 22.04 system using the ppa

Jim A

On Wed, Oct 11, 2023 at 8:58?AM James Abernathy <jfabernathy@gmail.com>
wrote:

>
>
> On Wed, Oct 11, 2023 at 8:55?AM James Abernathy <jfabernathy@gmail.com>
> wrote:
>
>>
>>
>> On Wed, Oct 11, 2023 at 8:42?AM David Hampton via mythtv-users <
>> mythtv-users@mythtv.org> wrote:
>>
>>> On Wed, 2023-10-11 at 07:58 -0400, James Abernathy wrote:
>>> >
>>> >
>>> > On Wed, Oct 11, 2023 at 7:51?AM John Pilkington
>>> > <johnpilk222@gmail.com> wrote:
>>> > > On 11/10/2023 12:42, James Abernathy wrote:
>>> > > >
>>> > > >
>>> > > > On Wed, Oct 11, 2023 at 7:22?AM James Abernathy
>>> > > > <jfabernathy@gmail.com
>>> > > > <mailto:jfabernathy@gmail.com>> wrote:
>>> > > >
>>> > > > I have my mythconverg backup script running daily and after
>>> > > > yesterday's update to master it didn't run this morning at
>>> > > > 5:40 as
>>> > > > it should. I know because I didn't get the email it usually
>>> > > > sends
>>> > > > to one of my gmail accounts.
>>> > > >
>>> > > > I checked the systemctl status and this is what I saw:
>>> > > >
>>> > > > Oct 11 05:40:02 kubuntu-closet systemd[1]: Starting Backup
>>> > > > MythTV
>>> > > > Database 'mythconverg'...
>>> > > > Oct 11 05:40:02 kubuntu-closet mythtv-database-
>>> > > > backup.sh[319303]:
>>> > > > Database schema 1379 not supported.
>>> > > > Oct 11 05:40:02 kubuntu-closet mythtv-database-
>>> > > > backup.sh[319303]:
>>> > > > Bindings support schema version 1378
>>> > > > Oct 11 05:40:02 kubuntu-closet systemd[1]:
>>> > > > mythtv-database-backup.service: Main process exited,
>>> > > > code=exited,
>>> > > > status=1/FAILURE
>>> > > > Oct 11 05:40:02 kubuntu-closet systemd[1]:
>>> > > > mythtv-database-backup.service: Failed with result 'exit-
>>> > > > code'.
>>> > > > Oct 11 05:40:02 kubuntu-closet systemd[1]: Failed to start
>>> > > > Backup
>>> > > > MythTV Database 'mythconverg'.
>>> > > >
>>> > > >
>>> > > > Not sure why it's talking about schema 1379??
>>> > > >
>>> > > > Jim A
>>> > > >
>>> > > >
>>> > > > BTW, the complete script that systemd runs to backup is below:
>>> > > > #!/bin/sh
>>> > > > # /etc/cron.weekly/mythtv-database script - check and backup
>>> > > > mythconverg
>>> > > > tables
>>> > > > # Copyright 2005/12/02 2006/10/08 Paul Andreassen
>>> > > > # 2010 Mario Limonciello
>>> > > >
>>> > > > set -e -u
>>> > > >
>>> > > > DBNAME="mythconverg"
>>> > > > USER="mythtv"
>>> > > > OPT_MYTHDB='/usr/share/doc/mythtv-
>>> > > > backend/contrib/maintenance/optimize_mythdb.pl
>>> > > > <http://optimize_mythdb.pl>'
>>> > > >
>>> > > > /usr/bin/mysqlcheck -s $DBNAME
>>> > > >
>>> > > > BKUP_LOG=/tmp/backup-mythconverg.log
>>> > > >
>>> > > > export MYTHCONFDIR=/home/mythtv/.mythtv/
>>> > > >
>>> > > > ${OPT_MYTHDB} | grep -v "^Analyzed:" 2>&1 > $BKUP_LOG
>>> > > >
>>> > > > sudo --preserve-env --user=$USER
>>> > > > /usr/share/mythtv/mythconverg_backup.pl
>>> > > > <http://mythconverg_backup.pl> \
>>> > > > --rotate=5 --verbose 2>&1 >> $BKUP_LOG
>>> > > >
>>> > > > if [ $? -eq 0 ]; then
>>> > > > MSG="kubuntu-closet $DBNAME Checked and Backed Up, RC=$?"
>>> > > > else
>>> > > > MSG="kubuntu-closet $DBNAME Back Up Failed, RC=$?"
>>> > > > fi
>>> > > >
>>> > > > cd /data/mythtv/db_backups/
>>> > > > ls -l --directory --block-size=K * | tail -10 >> $BKUP_LOG
>>> > > >
>>> > > > mail -s "$MSG" my.email@gmail.com <mailto:my.email@gmail.com> <
>>> > > > $BKUP_LOG
>>> > > >
>>> > > > --------------------------
>>> > > >
>>> > > > The actual error I get when it's run from the console is:
>>> > > >
>>> > > > Database schema 1379 not supported.
>>> > > > Bindings support schema version 1378
>>> > > >
>>> > > > Jim A
>>> > > >
>>> > > chema 1379 came with yesterday's commit for gallery images.
>>> > >
>>> > >
>>> > >
>>> https://github.com/MythTV/mythtv/commit/5825b36c97ec742f908845ccd11eee40040c0529
>>> > >
>>> > > ISTR that these updates used to get a bigger flag. Nowadays they
>>> > > just
>>> > > happen...
>>> > >
>>> > >
>>> >
>>> >
>>> > It seems that normal TV program recording and playback still works
>>> > fine, so I'll wait for things to just clear up.
>>>
>>> Did your MythTV perl bindings get updated at the same time your backend
>>> was updated? They should both use schema 1379. What's the output of:
>>>
>>> grep SCHEMA $(find /usr -name MythTV.pm 2>/dev/null) | head -1
>>>
>>> I was able to run a database backup on my production system (schema
>>> 1379) without a problem.
>>>
>>> David
>>>
>>>
>> jim@kubuntu-closet:~$ grep SCHEMA $(find /usr -name MythTV.pm
>> 2>/dev/null) | head -1
>> /usr/local/share/perl/5.34.0/MythTV.pm: our $SCHEMA_VERSION = "1378";
>> jim@kubuntu-closet:~$
>>
>>
>> Jim A
>>
>>
> FYI, I tried this on a Debian 12 build and it showed
> jim@debian-mythtv:~$ grep SCHEMA $(find /usr -name MythTV.pm
> 2>/dev/null) | head -1
> /usr/share/perl5/MythTV.pm: our $SCHEMA_VERSION = "1379";
>
> The previous run was on a Ubuntu 22.04 system using the ppa
>
> Jim A
>

I did some more digging and it is definitely a Ubuntu PPA v34 related
issue. The Debian 12 backend where I build my own packages did run the
mythconverg optimize and backup just fine this morning and it's stamped as
a 1379 schema.

Jim A

On 11/10/2023 14:52, James Abernathy wrote:

>
>
> On Wed, Oct 11, 2023 at 8:58?AM James Abernathy
> <jfabernathy@gmail.com> wrote:
>
>
>
> On Wed, Oct 11, 2023 at 8:55?AM James Abernathy
> <jfabernathy@gmail.com> wrote:
>
>
>
> On Wed, Oct 11, 2023 at 8:42?AM David Hampton via mythtv-users
> <mythtv-users@mythtv.org> wrote:
>
> On Wed, 2023-10-11 at 07:58 -0400, James Abernathy wrote:
> >
> >
> > On Wed, Oct 11, 2023 at 7:51?AM John Pilkington
> > <johnpilk222@gmail.com> wrote:
> > > On 11/10/2023 12:42, James Abernathy wrote:
> > > >
> > > >
> > > > On Wed, Oct 11, 2023 at 7:22?AM James Abernathy
> > > > <jfabernathy@gmail.com
> > > > <mailto:jfabernathy@gmail.com>> wrote:
> > > >
> > > >      I have my mythconverg backup script running
> daily and after
> > > >      yesterday's update to master it didn't run this
> morning at
> > > > 5:40 as
> > > >      it should.  I know because I didn't get the
> email it usually
> > > > sends
> > > >      to one of my gmail accounts.
> > > >
> > > >      I checked the systemctl status and this is what
> I saw:
> > > >
> > > >      Oct 11 05:40:02 kubuntu-closet systemd[1]:
> Starting Backup
> > > > MythTV
> > > >      Database 'mythconverg'...
> > > >      Oct 11 05:40:02 kubuntu-closet mythtv-database-
> > > > backup.sh[319303]:
> > > >      Database schema 1379 not supported.
> > > >      Oct 11 05:40:02 kubuntu-closet mythtv-database-
> > > > backup.sh[319303]:
> > > >      Bindings support schema version 1378
> > > >      Oct 11 05:40:02 kubuntu-closet systemd[1]:
> > > >  mythtv-database-backup.service: Main process exited,
> > > > code=exited,
> > > >      status=1/FAILURE
> > > >      Oct 11 05:40:02 kubuntu-closet systemd[1]:
> > > >  mythtv-database-backup.service: Failed with result
> 'exit-
> > > > code'.
> > > >      Oct 11 05:40:02 kubuntu-closet systemd[1]:
> Failed to start
> > > > Backup
> > > >      MythTV Database 'mythconverg'.
> > > >
> > > >
> > > >      Not sure why it's talking about schema 1379??
> > > >
> > > >      Jim A
> > > >
> > > >
> > > > BTW, the complete script that systemd runs to backup
> is below:
> > > > #!/bin/sh
> > > > # /etc/cron.weekly/mythtv-database script - check
> and backup
> > > > mythconverg
> > > > tables
> > > > # Copyright 2005/12/02 2006/10/08 Paul Andreassen
> > > > #                      2010 Mario Limonciello
> > > >
> > > > set -e -u
> > > >
> > > > DBNAME="mythconverg"
> > > > USER="mythtv"
> > > > OPT_MYTHDB='/usr/share/doc/mythtv-
> > > > backend/contrib/maintenance/optimize_mythdb.pl
> <http://optimize_mythdb.pl>
> > > > <http://optimize_mythdb.pl>'
> > > >
> > > > /usr/bin/mysqlcheck -s $DBNAME
> > > >
> > > > BKUP_LOG=/tmp/backup-mythconverg.log
> > > >
> > > > export MYTHCONFDIR=/home/mythtv/.mythtv/
> > > >
> > > > ${OPT_MYTHDB} | grep -v "^Analyzed:" 2>&1 > $BKUP_LOG
> > > >
> > > > sudo --preserve-env --user=$USER
> > > > /usr/share/mythtv/mythconverg_backup.pl
> <http://mythconverg_backup.pl>
> > > > <http://mythconverg_backup.pl> \
> > > >       --rotate=5 --verbose 2>&1 >> $BKUP_LOG
> > > >
> > > > if [ $? -eq 0 ]; then
> > > >       MSG="kubuntu-closet $DBNAME Checked and Backed
> Up, RC=$?"
> > > > else
> > > >       MSG="kubuntu-closet $DBNAME Back Up Failed, RC=$?"
> > > > fi
> > > >
> > > > cd /data/mythtv/db_backups/
> > > > ls -l --directory --block-size=K * | tail -10 >>
> $BKUP_LOG
> > > >
> > > > mail -s "$MSG" my.email@gmail.com
> <mailto:my.email@gmail.com> <
> > > > $BKUP_LOG
> > > >
> > > >    --------------------------
> > > >
> > > > The actual error I get when it's run from the
> console is:
> > > >
> > > > Database schema 1379 not supported.
> > > > Bindings support schema version 1378
> > > >
> > > > Jim A
> > > >
> > > chema 1379 came with yesterday's commit for gallery
> images.
> > >
> > >
> > >
> https://github.com/MythTV/mythtv/commit/5825b36c97ec742f908845ccd11eee40040c0529
> > >
> > > ISTR that these updates used to get a bigger flag. 
> Nowadays they
> > > just
> > > happen...
> > >
> > >
> >
> >
> > It seems that normal TV program recording and playback
> still works
> > fine, so I'll  wait for things to just clear up.
>
> Did your MythTV perl bindings get updated at the same time
> your backend
> was updated?  They should both use schema 1379. What's the
> output of:
>
>    grep SCHEMA $(find /usr -name MythTV.pm 2>/dev/null) |
> head -1
>
> I was able to run a database backup on my production
> system (schema
> 1379) without a problem.
>
> David
>
>
> jim@kubuntu-closet:~$ grep SCHEMA $(find /usr -name MythTV.pm
> 2>/dev/null) | head -1
> /usr/local/share/perl/5.34.0/MythTV.pm:    our $SCHEMA_VERSION
> = "1378";
> jim@kubuntu-closet:~$
>
>
> Jim A
>
>
> FYI, I tried this on a Debian 12 build and it showed
> jim@debian-mythtv:~$    grep SCHEMA $(find /usr -name MythTV.pm
> 2>/dev/null) | head -1
> /usr/share/perl5/MythTV.pm:    our $SCHEMA_VERSION = "1379";
>
> The previous run was on a Ubuntu 22.04 system using the ppa
>
> Jim A
>
>
> I did some more digging and it is definitely a Ubuntu PPA v34 related
> issue.  The Debian 12 backend where I build my own packages did run
> the mythconverg optimize and backup just fine this morning and it's
> stamped as a 1379 schema.
>
> Jim A
>
>

There can be up to 24 hours delay in the building of the PPA packages.
Are you sure you have the latest build installed?

You can use apt-cache policy libmythtv-perl to see what version of the
perl binding you have installed.


Paul H.

On Wed, Oct 11, 2023 at 11:05?AM Paul Harrison <mythtv@mythqml.net> wrote:

> On 11/10/2023 14:52, James Abernathy wrote:
>
>
>
> On Wed, Oct 11, 2023 at 8:58?AM James Abernathy <jfabernathy@gmail.com>
> wrote:
>
>>
>>
>> On Wed, Oct 11, 2023 at 8:55?AM James Abernathy <jfabernathy@gmail.com>
>> wrote:
>>
>>>
>>>
>>> On Wed, Oct 11, 2023 at 8:42?AM David Hampton via mythtv-users <
>>> mythtv-users@mythtv.org> wrote:
>>>
>>>> On Wed, 2023-10-11 at 07:58 -0400, James Abernathy wrote:
>>>> >
>>>> >
>>>> > On Wed, Oct 11, 2023 at 7:51?AM John Pilkington
>>>> > <johnpilk222@gmail.com> wrote:
>>>> > > On 11/10/2023 12:42, James Abernathy wrote:
>>>> > > >
>>>> > > >
>>>> > > > On Wed, Oct 11, 2023 at 7:22?AM James Abernathy
>>>> > > > <jfabernathy@gmail.com
>>>> > > > <mailto:jfabernathy@gmail.com>> wrote:
>>>> > > >
>>>> > > > I have my mythconverg backup script running daily and after
>>>> > > > yesterday's update to master it didn't run this morning at
>>>> > > > 5:40 as
>>>> > > > it should. I know because I didn't get the email it usually
>>>> > > > sends
>>>> > > > to one of my gmail accounts.
>>>> > > >
>>>> > > > I checked the systemctl status and this is what I saw:
>>>> > > >
>>>> > > > Oct 11 05:40:02 kubuntu-closet systemd[1]: Starting Backup
>>>> > > > MythTV
>>>> > > > Database 'mythconverg'...
>>>> > > > Oct 11 05:40:02 kubuntu-closet mythtv-database-
>>>> > > > backup.sh[319303]:
>>>> > > > Database schema 1379 not supported.
>>>> > > > Oct 11 05:40:02 kubuntu-closet mythtv-database-
>>>> > > > backup.sh[319303]:
>>>> > > > Bindings support schema version 1378
>>>> > > > Oct 11 05:40:02 kubuntu-closet systemd[1]:
>>>> > > > mythtv-database-backup.service: Main process exited,
>>>> > > > code=exited,
>>>> > > > status=1/FAILURE
>>>> > > > Oct 11 05:40:02 kubuntu-closet systemd[1]:
>>>> > > > mythtv-database-backup.service: Failed with result 'exit-
>>>> > > > code'.
>>>> > > > Oct 11 05:40:02 kubuntu-closet systemd[1]: Failed to start
>>>> > > > Backup
>>>> > > > MythTV Database 'mythconverg'.
>>>> > > >
>>>> > > >
>>>> > > > Not sure why it's talking about schema 1379??
>>>> > > >
>>>> > > > Jim A
>>>> > > >
>>>> > > >
>>>> > > > BTW, the complete script that systemd runs to backup is below:
>>>> > > > #!/bin/sh
>>>> > > > # /etc/cron.weekly/mythtv-database script - check and backup
>>>> > > > mythconverg
>>>> > > > tables
>>>> > > > # Copyright 2005/12/02 2006/10/08 Paul Andreassen
>>>> > > > # 2010 Mario Limonciello
>>>> > > >
>>>> > > > set -e -u
>>>> > > >
>>>> > > > DBNAME="mythconverg"
>>>> > > > USER="mythtv"
>>>> > > > OPT_MYTHDB='/usr/share/doc/mythtv-
>>>> > > > backend/contrib/maintenance/optimize_mythdb.pl
>>>> > > > <http://optimize_mythdb.pl>'
>>>> > > >
>>>> > > > /usr/bin/mysqlcheck -s $DBNAME
>>>> > > >
>>>> > > > BKUP_LOG=/tmp/backup-mythconverg.log
>>>> > > >
>>>> > > > export MYTHCONFDIR=/home/mythtv/.mythtv/
>>>> > > >
>>>> > > > ${OPT_MYTHDB} | grep -v "^Analyzed:" 2>&1 > $BKUP_LOG
>>>> > > >
>>>> > > > sudo --preserve-env --user=$USER
>>>> > > > /usr/share/mythtv/mythconverg_backup.pl
>>>> > > > <http://mythconverg_backup.pl> \
>>>> > > > --rotate=5 --verbose 2>&1 >> $BKUP_LOG
>>>> > > >
>>>> > > > if [ $? -eq 0 ]; then
>>>> > > > MSG="kubuntu-closet $DBNAME Checked and Backed Up, RC=$?"
>>>> > > > else
>>>> > > > MSG="kubuntu-closet $DBNAME Back Up Failed, RC=$?"
>>>> > > > fi
>>>> > > >
>>>> > > > cd /data/mythtv/db_backups/
>>>> > > > ls -l --directory --block-size=K * | tail -10 >> $BKUP_LOG
>>>> > > >
>>>> > > > mail -s "$MSG" my.email@gmail.com <mailto:my.email@gmail.com> <
>>>> > > > $BKUP_LOG
>>>> > > >
>>>> > > > --------------------------
>>>> > > >
>>>> > > > The actual error I get when it's run from the console is:
>>>> > > >
>>>> > > > Database schema 1379 not supported.
>>>> > > > Bindings support schema version 1378
>>>> > > >
>>>> > > > Jim A
>>>> > > >
>>>> > > chema 1379 came with yesterday's commit for gallery images.
>>>> > >
>>>> > >
>>>> > >
>>>> https://github.com/MythTV/mythtv/commit/5825b36c97ec742f908845ccd11eee40040c0529
>>>> > >
>>>> > > ISTR that these updates used to get a bigger flag. Nowadays they
>>>> > > just
>>>> > > happen...
>>>> > >
>>>> > >
>>>> >
>>>> >
>>>> > It seems that normal TV program recording and playback still works
>>>> > fine, so I'll wait for things to just clear up.
>>>>
>>>> Did your MythTV perl bindings get updated at the same time your backend
>>>> was updated? They should both use schema 1379. What's the output of:
>>>>
>>>> grep SCHEMA $(find /usr -name MythTV.pm 2>/dev/null) | head -1
>>>>
>>>> I was able to run a database backup on my production system (schema
>>>> 1379) without a problem.
>>>>
>>>> David
>>>>
>>>>
>>> jim@kubuntu-closet:~$ grep SCHEMA $(find /usr -name MythTV.pm
>>> 2>/dev/null) | head -1
>>> /usr/local/share/perl/5.34.0/MythTV.pm: our $SCHEMA_VERSION = "1378";
>>> jim@kubuntu-closet:~$
>>>
>>>
>>> Jim A
>>>
>>>
>> FYI, I tried this on a Debian 12 build and it showed
>> jim@debian-mythtv:~$ grep SCHEMA $(find /usr -name MythTV.pm
>> 2>/dev/null) | head -1
>> /usr/share/perl5/MythTV.pm: our $SCHEMA_VERSION = "1379";
>>
>> The previous run was on a Ubuntu 22.04 system using the ppa
>>
>> Jim A
>>
>
> I did some more digging and it is definitely a Ubuntu PPA v34 related
> issue. The Debian 12 backend where I build my own packages did run the
> mythconverg optimize and backup just fine this morning and it's stamped as
> a 1379 schema.
>
> Jim A
>
>
>
> There can be up to 24 hours delay in the building of the PPA packages. Are
> you sure you have the latest build installed?
>
> You can use apt-cache policy libmythtv-perl to see what version of the
> perl binding you have installed.
>
>
> Paul H.
>

apt-cache policy libmythtv-perl
libmythtv-perl:
Installed: 2:34.0~master.202310100432.20594a9a1e~ubuntu22.04.1
Candidate: 2:34.0~master.202310100432.20594a9a1e~ubuntu22.04.1
Version table:
*** 2:34.0~master.202310100432.20594a9a1e~ubuntu22.04.1 500
500 https://ppa.launchpadcontent.net/mythbuntu/34/ubuntu jammy/main
amd64 Packages
500 https://ppa.launchpadcontent.net/mythbuntu/34/ubuntu jammy/main
i386 Packages
100 /var/lib/dpkg/status
2:32.0+fixes.20220325.f69ce764b7-0ubuntu1 500
500 http://us.archive.ubuntu.com/ubuntu jammy/multiverse amd64
Packages
500 http://us.archive.ubuntu.com/ubuntu jammy/multiverse i386
Packages

On 11/10/2023 16:08, James Abernathy wrote:

>
> apt-cache policy libmythtv-perl
> libmythtv-perl:
>   Installed: 2:34.0~master.202310100432.20594a9a1e~ubuntu22.04.1
>   Candidate: 2:34.0~master.202310100432.20594a9a1e~ubuntu22.04.1
>   Version table:
>  *** 2:34.0~master.202310100432.20594a9a1e~ubuntu22.04.1 500
>         500 https://ppa.launchpadcontent.net/mythbuntu/34/ubuntu
> jammy/main amd64 Packages
>         500 https://ppa.launchpadcontent.net/mythbuntu/34/ubuntu
> jammy/main i386 Packages
>         100 /var/lib/dpkg/status
>      2:32.0+fixes.20220325.f69ce764b7-0ubuntu1 500
>         500 http://us.archive.ubuntu.com/ubuntu jammy/multiverse amd64
> Packages
>         500 http://us.archive.ubuntu.com/ubuntu jammy/multiverse i386
> Packages
> jim@kubuntu-closet:~$ grep SCHEMA $(find /usr -name MythTV.pm
> 2>/dev/null) | head -1
> /usr/local/share/perl/5.34.0/MythTV.pm:    our $SCHEMA_VERSION = "1378";
> jim@kubuntu-closet:~$
>
>

I've just checked the MythTV.pm from the Ubuntu package and it has 1379
for the schema as it should so it looks like there is something a little
mixed up with your install.

Maybe you have multiple versions of the bindings installed and the one
with 1378 for the schema is the first one to be found?


Paul H.

On Wed, Oct 11, 2023 at 11:43?AM Paul Harrison <mythtv@mythqml.net> wrote:

> On 11/10/2023 16:08, James Abernathy wrote:
>
>
> apt-cache policy libmythtv-perl
> libmythtv-perl:
> Installed: 2:34.0~master.202310100432.20594a9a1e~ubuntu22.04.1
> Candidate: 2:34.0~master.202310100432.20594a9a1e~ubuntu22.04.1
> Version table:
> *** 2:34.0~master.202310100432.20594a9a1e~ubuntu22.04.1 500
> 500 https://ppa.launchpadcontent.net/mythbuntu/34/ubuntu
> jammy/main amd64 Packages
> 500 https://ppa.launchpadcontent.net/mythbuntu/34/ubuntu
> jammy/main i386 Packages
> 100 /var/lib/dpkg/status
> 2:32.0+fixes.20220325.f69ce764b7-0ubuntu1 500
> 500 http://us.archive.ubuntu.com/ubuntu jammy/multiverse amd64
> Packages
> 500 http://us.archive.ubuntu.com/ubuntu jammy/multiverse i386
> Packages
>
> jim@kubuntu-closet:~$ grep SCHEMA $(find /usr -name MythTV.pm
> 2>/dev/null) | head -1
> /usr/local/share/perl/5.34.0/MythTV.pm: our $SCHEMA_VERSION = "1378";
> jim@kubuntu-closet:~$
>
>
>
> I've just checked the MythTV.pm from the Ubuntu package and it has 1379
> for the schema as it should so it looks like there is something a little
> mixed up with your install.
>
> Maybe you have multiple versions of the bindings installed and the one
> with 1378 for the schema is the first one to be found?
>
>
> Paul H.
>

Paul, this is my production system so it has been upgraded in place from
Ubuntu 20.04 to 22.04 and from mythtv v32 to v33 and now to v34. not sure
how to proceed. I run Timeshift and my file system is BTRFS so I have a
week of snapshots I can restore from, but not really sure where to start
from.

JIm A

On Wed, Oct 11, 2023 at 11:51?AM James Abernathy <jfabernathy@gmail.com>
wrote:

>
>
> On Wed, Oct 11, 2023 at 11:43?AM Paul Harrison <mythtv@mythqml.net> wrote:
>
>> On 11/10/2023 16:08, James Abernathy wrote:
>>
>>
>> apt-cache policy libmythtv-perl
>> libmythtv-perl:
>> Installed: 2:34.0~master.202310100432.20594a9a1e~ubuntu22.04.1
>> Candidate: 2:34.0~master.202310100432.20594a9a1e~ubuntu22.04.1
>> Version table:
>> *** 2:34.0~master.202310100432.20594a9a1e~ubuntu22.04.1 500
>> 500 https://ppa.launchpadcontent.net/mythbuntu/34/ubuntu
>> jammy/main amd64 Packages
>> 500 https://ppa.launchpadcontent.net/mythbuntu/34/ubuntu
>> jammy/main i386 Packages
>> 100 /var/lib/dpkg/status
>> 2:32.0+fixes.20220325.f69ce764b7-0ubuntu1 500
>> 500 http://us.archive.ubuntu.com/ubuntu jammy/multiverse amd64
>> Packages
>> 500 http://us.archive.ubuntu.com/ubuntu jammy/multiverse i386
>> Packages
>>
>> jim@kubuntu-closet:~$ grep SCHEMA $(find /usr -name MythTV.pm
>> 2>/dev/null) | head -1
>> /usr/local/share/perl/5.34.0/MythTV.pm: our $SCHEMA_VERSION = "1378";
>> jim@kubuntu-closet:~$
>>
>>
>>
>> I've just checked the MythTV.pm from the Ubuntu package and it has 1379
>> for the schema as it should so it looks like there is something a little
>> mixed up with your install.
>>
>> Maybe you have multiple versions of the bindings installed and the one
>> with 1378 for the schema is the first one to be found?
>>
>>
>> Paul H.
>>
>
> Paul, this is my production system so it has been upgraded in place from
> Ubuntu 20.04 to 22.04 and from mythtv v32 to v33 and now to v34. not sure
> how to proceed. I run Timeshift and my file system is BTRFS so I have a
> week of snapshots I can restore from, but not really sure where to start
> from.
>
> JIm A
>

So I restored from a snapshot a few days before the last mythtv update. As
soon as I booted it ran the mythconverg backup on schema 1378. Then I sudo
apt update and upgrade, and now I am back to where the database has indeed
been updated to 1379 but the backup will not run because the binding
support schema is still 1378.

Jim A

On Wed, Oct 11, 2023 at 12:20?PM James Abernathy <jfabernathy@gmail.com>
wrote:

>
>
>
> On Wed, Oct 11, 2023 at 11:51?AM James Abernathy <jfabernathy@gmail.com>
> wrote:
>
>>
>>
>> On Wed, Oct 11, 2023 at 11:43?AM Paul Harrison <mythtv@mythqml.net>
>> wrote:
>>
>>> On 11/10/2023 16:08, James Abernathy wrote:
>>>
>>>
>>> apt-cache policy libmythtv-perl
>>> libmythtv-perl:
>>> Installed: 2:34.0~master.202310100432.20594a9a1e~ubuntu22.04.1
>>> Candidate: 2:34.0~master.202310100432.20594a9a1e~ubuntu22.04.1
>>> Version table:
>>> *** 2:34.0~master.202310100432.20594a9a1e~ubuntu22.04.1 500
>>> 500 https://ppa.launchpadcontent.net/mythbuntu/34/ubuntu
>>> jammy/main amd64 Packages
>>> 500 https://ppa.launchpadcontent.net/mythbuntu/34/ubuntu
>>> jammy/main i386 Packages
>>> 100 /var/lib/dpkg/status
>>> 2:32.0+fixes.20220325.f69ce764b7-0ubuntu1 500
>>> 500 http://us.archive.ubuntu.com/ubuntu jammy/multiverse amd64
>>> Packages
>>> 500 http://us.archive.ubuntu.com/ubuntu jammy/multiverse i386
>>> Packages
>>>
>>> jim@kubuntu-closet:~$ grep SCHEMA $(find /usr -name MythTV.pm
>>> 2>/dev/null) | head -1
>>> /usr/local/share/perl/5.34.0/MythTV.pm: our $SCHEMA_VERSION = "1378";
>>> jim@kubuntu-closet:~$
>>>
>>>
>>>
>>> I've just checked the MythTV.pm from the Ubuntu package and it has 1379
>>> for the schema as it should so it looks like there is something a little
>>> mixed up with your install.
>>>
>>> Maybe you have multiple versions of the bindings installed and the one
>>> with 1378 for the schema is the first one to be found?
>>>
>>>
>>> Paul H.
>>>
>>
>> Paul, this is my production system so it has been upgraded in place from
>> Ubuntu 20.04 to 22.04 and from mythtv v32 to v33 and now to v34. not sure
>> how to proceed. I run Timeshift and my file system is BTRFS so I have a
>> week of snapshots I can restore from, but not really sure where to start
>> from.
>>
>> JIm A
>>
>
> So I restored from a snapshot a few days before the last mythtv update.
> As soon as I booted it ran the mythconverg backup on schema 1378. Then I
> sudo apt update and upgrade, and now I am back to where the database has
> indeed been updated to 1379 but the backup will not run because the binding
> support schema is still 1378.
>
> Jim A
>

And I cannot run ./find_orphans_jfa.py for the same reason.

2023-10-11 12:20:20.226853 E [2272] Python Database Connection Database
schema mismatch: we speak 1378 but database speaks 1379
Traceback (most recent call last):
File "/home/jim/./find_orphans_jfa.py", line 223, in <module>
DB = MythDB()
File "/usr/local/lib/python3.10/dist-packages/MythTV/database.py", line
1272, in __init__
elif self._testconfig(tmpconfig):
File "/usr/local/lib/python3.10/dist-packages/MythTV/database.py", line
1301, in _testconfig
self._check_schema(self._schema_value, self._schema_local,
File "/usr/local/lib/python3.10/dist-packages/MythTV/database.py", line
1335, in _check_schema
raise MythDBError(MythError.DB_SCHEMAMISMATCH, value, sver, local)
MythTV.exceptions.MythDBError: Mismatched schema version for 'DBSchemaVer':
database speaks version 1379, we speak version 1378

Jim A

On 11/10/2023 17:22, James Abernathy wrote:

>
> So I restored from a snapshot a few days before the last mythtv
> update.  As soon as I booted it ran the mythconverg backup on
> schema 1378.  Then I sudo apt update and upgrade, and now I am
> back to where the database has indeed been updated to 1379 but the
> backup will not run because the binding support schema is still 1378.
>
> Jim A
>
>
> And I cannot run  ./find_orphans_jfa.py for the same reason.
>
> 2023-10-11 12:20:20.226853 E [2272] Python Database Connection
> Database schema mismatch: we speak 1378 but database speaks 1379
> Traceback (most recent call last):
>   File "/home/jim/./find_orphans_jfa.py", line 223, in <module>
>     DB = MythDB()
>   File "/usr/local/lib/python3.10/dist-packages/MythTV/database.py",
> line 1272, in __init__
>     elif self._testconfig(tmpconfig):
>   File "/usr/local/lib/python3.10/dist-packages/MythTV/database.py",
> line 1301, in _testconfig
>     self._check_schema(self._schema_value, self._schema_local,
>   File "/usr/local/lib/python3.10/dist-packages/MythTV/database.py",
> line 1335, in _check_schema
>     raise MythDBError(MythError.DB_SCHEMAMISMATCH, value, sver, local)
> MythTV.exceptions.MythDBError: Mismatched schema version for
> 'DBSchemaVer': database speaks version 1379, we speak version 1378
>
> Jim A
>
>

I would look in /usr/local/share/perl/ and see if there are different
version of the binding in different directories. Look for different
version of MythTV.pm

I don't speak perl but I would guess if you look at your perl --version
you should have a corresponding directory in /usr/local/share/perl/ in
which you should find a MythTV.pm.

There is a dpkg command to see what a package installs and where I thing
it is something like dpkg -L libmythtv-perl to see if the bindings are
being installed in the correct directory for your version of Perl.


Paul H.

On Wed, Oct 11, 2023 at 6:42?PM Paul Harrison <mythtv@mythqml.net> wrote:

> On 11/10/2023 17:22, James Abernathy wrote:
>
>
> So I restored from a snapshot a few days before the last mythtv update.
>> As soon as I booted it ran the mythconverg backup on schema 1378. Then I
>> sudo apt update and upgrade, and now I am back to where the database has
>> indeed been updated to 1379 but the backup will not run because the binding
>> support schema is still 1378.
>>
>> Jim A
>>
>
> And I cannot run ./find_orphans_jfa.py for the same reason.
>
> 2023-10-11 12:20:20.226853 E [2272] Python Database Connection Database
> schema mismatch: we speak 1378 but database speaks 1379
> Traceback (most recent call last):
> File "/home/jim/./find_orphans_jfa.py", line 223, in <module>
> DB = MythDB()
> File "/usr/local/lib/python3.10/dist-packages/MythTV/database.py", line
> 1272, in __init__
> elif self._testconfig(tmpconfig):
> File "/usr/local/lib/python3.10/dist-packages/MythTV/database.py", line
> 1301, in _testconfig
> self._check_schema(self._schema_value, self._schema_local,
> File "/usr/local/lib/python3.10/dist-packages/MythTV/database.py", line
> 1335, in _check_schema
> raise MythDBError(MythError.DB_SCHEMAMISMATCH, value, sver, local)
> MythTV.exceptions.MythDBError: Mismatched schema version for
> 'DBSchemaVer': database speaks version 1379, we speak version 1378
>
> Jim A
>
>
>
> I would look in /usr/local/share/perl/ and see if there are different
> version of the binding in different directories. Look for different version
> of MythTV.pm
>
> I don't speak perl but I would guess if you look at your perl --version
> you should have a corresponding directory in /usr/local/share/perl/ in
> which you should find a MythTV.pm.
>
> There is a dpkg command to see what a package installs and where I thing
> it is something like dpkg -L libmythtv-perl to see if the bindings are
> being installed in the correct directory for your version of Perl.
>
>
> Paul H.
>

IMHO, Ubuntu ppa packages installs the bindings into /usr and not into
/usr/local and
the packages in /usr/local have precedence.
I guess, you did a local build/install somewhere in the past.
Try in a terminal
locate MythTV.pm
locate static.py

Roland

On Wed, Oct 11, 2023 at 1:30?PM Roland Ernst <rcrernst@gmail.com> wrote:

>
>
> On Wed, Oct 11, 2023 at 6:42?PM Paul Harrison <mythtv@mythqml.net> wrote:
>
>> On 11/10/2023 17:22, James Abernathy wrote:
>>
>>
>> So I restored from a snapshot a few days before the last mythtv update.
>>> As soon as I booted it ran the mythconverg backup on schema 1378. Then I
>>> sudo apt update and upgrade, and now I am back to where the database has
>>> indeed been updated to 1379 but the backup will not run because the binding
>>> support schema is still 1378.
>>>
>>> Jim A
>>>
>>
>> And I cannot run ./find_orphans_jfa.py for the same reason.
>>
>> 2023-10-11 12:20:20.226853 E [2272] Python Database Connection Database
>> schema mismatch: we speak 1378 but database speaks 1379
>> Traceback (most recent call last):
>> File "/home/jim/./find_orphans_jfa.py", line 223, in <module>
>> DB = MythDB()
>> File "/usr/local/lib/python3.10/dist-packages/MythTV/database.py", line
>> 1272, in __init__
>> elif self._testconfig(tmpconfig):
>> File "/usr/local/lib/python3.10/dist-packages/MythTV/database.py", line
>> 1301, in _testconfig
>> self._check_schema(self._schema_value, self._schema_local,
>> File "/usr/local/lib/python3.10/dist-packages/MythTV/database.py", line
>> 1335, in _check_schema
>> raise MythDBError(MythError.DB_SCHEMAMISMATCH, value, sver, local)
>> MythTV.exceptions.MythDBError: Mismatched schema version for
>> 'DBSchemaVer': database speaks version 1379, we speak version 1378
>>
>> Jim A
>>
>>
>>
>> I would look in /usr/local/share/perl/ and see if there are different
>> version of the binding in different directories. Look for different version
>> of MythTV.pm
>>
>> I don't speak perl but I would guess if you look at your perl --version
>> you should have a corresponding directory in /usr/local/share/perl/ in
>> which you should find a MythTV.pm.
>>
>> There is a dpkg command to see what a package installs and where I thing
>> it is something like dpkg -L libmythtv-perl to see if the bindings are
>> being installed in the correct directory for your version of Perl.
>>
>>
>> Paul H.
>>
>
> IMHO, Ubuntu ppa packages installs the bindings into /usr and not into
> /usr/local and
> the packages in /usr/local have precedence.
> I guess, you did a local build/install somewhere in the past.
> Try in a terminal
> locate MythTV.pm
> locate static.py
>
> Roland
>

jim@den-pc:~$ sudo dpkg -L libmythtv-perl
/.
/usr
/usr/share
/usr/share/doc
/usr/share/doc/libmythtv-perl
/usr/share/doc/libmythtv-perl/changelog.Debian.gz
/usr/share/doc/libmythtv-perl/copyright
/usr/share/perl5
/usr/share/perl5/IO
/usr/share/perl5/IO/Socket
/usr/share/perl5/IO/Socket/INET
/usr/share/perl5/IO/Socket/INET/MythTV.pm
/usr/share/perl5/MythTV
/usr/share/perl5/MythTV/Channel.pm
/usr/share/perl5/MythTV/Program.pm
/usr/share/perl5/MythTV/Recording.pm
/usr/share/perl5/MythTV/StorageGroup.pm
/usr/share/perl5/MythTV.pm
---------------

jim@den-pc:~$ locate MythTV.pm
/usr/share/perl5/MythTV.pm
/usr/share/perl5/IO/Socket/INET/MythTV.pm
jim@den-pc:~$ locate static.py
/usr/lib/python3/dist-packages/MythTV/static.py

JIm A

On Wed, Oct 11, 2023 at 7:40?PM James Abernathy <jfabernathy@gmail.com>
wrote:

>
>
> On Wed, Oct 11, 2023 at 1:30?PM Roland Ernst <rcrernst@gmail.com> wrote:
>
>>
>>
>> On Wed, Oct 11, 2023 at 6:42?PM Paul Harrison <mythtv@mythqml.net> wrote:
>>
>>> On 11/10/2023 17:22, James Abernathy wrote:
>>>
>>>
>>> So I restored from a snapshot a few days before the last mythtv update.
>>>> As soon as I booted it ran the mythconverg backup on schema 1378. Then I
>>>> sudo apt update and upgrade, and now I am back to where the database has
>>>> indeed been updated to 1379 but the backup will not run because the binding
>>>> support schema is still 1378.
>>>>
>>>> Jim A
>>>>
>>>
>>> And I cannot run ./find_orphans_jfa.py for the same reason.
>>>
>>> 2023-10-11 12:20:20.226853 E [2272] Python Database Connection Database
>>> schema mismatch: we speak 1378 but database speaks 1379
>>> Traceback (most recent call last):
>>> File "/home/jim/./find_orphans_jfa.py", line 223, in <module>
>>> DB = MythDB()
>>> File "/usr/local/lib/python3.10/dist-packages/MythTV/database.py",
>>> line 1272, in __init__
>>> elif self._testconfig(tmpconfig):
>>> File "/usr/local/lib/python3.10/dist-packages/MythTV/database.py",
>>> line 1301, in _testconfig
>>> self._check_schema(self._schema_value, self._schema_local,
>>> File "/usr/local/lib/python3.10/dist-packages/MythTV/database.py",
>>> line 1335, in _check_schema
>>> raise MythDBError(MythError.DB_SCHEMAMISMATCH, value, sver, local)
>>> MythTV.exceptions.MythDBError: Mismatched schema version for
>>> 'DBSchemaVer': database speaks version 1379, we speak version 1378
>>>
>>> Jim A
>>>
>>>
>>>
>>> I would look in /usr/local/share/perl/ and see if there are different
>>> version of the binding in different directories. Look for different version
>>> of MythTV.pm
>>>
>>> I don't speak perl but I would guess if you look at your perl --version
>>> you should have a corresponding directory in /usr/local/share/perl/ in
>>> which you should find a MythTV.pm.
>>>
>>> There is a dpkg command to see what a package installs and where I thing
>>> it is something like dpkg -L libmythtv-perl to see if the bindings are
>>> being installed in the correct directory for your version of Perl.
>>>
>>>
>>> Paul H.
>>>
>>
>> IMHO, Ubuntu ppa packages installs the bindings into /usr and not into
>> /usr/local and
>> the packages in /usr/local have precedence.
>> I guess, you did a local build/install somewhere in the past.
>> Try in a terminal
>> locate MythTV.pm
>> locate static.py
>>
>> Roland
>>
>
> jim@den-pc:~$ sudo dpkg -L libmythtv-perl
> /.
> /usr
> /usr/share
> /usr/share/doc
> /usr/share/doc/libmythtv-perl
> /usr/share/doc/libmythtv-perl/changelog.Debian.gz
> /usr/share/doc/libmythtv-perl/copyright
> /usr/share/perl5
> /usr/share/perl5/IO
> /usr/share/perl5/IO/Socket
> /usr/share/perl5/IO/Socket/INET
> /usr/share/perl5/IO/Socket/INET/MythTV.pm
> /usr/share/perl5/MythTV
> /usr/share/perl5/MythTV/Channel.pm
> /usr/share/perl5/MythTV/Program.pm
> /usr/share/perl5/MythTV/Recording.pm
> /usr/share/perl5/MythTV/StorageGroup.pm
> /usr/share/perl5/MythTV.pm
> ---------------
>
> jim@den-pc:~$ locate MythTV.pm
> /usr/share/perl5/MythTV.pm
> /usr/share/perl5/IO/Socket/INET/MythTV.pm
> jim@den-pc:~$ locate static.py
> /usr/lib/python3/dist-packages/MythTV/static.py
>
> JIm A
>
>
Your traceback from python shows
File "/usr/*local*/lib/python3.10/dist-packages/MythTV/database.py",

Roland

On Wed, Oct 11, 2023 at 1:46?PM Roland Ernst <rcrernst@gmail.com> wrote:

>
>
> On Wed, Oct 11, 2023 at 7:40?PM James Abernathy <jfabernathy@gmail.com>
> wrote:
>
>>
>>
>> On Wed, Oct 11, 2023 at 1:30?PM Roland Ernst <rcrernst@gmail.com> wrote:
>>
>>>
>>>
>>> On Wed, Oct 11, 2023 at 6:42?PM Paul Harrison <mythtv@mythqml.net>
>>> wrote:
>>>
>>>> On 11/10/2023 17:22, James Abernathy wrote:
>>>>
>>>>
>>>> So I restored from a snapshot a few days before the last mythtv
>>>>> update. As soon as I booted it ran the mythconverg backup on schema 1378.
>>>>> Then I sudo apt update and upgrade, and now I am back to where the database
>>>>> has indeed been updated to 1379 but the backup will not run because the
>>>>> binding support schema is still 1378.
>>>>>
>>>>> Jim A
>>>>>
>>>>
>>>> And I cannot run ./find_orphans_jfa.py for the same reason.
>>>>
>>>> 2023-10-11 12:20:20.226853 E [2272] Python Database Connection Database
>>>> schema mismatch: we speak 1378 but database speaks 1379
>>>> Traceback (most recent call last):
>>>> File "/home/jim/./find_orphans_jfa.py", line 223, in <module>
>>>> DB = MythDB()
>>>> File "/usr/local/lib/python3.10/dist-packages/MythTV/database.py",
>>>> line 1272, in __init__
>>>> elif self._testconfig(tmpconfig):
>>>> File "/usr/local/lib/python3.10/dist-packages/MythTV/database.py",
>>>> line 1301, in _testconfig
>>>> self._check_schema(self._schema_value, self._schema_local,
>>>> File "/usr/local/lib/python3.10/dist-packages/MythTV/database.py",
>>>> line 1335, in _check_schema
>>>> raise MythDBError(MythError.DB_SCHEMAMISMATCH, value, sver, local)
>>>> MythTV.exceptions.MythDBError: Mismatched schema version for
>>>> 'DBSchemaVer': database speaks version 1379, we speak version 1378
>>>>
>>>> Jim A
>>>>
>>>>
>>>>
>>>> I would look in /usr/local/share/perl/ and see if there are different
>>>> version of the binding in different directories. Look for different version
>>>> of MythTV.pm
>>>>
>>>> I don't speak perl but I would guess if you look at your perl --version
>>>> you should have a corresponding directory in /usr/local/share/perl/ in
>>>> which you should find a MythTV.pm.
>>>>
>>>> There is a dpkg command to see what a package installs and where I
>>>> thing it is something like dpkg -L libmythtv-perl to see if the
>>>> bindings are being installed in the correct directory for your version of
>>>> Perl.
>>>>
>>>>
>>>> Paul H.
>>>>
>>>
>>> IMHO, Ubuntu ppa packages installs the bindings into /usr and not into
>>> /usr/local and
>>> the packages in /usr/local have precedence.
>>> I guess, you did a local build/install somewhere in the past.
>>> Try in a terminal
>>> locate MythTV.pm
>>> locate static.py
>>>
>>> Roland
>>>
>>
>> jim@den-pc:~$ sudo dpkg -L libmythtv-perl
>> /.
>> /usr
>> /usr/share
>> /usr/share/doc
>> /usr/share/doc/libmythtv-perl
>> /usr/share/doc/libmythtv-perl/changelog.Debian.gz
>> /usr/share/doc/libmythtv-perl/copyright
>> /usr/share/perl5
>> /usr/share/perl5/IO
>> /usr/share/perl5/IO/Socket
>> /usr/share/perl5/IO/Socket/INET
>> /usr/share/perl5/IO/Socket/INET/MythTV.pm
>> /usr/share/perl5/MythTV
>> /usr/share/perl5/MythTV/Channel.pm
>> /usr/share/perl5/MythTV/Program.pm
>> /usr/share/perl5/MythTV/Recording.pm
>> /usr/share/perl5/MythTV/StorageGroup.pm
>> /usr/share/perl5/MythTV.pm
>> ---------------
>>
>> jim@den-pc:~$ locate MythTV.pm
>> /usr/share/perl5/MythTV.pm
>> /usr/share/perl5/IO/Socket/INET/MythTV.pm
>> jim@den-pc:~$ locate static.py
>> /usr/lib/python3/dist-packages/MythTV/static.py
>>
>> JIm A
>>
>>
> Your traceback from python shows
> File "/usr/*local*/lib/python3.10/dist-packages/MythTV/database.py",
>
> Roland
>

I see what you mean, but I'm not sure how to recover from this. I just
finished spinning up a Linux Mint Debian Edition (Faye) debian 12 system
that has access to HDHR tuners. I have Mythtv v34 running on it with most
of my critical recording rules duplication there. So I have some time to
recover the production backend.

I imagine that my only choice would be to completely rebuild, which I was
planning to do at some point and switch it from Kubuntu to some flavor of
Debian 12. My biggest issue is not Mythtv. This hardware is also my Home
NAS. SO the only safe way to rebuild is to buy a new boot SSD and 2 new
4TB HDD for a 4TB mirror.

So I'm willing to try some suggestions if you have any. I could uninstall
mythtv and reinstall after deleting any /usr/local stuff if I can identify
it all without killing what I have that is not mythtv related. I have a DB
backup and all my recordings are on the NAS part of the system.

Jim A

On Wed, Oct 11, 2023 at 12:44?PM Paul Harrison <mythtv@mythqml.net> wrote:

> On 11/10/2023 17:22, James Abernathy wrote:
>
>
> So I restored from a snapshot a few days before the last mythtv update.
>> As soon as I booted it ran the mythconverg backup on schema 1378. Then I
>> sudo apt update and upgrade, and now I am back to where the database has
>> indeed been updated to 1379 but the backup will not run because the binding
>> support schema is still 1378.
>>
>> Jim A
>>
>
> And I cannot run ./find_orphans_jfa.py for the same reason.
>
> 2023-10-11 12:20:20.226853 E [2272] Python Database Connection Database
> schema mismatch: we speak 1378 but database speaks 1379
> Traceback (most recent call last):
> File "/home/jim/./find_orphans_jfa.py", line 223, in <module>
> DB = MythDB()
> File "/usr/local/lib/python3.10/dist-packages/MythTV/database.py", line
> 1272, in __init__
> elif self._testconfig(tmpconfig):
> File "/usr/local/lib/python3.10/dist-packages/MythTV/database.py", line
> 1301, in _testconfig
> self._check_schema(self._schema_value, self._schema_local,
> File "/usr/local/lib/python3.10/dist-packages/MythTV/database.py", line
> 1335, in _check_schema
> raise MythDBError(MythError.DB_SCHEMAMISMATCH, value, sver, local)
> MythTV.exceptions.MythDBError: Mismatched schema version for
> 'DBSchemaVer': database speaks version 1379, we speak version 1378
>
> Jim A
>
>
>
> I would look in /usr/local/share/perl/ and see if there are different
> version of the binding in different directories. Look for different version
> of MythTV.pm
>
> I don't speak perl but I would guess if you look at your perl --version
> you should have a corresponding directory in /usr/local/share/perl/ in
> which you should find a MythTV.pm.
>
> There is a dpkg command to see what a package installs and where I thing
> it is something like dpkg -L libmythtv-perl to see if the bindings are
> being installed in the correct directory for your version of Perl.
>
>
> Paul H.
>

BTW, the only items in /usr/local/lib are python3.10 and x86_64-linux-gnu

Jim A

On Wed, Oct 11, 2023 at 8:13?PM James Abernathy <jfabernathy@gmail.com>
wrote:

>
>
> On Wed, Oct 11, 2023 at 1:46?PM Roland Ernst <rcrernst@gmail.com> wrote:
>
>>
>>
>> On Wed, Oct 11, 2023 at 7:40?PM James Abernathy <jfabernathy@gmail.com>
>> wrote:
>>
>>>
>>>
>>> On Wed, Oct 11, 2023 at 1:30?PM Roland Ernst <rcrernst@gmail.com> wrote:
>>>
>>>>
>>>>
>>>> On Wed, Oct 11, 2023 at 6:42?PM Paul Harrison <mythtv@mythqml.net>
>>>> wrote:
>>>>
>>>>> On 11/10/2023 17:22, James Abernathy wrote:
>>>>>
>>>>>
>>>>> So I restored from a snapshot a few days before the last mythtv
>>>>>> update. As soon as I booted it ran the mythconverg backup on schema 1378.
>>>>>> Then I sudo apt update and upgrade, and now I am back to where the database
>>>>>> has indeed been updated to 1379 but the backup will not run because the
>>>>>> binding support schema is still 1378.
>>>>>>
>>>>>> Jim A
>>>>>>
>>>>>
>>>>> And I cannot run ./find_orphans_jfa.py for the same reason.
>>>>>
>>>>> 2023-10-11 12:20:20.226853 E [2272] Python Database Connection
>>>>> Database schema mismatch: we speak 1378 but database speaks 1379
>>>>> Traceback (most recent call last):
>>>>> File "/home/jim/./find_orphans_jfa.py", line 223, in <module>
>>>>> DB = MythDB()
>>>>> File "/usr/local/lib/python3.10/dist-packages/MythTV/database.py",
>>>>> line 1272, in __init__
>>>>> elif self._testconfig(tmpconfig):
>>>>> File "/usr/local/lib/python3.10/dist-packages/MythTV/database.py",
>>>>> line 1301, in _testconfig
>>>>> self._check_schema(self._schema_value, self._schema_local,
>>>>> File "/usr/local/lib/python3.10/dist-packages/MythTV/database.py",
>>>>> line 1335, in _check_schema
>>>>> raise MythDBError(MythError.DB_SCHEMAMISMATCH, value, sver, local)
>>>>> MythTV.exceptions.MythDBError: Mismatched schema version for
>>>>> 'DBSchemaVer': database speaks version 1379, we speak version 1378
>>>>>
>>>>> Jim A
>>>>>
>>>>>
>>>>>
>>>>> I would look in /usr/local/share/perl/ and see if there are different
>>>>> version of the binding in different directories. Look for different version
>>>>> of MythTV.pm
>>>>>
>>>>> I don't speak perl but I would guess if you look at your perl
>>>>> --version you should have a corresponding directory in /usr/local/share/perl/
>>>>> in which you should find a MythTV.pm.
>>>>>
>>>>> There is a dpkg command to see what a package installs and where I
>>>>> thing it is something like dpkg -L libmythtv-perl to see if the
>>>>> bindings are being installed in the correct directory for your version of
>>>>> Perl.
>>>>>
>>>>>
>>>>> Paul H.
>>>>>
>>>>
>>>> IMHO, Ubuntu ppa packages installs the bindings into /usr and not into
>>>> /usr/local and
>>>> the packages in /usr/local have precedence.
>>>> I guess, you did a local build/install somewhere in the past.
>>>> Try in a terminal
>>>> locate MythTV.pm
>>>> locate static.py
>>>>
>>>> Roland
>>>>
>>>
>>> jim@den-pc:~$ sudo dpkg -L libmythtv-perl
>>> /.
>>> /usr
>>> /usr/share
>>> /usr/share/doc
>>> /usr/share/doc/libmythtv-perl
>>> /usr/share/doc/libmythtv-perl/changelog.Debian.gz
>>> /usr/share/doc/libmythtv-perl/copyright
>>> /usr/share/perl5
>>> /usr/share/perl5/IO
>>> /usr/share/perl5/IO/Socket
>>> /usr/share/perl5/IO/Socket/INET
>>> /usr/share/perl5/IO/Socket/INET/MythTV.pm
>>> /usr/share/perl5/MythTV
>>> /usr/share/perl5/MythTV/Channel.pm
>>> /usr/share/perl5/MythTV/Program.pm
>>> /usr/share/perl5/MythTV/Recording.pm
>>> /usr/share/perl5/MythTV/StorageGroup.pm
>>> /usr/share/perl5/MythTV.pm
>>> ---------------
>>>
>>> jim@den-pc:~$ locate MythTV.pm
>>> /usr/share/perl5/MythTV.pm
>>> /usr/share/perl5/IO/Socket/INET/MythTV.pm
>>> jim@den-pc:~$ locate static.py
>>> /usr/lib/python3/dist-packages/MythTV/static.py
>>>
>>> JIm A
>>>
>>>
>> Your traceback from python shows
>> File "/usr/*local*/lib/python3.10/dist-packages/MythTV/database.py",
>>
>> Roland
>>
>
> I see what you mean, but I'm not sure how to recover from this. I just
> finished spinning up a Linux Mint Debian Edition (Faye) debian 12 system
> that has access to HDHR tuners. I have Mythtv v34 running on it with most
> of my critical recording rules duplication there. So I have some time to
> recover the production backend.
>
> I imagine that my only choice would be to completely rebuild, which I was
> planning to do at some point and switch it from Kubuntu to some flavor of
> Debian 12. My biggest issue is not Mythtv. This hardware is also my Home
> NAS. SO the only safe way to rebuild is to buy a new boot SSD and 2 new
> 4TB HDD for a 4TB mirror.
>
> So I'm willing to try some suggestions if you have any. I could uninstall
> mythtv and reinstall after deleting any /usr/local stuff if I can identify
> it all without killing what I have that is not mythtv related. I have a DB
> backup and all my recordings are on the NAS part of the system.
>
> Jim A
>
>
I would start with
sudo updatedb
and repeat the above search with locate.
The try to run for each mythtv program e.g.:
which mythbackend
and see if it is located in the /usr folder ( on Ubuntu, if installed,
replace 'mythfrontend' with 'mythfrontend.real'
Check this with
apt-cache policy
and
dpkg -l | grep myth

No need to re-install anything. Just remove the old remnants.

Roland

On Wed, Oct 11, 2023 at 2:30?PM Roland Ernst <rcrernst@gmail.com> wrote:

>
>
> I would start with
> sudo updatedb
> and repeat the above search with locate.
> The try to run for each mythtv program e.g.:
> which mythbackend
> and see if it is located in the /usr folder ( on Ubuntu, if installed,
> replace 'mythfrontend' with 'mythfrontend.real'
> Check this with
> apt-cache policy
> and
> dpkg -l | grep myth
>
> No need to re-install anything. Just remove the old remnants.
>
> Roland
>
>

Thanks, I think I'm making progress.

im@kubuntu-closet:~$ locate MythTV.pm
/usr/local/share/perl/5.34.0/MythTV.pm
/usr/local/share/perl/5.34.0/IO/Socket/INET/MythTV.pm
/usr/share/perl5/MythTV.pm
/usr/share/perl5/IO/Socket/INET/MythTV.pm

jim@kubuntu-closet:~$ locate static.py
/usr/lib/python3/dist-packages/MythTV/static.py
/usr/lib/python3/dist-packages/ansible_collections/fortinet/fortios/plugins/modules/fortios_router_static.py

It seems the python stuff is working as I can run ./find_orphans.py and
clean up the lost stuff. However when I run the backup script it still
fails because of thinking it's schema 1378

grep SCHEMA $(find /usr -name MythTV.pm 2>/dev/null) | head -1d -1
/usr/local/share/perl/5.34.0/MythTV.pm: our $SCHEMA_VERSION = "1378";

which perl
/usr/bin/perl

Not sure what is going on with perl. I have one in local that seems to be
getting updated occasionally.

jim@kubuntu-closet:~$ ls /usr/share/perl -l
lrwxrwxrwx 1 root root 6 Feb 6 2022 5.34 -> 5.34.0
drwxr-xr-x 1 root root 1990 Jun 6 13:58 5.34.0

jim@kubuntu-closet:~$ ls -l /usr/local/share/perl

drwxrwxr-x 1 root root 26 Jan 25 2022 5.32.1
drwxrwxr-x 1 root root 34 Jun 18 11:13 5.34.0
jim@kubuntu-closet:~$

Jim A

On Wed, Oct 11, 2023 at 3:16?PM James Abernathy <jfabernathy@gmail.com>
wrote:

>
>
> On Wed, Oct 11, 2023 at 2:30?PM Roland Ernst <rcrernst@gmail.com> wrote:
>
>>
>>
>> I would start with
>> sudo updatedb
>> and repeat the above search with locate.
>> The try to run for each mythtv program e.g.:
>> which mythbackend
>> and see if it is located in the /usr folder ( on Ubuntu, if installed,
>> replace 'mythfrontend' with 'mythfrontend.real'
>> Check this with
>> apt-cache policy
>> and
>> dpkg -l | grep myth
>>
>> No need to re-install anything. Just remove the old remnants.
>>
>> Roland
>>
>>
>
> Thanks, I think I'm making progress.
>
> im@kubuntu-closet:~$ locate MythTV.pm
> /usr/local/share/perl/5.34.0/MythTV.pm
> /usr/local/share/perl/5.34.0/IO/Socket/INET/MythTV.pm
> /usr/share/perl5/MythTV.pm
> /usr/share/perl5/IO/Socket/INET/MythTV.pm
>
> jim@kubuntu-closet:~$ locate static.py
> /usr/lib/python3/dist-packages/MythTV/static.py
>
> /usr/lib/python3/dist-packages/ansible_collections/fortinet/fortios/plugins/modules/fortios_router_static.py
>
> It seems the python stuff is working as I can run ./find_orphans.py and
> clean up the lost stuff. However when I run the backup script it still
> fails because of thinking it's schema 1378
>
> grep SCHEMA $(find /usr -name MythTV.pm 2>/dev/null) | head -1d -1
> /usr/local/share/perl/5.34.0/MythTV.pm: our $SCHEMA_VERSION = "1378";
>
> which perl
> /usr/bin/perl
>
> Not sure what is going on with perl. I have one in local that seems to be
> getting updated occasionally.
>
> jim@kubuntu-closet:~$ ls /usr/share/perl -l
> lrwxrwxrwx 1 root root 6 Feb 6 2022 5.34 -> 5.34.0
> drwxr-xr-x 1 root root 1990 Jun 6 13:58 5.34.0
>
> jim@kubuntu-closet:~$ ls -l /usr/local/share/perl
>
> drwxrwxr-x 1 root root 26 Jan 25 2022 5.32.1
> drwxrwxr-x 1 root root 34 Jun 18 11:13 5.34.0
> jim@kubuntu-closet:~$
>
> Jim A
>


FOUND IT. I moved the /usr/local/share/perl to a hidden place and now the
database backup stuff works.

$ locate MythTV.pm
/usr/share/perl5/MythTV.pm
/usr/share/perl5/IO/Socket/INET/MythTV.pm

$ locate static.py
/usr/lib/python3/dist-packages/MythTV/static.py
/usr/lib/python3/dist-packages/ansible_collections/fortinet/fortios/plugins/modules/fortios_router_static.py

Thanks for the help,

Jim A

On Wed, Oct 11, 2023 at 9:27?PM James Abernathy <jfabernathy@gmail.com>
wrote:

>
>
> On Wed, Oct 11, 2023 at 3:16?PM James Abernathy <jfabernathy@gmail.com>
> wrote:
>
>>
>>
>> On Wed, Oct 11, 2023 at 2:30?PM Roland Ernst <rcrernst@gmail.com> wrote:
>>
>>>
>>>
>>> I would start with
>>> sudo updatedb
>>> and repeat the above search with locate.
>>> The try to run for each mythtv program e.g.:
>>> which mythbackend
>>> and see if it is located in the /usr folder ( on Ubuntu, if installed,
>>> replace 'mythfrontend' with 'mythfrontend.real'
>>> Check this with
>>> apt-cache policy
>>> and
>>> dpkg -l | grep myth
>>>
>>> No need to re-install anything. Just remove the old remnants.
>>>
>>> Roland
>>>
>>>
>>
>> Thanks, I think I'm making progress.
>>
>> im@kubuntu-closet:~$ locate MythTV.pm
>> /usr/local/share/perl/5.34.0/MythTV.pm
>> /usr/local/share/perl/5.34.0/IO/Socket/INET/MythTV.pm
>> /usr/share/perl5/MythTV.pm
>> /usr/share/perl5/IO/Socket/INET/MythTV.pm
>>
>> jim@kubuntu-closet:~$ locate static.py
>> /usr/lib/python3/dist-packages/MythTV/static.py
>>
>> /usr/lib/python3/dist-packages/ansible_collections/fortinet/fortios/plugins/modules/fortios_router_static.py
>>
>> It seems the python stuff is working as I can run ./find_orphans.py and
>> clean up the lost stuff. However when I run the backup script it still
>> fails because of thinking it's schema 1378
>>
>> grep SCHEMA $(find /usr -name MythTV.pm 2>/dev/null) | head -1d -1
>> /usr/local/share/perl/5.34.0/MythTV.pm: our $SCHEMA_VERSION = "1378";
>>
>> which perl
>> /usr/bin/perl
>>
>> Not sure what is going on with perl. I have one in local that seems to be
>> getting updated occasionally.
>>
>> jim@kubuntu-closet:~$ ls /usr/share/perl -l
>> lrwxrwxrwx 1 root root 6 Feb 6 2022 5.34 -> 5.34.0
>> drwxr-xr-x 1 root root 1990 Jun 6 13:58 5.34.0
>>
>> jim@kubuntu-closet:~$ ls -l /usr/local/share/perl
>>
>> drwxrwxr-x 1 root root 26 Jan 25 2022 5.32.1
>> drwxrwxr-x 1 root root 34 Jun 18 11:13 5.34.0
>> jim@kubuntu-closet:~$
>>
>> Jim A
>>
>
>
> FOUND IT. I moved the /usr/local/share/perl to a hidden place and now the
> database backup stuff works.
>
> $ locate MythTV.pm
> /usr/share/perl5/MythTV.pm
> /usr/share/perl5/IO/Socket/INET/MythTV.pm
>
> $ locate static.py
> /usr/lib/python3/dist-packages/MythTV/static.py
>
> /usr/lib/python3/dist-packages/ansible_collections/fortinet/fortios/plugins/modules/fortios_router_static.py
>
> Thanks for the help,
>
> Jim A
>
> Great, and for the python bindings, a
locate database.py
does only find the file in
/usr/lib/python3/dist-packages/MythTV/ ?

Roland

On Wed, Oct 11, 2023 at 3:53?PM Roland Ernst <rcrernst@gmail.com> wrote:

>
>
> On Wed, Oct 11, 2023 at 9:27?PM James Abernathy <jfabernathy@gmail.com>
> wrote:
>
>>
>>
>> On Wed, Oct 11, 2023 at 3:16?PM James Abernathy <jfabernathy@gmail.com>
>> wrote:
>>
>>>
>>>
>>> On Wed, Oct 11, 2023 at 2:30?PM Roland Ernst <rcrernst@gmail.com> wrote:
>>>
>>>>
>>>>
>>>> I would start with
>>>> sudo updatedb
>>>> and repeat the above search with locate.
>>>> The try to run for each mythtv program e.g.:
>>>> which mythbackend
>>>> and see if it is located in the /usr folder ( on Ubuntu, if installed,
>>>> replace 'mythfrontend' with 'mythfrontend.real'
>>>> Check this with
>>>> apt-cache policy
>>>> and
>>>> dpkg -l | grep myth
>>>>
>>>> No need to re-install anything. Just remove the old remnants.
>>>>
>>>> Roland
>>>>
>>>>
>>>
>>> Thanks, I think I'm making progress.
>>>
>>> im@kubuntu-closet:~$ locate MythTV.pm
>>> /usr/local/share/perl/5.34.0/MythTV.pm
>>> /usr/local/share/perl/5.34.0/IO/Socket/INET/MythTV.pm
>>> /usr/share/perl5/MythTV.pm
>>> /usr/share/perl5/IO/Socket/INET/MythTV.pm
>>>
>>> jim@kubuntu-closet:~$ locate static.py
>>> /usr/lib/python3/dist-packages/MythTV/static.py
>>>
>>> /usr/lib/python3/dist-packages/ansible_collections/fortinet/fortios/plugins/modules/fortios_router_static.py
>>>
>>> It seems the python stuff is working as I can run ./find_orphans.py and
>>> clean up the lost stuff. However when I run the backup script it still
>>> fails because of thinking it's schema 1378
>>>
>>> grep SCHEMA $(find /usr -name MythTV.pm 2>/dev/null) | head -1d -1
>>> /usr/local/share/perl/5.34.0/MythTV.pm: our $SCHEMA_VERSION = "1378";
>>>
>>> which perl
>>> /usr/bin/perl
>>>
>>> Not sure what is going on with perl. I have one in local that seems to
>>> be getting updated occasionally.
>>>
>>> jim@kubuntu-closet:~$ ls /usr/share/perl -l
>>> lrwxrwxrwx 1 root root 6 Feb 6 2022 5.34 -> 5.34.0
>>> drwxr-xr-x 1 root root 1990 Jun 6 13:58 5.34.0
>>>
>>> jim@kubuntu-closet:~$ ls -l /usr/local/share/perl
>>>
>>> drwxrwxr-x 1 root root 26 Jan 25 2022 5.32.1
>>> drwxrwxr-x 1 root root 34 Jun 18 11:13 5.34.0
>>> jim@kubuntu-closet:~$
>>>
>>> Jim A
>>>
>>
>>
>> FOUND IT. I moved the /usr/local/share/perl to a hidden place and now
>> the database backup stuff works.
>>
>> $ locate MythTV.pm
>> /usr/share/perl5/MythTV.pm
>> /usr/share/perl5/IO/Socket/INET/MythTV.pm
>>
>> $ locate static.py
>> /usr/lib/python3/dist-packages/MythTV/static.py
>>
>> /usr/lib/python3/dist-packages/ansible_collections/fortinet/fortios/plugins/modules/fortios_router_static.py
>>
>> Thanks for the help,
>>
>> Jim A
>>
>> Great, and for the python bindings, a
> locate database.py
> does only find the file in
> /usr/lib/python3/dist-packages/MythTV/ ?
>
> Roland
>

Yes,
/usr/lib/python3/dist-packages/MythTV/database.py

JIm A