Description of problem: mysql clean install will not start because no tables were created. # head -13 /var/log/mysqld/mysqld.log mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql /usr/sbin/mysqld: Table 'mysql.plugin' doesn't exist [ERROR] Can't open the mysql.plugin table. Please run mysql_upgrade to create it. InnoDB: The InnoDB memory heap is disabled InnoDB: Mutexes and rw_locks use GCC atomic builtins InnoDB: Compressed tables use zlib 1.2.5 InnoDB: Using Linux native AIO InnoDB: Initializing buffer pool, size = 128.0M InnoDB: Completed initialization of buffer pool InnoDB: highest supported file format is Barracuda. InnoDB: Waiting for the background threads to start InnoDB: 1.1.8 started; log sequence number 1595675 [ERROR] Fatal error: Can't open and lock privilege tables: Table 'mysql.host' doesn't exist Version-Release number of selected component (if applicable): How reproducible: Always Steps to Reproduce: 1. clean install, apply all updates, reboot 2. click up a terminal 3. su - root 4. urpmi --auto mysql 5. service mysqld restart 6. as soon as it fails, service mysqld stop If you look over in /var/lib/mysql/mysql, you will see no database files. Since I run mythtv, this is a show stopper for me. :(
CC: (none) => alien, arnaud.patard, balcaen.john, dmorganec, guillomovitch
Hi, thanks for reporting this bug. As there is no maintainer for this package I added the committers in CC. (Please set the status to 'assigned' if you are working on it)
i just want to note that my last commit essentially made the logs working, which it didn't before. i tried to reproduce this with a local build of mariadb (instead of mysql), but it had no problems generating the mysql database (at least not inside a chroot), even with a maybe serious bug: "/usr/share/rpm-helper/add-service: regel 112: /bin/systemctl: Bestand of map bestaat niet" odd, since by default it should be sysvinit, it was top of the choice thus auto should've picked it up... so, i donno why this /bin/systemctl is here? it may be related to that? or perhaps the permissions are just wrong? It may be cold of myself, but since i'm planning on obsoleting mysql, i'm not really inclined to assign this bug to myself. sorry. at least there's perhaps some info to go on.
just some info on this ticket. mysql had no maintainer and i'm planning on obsoleting tmysql with mariadb, with mariadb this issue is normally resolved, so i'm closing this as wontfix.
Status: NEW => RESOLVEDResolution: (none) => WONTFIX