| LinHES Forums http://forum.linhes.org/ |
|
| Backend appears to be hung http://forum.linhes.org/viewtopic.php?f=6&t=11243 |
Page 1 of 1 |
| Author: | marc.aronson [ Tue Aug 22, 2006 8:58 am ] |
| Post subject: | Backend appears to be hung |
After sevarl weeks of stable running, I've run into a problem where the backend appaers to be hung when I check it n the morning. It looks like the problem is happening every other day. The first symptom shows up when I call mythweb from my browser and see the following: Code: -------------------------------------------------------------------------------- User Notice at /usr/share/mythtv/mythweb/includes/mythbackend.php, line 159: Unexpected response to MYTH_PROTO_VERSION 'MYTH_PROTO_VERSION 15': -------------------------------------------------------------------------------- -------------------------------------------------------------------------------- Fatal Error at /usr/share/mythtv/mythweb/includes/mythbackend.php, line 32: Unable to connect to mythbackend, is it running? The system administrator has been notified and the problem will be remedied shortly. -------------------------------------------------------------------------------- This morning mythbackend.log only had a few lines, so I am also including the last chunk of mthbackend.log.1 Code: The last few lines of mythback.log.1 contains
--01:43:29-- http://datadirect.webservices.zap2it.com/tvlistings/xtvdService => `-' Resolving datadirect.webservices.zap2it.com... 206.18.98.160 Connecting to datadirect.webservices.zap2it.com[206.18.98.160]:80... connected. HTTP request sent, awaiting response... 401 Unauthorized Connecting to datadirect.webservices.zap2it.com[206.18.98.160]:80... connected. HTTP request sent, awaiting response... 200 OK Length: unspecified [text/xml] 0K .......... .......... .......... .......... .......... 19.69 KB/s 50K .......... .......... .......... .......... .......... 157.87 KB/s 100K .......... .......... .......... .......... .......... 215.96 KB/s 150K .......... .......... .......... .......... .......... 168.83 KB/s 200K .......... .......... .......... .......... .......... 123.79 KB/s 250K .......... .......... .......... .......... ....... 125.74 KB/s 01:43:37 (71.45 KB/s) - `-' saved [305007] Your subscription expires on 10/09/06 03:37:58 2006-08-22 01:44:01.843 Connecting to backend server: 192.168.0.11:6543 (try 1 of 5) 2006-08-22 01:44:02.748 Using protocol version 15 2006-08-22 01:44:02.764 MainServer::HandleAnnounce Playback 2006-08-22 01:44:02.768 adding: mythhd as a client (events: 0) 2006-08-22 01:44:02.802 unknown socket mythback.log contains only the following lines: 2006-08-22 07:19:24.634 MainServer::HandleAnnounce Playback 2006-08-22 07:19:24.640 adding: mythhd as a client (events: 0) A few more observations: 1. I've looked at messages and kern.log -- nothing much there. 2. ps auxw | grep mythback shows that the backend process still exists. 3. Running "top" shows that no CPU time is being consumed. The system is idle. I am running R5A30.2. Any help would be greatly apprecaited. marc |
|
| Author: | nickread [ Tue Aug 22, 2006 6:58 pm ] |
| Post subject: | |
The last time I had this sort of problem, it was due to the / partition being full. This (as in my case) is usually due to overflowing logs (often mysql.log). Try 'df' to get a summary of your file system situation. |
|
| Author: | marc.aronson [ Tue Aug 22, 2006 7:17 pm ] |
| Post subject: | |
nickread, thanks for replying. I've already checked that and unfortunately, that's not my problem. The interesting thing is that the backend process is still there, it simply isn't responding... Marc Code: Filesystem Size Used Avail Use% Mounted on
/dev/hda1 3.9G 2.4G 1.4G 65% / /dev/hda3 12G 24K 12G 1% /cache /dev/vg/myth 343G 272G 72G 80% /myth |
|
| Author: | nickread [ Tue Aug 22, 2006 7:49 pm ] |
| Post subject: | |
Hmm - does killing/restarting the backend resolve it or do you need to reboot? Or something else? Maybe a network issue? |
|
| Author: | marc.aronson [ Tue Aug 22, 2006 11:09 pm ] |
| Post subject: | |
I do not need to reboot -- a simple "restart" of the backend solves the problem. I do have a suspicion it has something to do with running "mythfilldatabase", as the problem always happens after one of these operations has been run. But I can't be sure, since typically I am checking in on things several hours after the mythfilldatabase run has completed. Also, there are times that mythfilldatabase runs and this problem doesn't happen. Having siad this, it is consistantly the case that the last thing that completed successfully in the backend logs is a mythfilldatabase run... |
|
| Author: | tjc [ Tue Aug 22, 2006 11:22 pm ] |
| Post subject: | |
Try running the reschedule by hand and see if it triggers your problem... Code: /usr/bin/mythbackend --resched
|
|
| Author: | marc.aronson [ Wed Aug 23, 2006 9:02 am ] |
| Post subject: | |
tjc, thank you for the suggestion. I tried the "--resched" as suggested, but the problem did not happen. I also tried maually running "mythfilldatabase" and the problem did not happen, so either the problem is unrelated to mythfilldatabase and the re-schedule or there is another factor at play. Marc |
|
| Page 1 of 1 | All times are UTC - 6 hours |
| Powered by phpBB® Forum Software © phpBB Group http://www.phpbb.com/ |
|