Backend seems to be dying, but nothing in the logs is showing me why. What I have done:
Repaired mysql tables
Checked HD space (df -h)
/dev/hda1 3.7G 1.8G 1.8G 50% /
/dev/hda3 13G 24K 13G 1% /cache
/dev/hda4 170G 105G 66G 62% /myth
Checked logs:
mythbackend.log and mythbackend.log.1 show no indication of a crash
syslog and messages also show no indication of it or mysql dying that I could notice.
However, the frontend comes back telling me it has lost connection to the backend, or the Watch Recordings list is empty and live tv just kicks back to the menus. If I stop and restart Mysql and the backend, it works again.
Nothing with the nVidia HW has changed, I have done nothing to the system is the last several months. What makes it odd is that it happens when no one is using it too. For example, the last item in the mythbackend.log was:
Code:
2005-08-12 06:35:45.958 MainServer::HandleAnnounce Playback
2005-08-12 06:35:46.982 adding: mythtv as a client (events: 0)
2005-08-12 06:35:47.020 unknown socket
prior to that was the housekeeping thread at about 2:30
Code:
2005-08-12 02:30:14.043 Connecting to backend server: 192.168.0.11:6543 (try 1 of 5)
2005-08-12 02:30:14.052 Using protocol version 15
2005-08-12 02:30:14.058 MainServer::HandleAnnounce Playback
2005-08-12 02:30:14.059 adding: mythtv as a client (events: 0)
2005-08-12 02:30:14.098 unknown socket
2005-08-12 02:30:14.143 mythbackend: Running housekeeping thread
Now, there was a scheduled recording at 2:00 p.m. that is not reflected here, nor did it record. It is General Hospital and records every day. Except the last couple of days when the back-end died sometime during the morning/early afternoon. I can't tell when though to narrow it down. Any other ideas of where to look for what is happening?
UPDATE:
I did some more test while sitting here watching the logs.
Code:
2005-08-12 16:58:31.551 Started recording "Becker" on channel: 1006 on cardid: 1, sourceid 1
2005-08-12 16:58:31.572 New DB connection, total: 4
2005-08-12 16:58:31.575 scheduler: Last message repeated 6 times
2005-08-12 16:58:31.603 scheduler: Schedule Change
2005-08-12 16:58:32.071 Changing from None to RecordingOnly
2005-08-12 17:32:00.003 Finished recording Becker on channel: 1006
2005-08-12 17:32:00.007 scheduler: Finished recording
2005-08-12 17:32:00.026 Changing from RecordingOnly to None
This is interesting, it recorded for 1/2 hour, but the file is 0 bytes. Nothing. And because of this, the backend is trying to generate a preview, and cannot:
Code:
2005-08-12 17:43:00.874 Invalid file handle when opening /myth/tv/1006_20050812165900_20050812173000.nuv. 4 retries remaining.
This machine has 3 PVR 250's.
LAST UPDATE
Code:
2005-08-12 18:02:02.733 Started recording "The Simpsons" on channel: 1011 on cardid: 1, sourceid 1
2005-08-12 18:02:02.753 scheduler: Schedule Change
2005-08-12 18:02:03.253 Changing from None to RecordingOnly
2005-08-12 18:02:12.242 NVP: Couldn't find a matching decoder for: /myth/tv/1011_20050812180200_20050812183000.nuv
2005-08-12 18:02:12.310 Not enough video to make thumbnail
2005-08-12 18:02:14.357 NVP: Couldn't find a matching decoder for: /myth/tv/1011_20050812180200_20050812183000.nuv
2005-08-12 18:02:14.423 Not enough video to make thumbnail
2005-08-12 18:02:17.251 NVP: Couldn't find a matching decoder for: /myth/tv/1011_20050812180200_20050812183000.nuv
2005-08-12 18:02:17.317 Not enough video to make thumbnail
I set all three cards to record. cardid 1, 2, 3 after changing priorities of the cards. 2, and 3 are recording fine and the .nuv files are growing. However number 1 is not. OUCH. Has this card gone bad. However, I did set it to a priority of 0, the others are higher, so it is the one that is used for live tv, which does work. It seems like the backend cannot use it all of a sudden for recording though. This is new.