I've tried several times with varying degrees of failure. The shortest number of steps to the main issues is as follows:
(set the password)
From a remote session
Configure some settings and exit. It asks if I want to start mythtv-backend, and I say yes. It now asks me for a password. I have tried the root password on the server, the mythtv password I set in step 2 above, and the password in /etc/mythtv/mysql.txt. Eventually I give up, and it asks me if I want to run mythfilldatabase. I say yes, and it appears to work.
After that, unsurprisingly, I cannot connect to MythTV from xbmc (using the default cmyth add-on in Frodo). If I ssh back into that machine, and run:
I get:
mythtv-backend stop/waiting
Obviously, I need to start the service, so logically, I run:
Then just to sanity check, I check the status again, and it still says stop/waiting. For what it's worth, the same command on mysql shows start/running. This is on a fresh install of Ubuntu server, but I'm not opposed to wiping it again and starting from scratch if that would help. I have to be doing something wrong, but I can't for the life of me figure out what.
Code:
sudo apt-get install mythtv-backend-master
sudo passwd mythtvFrom a remote session
Code:
ssh -X mythtv@server mythtv-setupConfigure some settings and exit. It asks if I want to start mythtv-backend, and I say yes. It now asks me for a password. I have tried the root password on the server, the mythtv password I set in step 2 above, and the password in /etc/mythtv/mysql.txt. Eventually I give up, and it asks me if I want to run mythfilldatabase. I say yes, and it appears to work.
After that, unsurprisingly, I cannot connect to MythTV from xbmc (using the default cmyth add-on in Frodo). If I ssh back into that machine, and run:
Code:
sudo service mythtv-backend statusmythtv-backend stop/waiting
Obviously, I need to start the service, so logically, I run:
Code:
sudo start mythtv-backendThen just to sanity check, I check the status again, and it still says stop/waiting. For what it's worth, the same command on mysql shows start/running. This is on a fresh install of Ubuntu server, but I'm not opposed to wiping it again and starting from scratch if that would help. I have to be doing something wrong, but I can't for the life of me figure out what.