Description of problem: mythtv requires timezone information loaded into the mysql schema. During timezone loading you get: Warning: Unable to load '/usr/share/zoneinfo/iso3166.tab' as time zone. Skipping it. Version-Release number of selected component (if applicable): How reproducible: Always Steps to Reproduce: 1. systemctl restart mysqld 2. /usr/bin/mysqladmin -u sysdba password 'secret' 3. mysql_tzinfo_to_sql /usr/share/zoneinfo | mysql --user=sysdba --password=secret mysql Reproducible: Steps to Reproduce:
Keywords: (none) => TriagedCC: (none) => luigiwalserAssignee: bugsquad => dmorganec
/usr/share/zoneinfo/posix is a symlink to '.' (aka the current directory in which that symlink is stored, aka /usr/share/zoneinfo), due to a change made upstream. Make sure the symlink is correct on your system (the code in the package to create this has gone through a few iterations, so if you've been upgrading a Cauldron system, you may have hit a transient issue with it being incorrect). Otherwise there's no apparent reason mythtv shouldn't be able to load iso3166.tab or any problem with the timezone package indicated here.
Assignee: dmorganec => mageiaSummary: 4_rc: /usr/share/zoneinfo/posix/posix symlink recursion => mythtv unable to load timezone informationSource RPM: timezone-2013i-2.mga4.src.rpm => mythtv
(In reply to David Walser from comment #1) > /usr/share/zoneinfo/posix is a symlink to '.' (aka the current directory in > which that symlink is stored, aka /usr/share/zoneinfo), due to a change made > upstream. Make sure the symlink is correct on your system I think you are saying this is correct. $ ll /usr/share/zoneinfo/posix lrwxrwxrwx 1 root root 1 Jan 19 14:57 /usr/share/zoneinfo/posix -> . (the code in the > package to create this has gone through a few iterations, so if you've been > upgrading a Cauldron system, you may have hit a transient issue with it > being incorrect). Pretty sure it is not a transit iteration problem. Downloaded Mageia-4-RC-x86_64-DVD.iso, good sum check, did a Hard Disk boot and did a clean install. Set mirrors, did the urpmi --test to get all updates on system, then ran without the --test option. and rebooted. > Otherwise there's no apparent reason mythtv shouldn't be > able to load iso3166.tab or any problem with the timezone package indicated > here. Well if the following is normal, the novice user might wonder if there are problems. when viewing this result. For readability I removed the duplicate "Warning: Unable to load" strings. # mysql_tzinfo_to_sql /usr/share/zoneinfo | mysql --user=root --password=kitty50 mysql Warning: Unable to load '/usr/share/zoneinfo/iso3166.tab' as time zone. Skipping it. '/usr/share/zoneinfo/posix/iso3166.tab' as time zone. Skipping it. '/usr/share/zoneinfo/posix/posix': to avoid infinite symlink recursion. '/usr/share/zoneinfo/posix/zone.tab' as time zone. Skipping it. '/usr/share/zoneinfo/zone.tab' as time zone. Skipping it.
And that command actually comes from mariadb. What is the real issue here though? I see a bunch of warning messages there, but they are possibly harmless. What's the real bug you are seeing? Those warning messages actually make some sense, as mostly /usr/share/zoneinfo contains files and directories corresponding to timezones, but those tab files are not, and it wouldn't want to recurse into a symlink to itself. Is anything actually not working, or is this bug just about warning messages? I suppose perhaps they could be silenced.
CC: (none) => mageiaAssignee: mageia => alienSummary: mythtv unable to load timezone information => mariadb produces warning messages while loading timezone information (as used by mythtv)Source RPM: mythtv => mariadb
(In reply to David Walser from comment #3) > And that command actually comes from mariadb. > > What is the real issue here though? With a little more research, guessing all failures except maybe the symlink recursion message. > I see a bunch of warning messages there, but they are possibly harmless. "possibly" is the key word here. Originally I just assumed the other messages were caused by the recursion link. Since your comment, I did a cat on the other files and they all are data files. > What's the real bug you are seeing? Off hand I would say the "Warning:" messages, but as a coder, any warning, error, fatal message I send to the console needed to be resolved. > Those warning messages actually make some sense, as mostly > /usr/share/zoneinfo contains files and directories corresponding to > timezones, but those tab files are not, and it wouldn't want to recurse into > a symlink to itself. > > Is anything actually not working, I am not sure. MythTv seems ok but that may be because I am in Central USA zone and not affected by any of the data in those other tables. > or is this bug just about warning messages? I have no clue. As a system admin, any install "Warning" message issued from an application indicates something should be corrected on the system. > I suppose perhaps they could be silenced. Seems to me, that decision has to be made by someone who knows what is going on. If the application is going to skip those files by design, then the code should not have issued the Warning:. I can accept the suggestion that the recursion link should be silenced.
i'm gonna doublecheck if those files are actually skipped
I have read the report but not 100 % sure of how to solve this a) Don't print the warning about the symlink (as it's not relevant) and add code to silently skip warnings about .tab files (as they are not timezone files) b) Have an option to not print any warnings (--silent) c) Run by default silently and only print warnings if --verbose is given I am happy to implement any of the above solutions. Maybe a) is the best option ? Do you think it's a good solution to just skip files with the .tab extension?
CC: (none) => monty
(In reply to Michael Widenius from comment #6) > I have read the report but not 100 % sure of how to solve this > a) Don't print the warning about the symlink (as it's not relevant) I'll agree to that one. > and add > code to silently skip warnings about .tab files (as they are not timezone > files) Code should process known timezone files. If tab files are not timezone files code should not attempt to process them. That way fault logic is never triggered. > Do you think it's a good solution to just skip files with the .tab extension? If you know .tab files are not the kind of files to process, then yes, skip them and the fault code will not be triggered. > b) Have an option to not print any warnings (--silent) > c) Run by default silently and only print warnings if --verbose is given Off hand I would be afraid that would hide any real problems. :( > I am happy to implement any of the above solutions. > Maybe a) is the best option ? I'll vote yes for that.
I have now fixed this in MariaDB 5.5 source tree for MariaDB 5.5.35 Here is the commit comment: Fixed Mageia Bug 12355: mariadb produces warning messages while loading timezo - Warnings about wrong symlink messages or non-timezone files with '.tab' are - Added long option handling - Added --help, --verbose and --version options
well... that was quick... i guess the 5.5.35 will fix all that (after mga4 release)
"mysql_tzinfo_to_sql /usr/share/zoneinfo | mysql mysql" renders no errors here using mariadb-5.5.35-1.mga4 as of https://bugs.mageia.org/show_bug.cgi?id=9878#c24
CC: (none) => oe
isn't this one resolved ages ago?
closing as resolved, please reopen if needed.
Status: NEW => RESOLVEDResolution: (none) => FIXED