<div class="gmail_quote">On Tue, Apr 17, 2012 at 9:51 PM, Keith Pyle <span dir="ltr"><<a href="mailto:kpyle@austin.rr.com">kpyle@austin.rr.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
On 04/16/12 22:54, Jerry Rubinow:<div class="im"><br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
My mythbackend computer locked up today, the whole computer, not just<br>
mythbackend. Following is the syslog at the time this happened. It's been<br>
rock steady for months, and I haven't made any changes lately. I rebooted<br>
and now it seems to be functioning normally.<br>
<br>
Any suggestions for what I should do? Is this a sign of disk errors?<br>
</blockquote></div>
I initially missed your message among the plethora of opinions on the proper use of this list.<br>
<br>
I consulted my kernel expert and he suggested you try to examine the syslog about 2-3 minutes before the first entry you posted. It appears you're using JFS and it seems that a JFS write by mythbackend was blocked, possibly because some other process had a lock on the filesystem. The first message shows that mythbackend had already been blocked for 2 minutes, so you might find a clue as to the problem 2-3 minutes before this message.</blockquote>
<div><br></div><div>Here are the immediately preceding lines to the first mythbackend call trace:</div><div><br></div><div><div>Apr 16 22:09:53 kenny dhclient: DHCPREQUEST of 192.168.1.3 on eth0 to 192.168.1.1 port 67</div>
<div>Apr 16 22:09:53 kenny dhclient: DHCPACK of 192.168.1.3 from 192.168.1.1</div><div>Apr 16 22:09:53 kenny dhclient: bound to 192.168.1.3 -- renewal in 33144 seconds.</div><div>Apr 16 22:17:02 kenny CRON[18058]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly)</div>
<div>Apr 16 22:19:25 kenny nagios: Auto-save of retention data completed successfully.</div><div>Apr 16 22:30:23 kenny kernel: [270720.200044] INFO: task mythbackend:17865 blocked for more than 120 seconds.</div></div><div>
<br></div><div>A good thought, but no dice. Note that there is nothing in cron.hourly.</div><div><br></div><div>-Jerry</div></div>