[mythtv-users] MythSocket(27f9020:71): readStringList: Error, timed out after 7000 ms

[Michael A Weber]

In a recent attempt to do some updating from 0.24, I have now encountered this problem that is not an occasional deadlocked BE for me, but an occasional NOT deadlocked BE.

I had been running 0.24 on CentOS 6.2 with a few crashes here and there, but nothing too terrible.  Some CentOS packages had been updated, so I grabbed those updates and reached for 0.25.2 for Myth as well.

After checking all prerequisites and compiling, I installed, updated the database from mythtv-setup when prompted, then ran the BE.  All looked good.  I launched the FE on that same box (combined BE/FE), and there was a lot of waiting and things just weren't working.  In the logs in the database, I see the above-listed error message posted by the FE with no errors listed from the BE.  I even put the BE into debug logging level and still didn't see anything.

There is one strange situation, however.  I also run a remote FE on Mac OS X and that, too, experiences poor function and posts to the database the same timed out error message above.  BUT…  if I put that FE to the Watch Recordings screen and let it sit in that state, unable to get anything, and restart the BE, for one time only the client gets added and the FE pulls up the information from the BE and logs a Protocol 72 usage.  Shortly thereafter, it begins its incessant timed out after 7000 ms error again.

Thinking this may be a problem with 0.25.2 and my distro, I reached for 0.26 beta, and got the exact same results on my CentOS BE/FE.  I didn't do the test with Mac OS X because I didn't compile a FE app for that box.

So, since I'm finding some errors like mine in all my Google searching, I'm sort of relieved to know that I'm not the only one having this issue.  But, there are not a lot of the errors, and I still have no idea at a solution.  I'm not convinced it's not a problem with the MythTV code, but I'm also not blaming the code since it's now happening with my distro update.

Does anyone have any idea where I can begin to try to remedy this?  Does anyone know if it's serverpool.cpp that is needing something in particular from my distro that seemed OK enough for compilation but is not correct for operation?

Any help would be greatly appreciated as I'm now about 48 hours into this from a simple update.

Mike