<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=us-ascii">
<meta name=Generator content="Microsoft Word 12 (filtered medium)">
<style>
<!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:windowtext;}
span.EmailStyle18
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page Section1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.Section1
{page:Section1;}
-->
</style>
<!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=EN-US link=blue vlink=purple>
<div class=Section1>
<p class=MsoNormal><span style='color:#1F497D'>I’ve fixed this problem, and
will document it here for anybody else who might have this/a similar issue:<o:p></o:p></span></p>
<p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='color:#1F497D'>Running “mythbackend &”
allowed mythbackend output to be visible; it became immediately obvious that it
was attempting to read from/write to a directory whose root I would normally
NFS mount and had not yet done, hence the path was not yet available. Fixing
this allows mythbackend to start successfully.<o:p></o:p></span></p>
<p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='color:#1F497D'>I’m still curious as to why I
have no log directory for mythtv (ok, I know it probably has something to do
with a step I missed in compilation); if anybody could help with this, I’d be
much obliged.<o:p></o:p></span></p>
<p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p>
<div>
<div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'>
<p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><span
style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>
mythtv-users-bounces@mythtv.org [mailto:mythtv-users-bounces@mythtv.org] <b>On
Behalf Of </b>Chuck Strusz<br>
<b>Sent:</b> Saturday, January 05, 2008 3:32 PM<br>
<b>To:</b> mythtv-users@mythtv.org<br>
<b>Subject:</b> [mythtv-users] mythbackend dies, can't find any more details<o:p></o:p></span></p>
</div>
</div>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal>I’ve got an existing system set up as a master backend using
a PVR-250, and it is working with multiple remote frontends. I’m trying
to add a slave backend (no frontend needed) and running into some trouble with
mythbackend dying on the new system almost immediately after it is started.<o:p></o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal>The existing master backend is a Dell 420SC running FC4,
kernel 2.6.17-1.2142_FC4 and (as mentioned) uses a PVR-250.<o:p></o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal>The new (not yet working) slave backend is an ASUS CUSL2
PIII/866 running with an Intel Pro/1000 MT and a pcHDTV-5500. It is
running FC7, kernel 2.6.21-1.3194.fc7.<o:p></o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal>Both systems are running MythTV 0.20.2, and were compiled
(successfully) from the same source tarball. I copied the appropriate
contrib scripts into the /etc/sysconfig and /etc/rc.d to “service-afy”
mythbackend.<o:p></o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal>I DO NOT have a ‘mythtv’ directory in /var/log, nor any
mythbackend logs for the slave backend. Doing “tail –f
/var/log/messages” on the slave backend and on the master backend (as well as
“tail –f /var/log/mythtv/mythbackend.log” on the master backend) reveals NOTHING
when I try to start the mythbackend service (“service mythbackend start”) on
the slave backend.<o:p></o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal>“service mythbackend start” says, “Starting
mythbackend: [ OK ]”, but if I check the status (“service mythbackend
status” or even “ps –ef |grep mythbackend”) immediately after that it is
apparent that mythbackend is not running:<o:p></o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal>“mythbackend dead but subsys locked” is what “service …
status” says.<o:p></o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal>An attempt to restart the service fails on the “stopping”,
appears to succeed on the “starting”, but it dies immediately (ps –ef |grep
mythbackend yields nothing).<o:p></o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal>I’m stumped as to where I should look for more info, and
don’t know what other info that might be relevant I’ve not included.<o:p></o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal>For what it is worth, the new slave backend can run
mythfrontend and connects to the master backend just fine.<o:p></o:p></p>
</div>
</body>
</html>