[mythtv-users] Myth FE, mythfilldatabase, and NFS Issue

[James Crow]

Last night I was watching a recorded show and my FE locked up. The 
picture was frozen on screen and the keys pressed on the remote seemed 
to be ignored. I went to my main desktop and sshed into the FE machine. 
The system was not hard locked and I was able to kill mythfrontend. I 
started looking at log files to see if I could find a cause. It appears 
that the NFS daemon on the master BE was no longer responding. This 
caused the FE to lock up. I restarted NFS on the MBE and started the FE 
back up and everything appeared fine.

Just as a precaution I looked at the BE log and /var/log/messages. Right 
near the time that the NFS daemon stopped responding mythfilldatabase 
had segfaulted. Has anyone seen similar behavior or know how to better 
test mythfilldb?

/var/log/messages from MBE:
Mar 19 21:02:03 mythfront -- MARK --
Mar 19 21:21:22 mythfront kernel: [790809.097285] nfsd: last server has 
exited, flushing export cache
Mar 19 21:21:24 mythfront kernel: [790810.437165] NFSD: Using 
/var/lib/nfs/v4recovery as the NFSv4 state recovery directory
Mar 19 21:21:24 mythfront kernel: [790810.437548] NFSD: starting 
90-second grace period
Mar 19 21:42:03 mythfront -- MARK --
Mar 19 22:02:03 mythfront -- MARK --
Mar 19 22:22:03 mythfront -- MARK --
Mar 19 22:41:36 mythfront kernel: [795622.497755] 
mythfilldatabas[21487]: segfault at 162e2c0 ip 000000000162e2c0 sp 
0000000042320dd8 error 15
Mar 19 23:02:06 mythfront -- MARK --

mythfilldatabase segfaulted again this morning:
Mar 20 08:42:06 mythfront -- MARK --
Mar 20 08:53:26 mythfront kernel: [832333.266066] 
mythfilldatabas[27033]: segfault at 103a660 ip 000000000103a660 sp 
00000000413c7dd8 error 15
Mar 20 09:22:06 mythfront -- MARK --

I am not sure if the nfs issue and the segfault are connected, but it 
seems odd that occurred at nearly the same time.

Thanks,
James