tmdb3.py crashed with TMDBRequestInvalid in handle_status(): Invalid id - The pre-requisite id is invalid or not found.

[brik]

I think this is just a info not found, it shouldnt generate a "crash"

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: mythtv-common 2:0.26.1+fixes.20140322.1a4cebf-0ubuntu0mythbuntu1 [origin: LP-PPA-mythbuntu-0.26]
ProcVersionSignature: Ubuntu 3.2.0-60.91-generic-pae 3.2.55
Uname: Linux 3.2.0-60-generic-pae i686
.var.log.mythtv.mythavtest.log:

.var.log.mythtv.mythccextractor.log:

.var.log.mythtv.mythjobqueue.log:

.var.log.mythtv.mythlcdserver.log:

.var.log.mythtv.mythmediaserver.log:

.var.log.mythtv.mythshutdown.log:

.var.log.mythtv.mythutil.log:

.var.log.mythtv.mythwelcome.log:

ApportVersion: 2.0.1-0ubuntu17.6
Architecture: i386
CrashDB: mythbuntu
Date: Fri Apr 11 12:00:28 2014
ExecutablePath: /usr/share/mythtv/metadata/Movie/tmdb3.py
InstallationMedia: Mythbuntu 12.04.1 "Precise Pangolin" - Release i386 (20120818.1)
Installed_mythtv_dbg: 0.0
InterpreterPath: /usr/bin/python2.7
MarkForUpload: True
ProcCmdline: python /usr/share/mythtv/metadata/Movie/tmdb3.py -l en -D 100981
ProcEnviron:
 TERM=xterm
 SHELL=/bin/bash
 PATH=(custom, no user)
 LANG=en_US.UTF-8
PythonArgs: ['/usr/share/mythtv/metadata/Movie/tmdb3.py', '-l', 'en', '-D', '100981']
SourcePackage: mythtv
Title: tmdb3.py crashed with TMDBRequestInvalid in handle_status(): Invalid id - The pre-requisite id is invalid or not found.
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip fuse lpadmin mythtv nopasswdlogin plugdev sambashare sudo video

[Stefan Pappalardo (sjuk)]

Was it a recording mythtv did the search for?
And was it a tv series?
Was it "Shark Tank" (http://thetvdb.com/?tab=series&id=100981)?

Then there could be more wrong than the crash. Mythtv choosed tmdb3.py (http://thetvdb.com, specialized on movies)
and not ttvdb.py (http://thetvdb.com specialized for tv series).

I informed the mythtv developers of the bug (https://code.mythtv.org/trac/ticket/12103).
But I think they are focused on other things.

[brik (brian-peppel)]

Hey, I'm fairly certain it was an OTA recording that kicked off the error.
I'm not sure what log to look at to follow the chain of events that led to
the error. I don't have images, I do have description and info, for a
recording from yesterday (The This Old House Hour). I don't know if that is
the search that caused the crash.

I do record Shark Tank, my last recording was a week ago and I do have meta
data images, etc for it.

On Fri, Apr 11, 2014 at 2:29 PM, Stefan Pappalardo <<email address hidden>
> wrote:

> Was it a recording mythtv did the search for?
> And was it a tv series?
> Was it "Shark Tank" (http://thetvdb.com/?tab=series&id=100981)?
>
> Then there could be more wrong than the crash. Mythtv choosed tmdb3.py (
> http://thetvdb.com, specialized on movies)
> and not ttvdb.py (http://thetvdb.com specialized for tv series).
>
> I informed the mythtv developers of the bug (
> https://code.mythtv.org/trac/ticket/12103).
> But I think they are focused on other things.
>
> ** Bug watch added: code.mythtv.org/trac/ #12103
> http://code.mythtv.org/trac/ticket/12103
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1306707
>
> Title:
> tmdb3.py crashed with TMDBRequestInvalid in handle_status(): Invalid
> id - The pre-requisite id is invalid or not found.
>
> Status in Mythbuntu, Ubuntu derivative focused upon MythTV:
> New
>
> Bug description:
> I think this is just a info not found, it shouldnt generate a "crash"
>
> ProblemType: Crash
> DistroRelease: Ubuntu 12.04
> Package: mythtv-common
> 2:0.26.1+fixes.20140322.1a4cebf-0ubuntu0mythbuntu1 [origin:
> LP-PPA-mythbuntu-0.26]
> ProcVersionSignature: Ubuntu 3.2.0-60.91-generic-pae 3.2.55
> Uname: Linux 3.2.0-60-generic-pae i686
> .var.log.mythtv.mythavtest.log:
>
> .var.log.mythtv.mythccextractor.log:
>
> .var.log.mythtv.mythjobqueue.log:
>
> .var.log.mythtv.mythlcdserver.log:
>
> .var.log.mythtv.mythmediaserver.log:
>
> .var.log.mythtv.mythshutdown.log:
>
> .var.log.mythtv.mythutil.log:
>
> .var.log.mythtv.mythwelcome.log:
>
> ApportVersion: 2.0.1-0ubuntu17.6
> Architecture: i386
> CrashDB: mythbuntu
> Date: Fri Apr 11 12:00:28 2014
> ExecutablePath: /usr/share/mythtv/metadata/Movie/tmdb3.py
> InstallationMedia: Mythbuntu 12.04.1 "Precise Pangolin" - Release i386
> (20120818.1)
> Installed_mythtv_dbg: 0.0
> InterpreterPath: /usr/bin/python2.7
> MarkForUpload: True
> ProcCmdline: python /usr/share/mythtv/metadata/Movie/tmdb3.py -l en -D
> 100981
> ProcEnviron:
> TERM=xterm
> SHELL=/bin/bash
> PATH=(custom, no user)
> LANG=en_US.UTF-8
> PythonArgs: ['/usr/share/mythtv/metadata/Movie/tmdb3.py', '-l', 'en',
> '-D', '100981']
> SourcePackage: mythtv
> Title: tmdb3.py crashed with TMDBRequestInvalid in handle_status():
> Invalid id - The pre-requisite id is invalid or not found.
> UpgradeStatus: No upgrade log present (probably fresh install)
> UserGroups: adm cdrom dip fuse lpadmin mythtv nopasswdlogin plugdev
> sambashare sudo video
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/mythbuntu/+bug/1306707/+...

[j spam (knowtrash2009)]

What ever this bug is. I see it quite alot, but can not submitted that often, because my software needs to be updated to current ones.

[j spam (knowtrash2009)]

Yes, this bug is still out there. hope this data helps to resolve the issue, what ever it ends up being.

[j spam (knowtrash2009)]

Yes, it does happen alot. this is only one day later.

[Thomas Mashos (tgm4883)]

We really do appreciate you opening this ticket to help improve Mythbuntu, but it needs to be closed for a number of reasons. The biggest one is that upstream has moved on to a new version and believes this to be fixed. Could you please verify if this issue still exists in the latest version?

Please do not let the closing of this ticket dissuade you from opening a new ticket if this (or any other) problem occurs with the newer versions.

[j spam (knowtrash2009)]

here is the error again. is the version being reported by my logs the old mythtv or the new one that you mentioned? my system was changed early last year to update mythtv on a very agressive schedule.