Closed ekristen closed 13 years ago
Here is the info. Hopefully it helps.
Just an update with my setup here, I loaded up a XP SP3 box and it connected just fine to the MythTV. So, just my Windows 7 x64 box is having problems.
I will be asking for help with this soon, I have to modify the mysql library and add some debug code to find out what sql queries are happening when it fails. When I get the modifications done I will post the new library up for use by those having the issue for testing.
Download http://github.com/ekristen/mythboxee/raw/interface/mysql/connector/cursor.py and replace in your mythboxee install, then reproduce the error, I think for most of you it is just by running the app. Post logs at http://mythboxee.pastebin.com/ and then paste the links here.
On my Vista box. http://mythboxee.pastebin.com/HjR7miVD
Opened a new ticket with the mysql library developer, hopefully he might be able to shed some light on the error message at least.
Ok. This is weird. I went into mythboxee on my Windows 7 x64 box and tried to load it up (before putting in your new cursor.py file) and it started off as having the same issue as #6 (missing configuration settings). So I only went out of mythboxee and then started it again and then my tv show were there and I could play them. Hmm...
If you have only run boxee twice then there will be two logs, boxee.log which is the latest and boxee.log.old which will be the one before. If you can post both to http://mythboxee.pastebin.com
Now after updating to 4.4.23.1.beta can't make it work like before. For some reason I can't post to pastebin, so I'm emailing my recent log to you.
Updated to 4.4.23.1 beta and still have the interface error on my Vista box. http://mythboxee.pastebin.com/Y1UgPgJj I will test it out soon on Ubuntu 10.04.
Matt, can you update your cursor.py file to http://github.com/ekristen/mythboxee/raw/interface/mysql/connector/cursor.py and re-post the log? Also if you can look at the log, see what the last query to be executed before the error is thrown, and run that manually through phpmyadmin and post the data returned that would also be helpful. Thanks.
Ok, I replaced cursor.py with the new one. Here is my new log. http://mythboxee.pastebin.com/XqPc8w7A What is it from there that you want me to check out in phpmyadmin? I see in the error log that on line 287 it says "18:47:55 T:5268 M:1276375040 NOTICE: SELECT * FROM recorded WHERE chanid=2140 AND starttime='2010-07-15 21:00:00'" right before the errors start to get spit back. In that table from phpmyadmin it refers to "Futurama The Duh-Vinci Code The crew races to future Rome to unearth the shock... Sitcom".
Is that what you're looking for? If not then I need you to explain what to do exactly. Thanks for working on tracking down these errors!
I looked at a 2nd log and I am pretty sure that I didn't do what you asked cause the show that I thought it got hung up on kept on changing. Whenever you're ready to work on this I'm going to need some guidance on what to do.
Well at this point I have no clue what the problem is, just keep posting logs here, the more I have the better I would image. Unfortunately it is no one query or no one thing that is causing the error to occur. It just happens randomly on all Windows Systems :(
First log with the brand new cursor file http://mythboxee.pastebin.com/eDn9ZGhF Second log, this time it seemed to have gone through more shows before the error happened. http://mythboxee.pastebin.com/nkKCzVuT
And at least now its a different error. "Empty buffer" mean anything to you?
I tried the new cursor.py file and got the same "Empty buffer" error.
Too many changes to list. Rewrote the entire mythboxee.py file, split code into classes mainly. Closed by 4dc12973561ad015c2bb1fc959dc6b26120807d3, #2, #4, #6
For unknown reasons on Windows systems only at this point the mysql library I am using throws an InterfaceError.
Known versions to be affected at this are:
If you are experiencing this error, please add a comment with the following information of your system: