<div dir="ltr"><div dir="ltr"><br></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Sat, Jul 25, 2020 at 9:14 AM Bill Meek <<a href="mailto:keemllib@gmail.com">keemllib@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">On 7/25/20 10:55 AM, DryHeat122 wrote:<br>
> <br>
> <br>
> On Sat, Jul 25, 2020 at 8:17 AM Jim Abernathy <<a href="mailto:jfabernathy@gmail.com" target="_blank">jfabernathy@gmail.com</a> <mailto:<a href="mailto:jfabernathy@gmail.com" target="_blank">jfabernathy@gmail.com</a>>> wrote:<br>
> <br>
> <br>
> On 7/25/20 11:09 AM, DryHeat122 wrote:<br>
>> I am replacing my Ubuntu 16.04 setup with a clean install of Myth on a clean install of Utuntu 20.04. I have the old mythconverg backed<br>
>> up and am getting ready to restore. The wiki backend migration page <<a href="https://www.mythtv.org/wiki/Backend_migration" rel="noreferrer" target="_blank">https://www.mythtv.org/wiki/Backend_migration</a>> says "Depending on<br>
>> how your distribution initialises the database upon installation of the backend, you may need to use the procedure for replacing the<br>
>> database by the backup <<a href="https://www.mythtv.org/wiki/Database_Backup_and_Restore#Replacing_an_existing_database" rel="noreferrer" target="_blank">https://www.mythtv.org/wiki/Database_Backup_and_Restore#Replacing_an_existing_database</a>>."<br>
>><br>
>> The referenced page says: " If you are replacing an existing database with a known-good backup by using a full restore--for example,<br>
>> because your database has been corrupted or a database schema upgrade failed or you're replacing a package-provided database with your<br>
>> "old" database after re-installing your distro--you will need to drop the existing database. "<br>
>><br>
>> I don't know how 20.04 initializes the DB. I am not replacing the DB because of corruption or failed upgrade. Do I run<br>
>> <a href="http://mythconverg_restore.pl" rel="noreferrer" target="_blank">mythconverg_restore.pl</a> <<a href="http://mythconverg_restore.pl" rel="noreferrer" target="_blank">http://mythconverg_restore.pl</a>> with defaults or include the drop and create arguments? Also to be clear, I should<br>
>> restore the DB after installing myth but before running setup, right?<br>
> <br>
> The last time I created fresh and wanted to restore from a good backup I had just run on the old system, I did the following command:<br>
> <br>
> /usr/share/mythtv/<a href="http://mythconverg_restore.pl" rel="noreferrer" target="_blank">mythconverg_restore.pl</a> <<a href="http://mythconverg_restore.pl" rel="noreferrer" target="_blank">http://mythconverg_restore.pl</a>> --drop_database --create_database --filename /full path to<br>
> directory/mythconverg-1214-20080626150513.sql.gz<br>
> <br>
> <br>
> Jim A<br>
> <br>
> <br>
> Thanks. I tried that and it's denying me access to the database. The --verbose option shows it has the right username, but says DBHostName, <br>
> DBUserName, and DBPassword are not defined and its expecting to find them in the Mysql Options File. Not sure what options file it means or <br>
> what password to specify.<br>
<br>
The user running the program must have a valid config.xml. It falls back to the old mysql.txt and<br>
those are the old variable names. It appears that neither was found (and mysql.txt hasn't been<br>
used for years so that's good!).<br>
<br>
Ubuntu packaging creates /etc/mythtv/config.xml and adds symbolic links to it from the login user<br>
and mythtv user's ~/.mythtv/config.xml. At least, that's what it should do.<br>
<br>
-- <br>
Bill<br></blockquote><div><br></div><div>There is a valid config file in /home/mythtv/.mythtv and it has the password for the db. The help on <a href="http://mythconverg_restore.pl">mythconverg_restore.pl</a> says to create a backuprc in ~/.mythtv, but on my machine ~ equals /home/steve, not /home/mythtv. Also when running that script with --verbose it ways MYTHCONFDIR is /home/steve/.mythtv and there is no such directory. So there's the problem. I guess I could just create ~/.mythtv, but I don't know why the installer put everything in /home/mythtv instead and I'm worried this might lead to other problems down the line.</div></div></div>