September 10, 2010, 04:45:14 pm GMT-1
Welcome,
Guest
. Please
login
or
register
.
Did you miss your
activation email?
1 Hour
1 Day
1 Week
1 Month
Forever
Login with username, password and session length
News
: Rule #1 for LinuxMCE - Be Patient
Home
Help
Search
Chat
Login
Register
LinuxMCE Forums
>
LinuxMCE
>
Installation issues
>
MythTV woes
Pages: [
1
]
« previous
next »
Print
Author
Topic: MythTV woes (Read 1148 times)
cckrobinson
Veteran
Posts: 124
MythTV woes
«
on:
April 01, 2007, 11:15:40 pm »
I tried to installing LinuxMCE on a machine that already had a functioning MythTV installation. Apparently that was a mistake. I'm currently running into database problems.
My original Myth Install created a mythtv user and a database called MythConverg. From the mythtv setup, you were required to supply a password for the mythtv user in order to access the database. That was fine and it worked.
When LinuxMCE tries to access the database it connects as user 'root'@'localhost' with NO password. When I run the mythtv setup from inside the orbiter it can't connect to the database, so it brings you to the screen where you need to supply the IP of the backend and the database\name password. You MUST supply a password here. To get by this issue, I can manually change the database to use a password for 'root@localhost'. That allows me to run the setup and configure my cards. The problem is that if you try to change anything from the Pluto admin (i.e. the PVR-150 settings) it fails because it tries to connect as 'root'@'localhost' with NO password.
So here are my questions:
1. Why does LinuxMCE always try to connect to the mysql as root? This isn't how a typical myth install is done.
2. Is it possible to change LinuxMCE so that it uses a password when connecting to mysql?
Logged
cckrobinson
Veteran
Posts: 124
Re: MythTV woes
«
Reply #1 on:
April 02, 2007, 05:26:23 am »
It appears that I was mistaken about how LinuxMCE was trying to connect to the mythconverg database. It wasn't using root@localhost after all. It connects as that user for other database stuff. For myth it seems to be using the username/password found in the /etc/mythtv/mysql.txt file. In my case this file had a goofy random password. I was able able to change it to a known value and then modify the password for that user in the mythconverg database to match. That seemed to resolve the connection issues. I also deleted the ~mythv/.mythtv and the ~root/.mythtv folders. These were hanging around from my previous myth install, and they aren't needed with Pluto.
Inside of LinuxMCE I still can't watch TV. When I select media->TV the mythfrontend launches correctly. I'm able to see the main menu. As soon as I hit 'Watch TV' the screen goes black for a few seconds and then turns grey. Since I'm not seeing the "unable to connect to database" message anymore, so I'm pretty sure the frontend is able to talk to the backend. I also know that the ivtv drivers are installed correctly for my PVR-150. I can run 'mplayer /dev/video0' and see video just fine.
Here's the error that I'm getting in the MythTV-Plugin log when I try to watch live TV:
/01/07 22:17:09.977 Parameter 159(PK_Screen): 128 <0xa7389ba0>
08 04/01/07 22:17:09.979 Parameter 5(Value To Assign): MythTV Player(LinuxMCE LiveTV) <0xaab90ba0>
08 04/01/07 22:17:09.979 Parameter 9(Text): <0xaab90ba0>
08 04/01/07 22:17:09.979 Parameter 29(PK_MediaType): 1 <0xaab90ba0>
08 04/01/07 22:17:09.979 Parameter 41(StreamID): 2 <0xaab90ba0>
08 04/01/07 22:17:09.979 Parameter 48(Value): 0 <0xaab90ba0>
08 04/01/07 22:17:09.979 Parameter 50(Name): mythfrontend.Mythfrontend <0xaab90ba0>
08 04/01/07 22:17:09.979 Parameter 103(List PK Device): 24,24,15,,1,1,0 <0xaab90ba0>
08 04/01/07 22:17:09.979 Parameter 120(Retransmit): 0 <0xaab90ba0>
08 04/01/07 22:17:10.005 Received Message from 19 (OnScreen Orbiter / Family Room) to 28 (Photo Screen Saver / Family Room), type 1 id 193 Command:Off, parameters: <0x79b2eba0>
08 04/01/07 22:17:10.005 Parameter 97(PK_Pipe): 0 <0x79b2eba0>
05 04/01/07 22:17:11.186 Socket::ReceiveData 0x85ec888 failed, bytes left 0 start: 1060000 1: 0 1b: 0 2: 0 2b: 0 m_Socket: 140 Incoming_Conn Socket 140 127.0.0.1EVENT 24 T=35 Event #24 <0x7b331ba0>
05 04/01/07 22:17:11.207 Socket::ReceiveString2 ReceiveData failed m_Socket: -1 Incoming_Conn Socket 140 127.0.0.1EVENT 24 T=35 Event #24 <0x7b331ba0>
05 04/01/07 22:17:11.207 TCPIP: Closing connection to 24 (Router Dev #0) 0x85ec888 m_Socket: -1 <0x7b331ba0>
05 04/01/07 22:17:11.207 Router::RemoveAndDeleteSocket 0x85ec888 24 <0x7b331ba0>
05 04/01/07 22:17:11.186 Socket::ReceiveData 0x85fddc8 failed, bytes left 0 start: 1060000 1: 0 1b: 0 2: 0 2b: 0 m_Socket: 141 Incoming_Conn Socket 141 127.0.0.1EVENT 24 T=35 Event #24 <0x7bb32ba0>
05 04/01/07 22:17:11.209 Socket::ReceiveString2 ReceiveData failed m_Socket: -1 Incoming_Conn Socket 141 127.0.0.1EVENT 24 T=35 Event #24 <0x7bb32ba0>
05 04/01/07 22:17:11.209 TCPIP: Closing connection to 24 (Router Dev #0) 0x85fddc8 m_Socket: -1 <0x7bb32ba0>
05 04/01/07 22:17:11.209 Router::RemoveAndDeleteSocket 0x85fddc8 24 <0x7bb32ba0>
05 04/01/07 22:17:25.384 Router::RemoveAndDeleteSocket 0x8619208 24 <0x7b331ba0>
Based on the socket errors, I can only assume that the pluto frontend is not getting any data from the backend so it eventually times out. That's probably why the screen turns grey.
Does anyone have a clue what's going on here?
Logged
webpaul1
Veteran
Posts: 140
Re: MythTV woes
«
Reply #2 on:
April 03, 2007, 05:44:02 am »
What do you see in the log /var/log/pluto/24*...
Note CPIP: Closing connection to 24 (Router Dev #0) 0x85fddc8 m_Socket: -1 <0x7bb32ba0>
that means device 24 has stopped responding.
Logged
cckrobinson
Veteran
Posts: 124
Re: MythTV woes
«
Reply #3 on:
April 03, 2007, 06:03:20 am »
I saw this over and over again in the 24_MythtTV_Player.log
========== NEW LOG SECTION ==========
1 04/01/07 16:16:23 24 (spawning-device) [1;00mStarting... 3[1;00m
1 04/01/07 16:16:23 24 (spawning-device) [1;00mFound ./MythTV_Player[1;00m
05 04/01/07 16:22:23.627 [33;1mI failed to kill the application launched with name: mythfrontend[0m <0xb6a9bba0>
05 04/01/07 16:23:15.493 [33;1mGoing to send command jump livetv[0m <0xb7a9dba0>
Return code: 139
3 04/01/07 16:23:16 24 (spawning-device) [1;31mDevice died... count=3/50 dev=24[1;00m
Sun Apr 1 16:23:16 CDT 2007 died
I couldn't get any further, so I bit the bullet and tried reinstalling. It just finished. I completely removed Pluto, Mythtv and all related databases. The installed went fine except for this error in the mce-installer-xxx.log which worries me:
Setting up pluto-mythtv-player (1.0) ...
ERROR 2002 (HY000): Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2)
tail: Warning: "+number" syntax is deprecated, please use "-n +number"
ERROR 2002 (HY000): Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2)
WARNING: fake invoke-rc.d called
Waiting 3 seconds so that myth backed is able to actually create the schema
ERROR 2002 (HY000): Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2)
ERROR 2002 (HY000): Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2)
ERROR 2002 (HY000): Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2)
ERROR 2002 (HY000): Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2)
ERROR 2002 (HY000): Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2)
ERROR 2002 (HY000): Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2)
ERROR 2002 (HY000): Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2)
ERROR 2002 (HY000): Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2)
ERROR 2002 (HY000): Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2)
ERROR 2002 (HY000): Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2)
ERROR 2002 (HY000): Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2)
ERROR 2002 (HY000): Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2)
ERROR 2002 (HY000): Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2)
ERROR 2002 (HY000): Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2)
ERROR 2002 (HY000): Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2)
ERROR 2002 (HY000): Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2)
ERROR 2002 (HY000): Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2)
ERROR 2002 (HY000): Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2)
ERROR 2002 (HY000): Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2)
ERROR 2002 (HY000): Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2)
********
There is an error in the mythtv backend setup. It looks like the database schema wasn't created properly
********
I'm going to try running the myth-setup from the Orbiter and see what happens.
Logged
Pages: [
1
]
Print
« previous
next »
Jump to:
Please select a destination:
-----------------------------
LinuxMCE
-----------------------------
=> Marketplace
===> Compatible Products & Services
===> Help Wanted
=> Users
=> Developers
=> Installation issues
=> Feature requests & roadmap
=> Archive
===> App Server Users
===> App Server Developers
===> Asterisk
===> Bluetooth Dongle
===> CX88 Blackbird Drivers
===> DCE Router Developers
===> DCE library General
===> DCE Router Users
===> Disk Drive
===> GC100 Users
===> Mozilla Plugin
===> MythTV Player Users
===> MythTV Player Developers
===> Pluto Main General Issues
===> Pluto Main Installation & IR codes
===> MythTV Plugin Users
===> Orbiter - Users
===> Orbiter - Developers
===> Orbiter Mobile - Users
===> Standard Plugins
===> Xine Player - Users
===> Xine Player - Developers
===> Xine Plugin
===> Request Action Library (RA)
-----------------------------
Standalone DCE
-----------------------------
=> Developers
Loading...