Mailing List Archive

metadata lookup not working on Debian
I'm testing Master on both Ubuntu 22.04 and Debian 12. I've noticed that in
recent days I've started getting error exit 128 on Metadata lookup on shows
that normally work fine but only on Debian 12.

As a test as user mythtv I ran:

mythmetadatalookup --refresh-all
on both systems and on Ubuntu I see:

2023-07-01 06:32:20.472224 I Testing grabbers and metadata sites for
functionality...
2023-07-01 06:32:20.472683 I Starting process signal handler
2023-07-01 06:32:20.472712 I Starting process manager
2023-07-01 06:32:20.472749 I Starting IO manager (read)
2023-07-01 06:32:20.473802 I Starting IO manager (write)
2023-07-01 06:32:21.274655 I All grabbers tested and working.
Continuing...
2023-07-01 06:32:21.281956 N MythMetadataLookup run complete.

But on Debian 12 I see:

2023-07-01 06:31:04.407539 I Testing grabbers and metadata sites for
functionality...
2023-07-01 06:31:04.411152 I Starting process signal handler
2023-07-01 06:31:04.411323 I Starting process manager
2023-07-01 06:31:04.411621 I Starting IO manager (read)
2023-07-01 06:31:04.419909 I Starting IO manager (write)
2023-07-01 06:31:04.562001 I Movie grabber not functional. Aborting this
run.

The Ubuntu mythtv is from the ppa:mythbuntu/34.
On Debian 12 the packages are built following the wiki:
https://www.mythtv.org/wiki/Installing_MythTV_on_Debian

the changes I used for Master were:

cd ~/build
git clone https://github.com/MythTV/packaging.git
cd packaging/deb
./build-debs.sh master

It's only in the last week that I've noticed the lost of the Metadata and
the exit 128 code, but only on Debian 12

Jim A
Re: metadata lookup not working on Debian [ In reply to ]
On Saturday 01 July 2023 05:46:10 AM (-05:00), James Abernathy wrote:

> I'm testing Master on both Ubuntu 22.04 and Debian 12. I've noticed that
in
> recent days I've started getting error exit 128 on Metadata lookup on
shows
> that normally work fine but only on Debian 12.
>
> As a test as user mythtv I ran:
>
> mythmetadatalookup --refresh-all
> on both systems and on Ubuntu I see:
>
> 2023-07-01 06:32:20.472224 I Testing grabbers and metadata sites for
> functionality...
> 2023-07-01 06:32:20.472683 I Starting process signal handler
> 2023-07-01 06:32:20.472712 I Starting process manager
> 2023-07-01 06:32:20.472749 I Starting IO manager (read)
> 2023-07-01 06:32:20.473802 I Starting IO manager (write)
> 2023-07-01 06:32:21.274655 I All grabbers tested and working.
> Continuing...
> 2023-07-01 06:32:21.281956 N MythMetadataLookup run complete.
>
> But on Debian 12 I see:
>
> 2023-07-01 06:31:04.407539 I Testing grabbers and metadata sites for
> functionality...
> 2023-07-01 06:31:04.411152 I Starting process signal handler
> 2023-07-01 06:31:04.411323 I Starting process manager
> 2023-07-01 06:31:04.411621 I Starting IO manager (read)
> 2023-07-01 06:31:04.419909 I Starting IO manager (write)
> 2023-07-01 06:31:04.562001 I Movie grabber not functional. Aborting
this
> run.
>
> The Ubuntu mythtv is from the ppa:mythbuntu/34.
> On Debian 12 the packages are built following the wiki:
> https://www.mythtv.org/wiki/Installing_MythTV_on_Debian
>
> the changes I used for Master were:
>
> cd ~/build
> git clone https://github.com/MythTV/packaging.git
> cd packaging/deb
> ./build-debs.sh master
>
> It's only in the last week that I've noticed the lost of the Metadata
and
> the exit 128 code, but only on Debian 12
>
> Jim A
>
If you add the --verbose system switch to the command, you'll see the
started and exited couplets. The commands will be similar to this:


/usr/share/mythtv/metadata/Movie/tmdb3.py -v


and you can run that from the command line to see what's failing.

--
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
Re: metadata lookup not working on Debian [ In reply to ]
On Sat, Jul 1, 2023 at 8:04?AM Bill Meek <keemllib@gmail.com> wrote:

>
> On Saturday 01 July 2023 05:46:10 AM (-05:00), James Abernathy wrote:
>
> > I'm testing Master on both Ubuntu 22.04 and Debian 12. I've noticed
> that
> in
> > recent days I've started getting error exit 128 on Metadata lookup on
> shows
> > that normally work fine but only on Debian 12.
> >
> > As a test as user mythtv I ran:
> >
> > mythmetadatalookup --refresh-all
> > on both systems and on Ubuntu I see:
> >
> > 2023-07-01 06:32:20.472224 I Testing grabbers and metadata sites for
> > functionality...
> > 2023-07-01 06:32:20.472683 I Starting process signal handler
> > 2023-07-01 06:32:20.472712 I Starting process manager
> > 2023-07-01 06:32:20.472749 I Starting IO manager (read)
> > 2023-07-01 06:32:20.473802 I Starting IO manager (write)
> > 2023-07-01 06:32:21.274655 I All grabbers tested and working.
> > Continuing...
> > 2023-07-01 06:32:21.281956 N MythMetadataLookup run complete.
> >
> > But on Debian 12 I see:
> >
> > 2023-07-01 06:31:04.407539 I Testing grabbers and metadata sites for
> > functionality...
> > 2023-07-01 06:31:04.411152 I Starting process signal handler
> > 2023-07-01 06:31:04.411323 I Starting process manager
> > 2023-07-01 06:31:04.411621 I Starting IO manager (read)
> > 2023-07-01 06:31:04.419909 I Starting IO manager (write)
> > 2023-07-01 06:31:04.562001 I Movie grabber not functional. Aborting
> this
> > run.
> >
> > The Ubuntu mythtv is from the ppa:mythbuntu/34.
> > On Debian 12 the packages are built following the wiki:
> > https://www.mythtv.org/wiki/Installing_MythTV_on_Debian
> >
> > the changes I used for Master were:
> >
> > cd ~/build
> > git clone https://github.com/MythTV/packaging.git
> > cd packaging/deb
> > ./build-debs.sh master
> >
> > It's only in the last week that I've noticed the lost of the Metadata
> and
> > the exit 128 code, but only on Debian 12
> >
> > Jim A
> >
> If you add the --verbose system switch to the command, you'll see the
> started and exited couplets. The commands will be similar to this:
>
>
> /usr/share/mythtv/metadata/Movie/tmdb3.py -v
>
>
> and you can run that from the command line to see what's failing.
>
> --
> Bill


I assumed that it was a package build issue since it worked fine on Ubuntu.
I created a new Debian 12 Minimal server VM and built a current setup of
Master packages. After putting those new packages in my NAS Debian repo, I
apt upgraded my test debian 12 backend and frontend. Now the metadata
lookups work. I requeued all the ones with the exit 128 and now they worked
without error and all had the complete setup of metadata.

So what I've learned is to not trust building packages in the same
directory as the last time. My method which seems to have worked for weeks
is to:
cd ~/build/package/deb/
git pull
./build-debs.sh master

However, something didn't get done correctly in regards to the code that
does the metadata lookup. So I guess the new method is to put:
rm ~/build/*
as the first statement and complete start over. I don't think this will
add more than a minute or 2 to the build process.

Jim A