[mythtv-users] mythbackend dies, can't find any more details

Chuck Strusz chuck at neondsl.com
Sat Jan 5 22:28:47 UTC 2008

I've fixed this problem, and will document it here for anybody else who
might have this/a similar issue:


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


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.


From: mythtv-users-bounces at mythtv.org
[mailto:mythtv-users-bounces at mythtv.org] On Behalf Of Chuck Strusz
Sent: Saturday, January 05, 2008 3:32 PM
To: mythtv-users at mythtv.org
Subject: [mythtv-users] mythbackend dies, can't find any more details


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.


The existing master backend is a Dell 420SC running FC4, kernel
2.6.17-1.2142_FC4 and (as mentioned) uses a PVR-250.


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


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.


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.


"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


"mythbackend dead but subsys locked" is what "service . status" says.


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).


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.


For what it is worth, the new slave backend can run mythfrontend and
connects to the master backend just fine.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mythtv.org/pipermail/mythtv-users/attachments/20080105/d943dce5/attachment.htm 

More information about the mythtv-users mailing list