<br><br><div><span class="gmail_quote">On 2/5/06, <b class="gmail_sendername">Steve Fallows</b> <<a href="mailto:sgfallows@ieee.org">sgfallows@ieee.org</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
I have had a single box system working well for about a year. I just setup a<br>slave backend on another machine (Hardware below). Both are KnoppMyth R5A15.<br><br>After some fiddling and learning about how mythtv-setup handles the capture
<br>cards and the database, I now have both encoders showing up in the system<br>status. I have setup no NFS shares so I assume each machine will store its<br>recordings locally and stream them when played.<br><br>I was able to schedule two recordings simultaneously. After they started,
<br>both were shown as in progress on MythWeb. However, after they finished the<br>one on the slave was gone. There were no other recordings on the slave.<br><br>The marked lines in this snippet of the slave backend log, imply that the
<br>recording was autoexpired immediately upon finishing:<br><br>[list]2006-01-14 15:37:11.799 MainServer::HandleAnnounce FileTransfer<br>2006-01-14 15:37:11.803 adding: mythtv as a remote file transfer<br>2006-01-14 15:37:
11.823 MainServer::HandleAnnounce Playback<br>2006-01-14 15:37:11.825 adding: mythtv as a client (events: 0)<br>2006-01-14 15:44:11.122 autoexpire: Expired Program<br><<<<<<<<<<< This seems to be the expiration of
<br>2006-01-14 15:44:11.235 Finished recording Fox NFL Pregame on channel: 1013<br><<<<<<<<<<< this<br>2006-01-14 15:44:11.274 scheduler: Finished recording<br>2006-01-14 15:44:11.335 Changing from RecordingOnly to None
<br>2006-01-14 15:54:11.243 mythbackend: Last message repeated 3 times<br>2006-01-14 15:54:11.267 mythbackend: Autoexpire Recording<br>2006-01-14 15:54:11.269 ERROR when trying to autoexpire files. No<br>recordings allowed to expire.[/list]
<br><br>I guess I have a misconfiguration of some kind on the slave. (O some<br>misunderstanding of how slaves work.) The myth partition is only 4% used.<br>Should a slave even do autoexpire?<br><br>Thanks for any help.<br>
<br>Master Backend:<br>Tyan S1590S Trinity 100AT, AMD K6-2 500MHz, VIA MVP chipset<br>PVR 350, 160 MB RAM, 160 GB WD HD<br>KnoppMyth R4V5 -> R5A15<br><br>Slave Backend:<br>Dell Dimension 8100, 1.3GHz<br>WinTV Card, 768MB, 120 GB HD
<br>KnoppMyth R5A15<br><br><br>_______________________________________________<br>mythtv-users mailing list<br><a href="mailto:mythtv-users@mythtv.org">mythtv-users@mythtv.org</a><br><a href="http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users">
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users</a><br></blockquote></div><br>
I noticed some strange messages about autoexpire on my backend earlier
this week. After investigating I found that the nfs link to my
recordings diretory on the master server was gone. The backend
must have seen this as a freespace violation and tried to autoexpire
recordings. I don't know, but I'd bet if this were the case
the recordings are just gone from the database but still on the
disk. I don't know because I have nothing set to allow for
autoexpire so my slave backend was just throwing messages about
not finding things to autoexpire. (I had a bad experinece with
autoexpire a while ago and turned it off everywhere).<br>
<br>
Hope that helps.<br>