Re: Fresh install of MySQL 5.6.23 fails to start on CentOS 7.0
Cameron, Did you run the recommended configuration script manually? mysql_install_db This is run once after install to put the stuff in your datadir= location which I pointed out may be missing (and was empty upon your inspection). Thanks, Robert
Re: Fresh install of MySQL 5.6.23 fails to start on CentOS 7.0
Cameron Mann cameron.mann at cybera.ca writes: Hi all, I've encountered a problem with MySQL 5.6.23 on CentOS 7.0 and would greatly appreciate any advice on what to do next. Synopsis: 1. Fresh install of CentOS 7.0 using minimal install ISO 2. yum update -y 3. rpm -i http://dev.mysql.com/get/mysql-community-release-el7- 5.noarch.rpm 4. yum install mysql-community-server -y 5. service mysqld start After installing mysql-community-server 5.6.23 on a fresh minimal install of CentOS 7.0 (running in VirtualBox 4.3.20) it will fail to start with the following error: Have you found any resolution for this as I'm having the exact same issue? Thanks -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql
Re: Fresh install of MySQL 5.6.23 fails to start on CentOS 7.0
Have you looked at the possible errors in http://man7.org/linux/man-pages/man3/pthread_create.3.html ? Seems like either a resource / ulimit thing, or perhaps limited by SELinux in some way? On Thu, Feb 19, 2015 at 12:11 AM, mike mdel...@rydin.com wrote: Cameron Mann cameron.mann at cybera.ca writes: Hi all, I've encountered a problem with MySQL 5.6.23 on CentOS 7.0 and would greatly appreciate any advice on what to do next. Synopsis: 1. Fresh install of CentOS 7.0 using minimal install ISO 2. yum update -y 3. rpm -i http://dev.mysql.com/get/mysql-community-release-el7- 5.noarch.rpm 4. yum install mysql-community-server -y 5. service mysqld start After installing mysql-community-server 5.6.23 on a fresh minimal install of CentOS 7.0 (running in VirtualBox 4.3.20) it will fail to start with the following error: Have you found any resolution for this as I'm having the exact same issue? Thanks -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql -- Regards, Rik Wasmus Head of Systems Administration T +31 53 480 58 63 M +31 6 380 67 332 F +31 53 480 58 61 rik.was...@takeaway.com Takeaway.com B.V. - Brouwerijstraat 10, 7523 XD Enschede, The Netherlands -- Takeaway.com http://www.takeaway.com/ | Thuisbezorgd.nl http://www.thuisbezorgd.nl/ | Lieferando.de http://www.lieferando.de/ | Lieferservice.de http://www.lieferservice.de/ | Lieferservice.at http://www.lieferservice.at/ | Lieferservice.ch http://www.lieferservice.ch/ | Pyszne.pl http://www.pyszne.pl/ | Pizza.be http://www.pizza.be/ | Pizza.fr http://www.pizza.fr/ | Pizza.lu http://www.pizza.lu/ No rights can be derived from this message.
Re: Fresh install of MySQL 5.6.23 fails to start on CentOS 7.0
Mike, check the datadir (usually /var/lib/mysql). If it's empty, manually execute mysql_install_db. This will place an initial db in place and mysql will start from then on On 02/18/2015 03:11 PM, mike wrote: Cameron Mann cameron.mann at cybera.ca writes: Hi all, I've encountered a problem with MySQL 5.6.23 on CentOS 7.0 and would greatly appreciate any advice on what to do next. Synopsis: 1. Fresh install of CentOS 7.0 using minimal install ISO 2. yum update -y 3. rpm -i http://dev.mysql.com/get/mysql-community-release-el7- 5.noarch.rpm 4. yum install mysql-community-server -y 5. service mysqld start After installing mysql-community-server 5.6.23 on a fresh minimal install of CentOS 7.0 (running in VirtualBox 4.3.20) it will fail to start with the following error: Have you found any resolution for this as I'm having the exact same issue? Thanks -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql
Re: Fresh install of MySQL 5.6.23 fails to start on CentOS 7.0
Dammit, that should've come from the other account with that work-signature...
Re: Fresh install of MySQL 5.6.23 fails to start on CentOS 7.0
Hi Robert, The value in my.cnf is datadir=/var/lib/mysql. The directory is initially empty, which I believe is normal; there shouldn't be anything in there until mysqld is started for the first time (at least that's the behaviour of 5.6.22, which works fine). After mysqld fails to start, an empty mysql directory is created. Cameron On Thu, Feb 12, 2015 at 2:35 PM, Bob Eby eby...@gmail.com wrote: Hi Cameron, I've seen a similar error running on windows 7. When you look in your datadir= specified in my.ini what is there exactly (hopefully not empty)? Do you have a mysql folder containing plugin.* files at this location? (say .MYI etc) It sounds like your data folders were either not copied to the correct place or not properly configured before starting the server. It's been a while, but I recall there being an install step to getting the correct basic database files into your datadir specified in my.ini. Good Luck, Robert Eby -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql
Re: Fresh install of MySQL 5.6.23 fails to start on CentOS 7.0
Hi Cameron, I've seen a similar error running on windows 7. When you look in your datadir= specified in my.ini what is there exactly (hopefully not empty)? Do you have a mysql folder containing plugin.* files at this location? (say .MYI etc) It sounds like your data folders were either not copied to the correct place or not properly configured before starting the server. It's been a while, but I recall there being an install step to getting the correct basic database files into your datadir specified in my.ini. Good Luck, Robert Eby
Re: Fresh install of MySQL 5.6.23 fails to start on CentOS 7.0
The mysql_upgrade errors look like the mysql command line client can't be located by the script... some kind of path error induced by a security fix I'm thinking On 02/12/2015 12:37 PM, Cameron Mann wrote: Hi all, I've encountered a problem with MySQL 5.6.23 on CentOS 7.0 and would greatly appreciate any advice on what to do next. Synopsis: 1. Fresh install of CentOS 7.0 using minimal install ISO 2. yum update -y 3. rpm -i http://dev.mysql.com/get/mysql-community-release-el7-5.noarch.rpm 4. yum install mysql-community-server -y 5. service mysqld start After installing mysql-community-server 5.6.23 on a fresh minimal install of CentOS 7.0 (running in VirtualBox 4.3.20) it will fail to start with the following error: $ sudo service mysqld start Redirecting to /bin/systemctl start mysqld.service Job for mysqld.service failed. See 'systemctl status mysqld.service' and 'journalctl -xn' for details. $ systemctl status mysqld.service mysqld.service - MySQL Community Server Loaded: loaded (/usr/lib/systemd/system/mysqld.service; enabled) Active: activating (start-post) since Thu 2015-02-12 20:07:08 UTC; 1min 30s ago Process: 5643 ExecStart=/usr/bin/mysqld_safe (code=exited, status=0/SUCCESS) Process: 5632 ExecStartPre=/usr/bin/mysql-systemd-start pre (code=exited, status=0/SUCCESS) Main PID: 5643 (code=exited, status=0/SUCCESS); : 5644 (mysql-systemd-s) CGroup: /system.slice/mysqld.service └─control ├─5644 /bin/bash /usr/bin/mysql-systemd-start post └─6115 sleep 1 Snippet from mysqld.log: 150212 19:47:08 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql 2015-02-12 19:47:08 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details). 2015-02-12 19:47:08 1244 [Warning] Buffered warning: Changed limits: max_open_files: 1024 (requested 5000) 2015-02-12 19:47:08 1244 [Warning] Buffered warning: Changed limits: table_cache: 431 (requested 2000) 2015-02-12 19:47:08 1244 [Note] Plugin 'FEDERATED' is disabled. /usr/sbin/mysqld: Table 'mysql.plugin' doesn't exist 2015-02-12 19:47:08 1244 [ERROR] Can't open the mysql.plugin table. Please run mysql_upgrade to create it. 2015-02-12 19:47:08 1244 [Note] InnoDB: Using atomics to ref count buffer pool pages 2015-02-12 19:47:08 1244 [Note] InnoDB: The InnoDB memory heap is disabled 2015-02-12 19:47:08 1244 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins 2015-02-12 19:47:08 1244 [Note] InnoDB: Memory barrier is not used 2015-02-12 19:47:08 1244 [Note] InnoDB: Compressed tables use zlib 1.2.3 2015-02-12 19:47:08 1244 [Note] InnoDB: Using Linux native AIO 2015-02-12 19:47:08 1244 [Note] InnoDB: Using CPU crc32 instructions 2015-02-12 19:47:08 1244 [Note] InnoDB: Initializing buffer pool, size = 128.0M 2015-02-12 19:47:08 1244 [Note] InnoDB: Completed initialization of buffer pool InnoDB: Error: pthread_create returned 13 150212 19:47:08 mysqld_safe mysqld from pid file /var/run/mysqld/mysqld.pid ended The suggested mysql_upgrade command gives the following output: $ mysql_upgrade Looking for 'mysql' as: mysql Looking for 'mysqlcheck' as: mysqlcheck FATAL ERROR: Upgrade failed $ mysql_upgrade -uroot --password= Warning: Using a password on the command line interface can be insecure. Looking for 'mysql' as: mysql Looking for 'mysqlcheck' as: mysqlcheck FATAL ERROR: Upgrade failed I've also observed the same behaviour on a CentOS 7.0 image (I believe from http://cloud.centos.org) running in OpenStack under the KVM hypervisor. I have not been able to test in a non-virtualized environment. I've attempted rebooting before and after installation of mysql-community-server to no effect. Previous versions of 5.6.x appear unaffected. Cameron Mann -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql
Re: Fresh install of MySQL 5.6.23 fails to start on CentOS 7.0
Well Mr Harald, I admit... It's not an out of the box behaviour put there by Oracle/MySQL. But it IS a behaviour introduced by distribution packagers and and it's only invoked the first time the db is start is attempted AND there is no basic db in place. mysql_install_db actually won't run without being forced on an installed system. Folks have come to expect it and it IS handy (when I tell MySQL to start, it just works, even if it's never been run before). Isn't that the entire idea behind all of the freedesktop junk... Things just work? Except when they don't. What slobs! On 02/12/2015 03:11 PM, Reindl Harald wrote: Am 13.02.2015 um 00:03 schrieb Bruce Ferrell: If the datadir is empty. you have to execute a different utility mysql_install_db. This will create a correct initial database. Jesus! I HATE systemd. The sysV init script handled this correctly. tell me *one* reason why it is the job of the init-system to check and fire up mysql_install_db at each start? guess what happens when that shell snippet makes a mistake and does that on a existing install frankly my mysql database was installed in 2003 on a windows machine and is the root for every mysql setup from then on Windows, OSX and Linux from MySQL 3.x to MariaDB 5.x up to MariaDB 10.x why would i want to do all the crap about set a sane default password for each and every install when tehre is a template setup? On 02/12/2015 02:06 PM, Cameron Mann wrote: Hi Robert, The value in my.cnf is datadir=/var/lib/mysql. The directory is initially empty, which I believe is normal; there shouldn't be anything in there until mysqld is started for the first time (at least that's the behaviour of 5.6.22, which works fine). After mysqld fails to start, an empty mysql directory is created. Cameron On Thu, Feb 12, 2015 at 2:35 PM, Bob Eby eby...@gmail.com wrote: Hi Cameron, I've seen a similar error running on windows 7. When you look in your datadir= specified in my.ini what is there exactly (hopefully not empty)? Do you have a mysql folder containing plugin.* files at this location? (say .MYI etc) It sounds like your data folders were either not copied to the correct place or not properly configured before starting the server. It's been a while, but I recall there being an install step to getting the correct basic database files into your datadir specified in my.ini -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql
Re: Fresh install of MySQL 5.6.23 fails to start on CentOS 7.0
It worked before, when you manually had to execute the script... It worked when the script was auto invoked. Now it's silently busted, causing problems for people you think that's OK. Whatever. Moving on On 02/12/2015 03:45 PM, Reindl Harald wrote: Am 13.02.2015 um 00:35 schrieb Bruce Ferrell: Well Mr Harald, I admit... It's not an out of the box behaviour put there by Oracle/MySQL. But it IS a behaviour introduced by distribution packagers and and it's only invoked the first time the db is start is attempted AND there is no basic db in place. mysql_install_db actually won't run without being forced on an installed system. Folks have come to expect it and it IS handy (when I tell MySQL to start, it just works, even if it's never been run before). Isn't that the entire idea behind all of the freedesktop junk... Things just work? Except when they don't. if you setup a *server* you have to configure the *server* if you don't mind to run a simple command don't setup a *server* honestly see all the damage left and right caused by servers (mail, web, adatabase...) by trained monkeys i whish there would be a ton of more barriers to at least require *some thougts* besides fine, i have no clue but it seems to work somehow for whatever reason -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql
Re: Fresh install of MySQL 5.6.23 fails to start on CentOS 7.0
If the datadir is empty. you have to execute a different utility mysql_install_db. This will create a correct initial database. Jesus! I HATE systemd. The sysV init script handled this correctly. On 02/12/2015 02:06 PM, Cameron Mann wrote: Hi Robert, The value in my.cnf is datadir=/var/lib/mysql. The directory is initially empty, which I believe is normal; there shouldn't be anything in there until mysqld is started for the first time (at least that's the behaviour of 5.6.22, which works fine). After mysqld fails to start, an empty mysql directory is created. Cameron On Thu, Feb 12, 2015 at 2:35 PM, Bob Eby eby...@gmail.com wrote: Hi Cameron, I've seen a similar error running on windows 7. When you look in your datadir= specified in my.ini what is there exactly (hopefully not empty)? Do you have a mysql folder containing plugin.* files at this location? (say .MYI etc) It sounds like your data folders were either not copied to the correct place or not properly configured before starting the server. It's been a while, but I recall there being an install step to getting the correct basic database files into your datadir specified in my.ini. Good Luck, Robert Eby -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql
Re: Fresh install of MySQL 5.6.23 fails to start on CentOS 7.0
Am 13.02.2015 um 00:35 schrieb Bruce Ferrell: Well Mr Harald, I admit... It's not an out of the box behaviour put there by Oracle/MySQL. But it IS a behaviour introduced by distribution packagers and and it's only invoked the first time the db is start is attempted AND there is no basic db in place. mysql_install_db actually won't run without being forced on an installed system. Folks have come to expect it and it IS handy (when I tell MySQL to start, it just works, even if it's never been run before). Isn't that the entire idea behind all of the freedesktop junk... Things just work? Except when they don't. if you setup a *server* you have to configure the *server* if you don't mind to run a simple command don't setup a *server* honestly see all the damage left and right caused by servers (mail, web, adatabase...) by trained monkeys i whish there would be a ton of more barriers to at least require *some thougts* besides fine, i have no clue but it seems to work somehow for whatever reason signature.asc Description: OpenPGP digital signature
Re: Fresh install of MySQL 5.6.23 fails to start on CentOS 7.0
Am 13.02.2015 um 00:03 schrieb Bruce Ferrell: If the datadir is empty. you have to execute a different utility mysql_install_db. This will create a correct initial database. Jesus! I HATE systemd. The sysV init script handled this correctly. tell me *one* reason why it is the job of the init-system to check and fire up mysql_install_db at each start? guess what happens when that shell snippet makes a mistake and does that on a existing install frankly my mysql database was installed in 2003 on a windows machine and is the root for every mysql setup from then on Windows, OSX and Linux from MySQL 3.x to MariaDB 5.x up to MariaDB 10.x why would i want to do all the crap about set a sane default password for each and every install when tehre is a template setup? On 02/12/2015 02:06 PM, Cameron Mann wrote: Hi Robert, The value in my.cnf is datadir=/var/lib/mysql. The directory is initially empty, which I believe is normal; there shouldn't be anything in there until mysqld is started for the first time (at least that's the behaviour of 5.6.22, which works fine). After mysqld fails to start, an empty mysql directory is created. Cameron On Thu, Feb 12, 2015 at 2:35 PM, Bob Eby eby...@gmail.com wrote: Hi Cameron, I've seen a similar error running on windows 7. When you look in your datadir= specified in my.ini what is there exactly (hopefully not empty)? Do you have a mysql folder containing plugin.* files at this location? (say .MYI etc) It sounds like your data folders were either not copied to the correct place or not properly configured before starting the server. It's been a while, but I recall there being an install step to getting the correct basic database files into your datadir specified in my.ini signature.asc Description: OpenPGP digital signature
