View unanswered posts    View active topics

All times are UTC - 6 hours





Post new topic Reply to topic  [ 10 posts ] 
Print view Previous topic   Next topic  
Author Message
Search for:
PostPosted: Tue Apr 10, 2007 5:47 pm 
Offline
Joined: Thu Dec 29, 2005 12:56 am
Posts: 87
So my backend is @ 192.168.2.110 and my frontend is @ 192.168.2.100
for some reason I can't get the frontend to lock anywhere but at itself. After it doesnt find the backend, i get the setup program (asks for the language then the backend ip/pw/etc). In this screen, it has the backend IP listed. Very odd that it's listed there yet it doesnt look there for the backend.

I should also mention that i have just done a fresh install on the frontend machine and the front end/backend talk worked fine before the upgrade--so it's a problem on the frontend side.

on my frontend in ~/.mythtv/mysql.txt I have:
Code:
DBHostName=192.168.2.110
DBUserName=mythtv
DBPassword=**********
DBName=mythconverg
DBType=QMYSQL3

and when I run mythfrontend I get:
Code:
mythtv@karl-desktop:~/.mythtv$ mythfrontend
X Error: BadDevice, invalid or uninitialized input device 167
  Major opcode:  144
  Minor opcode:  3
  Resource id:  0x0
Failed to open device
X Error: BadDevice, invalid or uninitialized input device 167
  Major opcode:  144
  Minor opcode:  3
  Resource id:  0x0
Failed to open device
2007-04-10 19:46:52.664 Using runtime prefix = /usr
2007-04-10 19:46:52.670 DPMS is active.
2007-04-10 19:46:52.699 New DB connection, total: 1
2007-04-10 19:46:52.746 Unable to connect to database!
2007-04-10 19:46:52.746 Driver error was [1/1045]:
QMYSQL3: Unable to connect
Database error was:
Access denied for user 'mythtv'@'192.168.2.100' (using password: YES)

QSqlQuery::exec: database not open
QSqlQuery::exec: database not open
2007-04-10 19:46:52.821 DB Error (KickDatabase):
Query was:
SELECT NULL;
No error type from QSqlError?  Strange...
2007-04-10 19:46:52.882 Unable to connect to database!
2007-04-10 19:46:52.882 Driver error was [1/1045]:


Top
 Profile  
 
 Post subject:
PostPosted: Tue Apr 10, 2007 5:57 pm 
Offline
Joined: Wed Aug 23, 2006 3:07 pm
Posts: 339
192.168.2.110?

First, that's an odd ip. Usually on home nets, it's 192.168.1.*, and sometimes the mask comes out as 1.255.

Check if you can ping the 192.168.2.110 from the 100 address, and the 100 from the 110.

Second, make sure the backend is running on 110. If it can't connect, it gives you that kind of display. Alt-3 on the backend. Just restarting the machine won't always start up the backend for some reason.

Third, in your card setup, under general, make sure the ips are correct for local machine and backend. It's pretty easy to accidentally swap them, or put in a wrong ip by mistake.


Top
 Profile  
 
 Post subject:
PostPosted: Tue Apr 10, 2007 6:01 pm 
Offline
Joined: Wed Aug 23, 2006 3:07 pm
Posts: 339
You may need to edit one more file to allow network access to the mysql system.

In the file /etc/mysql/my.cnf, there's a line that says "skip-networking". You *MAY* need to comment out the line in that section. The current version of that file was changed to bind-address.

I was told to comment that line out entirely, but checking my own file, it's not commented out and it's working, so I don't know. I haven't tried using the sbe to play anything from the mbe yet though.


Top
 Profile  
 
 Post subject:
PostPosted: Tue Apr 10, 2007 6:06 pm 
Offline
Joined: Thu Dec 29, 2005 12:56 am
Posts: 87
i forgot to mention that i had also been in there... it's this now
that doesn't work with or without the 192.168.2.110 commented out
Code:
# Instead of skip-networking the default is now to listen only on
# localhost which is more compatible and is not less secure.
#bind-address           = 127.0.0.1
bind-address            = 192.168.2.110
#


Top
 Profile  
 
PostPosted: Tue Apr 10, 2007 6:13 pm 
Offline
Joined: Wed Nov 16, 2005 8:55 pm
Posts: 1381
Location: Farmington, MI USA
Irishcream wrote:
on my frontend in ~/.mythtv/mysql.txt I have:
Code:
DBHostName=192.168.2.110
DBUserName=mythtv
DBPassword=**********
DBName=mythconverg
DBType=QMYSQL3
And did you set LocalHostName= to something unique? If not, the MBE won't know who's "calling", and the frontend will send you into the setup screen. This setting can also be configured in Setup -> General -> "Use custom identifier for frontend preferences" on the 2nd page of the frontend. This is on my R5D1 + .20, not sure if it's in a different spot/named differently in R5E50.

EDIT: Be sure to use the same name you used before the upgrade. /EDIT


Top
 Profile  
 
 Post subject:
PostPosted: Tue Apr 10, 2007 6:15 pm 
Offline
Joined: Thu Dec 29, 2005 12:56 am
Posts: 87
and yes, my frontend is @ 192.168.2.100 and i can access and use mythweb @ 192.168.2.110 (which indicates that i can ping it and that the backend is up)


Top
 Profile  
 
 Post subject:
PostPosted: Tue Apr 10, 2007 6:19 pm 
Offline
Joined: Thu Dec 29, 2005 12:56 am
Posts: 87
for somereason it's not bothering to look at the backend, it just looks at itself... in the above posting i showed that it's just looking for a database @ 192.168.2.100 and at no point does it give up and try 192.168.2.110


Top
 Profile  
 
 Post subject:
PostPosted: Tue Apr 10, 2007 6:41 pm 
Offline
Joined: Wed Nov 16, 2005 8:55 pm
Posts: 1381
Location: Farmington, MI USA
Irishcream wrote:
for somereason it's not bothering to look at the backend, it just looks at itself... in the above posting i showed that it's just looking for a database @ 192.168.2.100 and at no point does it give up and try 192.168.2.110
I'm not sure who this response was meant for, but I'm not seeing where the frontend is looking to the backend at all. I see
Quote:
Access denied for user 'mythtv'@'192.168.2.100' (using password: YES)
which indicates to me that the frontend cannot access the database, but doesn't tell me where it's looking for that database. Maybe I'm just reading it wrong...


Are you running R5E50? You should be changing /etc/mythtv/mysql.txt according to http://www.knoppmythwiki.org/index.php? ... nlyInstall


Top
 Profile  
 
 Post subject:
PostPosted: Tue Apr 10, 2007 6:47 pm 
Offline
Joined: Thu Dec 29, 2005 12:56 am
Posts: 87
to me that line says it's trying to login to the backend at 192.168.2.100 when it should be looking at 192.168.2.110. am i reading that wrong?

the backend is setup correctly (and the frontend worked with it fine before i upgraded to fiesty)


Top
 Profile  
 
 Post subject:
PostPosted: Tue Apr 10, 2007 6:52 pm 
Offline
Joined: Thu Dec 29, 2005 12:56 am
Posts: 87
ok, you are correct about that line not giving hints as to where it is looking for the server.

so taking your advice, i looked at the old copy of mysql.txt i had and noticed that i hadnt changed it to my normal password but had left it as default.... so it was an authentication failure.

thanks for all the help, problem is solved now.. and i feel like an idiot


Top
 Profile  
 

Display posts from previous:  Sort by  
Post new topic Reply to topic  [ 10 posts ] 


All times are UTC - 6 hours




Who is online

Users browsing this forum: No registered users and 5 guests


You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot post attachments in this forum

Jump to:  
cron
Powered by phpBB® Forum Software © phpBB Group

Theme Created By ceyhansuyu