Description of problem: mga7 dev0 mythbackend fails to start. MySQL time zone support is missing. Please install it and try again. See 'mysql_tzinfo_to_sql' for assistance. Thought about opening problem against timezone-2018d-2.mga7.src.rpm but guessing fix should be in post install trigger for mythtv Version-Release number of selected component (if applicable): How reproducible: Always Steps to Reproduce: 1. systemctl start mysqld 2. mysql_tzinfo_to_sql /usr/share/zoneinfo | mysql --user=root ignore Warning: Unable to load for /usr/share/zoneinfo/leapseconds /usr/share/zoneinfo/posix/leapseconds /usr/share/zoneinfo/posix/tzdata.zi /usr/share/zoneinfo/tzdata.zi as time zone. Skipping it. 3. install transcode, perl-Net-UPnP, mythtv-frontend, perl-MythTV, mythtv-backend, mythtv-setup 4. run mythtv-setup 5. systemctl start mythbackend 6. systemctl status mythbackend Note startup failed. Workaround: See https://www.mythtv.org/wiki/MySQL_Time_Zone_Tables # cd /usr/share/zoneinfo/Etc # mv UTC UTC_bkup # ln -s ../Zulu UTC # mysql_tzinfo_to_sql /usr/share/zoneinfo | mysql --user=root Run step 5 and 6. Other mythtv install related bugs, bug 19127, bug 20227
That workaround shouldn't be necessary, as our timezone package does provide the Zulu file. The link said you only need to make the symlink if it's missing. If doing that really is necessary for it to work, that would be a bug in mariadb.
(In reply to David Walser from comment #1) > That workaround shouldn't be necessary, as our timezone package does provide > the Zulu file. Yes, it bother me that I found a UTC file where I had to place the link to get mythbackend to see the data. > The link said you only need to make the symlink if it's > missing. If doing that really is necessary for it to work, It was, since the previous 5+ clean installs failed mythbackend from starting. > that would be a bug in mariadb. I'll take your word for it and change Source rpm. Leaving summary as is so anyone searching for mythbackend error message can find this workaround.
Source RPM: mythtv-29.1-20180521.2.mga7.tainted.src.rpm => mariadb-10.3.9-1.mga7.src.rpm
(In reply to Bit Twister from comment #2) > > > The link said you only need to make the symlink if it's > > missing. If doing that really is necessary for it to work, > > It was, since the previous 5+ clean installs failed mythbackend from > starting. > > > that would be a bug in mariadb. > > I'll take your word for it and change Source rpm. Leaving summary as is so > anyone searching for mythbackend error message can find this workaround. Assigning to the basesystem maintainers and CC'ing the registered mariadb maintainer and the de facto maintainer.
Assignee: bugsquad => basesystemCC: (none) => alien, mageia, marja11
the only thing to be done is to run mysql_tzinfo_to_sql /usr/share/zoneinfo |mysql maybe it is a good idea to add these infos in postinstall
after install of mysql, the service is not started automatically, so we are not able to add this info in post stage.
you can add it as an README.urpmi.update to get it to show on rpm update
CC: (none) => tmb
thx, I'll put another line to README.urpmi, since this is no mysql-issue. And it depends on the use case if you really need this data.
Assignee: basesystem => mageia
added a new line to readme.urpmi
Status: NEW => RESOLVEDResolution: (none) => FIXED
(In reply to Marc Krämer from comment #4) > the only thing to be done is to run > mysql_tzinfo_to_sql /usr/share/zoneinfo |mysql I ran the mysql_tzinfo_to_sql on 5+ installs. None worked until I did the workaround. > maybe it is a good idea to add these infos in postinstall If adding the workaround in the infos, then Ok, but if just adding the command to run mysql_tzinfo_to_sql then that is not going to solve the problem.
You have to execute mysql_tzinfo_to_sql /usr/share/zoneinfo | mysql -D mysql which will select the mysql-database and run the insert statements on this database. Otherwise you will get an error like "you have to select a database..."