Description of problem: Unable to do a clean install of mythtv and have mythbackend come up based on install documentation. mysqld Ver 10.1.16-MariaDB enforces medium password checking and and host id as part of login. 1. passwords in /usr/share/mythtv/initialdb/mc.sql need to be 8 characters or longer. 2. host id needs to match documentation and what the uses has to enter during mythtv-setup. 3. Environment=MYTHCONFDIR=@syscondir@/mythtv needs to match mythtv home directory seen in /etc/passwd. Version-Release number of selected component (if applicable): How reproducible: Always Steps to Reproduce: 1. click up a root terminal 2. mysql --user=root source /usr/share/mythtv/initialdb/mc.sql note password failure message. 3. run mythtv-setup change host 127.0.0.1 from localhost and use the new password used in step 2. 4. systemctl start mythbackend 5. grep -i syscondir /var/log/mythtv/* Note errors. Workarounds: For problems 1 and 2 change from mythtv@localhost IDENTIFIED BY "mythtv"; to mythtv@127.0.0.1 IDENTIFIED BY "mythtv_Password"; in /usr/share/mythtv/initialdb/mc.sql Rather than change /usr/lib/systemd/system/mythbackend.service if supplied via upstream, and may change over time, do the following: mkdir -p /etc/systemd/system/mythbackend.service.d/ cat > /etc/systemd/system/mythbackend.service.d/local.conf [Service] Environment=MYTHCONFDIR=/var/lib/mythtv ^d The ^d is a Ctrl+d used to close cat input to /etc/systemd/system/mythbackend.service.d/local.conf
Found that /etc/sysconfig/mythbackend is not setting MYTHTV_HOME Easy fix is to add it to /etc/systemd/system/mythbackend.service.d/local.conf cat > /etc/systemd/system/mythbackend.service.d/local.conf [Service] Environment=MYTHTV_HOME=/var/lib/mythtv Environment=MYTHCONFDIR=/var/lib/mythtv ^d
CC: (none) => geiger.david68210Assignee: bugsquad => mageia
https://bugs.mageia.org/show_bug.cgi?id=19223#c8 suggests a number is required in the password.
List of MythTv files needing new password: System: /usr/share/mythtv/initialdb/mc.sql /var/lib/mythtv/config.xml Users: $HOME/.mythtv/config.xml
After importing my mga5 mythtv dump on mga6, I could no longer log into mysql as root. Solution, o change root and mythtv passwords to pass mga6 mysql restrictions on mga5 o set new password in files in comment 3 on mga5 o export the mythconverg database to dump.sql o set same root password on mga6 as mga5 o /usr/bin/mysqladmin --user=root password 'new_pw' o mysql_tzinfo_to_sql /usr/share/zoneinfo | mysql --user=root --password=new_pw mysql o set new password in files in comment 3 on mga6 o mysql --user=root --password=new_pw mysql < dump.sql
Keywords: (none) => FOR_ERRATA6
Source RPM: mythtv-0.27.4-20141022.6.mga6.tainted.src.rpm => drakxtools-17.71-1.mga6.src.rpmSummary: 6_rc0: mythtv install problems => mythtv install problemsStatus comment: (none) => 6_s2
Status comment: 6_s2 => (none)Keywords: (none) => 6sta2
(In reply to Bit Twister from comment #4) > After importing my mga5 mythtv dump on mga6, I could no longer log into > mysql as root. root login problem was my fault. My dump contained the mysql schema. Removed mysql schema from the dump.
FYI: 0.28 on 11-April-2016
Source RPM: drakxtools-17.71-1.mga6.src.rpm => mythtv-0.27.4-20141022.11.mga6.tainted.src.rpm
Keywords: FOR_ERRATA6 => IN_ERRATA6CC: (none) => marja11
CC: (none) => wilcal.int
I'm going to start tinkering with this. The hardware I am using is a Hauppauge WinTV-HVR-955Q USB TV Tuner with a Mohu Leaf 50 TV Antenna.
Kaffeine works just fine on my test systems.
FYI: 29.0 released 01-February-2017
Source RPM: mythtv-0.27.4-20141022.11.mga6.tainted.src.rpm => mythtv-backend-29.1-20180521.2.mga7.tainted
CC'ing some more committers, because the registered maintainer is unavailable
CC: (none) => cjw, eatdirt, guillomovitch
See bug 24104 to get mythtv-setup to access to database. Might not hurt to get errata updated to have echo "MYTHTV_HOME=/var/lib/mythtv" >> /etc/sysconfig/mythbackend echo "MYTHCONFDIR=/var/lib/mythtv" >> /etc/sysconfig/mythbackend
mga6 users need to read https://bugs.mageia.org/show_bug.cgi?id=24104 mga7 users need just the above comment #11 workaround for mythtv-setup and mythbackend.
Fix in next mythtv-29.1-20181230.1.1.mga6 update and for cauldron too in mythtv-29.1-20181230.2.mga7
It looks as if this & bug 24243 could be fixed by either adapting /usr/share/doc/mythtv-doc/README /usr/share/doc/mythtv-doc/UPGRADING with the necessary instructions, if this is permitted; or create as suggested a /usr/share/doc/mythtv/README.mageia file about this reference https://bugs.mageia.org/show_bug.cgi?id=24243#c4 and https://bugs.mageia.org/show_bug.cgi?id=24243#c8 The registered maintainer for mythtv is no longer active, so assigning this globally. DavidG is already involved. Doubtful that we enhance ERRATA post release, but just in case this is possible, CC'ing Atelier.
Assignee: mageia => pkg-bugsCC: marja11 => atelier-bugs, lewyssmithSource RPM: mythtv-backend-29.1-20180521.2.mga7.tainted => mythtv-30.0-20190202.5.mga7.[tainted].src.rpmSee Also: (none) => https://bugs.mageia.org/show_bug.cgi?id=24243
Awaiting clarification of what points from comment 0 should be in ERRATA 7.
(In reply to Lewis Smith from comment #15) > Awaiting clarification of what points from comment 0 should be in ERRATA 7. mysql's requirement to have stronger passwords prevents mythtv install using a short password. Solution would be to change all IDENTIFIED BY "mythtv" to IDENTIFIED BY "mythtv_Password" in /usr/share/mythtv/initialdb/mc.sql and use mythtv_Password at all password prompts and ignore all documentation that indicates "mythtv" is to be used as password. User is responsible for picking a consent node/ip value.
Thanks for the note. Done.
Keywords: (none) => IN_ERRATA7Status: NEW => RESOLVEDResolution: (none) => WORKSFORME