jamu.py crashed with timeout in recv()

[Aaron Whitehouse]

Binary package hint: mythplugins

Sorry, I don't know what went wrong -- hopefully the attachments explain.

ProblemType: Crash
DistroRelease: Ubuntu 10.04
Package: mythvideo 0.23.0+fixes23825-0ubuntu1
ProcVersionSignature: Ubuntu 2.6.32-19.28-generic 2.6.32.10+drm33.1
Uname: Linux 2.6.32-19-generic x86_64
NonfreeKernelModules: nvidia
Architecture: amd64
Date: Sun Apr 11 09:21:08 2010
ExecutablePath: /usr/share/mythtv/mythvideo/scripts/jamu.py
InstallationMedia: Mythbuntu 10.04 "Lucid Lynx" - Beta amd64 (20100318)
Installed_mythplugins-dbg: 0.0
Installed_mythtv-dbg: 0.0
InterpreterPath: /usr/bin/python2.6
ProcCmdline: /usr/bin/python /usr/share/mythtv/mythvideo/scripts/jamu.py -MW
ProcEnviron:
 LANG=en_NZ.UTF-8
 SHELL=/bin/sh
PythonArgs: ['/usr/share/mythtv/mythvideo/scripts/jamu.py', '-MW']
SourcePackage: mythplugins
Title: jamu.py crashed with timeout in recv()
UserGroups: audio cdrom dialout video

[MarcRandolph (mrand)]

Thank you for helping to improve Mythbuntu by opening this ticket. I am marking this ticket as confirmed because it appears to have enough information to help the developers understand the problem. It is possible I am wrong and another more experienced triager or developer may adjust the status of the ticket to "incomplete" and request additional information.

[doug (r-d-vaughan)]

From the trace this looks like a time out between the Python bindings and the MythTV data base.

Has this happen just once or is this a frequent occurrence? Are other data base related activities working? Such as viewing your the Watch Recordings screen which is the data base request that was being executed (getRecordings() function).

As this code is used with every jamu run of the "-MW" options and it is not been reported before, I suspect that this is one of the following:
A one-off error, installation error, database server issue or network issue.

[MarcRandolph (mrand)]

Closing since no response was given to developer and he believes it is unlikely a problem with jamu itself. If you can reproduce this problem, please feel free to re-open with more info.