Summary: | emerge --config =dev-db/mysql-5.1.61 fails to create initial database | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Thomas Beutin <tb> |
Component: | Current packages | Assignee: | Gentoo Linux MySQL bugs team <mysql-bugs> |
Status: | RESOLVED OBSOLETE | ||
Severity: | normal | ||
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | AMD64 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: |
/var/tmp/portage/dev-db/mysql-5.1.61/temp/mysql_install_db.log
/var/log/mysql/mysqld.err |
Description
Thomas Beutin
2012-04-21 12:24:22 UTC
Created attachment 309717 [details]
/var/tmp/portage/dev-db/mysql-5.1.61/temp/mysql_install_db.log
Created attachment 309719 [details]
/var/log/mysql/mysqld.err
Actually, i'm able to start the mysql database even though the failed initialisation, but im unable to login. /var/log/mysql/mysqld.err contain now (additionally lines): 120421 14:26:36 [Warning] No argument was provided to --log-bin, and --log-bin-index was not used; so replication may break when this MySQL server acts as a master and has his hostname changed!! Please use '--log-bin=mysqld-bin' to avoid this problem. 120421 14:26:36 InnoDB: Initializing buffer pool, size = 16.0M 120421 14:26:36 InnoDB: Completed initialization of buffer pool InnoDB: The first specified data file ./ibdata1 did not exist: InnoDB: a new database to be created! 120421 14:26:36 InnoDB: Setting file ./ibdata1 size to 10 MB InnoDB: Database physically writes the file full: wait... 120421 14:26:37 InnoDB: Log file ./ib_logfile0 did not exist: new to be created InnoDB: Setting log file ./ib_logfile0 size to 5 MB InnoDB: Database physically writes the file full: wait... 120421 14:26:37 InnoDB: Log file ./ib_logfile1 did not exist: new to be created InnoDB: Setting log file ./ib_logfile1 size to 5 MB InnoDB: Database physically writes the file full: wait... InnoDB: Doublewrite buffer not found: creating new InnoDB: Doublewrite buffer created InnoDB: Creating foreign key constraint system tables InnoDB: Foreign key constraint system tables created 120421 14:26:37 InnoDB: Started; log sequence number 0 0 120421 14:26:37 [Note] Recovering after a crash using mysqld-bin 120421 14:26:37 [Note] Starting crash recovery... 120421 14:26:37 [Note] Crash recovery finished. 120421 14:26:37 [Note] Event Scheduler: Loaded 0 events 120421 14:26:37 [Note] /usr/sbin/mysqld: ready for connections. Version: '5.1.61-log' socket: '/var/run/mysqld/mysqld.sock' port: 3306 Gentoo Linux mysql-5.1.61 Stopping is also possible (more lines): 120421 14:32:05 [Note] /usr/sbin/mysqld: Normal shutdown 120421 14:32:05 [Note] Event Scheduler: Purging the queue. 0 events 120421 14:32:05 InnoDB: Starting shutdown... 120421 14:32:09 InnoDB: Shutdown completed; log sequence number 0 44233 120421 14:32:09 [Note] /usr/sbin/mysqld: Shutdown complete Unfortunally the trick from http://dev.mysql.com/doc/refman/5.1/en/resetting-permissions.html does not work: # mysql Welcome to the MySQL monitor. Commands end with ; or \g. Your MySQL connection id is 1 Server version: 5.1.61-log Gentoo Linux mysql-5.1.61 Copyright (c) 2000, 2011, Oracle and/or its affiliates. All rights reserved. Oracle is a registered trademark of Oracle Corporation and/or its affiliates. Other names may be trademarks of their respective owners. Type 'help;' or '\h' for help. Type '\c' to clear the current input statement. mysql> UPDATE mysql.user SET Password=PASSWORD('root') WHERE User='root'; Query OK, 0 rows affected (0.00 sec) Rows matched: 0 Changed: 0 Warnings: 0 mysql> FLUSH PRIVILEGES; Query OK, 0 rows affected (0.00 sec) mysql> \q Bye i still cannot login after regular restart. hm, after an almost sleepless night and reading a lot of stuff in the net i tried a microcode update using sys-kernel/amd-ucode. this leads to the following: # dmesg | tail -9 e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx NET: Registered protocol family 10 eth0: no IPv6 routers present mysqld[17565] general protection ip:7fa7efb1b47b sp:7fa7eda8c210 error:0 in libgcc_s.so.1[7fa7efb0c000+15000] microcode: CPU0: patch_level=0x05000026 microcode: CPU0: new patch_level=0x05000028 microcode: CPU1: patch_level=0x05000026 microcode: CPU1: new patch_level=0x05000028 microcode: Microcode Update Driver: v2.00 <tigran@aivazian.fsnet.co.uk>, Peter Oruba silencio ~ # emerge --config =dev-db/mysql-5.1.61 Configuring pkg... * Please provide a password for the mysql 'root' user now, in the * MYSQL_ROOT_PASSWORD env var or through the /root/.my.cnf file. * Avoid ["'\_%] characters in the password > * Retype the password > * Creating the mysql database and setting proper * permissions on it ... * Starting mysqld ... [ ok ] * Setting root password ... [ ok ] * Loading "zoneinfo", this step may require a few seconds ... ... [ ok ] * Stopping the server ... * Done Now i can start mysql and login to the database :) (i tried it again without the microcode patch after system startup and it failed like before) btw: this is the same machine as the one in the bug #381061 maybe i'll find the time to check next weekend. (In reply to comment #5) > btw: this is the same machine as the one in the bug #381061 > maybe i'll find the time to check next weekend. Has this been resolved? With your other bug listed as connected to the compilation failure meta bug, I'm inclined to ask if it was your hardware or something not related to MySQL. Yes, it seems that this problem is somewhat hardware related to the AMD E-350 Processor. After the microcode and BIOS update the whole system runs stable for months. Thanks! |