Opened 8 years ago

Closed 8 years ago

Last modified 8 years ago

#11698 closed Bug Report - General (Invalid)

mythtv will not connect to mythconverg database

Reported by: robert.peake@… Owned by:
Priority: minor Milestone: unknown
Component: MythTV - General Version: 0.26-fixes
Severity: medium Keywords:
Cc: Ticket locked: yes


Version: mythtv 2:2.0.26+fixes.20121118.340ubuntu1 Ubuntu 13.04 64-bit: AMD Phenom II x6 1090T

I am attempting to configure MythTV backend for use with XBMC.

Myth backend 0.26 is installed on my server with IP MySQL connections have been established for database mythconverg, user mythtv at host name on port 3306 and are accessible locally and remotely [verified using MySQL Workbench]. Running the backend setup [sudo /usr/bin/mythtv-setup] and entering for the IP, 3306 for the port, mythconverg for the database name and mythtv as the user with the password, as listed in config.xml, and proceeding to FINISH results in the error: "MythTV could not connect to the database. Please verify your database settings below."

I have run sudo dpkg-reconfigure mythtv-common to no avail. My config.xml:



<PingHost?>1</PingHost?> <Host></Host> <UserName?>mythtv</UserName?> <Password>85ctXLIf</Password> <DatabaseName?>mythconverg</DatabaseName?> <Port>3306</Port>

</Database> <WakeOnLAN>

<Enabled>0</Enabled> <SQLReconnectWaitTime>0</SQLReconnectWaitTime> <SQLConnectRetry>5</SQLConnectRetry> <Command>echo 'WOLsqlServerCommand not set'</Command>



I did not get the error message before editing the IP address from the default "localhost" to the static IP address of the backend server. I have not been able to find a workaround and conclude this is a bug.

Please let me know the name and location of any files you would like me to submit.

Change History (3)

comment:1 Changed 8 years ago by Kenni Lund [kenni a kelu dot dk]

Resolution: Invalid
Status: newclosed

Please seek help on the mythtv-users mailing list. From the information you have provided, this appears to be a configuration issue on your system.

comment:2 Changed 8 years ago by robert.peake@…

Just so we are clear, I develop Java enterprise, container-managed database programs running in a Glassfish embedded container and using MySQL as the database. Thus, I have acquired a modicum of experience in resolving configuration issues. Though you seem reluctant to acknowledge it, a configuration that works perfectly well in MySQL cannot be made to work in MythTV (at least not by any apparent means). Whether this is a "bug" or a deficiency in documentation, it seriously impairs the usability of your program. Since there seems to be obvious disinterest in improving the program by resolving a recurring issue, I will not in future take the time and effort to file bug reports.

comment:3 Changed 8 years ago by Raymond Wagner

Ticket locked: set

Your first issue reported here was a problem you were experiencing in Mythbuntu. They have a script wrapped around mythtv-setup that adds a lot of additional behavior, specifically the behavior you were having trouble with. While we do not want to discourage use of Mythbuntu, we do not maintain it here, and thus cannot support problems with it here.

This issue you are experiencing here is a user configuration issue. MythTV sets up initial access to the mythconverg database for the local machine and the username and password mythtv when the mc.sql file is manually imported by the user. Any GRANTs beyond that need to be configured manually by the user, as described in the documentation. Access to the database from other machines requires manual changes to the database server configuration, also described in the documentation. MythTV is not given administrative privileges to the database server or the host system, and thus cannot make these changes for you. User configuration issues are to be dealt with through user support channels, either the mailing list or IRC channel. Much of the database configuration is performed automatically by Mythbuntu, but then as mentioned before, we do not maintain it here, and cannot support it here.

Note: See TracTickets for help on using tickets.