Hi

I have Installed KnoppMyth R5A10, too.

It works great!

But mythbackend doesn't start at boot.

I must start it with mythbackend & after the boot.
Why?


Thanks!

I also experience this. Initially I thought it was because of a missing log file. I kept getting errors about not being able to access /var/log/mythtv/mythbackend.log. I created the file and then made it writable. The next time I booted mythbackend started up right away. But after that one time, I have had to start it manually. Not sure what to try next.

check in /etc/rc5.d/ and make sure you have a file like S??myth??backend

_________________
Have a question search the forum and have a look at the KnoppMythWiki.

Xsecrets

It is there:

S25mythtv-backend -> ../init.d/mythtv-backend

Plus when I boot I see messages about it starting so I think the problem happens after that. Other ideas or information I can give you?

Hi I had the same problem a simple

fixed it for me. I've now restarted my machine at least 20 times and it seemes to be working.

So to fix it you had to remove the log file? But doesn't that give the missing log file error which also prevents the backend from starting?

At a guess the file had the wrong ownerships or permissions and deleting it lets be be recreated with good ones.

That was my thoughts also , I tried changing permissions and ownerships to the original file but that still didn't work , messed around with the startup file blahblahblah . After looking through the startup file I noticed it was created after every reboot so in essense removing the original and letting the script take care of it properly seemed only logical .

BTW. This Knoppmyth is great , but getting to understand Debian is well...I wish it were Gentoo All joking aside great work to all involved.

The script /etc/init.d/mythbackend started with no error.

But the mythbackend Server isn't running...

I think something is wrong with this script...

Perhaps you should take a look at he log to see why the backend is dying? Perhaps starting the backend in and xterm and see what kills it?

OK..

this is written in the log file:
2005-02-23 11:41:06.327 Unable to read configuration file mysql.txt
2005-02-23 11:41:06.331 Could not create ~/.mythtv
2005-02-23 11:41:10.209 Unable to read configuration file mysql.txt
2005-02-23 11:41:10.214 Could not create ~/.mythtv

then I created ~/.mythtv and the log says:
2005-02-23 11:42:05.296 Unable to read configuration file mysql.txt
2005-02-23 11:42:05.302 Could not open settings file /root/.mythtv/mysql.txt for writing

I do this:

copy /usr/share/mythtv/mysql.txt to /root/.mythtv/mysql.txt

and it works!!!

That is strange, because I thought the backend runs as user mythtv,
so shouldn't it be looking for /home/mythtv/.mythtv/mysql.txt ?

_________________
| Nigel Pearson, nigel.pearson.au@gmail.com
| "Things you own end up owning you" - Tyler, Fight Club

I have a /root/.mythtv as well as a /home/mythtv/.mythtv and both directories have a fully accessible mysql.txt file in them. Yet I still receive the following errors in the log file.

Unable to read configuration file mysql.txt
Could not create ~/.mythtv

I can't understand why my machine would act differently. Any ideas?

/usr/share/mythtv/mysql.txt

_________________
cesman

When the source is open, the possibilities are endless!