<html><head></head><body><div style="font-family: Verdana;font-size: 12.0px;"><div>> I'm seeing the same issue. I'm on the latest 0.27.4 release (v0.27.4-6-ge0b0027). The frontend can sometimes lock up for several minutes. I have remote frontends but they are on the same version. Sometimes mythbackend goes to 100% CPU and is unresponsive to all clients including mythweb. It started happening since I upgraded to 0.27 and Ubuntu 14.04 (on the latest version).<br/>
><br/>
> On the backend I'm seeing problems keeping connected with the client. See log below.<br/>
</div>
<div> </div>
<div> </div>
<div>I managed to solve this problem. The backend had locked up which is why the communications between the frontend and the backend was failing which was shown by the WriteStringList error messages. </div>
<div>The backend was becoming deadlocked due to the EIT scanner. Some recent changes in 0.27 must have caused it. So I disabled the EIT scanner and all was fine.</div>
<div> </div>
<div>Going into more detail; I had the EIT scanner off in the video source (I'm using xmltv grabber) but it was still on in the capture card settings (in the card's Recording Options). I had EIT enabled on all cards which I have read in the EIT wiki can cause problems.</div>
<div> </div>
<div>Finding the problem was quite tricky because the logs weren't that helpful. The only error messages were the WriteStringList messages. To find the problem I used gcore to generate a core dump while it was locked up and a core dump of when it was not locked up. After doing a thread backtrace on each core file and comparing the two I noticed there were multiple EIT grabbing threads (see the wiki on Debugging for more info). The locking only occurred while recording so I think its a conflict between EIT grabbing and recording at the same time. I have 4 Haupauge Nova-T's and a TBS 6920. So this is either a bug or a problem with setting EIT grabbing on all of my capture cards. The WriteStringList error messages are to do with sockets on the frontend timing out because the backend was busy. The messages on the backend are caused by trying to write to sockets that the frontend disconnected because of the timeouts.</div>
<div> </div>
<div>EIT scanning might not be the original posters problem but it may be due to the backend locking up for some reason so its worth investigating.</div>
<div> </div>
<div>Hope this helps.</div>
<div> </div>
<div>Paul</div></div></body></html>