[mythtv-users] Re: Newbie: FC3 - MythTV backend setup - stuck. 2.
Also setup GUI issue. 3. Also UK settings?
Clive at Rational
clive at rational-communications.com
Wed Dec 29 13:22:10 UTC 2004
> Hello,
>
> I have searched through the MythTV mailing list
> and not found answer to this - sorry if it HAS
> already
> been answered.
>
> Setup: Conexant WinFast TV2000 XP input card
> (a.k.a GDI Black Gold) - works fine under WinXPPro
> SP2
> Trying to run card under MythTV on a Fedora Core 3
> (FC3) kernel 2.6.9.something.
>
> The TV signal is being provided from a "terrestrial"
> aerial / antenna.
>
Progress on issue 1 from previous posting -
mythtvsetup
I tried to re-connect to mythtvsetup to "fiddle" with
the settings to see if I could make something happen.
I got an Sql "connect failure" (see below). I went
back to the documentation. I ran the Sql commands
suggested, then re-ran mythtvsetup and tried
"mythfill" . All results are below. Basically I think
I have made some progress and now think the problem is
because 1. I do not have the correct UK settings for
the Conexant card. 2. I am in UK so the zap2it listing
service is not relevant to me.
Can anyone help me "step around" this listing problem
for now so I can just get on to "channel detection" in
UK and start viewing Freeview?
I also gave mythbackend a shot but I don't think it
achieved much. It's all below.
********************************************
[root at Linux28GHz ~]# mythtvsetup
Unable to connect to database!
Driver error was [1/1045]:
QMYSQL3: Unable to connect
Database error was:
Access denied for user: 'mythtv at localhost' (Using
password: YES)
Unable to open database:
Driver error was:
QMYSQL3: Unable to connect
Database error was:
Access denied for user: 'mythtv at localhost' (Using
password: YES)
[root at Linux28GHz ~]# ./mythtvsetup
bash: ./mythtvsetup: No such file or directory
[root at Linux28GHz ~]# cd /usr/bin
[root at Linux28GHz bin]# mythtvsetup
Unable to connect to database!
Driver error was [1/1045]:
QMYSQL3: Unable to connect
Database error was:
Access denied for user: 'mythtv at localhost' (Using
password: YES)
Unable to open database:
Driver error was:
QMYSQL3: Unable to connect
Database error was:
Access denied for user: 'mythtv at localhost' (Using
password: YES)
[root at Linux28GHz bin]#
[root at Linux28GHz bin]# mysql -u root mysql
Reading table information for completion of table and
column names
You can turn off this feature to get a quicker startup
with -A
Welcome to the MySQL monitor. Commands end with ; or
\g.
Your MySQL connection id is 7 to server version:
3.23.58
Type 'help;' or '\h' for help. Type '\c' to clear the
buffer.
mysql> UPDATE user SET Password=PASSWORD('**********')
WHERE user='root';
Query OK, 2 rows affected (0.25 sec)
Rows matched: 2 Changed: 2 Warnings: 0
mysql> FLUSH PRIVILEGES;
Query OK, 0 rows affected (0.05 sec)
mysql> quit
Bye
[root at Linux28GHz bin]# mysql -u root -p <
/usr/share/doc/mythtv-0.16/database/mc.sql
Enter password:
ERROR 1064 at line 4: You have an error in your SQL
syntax near 'TEMPORARY TABLES ON mythconverg.* TO
mythtv at localhost IDENTIFIED BY "mythtv"' at line 1
[root at Linux28GHz bin]# mythtvsetup 2004-12-29 09:10:36
Inserting MythTV initial database information.
2004-12-29 09:10:36 Upgrading to schema version 1003
2004-12-29 09:10:36 Upgrading to schema version 1004
2004-12-29 09:10:36 Upgrading to schema version 1005
2004-12-29 09:10:36 Upgrading to schema version 1006
2004-12-29 09:10:36 Upgrading to schema version 1007
2004-12-29 09:10:36 Upgrading to schema version 1008
2004-12-29 09:10:36 Upgrading to schema version 1009
2004-12-29 09:10:36 Upgrading to schema version 1010
2004-12-29 09:10:36 Upgrading to schema version 1011
2004-12-29 09:10:36 Upgrading to schema version 1012
2004-12-29 09:10:36 Upgrading to schema version 1013
2004-12-29 09:10:36 Upgrading to schema version 1014
2004-12-29 09:10:36 Upgrading to schema version 1015
2004-12-29 09:10:36 Upgrading to schema version 1016
2004-12-29 09:10:36 Upgrading to schema version 1017
2004-12-29 09:10:36 Upgrading to schema version 1018
2004-12-29 09:10:36 Upgrading to schema version 1019
2004-12-29 09:10:36 Upgrading to schema version 1020
2004-12-29 09:10:36 Upgrading to schema version 1021
2004-12-29 09:10:36 Upgrading to schema version 1022
2004-12-29 09:10:36 This could take a few minutes.
2004-12-29 09:10:36 Upgrading to schema version 1023
2004-12-29 09:10:36 Upgrading to schema version 1024
2004-12-29 09:10:36 Upgrading to schema version 1025
2004-12-29 09:10:36 Upgrading to schema version 1026
2004-12-29 09:10:36 Upgrading to schema version 1027
2004-12-29 09:10:36 Upgrading to schema version 1028
2004-12-29 09:10:36 Upgrading to schema version 1029
2004-12-29 09:10:36 Upgrading to schema version 1030
2004-12-29 09:10:36 Upgrading to schema version 1031
2004-12-29 09:10:36 Upgrading to schema version 1032
2004-12-29 09:10:36 Upgrading to schema version 1033
2004-12-29 09:10:36 Upgrading to schema version 1034
2004-12-29 09:10:36 Upgrading to schema version 1035
2004-12-29 09:10:36 Upgrading to schema version 1036
2004-12-29 09:10:36 Upgrading to schema version 1037
2004-12-29 09:10:36 Upgrading to schema version 1038
2004-12-29 09:10:36 Upgrading to schema version 1039
2004-12-29 09:10:36 Upgrading to schema version 1040
2004-12-29 09:10:36 Upgrading to schema version 1041
2004-12-29 09:10:36 Upgrading to schema version 1042
2004-12-29 09:10:36 Upgrading to schema version 1043
2004-12-29 09:10:36 Upgrading to schema version 1044
2004-12-29 09:10:36 Upgrading to schema version 1045
2004-12-29 09:10:36 Upgrading to schema version 1046
2004-12-29 09:10:36 Upgrading to schema version 1047
2004-12-29 09:10:36 Upgrading to schema version 1048
2004-12-29 09:10:36 Upgrading to schema version 1049
2004-12-29 09:10:36 Upgrading to schema version 1050
2004-12-29 09:10:36 Upgrading to schema version 1051
2004-12-29 09:10:36 Upgrading to schema version 1052
2004-12-29 09:10:36 Upgrading to schema version 1053
2004-12-29 09:10:36 Upgrading to schema version 1054
2004-12-29 09:10:36 Upgrading to schema version 1055
Would you like to clear all capture card
settings before starting configuration? [no] no
Would you like to clear all program/channel
settings before starting configuration? [no] yes
mythtv: could not connect to socket
mythtv: No such file or directory
lirc_init failed for mythtv, see preceding messages
If this is the master backend server:
Now, please run 'mythfilldatabase' to populate the
database
with channel information.
[root at Linux28GHz bin]# mythtvsetup
Would you like to clear all capture card
settings before starting configuration? [no] no
Would you like to clear all program/channel
settings before starting configuration? [no] yes
mythtv: could not connect to socket
mythtv: No such file or directory
lirc_init failed for mythtv, see preceding messages
Couldn't open If this is the master backend server:
Now, please run 'mythfilldatabase' to populate the
database
with channel information.
[root at Linux28GHz bin]# mythfilldatabase
Refreshing Tomorrow's data
Retrieving datadirect data...
Grabbing data for Wed Dec 29 2004 offset 1
>From : Thu Dec 30 00:00:00 2004 To : Fri Dec 31
00:00:00 2004 (UTC)
--09:16:36--
http://datadirect.webservices.zap2it.com/tvlistings/xtvdService
=> `-'
Resolving datadirect.webservices.zap2it.com...
206.18.98.160
Connecting to
datadirect.webservices.zap2it.com[206.18.98.160]:80...
connected.
HTTP request sent, awaiting response... 401
Unauthorized
Connecting to
datadirect.webservices.zap2it.com[206.18.98.160]:80...
connected.
HTTP request sent, awaiting response... 401
Unauthorized
Authorization failed.
Grab complete. Actual data from --09:16:41--
http://datadirect.webservices.zap2it.com/tvlistings/xtvdService
=> `-'
Resolving datadirect.webservices.zap2it.com...
206.18.98.160
Connecting to
datadirect.webservices.zap2it.com[206.18.98.160]:80...
connected.
HTTP request sent, awaiting response... 401
Unauthorized
Connecting to
datadirect.webservices.zap2it.com[206.18.98.160]:80...
connected.
HTTP request sent, awaiting response... 401
Unauthorized
Authorization failed.
<< repeat many,many times >>
--09:16:49--
http://datadirect.webservices.zap2it.com/tvlistings/xtvdService
=> `-'
Resolving datadirect.webservices.zap2it.com...
206.18.98.160
Connecting to
datadirect.webservices.zap2it.com[206.18.98.160]:80...
connected.
HTTP request sent, awaiting response... 401
Unauthorized
Connecting to
datadirect.webservices.zap2it.com[206.18.98.160]:80...
connected.
HTTP request sent, awaiting response... 401
Unauthorized
Authorization failed.
--09:16:50--
http://datadirect.webservices.zap2it.com/tvlistings/xtvdService
=> `-'
Resolving datadirect.webservices.zap2it.com...
206.18.98.160
Connecting to
datadirect.webservices.zap2it.com[206.18.98.160]:80...
connected.
HTTP request sent, awaiting response... 401
Unauthorized
Connecting to
datadirect.webservices.zap2it.com[206.18.98.160]:80...
connected.
HTTP request sent, awaiting response... 401
Unauthorized
Authorization failed.
[root at Linux28GHz bin]#
[root at Linux28GHz bin]# mythbackend &
[1] 12001
[root at Linux28GHz bin]# Starting up as the master
server.
2004-12-29 09:18:26 Channel::Open(): Can't open:
No such file or directory
2004-12-29 09:18:26 Channel::Open(): Can't open:
No such file or directory
Couldn't find input: Television on card
2004-12-29 09:18:26 Channel::Open(): Can't open:
No such file or directory
2004-12-29 09:18:26 Channel::Open(): Can't open:
No such file or directory
Couldn't find input: Television on card
2004-12-29 09:18:26 Channel::Open(): Can't open:
No such file or directory
2004-12-29 09:18:26 Channel::Open(): Can't open:
No such file or directory
Couldn't find input: Television on card
is defined, but isn't attached to a cardinput.
2004-12-29 09:18:26 mythbackend version:
0.16.20040906-1 www.mythtv.org
2004-12-29 09:18:26 Enabled verbose msgs : important
general
/mnt/store//nfslockfile.lock: No such file or
directory
Unable to open lockfile!
Be sure that '/mnt/store/' exists and that both
the directory and that file are writeable by this
user.
[1]+ Exit 255 mythbackend
[root at Linux28GHz bin]#
More information about the mythtv-users
mailing list