that netstat command should be enough, on my box I get this: tv root # netstat -apn | grep 6543 tcp 0 0 0.0.0.0:6543 0.0.0.0:* LISTEN 6678/mythbackend tcp 0 0 127.0.0.1:6543 127.0.0.1:1115 ESTABLISHED 6678/mythbackend tcp 0 0 127.0.0.1:6543 127.0.0.1:1114 ESTABLISHED 6678/mythbackend tcp 0 0 127.0.0.1:1114 127.0.0.1:6543 ESTABLISHED 14833/mythfrontend tcp 0 0 127.0.0.1:1115 127.0.0.1:6543 ESTABLISHED 14833/mythfrontend
I admit, I run my backend as root, so the log file might be causing your problems somehow. I know mine works with both 127.0.0.1 and its real ip, since I"ve used both. I'd make sure that user can read/write the log. other than that I don't know. Does mythbackend show up in ps -A? Lucien On 4/23/05, Mark Knecht <[EMAIL PROTECTED]> wrote: > Hi, > Continuing with my MythTV install this morning. I'm signed up with > ZapIt and receiving cable TV channel info which I see correctly in > mythtv-setup. However when I try to do the mythfilldatabase step I get > a funny message that doesn't look right: > > dragonfly ~ # mythfilldatabase > 2005-04-23 09:42:38.508 New DB connection, total: 1 > 2005-04-23 09:42:38.513 New DB connection, total: 2 > Refreshing Tomorrow's data > > <BIG SNIP> > > 0 replacements made. > Marking repeats...found 1428 > Unmarking repeats from grabber that fall within our new episode > window...found 6 > 2005-04-23 09:43:03.589 Connecting to backend server: > 192.168.10.55:6543 (try 1 of 5) > Connection timed out. > You probably should modify the Master Server settings > in the setup program and set the proper IP address. > error resceduling id -1 in ScheduledRecording::signalChange > dragonfly ~ # > > I believe that I've started the mythbackend server correctly but it > doesn't seem to be listening: > > dragonfly ~ # /etc/init.d/mythbackend status > * status: stopped > dragonfly ~ # netstat -apn | grep 6543 > dragonfly ~ # /etc/init.d/mythbackend start > * Starting myth backend ... [ > ok ] > dragonfly ~ # netstat -apn | grep 6543 > dragonfly ~ # > > 1) Is the netstat command above sufficient to find the backend server > if it's running? > > 2) Is there some configuration step that I missed somewhere? Here's > the guts of /etc/conf.d/mythbackend.conf: > > ********** > > MYTH_WARN=yes > > # Specify which user to run as > # > # NOTE: this user must have permissions to write > # to the LOG and PID directories specified > # below. Furthermore, this user must be able > # to write to the audio and video devices > # that are configured in MythTV. This can > # be achieved by adding this user to the > # audio and video groups. > MYTH_USER=mark > > MYTH_LOG=/var/log/mythtv/mythbackend.log > > MYTH_PID=/var/run/mythtv/mythbackend.pid > > MYTH_VERBOSE="none" > > MYTH_NICE="0" > > ********** > > NOTE: I've tried this with IP addressesof 127.0.0.1 and 192.168.10.55 > (the fixed IP of the machine) and got the same results both times. > > I've added myself to the /etc/groups file for audio and video: > > audio:x:18:root,mark > cdrom:x:19:root,mark > > Does this give me correct permissions to write the backend logs? > Possibly not? Should I move them? > > What might I try next? > > Thanks in advance, > Mark > > -- > gentoo-user@gentoo.org mailing list > > -- gentoo-user@gentoo.org mailing list
