[mythtv-users] Mythtv is using all inputs, but there are no active recordings

[Kevin Johnson]

Hi
Mike:  I will do my best to answer this. 




>
I had a previous post titled. 
> 
> upgrade
database
schema
from
1224
to
1242
fails

> That is now fixed thanks to
you guys. 
> 

Can you please post to
that thread some information on what caused the 
original failure
and what you did to
fix it? It would help me to
try to 
make sure
we make the upgrade
as failure-proof as possible, and it would 
likely help anyone
else who has similar issues. 




Not
sure what I did to cause the original failure.  I finally
completed/fixed the upgrade by dumping the database using this
thread.  I did not restore my old database, just created a new one.



http://www.mythtv.org/wiki/Database_Backup_and_Restore#Database_Restore



After
I made the new database, I ran the mythbackend setup, and it was able
to upgrade then.


>
Now. a new issue 
> 
> I just moved to
trunk .22 
> 
> I have finally got my backend running. I
upgraded the frontend to
.22 also. 
> 
> When I start mythtv on the frontend, I
get an error message. 
> 
> Mythtv is using all inputs,
but there are no active recordings 
> 
> Here is a post
from
the error log. 
> 
> 
> 
> 2009-08-25
00:20:29.585 Driver error was [1/2003]: 
> QMYSQL: Unable to
connect 
> Database
error was: 
> Can't connect to
MySQL server on 'myth-backend' (111) 
> QSqlQuery::exec:
database
not open 
> QSqlQuery::exec: database
not open 
> 2009-08-25 00:20:29.635 No error type from
QSqlError? Strange... 
> 2009-08-25 00:20:29.685 Database
not open while trying to
load setting: Theme 
> 2009-08-25 00:20:29.686 Unable to
connect to
database!

> 
... 
>
kevin[at]mythtv:/var/log/mythtv$ mythtv 
> 

mythtv
is not the name of the binary you run. It's a test application. 
You
want to run
mythfrontend. 



I
will do that when I get home.

>
2009-08-25 00:45:42.397 Using runtime prefix = /usr 
>
2009-08-25 00:45:42.397 Empty LocalHostName. 
> 2009-08-25
00:45:42.398 Using localhost value of mythtv 
> 2009-08-25
00:45:42.398 Testing network connectivity to
'myth-backend' 
> 
... 
>
2009-08-25 00:45:44.515 Connecting to
backend server: 127.0.0.1:6543 (try 1 of 5) 
> 2009-08-25
00:45:44.515 Connection timed out. 
> You probably should
modify the Master Server 
> settings in the setup program and
set the 
> proper IP address. 
> 
... 
>
Which would leave me to
believe that I cant connect to
the database.

> But if I do a mysql -h myth-backend -u mythtv -p mythconverg

> it will bring me to
the mysql prompt. 
> I am pretty sure the backend is set up
correctly. ( I set it up like I had it before the upgrade
) 
> 

How many hosts are involved here? Is it a
single combined 
frontend/backend system? If not, you need to
fix your server settings 
with mythtv-setup so that you don't use
127.0.0.1 anywhere in any of the 
"IP address" settings.
It seems that the first program failed to

connect to the
database whereas the
second program failed to
connect to 
the
master backend (but successfully connected to
the database). 




It
is a seperate frontend backend.  I have three frontends and one
backend.  I have two of the frontends shutoff until I get at least
this one frontend working with the backend.
I
will check all fo my ip setting to make sure 127.0.0.1 is not setup
anywhere.

That likely means that
/home/kevin/.mythtv/config.xml (which was used to

get the DB config for the 2nd program) is good, but the

$HOME/.mythtv/config.xml for the user running the first program
is not 
good. You'd just need to
copy the config.xml from
under your home to

the same location in the other user's home. 



I
will try that when I get home.

>
Any ideas? 
> 
> I use a hdhomerun and 2 ati hdtv wonder
cards. The wonder cards are not yet installed, but they are in the
pci slots. (I have not istalled them in the setup of myth backend) 
>
I want to
get it working with the hdhomerun first. 
> 

That's
not a problem. The opposite--having the cards configured in Myth 
and
not present in the machine--is a problem, but if Myth doesn't know

about the cards, they can't cause any issues. 

Mike 




      
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mythtv.org/pipermail/mythtv-users/attachments/20090825/9a5c0e38/attachment-0001.htm>