Re: mysql_upgrade then mysqld. I feel very ID-10-T PEBKAC today
Subject: Re: mysql_upgrade then mysqld. I feel very ID-10-T PEBKAC today > 2018-02-23T14:02:33.962240Z 0 [ERROR] [MY-010735] Can't open the mysql.plugin table. Please run mysql_upgrade to create it. > How do I run mysql_upgrade if the mysqld server won't start? Please don't bother to answer, I did figure it out, I'm sorry, for a bad question and worse followup. Apparently I'm a spammer as well. Apparently the error was caused by something else besides plugins in my configuration. After carefully running --initialize from scratch and modifying my.ini I was able to get mysqld.exe up and running just fine on Windows 64 for MySQL 8.0 RC. After that mysql_upgrade worked a treat. I did have a couple issues since it was my first time *NOT* using --initialize_insecure in this configuration but it all works if you do it right. As per usual. Sorry for the noise here, Robert Eby
Re: mysql_upgrade then mysqld. I feel very ID-10-T PEBKAC today
Am 23.02.2018 um 15:15 schrieb Bob Eby: 2018-02-23T14:02:33.962240Z 0 [ERROR] [MY-010735] Can't open the mysql.plugin table. Please run mysql_upgrade to create it. How do I run mysql_upgrade if the mysqld server won't start? post the *full* errorlog and watch for invaluid config stuff most likely start mysqld without grant-tables (CAUTION: every user with and without password works for that time from everywhere!) would break the loop so that "mysql_upgrade" suceeds and after that *mmedidiatly* start the sevrer again with permission system enabled https://stackoverflow.com/questions/1708409/how-to-start-mysql-with-skip-grant-tables https://ma.ttias.be/mysql-table-mysql-plugin-doesnt-exist-after-mysql-upgrade/ -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql
mysql_upgrade then mysqld. I feel very ID-10-T PEBKAC today
2018-02-23T14:02:33.962240Z 0 [ERROR] [MY-010735] Can't open the mysql.plugin table. Please run mysql_upgrade to create it. How do I run mysql_upgrade if the mysqld server won't start? Man how stupid am I? -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql
Start mysqld 5.7.7 with new disk
Hello I had to replace the datadisk where mysql had its innodb files. But after I had added a new disk I'm not able to initialize mysql files any more: # mysqld --initialize --user=mysql 2015-12-23T13:07:08.216472Z 0 [ERROR] Plugin 'InnoDB' init function returned error. 2015-12-23T13:07:08.216556Z 0 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed. 2015-12-23T13:07:08.216577Z 0 [ERROR] Failed to initialize plugins. 2015-12-23T13:07:08.216595Z 0 [ERROR] Aborting I have created the directories stored in my /etc/my.cnf and changed group and ownership to the directories to mysql:mysql Any suggestions how to fix this? -- Jørn Dahl-Stamnes homepage: http://photo.dahl-stamnes.net/ -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql
Re: Start mysqld 5.7.7 with new disk
Am 23.12.2015 um 14:11 schrieb Jørn Dahl-Stamnes: I had to replace the datadisk where mysql had its innodb files. But after I had added a new disk I'm not able to initialize mysql files any more: # mysqld --initialize --user=mysql 2015-12-23T13:07:08.216472Z 0 [ERROR] Plugin 'InnoDB' init function returned error. 2015-12-23T13:07:08.216556Z 0 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed. 2015-12-23T13:07:08.216577Z 0 [ERROR] Failed to initialize plugins. 2015-12-23T13:07:08.216595Z 0 [ERROR] Aborting I have created the directories stored in my /etc/my.cnf and changed group and ownership to the directories to mysql:mysql man mysql_install_db NAME mysql_install_db - initialize MariaDB data directory SYNOPSIS mysql_install_db [options] DESCRIPTION mysql_install_db initializes the MariaDB data directory and creates the system tables that it contains, if they do not exist. To invoke mysql_install_db, use the following syntax: shell> mysql_install_db [options] Because the MariaDB server, mysqld, needs to access the data directory when it runs later, you should either run mysql_install_db from the same account that will be used for running mysqld or run it as root and use the --user option to indicate the user name that mysqld will run as. It might be necessary to specify other options such as --basedir or --datadir if mysql_install_db does not use the correct locations for the installation directory or data directory. For example: shell> bin/mysql_install_db --user=mysql \ --basedir=/opt/mysql/mysql \ --datadir=/opt/mysql/mysql/data signature.asc Description: OpenPGP digital signature
Re: Start mysqld 5.7.7 with new disk
On Wednesday, December 23, 2015, Jørn Dahl-Stamnes wrote: > Hello > > I had to replace the datadisk where mysql had its innodb files. > > But after I had added a new disk I'm not able to initialize mysql files any > more: > > # mysqld --initialize --user=mysql > 2015-12-23T13:07:08.216472Z 0 [ERROR] Plugin 'InnoDB' init function > returned error. 2015-12-23T13:07:08.216556Z 0 [ERROR] Plugin 'InnoDB' > registration as a STORAGE ENGINE failed. 2015-12-23T13:07:08.216577Z 0 > [ERROR] Failed to initialize plugins. 2015-12-23T13:07:08.216595Z 0 > [ERROR] Aborting Is'nt it typical... after I posted my message I found the error in my /etc/my.cnf file. I had changed this line: innodb_data_file_path = ibdata1:60G;ibdata2:60G;ibdata3:60G;ibdata4:60G:;ibdata5:60G:autoextend Notice the extra column in "ibdata4:60G:". After I removed it, it worked. -- Jørn Dahl-Stamnes homepage: http://photo.dahl-stamnes.net/ -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql
Re: Getting error while launching mysqld
Have you changed the default mysqld port? Could you share with us the below command output? $ my_print_defaults mysqld -- *Wagner Bianchi, MySQL Database Specialist* Mobile: +55.31.8654.9510 E-mail: m...@wagnerbianchi.com Twitter: @wagnerbianchijr 2014-09-04 4:33 GMT-03:00 Banerjee, Somnath somnath_baner...@mentor.com: Hi, We are getting following error while launching mysqld_safe in local machine. Any help would be appreciated. -- connect to address 127.0.0.1 port 544: Connection refused connect to address 127.0.0.1 port 544: Connection refused trying normal rsh (/usr/bin/rsh) - The command used is: rsh $HOST -n mysql install dir/bin/mysqld_safe --defaults-file=$MYSQL_CONFIG --port=$PORT
RE: Getting error while launching mysqld
Thanks a lot. I changed rsh to ssh and things worked ! -somnath From: shawn l.green [shawn.l.gr...@oracle.com] Sent: Friday, September 05, 2014 8:21 PM To: mysql@lists.mysql.com Subject: Re: Getting error while launching mysqld Hello Somnath, On 9/4/2014 3:33 AM, Banerjee, Somnath wrote: Hi, We are getting following error while launching mysqld_safe in local machine. Any help would be appreciated. -- connect to address 127.0.0.1 port 544: Connection refused connect to address 127.0.0.1 port 544: Connection refused trying normal rsh (/usr/bin/rsh) - The command used is: rsh $HOST -n mysql install dir/bin/mysqld_safe --defaults-file=$MYSQL_CONFIG --port=$PORT This looks more like a problem with your permissions to use the rsh command than MySQL. MySQL should never operate on port 554 as that is already reserved for a different well-known service. -- Shawn Green MySQL Senior Principal Technical Support Engineer Oracle USA, Inc. - Hardware and Software, Engineered to Work Together. Office: Blountville, TN -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql
Getting error while launching mysqld
Hi, We are getting following error while launching mysqld_safe in local machine. Any help would be appreciated. -- connect to address 127.0.0.1 port 544: Connection refused connect to address 127.0.0.1 port 544: Connection refused trying normal rsh (/usr/bin/rsh) - The command used is: rsh $HOST -n mysql install dir/bin/mysqld_safe --defaults-file=$MYSQL_CONFIG --port=$PORT
Re: open files in mysqld 5.1.53
Am 12.06.2013 12:33, schrieb Manuel Arostegui: 2013/6/12 walter harms wha...@bfs.de Hi list, i am trying to understand the incredible use of filepointers in our mysql server (5.1.53). under normal condition the server reports 10k-15k open files pointer. I run a 'flush tables' every 2h to avoid problems, the number of users/connections is constant It is an automatic system but a few human users, a happy mix of myisam and innodb tables running with no problems on mysqld 5.0 . But now sometimes i am hit with an insane increase hitting the ceiling at 60k. I do not like the idea to increase the limit further because i do not understand why this is happening (I seems to happen at random times). I am running out of idea what my cause the unexpected increase, any idea what to watch ? I had a similar problem some years ago with 5.0.84. It was a database with thousand of tables (mostly in MyISAM). It turned to be the --myisam-recover option in Debian init scripts ( /usr/share/mysql/debian-start.inc.sh) . Obviously it's not a good idea to remove it, as if the server crashes, you will needed it. This used to be our db server after getting started: dXX:~# find /proc/`cat /var/run/mysqld/mysqld.pid`/fd -follow -type f 2/dev/null | wc -l 116810 This is what I saw at the time after removing that MyISAM check: dXX:~# find /proc/`cat /var/run/mysqld/mysqld.pid`/fd -follow -type f 2/dev/null | wc -l 10730 I would not recommend to keep this as a for-good-solution but a temporary one till you decide what to do. We migrated most of the tables to InnoDB (there was no reason to keep them as MyISAM, it was just legacy stuff). And these problems were gone. I don't know if this can be your case, but this is what happened to us. Hello Manuel, thx for your tip. We caught the problem when we moved to partitions. Strange is that while testing the problem did not show up and even now we no clue why we experience the sudden burst of use for file descriptors. btw: i checked for that option and it seems that it is not set on the commandline maybe it is hidden somewhere, since we use the mysql_safe wapper it should no be but you never know. re, wh -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql
Re: open files in mysqld 5.1.53
Am 13.06.2013 12:07, schrieb Hartmut Holzgraefe: On 06/13/2013 09:41 AM, walter harms wrote: Hello Manuel, thx for your tip. We caught the problem when we moved to partitions. Strange is that while testing the problem did not show up and even now we no clue why we experience the sudden burst of use for file descriptors. problem with partitions is that all partition files get opened when a partitioned table is used, even when only actually touching a single partition this combined with file-per-table engines like MyISAM or ARCHIVE (maybe with InnoDB with innodb-file-per-table being active, too?) may well lead to a lot of file handles being used, and this again combined with the table_cache keeping opened tables (and the related files) open for later reuse can lead to a lot of file handles being used and kept in use ... FLUSH TABLES may help here by at least releasing those handles that are just kept open by the table cache ... see also bug reports like e.g. http://bugs.mysql.com/bug.php?id=64498 yes that seems related, a quick check show that we have ~800 file/table we have already increased our files limit some time ago, so this should not be a problem. re, wh -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql
Re: open files in mysqld 5.1.53
On 06/13/2013 09:41 AM, walter harms wrote: Hello Manuel, thx for your tip. We caught the problem when we moved to partitions. Strange is that while testing the problem did not show up and even now we no clue why we experience the sudden burst of use for file descriptors. problem with partitions is that all partition files get opened when a partitioned table is used, even when only actually touching a single partition this combined with file-per-table engines like MyISAM or ARCHIVE (maybe with InnoDB with innodb-file-per-table being active, too?) may well lead to a lot of file handles being used, and this again combined with the table_cache keeping opened tables (and the related files) open for later reuse can lead to a lot of file handles being used and kept in use ... FLUSH TABLES may help here by at least releasing those handles that are just kept open by the table cache ... see also bug reports like e.g. http://bugs.mysql.com/bug.php?id=64498 -- hartmut -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql
Re: open files in mysqld 5.1.53
Am 13.06.2013 12:07, schrieb Hartmut Holzgraefe: this combined with file-per-table engines like MyISAM or ARCHIVE (maybe with InnoDB with innodb-file-per-table being active, too?) may well lead to a lot of file handles being used, and this again combined with the table_cache keeping opened tables (and the related files) open for later reuse can lead to a lot of file handles being used and kept in use ... FLUSH TABLES may help here by at least releasing those handles that are just kept open by the table cache ... it is a simple calculation but the handling is wrong 4861x32 = 12 471206 / 12 = 3 each table has 3 files on disk (frm, myd, myi) however - i do not buy the logic that every of the 32 cached threads had accessed ANY of the 4861 tables - impossible, there are databases from websites which have very low traffic and so it is unlikely that in 3 days avery thread has accessed every table on the machine __ [root@localhost:~]$ lsof | grep mysqld | wc -l 471206 nobody but oracle knows why there are so much file handles and this is MySQL 5.5.32 [--] Data in MyISAM tables: 481M (Tables: 4861) [OK] Highest usage of available connections: 6% (32/500) [OK] Thread cache hit rate: 99% (32 created / 425K connections) signature.asc Description: OpenPGP digital signature
Re: open files in mysqld 5.1.53
Am 12.06.2013 12:03, schrieb walter harms: i am trying to understand the incredible use of filepointers in our mysql server (5.1.53). under normal condition the server reports 10k-15k open files pointer harmless :-) [root@localhost:~]$ lsof | grep mysqld | wc -l 471206 nobody but oracle knows why there are so much file handles and this is MySQL 5.5.32 [--] Data in MyISAM tables: 481M (Tables: 4861) [OK] Highest usage of available connections: 6% (32/500) [OK] Thread cache hit rate: 99% (32 created / 425K connections) signature.asc Description: OpenPGP digital signature
Re: open files in mysqld 5.1.53
2013/6/12 walter harms wha...@bfs.de Hi list, i am trying to understand the incredible use of filepointers in our mysql server (5.1.53). under normal condition the server reports 10k-15k open files pointer. I run a 'flush tables' every 2h to avoid problems, the number of users/connections is constant It is an automatic system but a few human users, a happy mix of myisam and innodb tables running with no problems on mysqld 5.0 . But now sometimes i am hit with an insane increase hitting the ceiling at 60k. I do not like the idea to increase the limit further because i do not understand why this is happening (I seems to happen at random times). I am running out of idea what my cause the unexpected increase, any idea what to watch ? I had a similar problem some years ago with 5.0.84. It was a database with thousand of tables (mostly in MyISAM). It turned to be the --myisam-recover option in Debian init scripts ( /usr/share/mysql/debian-start.inc.sh) . Obviously it's not a good idea to remove it, as if the server crashes, you will needed it. This used to be our db server after getting started: dXX:~# find /proc/`cat /var/run/mysqld/mysqld.pid`/fd -follow -type f 2/dev/null | wc -l 116810 This is what I saw at the time after removing that MyISAM check: dXX:~# find /proc/`cat /var/run/mysqld/mysqld.pid`/fd -follow -type f 2/dev/null | wc -l 10730 I would not recommend to keep this as a for-good-solution but a temporary one till you decide what to do. We migrated most of the tables to InnoDB (there was no reason to keep them as MyISAM, it was just legacy stuff). And these problems were gone. I don't know if this can be your case, but this is what happened to us. Hope this helps. Manuel.
RE: Innodb, MySQL 5.5.28 - Would an incorrect setting in my.cnf cause mysqld to randomly crash on high load?
Nothing looks bad. 96G for the buffer_pool is bigger than I have experienced, but I know of no reason for it to fail (given that you have 128GB of RAM). -Original Message- From: Tom [mailto:livefortheda...@gmail.com] Sent: Wednesday, November 21, 2012 5:17 PM To: mysql@lists.mysql.com Subject: Innodb, MySQL 5.5.28 - Would an incorrect setting in my.cnf cause mysqld to randomly crash on high load? We have a high-end server, 128GB RAM, 32 Core , Xeon, SSD RAID 10 - running Ubuntu 12.04 with MySQL 5.5.28 . Doing random imports to large InnoDB tables, over 50+ gigs, randomly after a few hours of heavy load, mysql does a Signal 11 and crashes. We have tried to move hardware. Doing a full dump (but not a restore yet) gives no issues. Usually on corrupted tables, a dump would fail no? Below is the crash log and my.cnf . --- 12:45:4 UTC - mysqld got signal 11 ; This could be because you hit a bug. It is also possible that this binary or one of the libraries it was linked against is corrupt, improperly built, or misconfigured. This error can also be caused by malfunctioning hardware. We will try our best to scrape up some info that will hopefully help diagnose the problem, but since we have already crashed, something is definitely wrong and this may fail. key_buffer_size=536870912 read_buffer_size=131072 max_used_connections=324 max_threads=200 thread_count=308 connection_count=308 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 965187 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. Thread pointer: 0x7fc7eb1b5040 Attempting backtrace. You can use the following information to find out where mysqld died. If you see no messages after this, something went terribly wrong... stack_bottom = 7fadf6abfe60 thread_stack 0x3 /usr/sbin/mysqld(my_print_stacktrace+0x29)[0x7fc758522759] /usr/sbin/mysqld(handle_fatal_signal+0x483)[0x7fc7583e9ae3] /lib/x86_64-linux-gnu/libpthread.so.0(+0xfcb0)[0x7fc75713bcb0] /usr/sbin/mysqld(+0x6671b0)[0x7fc75863a1b0] /usr/sbin/mysqld(+0x61d6b9)[0x7fc7585f06b9] /usr/sbin/mysqld(+0x630d12)[0x7fc758603d12] /usr/sbin/mysqld(+0x6319c2)[0x7fc7586049c2] /usr/sbin/mysqld(+0x631d85)[0x7fc758604d85] /usr/sbin/mysqld(+0x626e7d)[0x7fc7585f9e7d] /usr/sbin/mysqld(+0x633cea)[0x7fc758606cea] /usr/sbin/mysqld(+0x6347e2)[0x7fc7586077e2] /usr/sbin/mysqld(+0x624426)[0x7fc7585f7426] /usr/sbin/mysqld(+0x610871)[0x7fc7585e3871] /usr/sbin/mysqld(+0x5d4cb0)[0x7fc7585a7cb0] /usr/sbin/mysqld(+0x5b7c9c)[0x7fc75858ac9c] /usr/sbin/mysqld(_ZN7handler21read_multi_range_nextEPP18st_key_multi_ra nge+0x24)[0x7fc7583e9fe4] /usr/sbin/mysqld(_ZN18QUICK_RANGE_SELECT8get_nextEv+0x3c)[0x7fc7584a3c8 c] /usr/sbin/mysqld(+0x4e9195)[0x7fc7584bc195] /usr/sbin/mysqld(_Z10sub_selectP4JOINP13st_join_tableb+0x71)[0x7fc7582f 1741] /usr/sbin/mysqld(+0x32f025)[0x7fc758302025] /usr/sbin/mysqld(_ZN4JOIN4execEv+0x4a5)[0x7fc758311155] /usr/sbin/mysqld(_Z12mysql_selectP3THDPPP4ItemP10TABLE_LISTjR4ListIS1_E S2_jP8st_orderSB_S2_SB_yP13select_resultP18st_select_lex_unitP13st_sele ct_lex+0x130)[0x7fc75830d000] /usr/sbin/mysqld(_Z13handle_selectP3THDP3LEXP13select_resultm+0x17c)[0x 7fc758312f5c] /usr/sbin/mysqld(+0x2f66b4)[0x7fc7582c96b4] /usr/sbin/mysqld(_Z21mysql_execute_commandP3THD+0x16d8)[0x7fc7582d1118] /usr/sbin/mysqld(_Z11mysql_parseP3THDPcjP12Parser_state+0x10f)[0x7fc758 2d5daf] /usr/sbin/mysqld(_Z16dispatch_command19enum_server_commandP3THDPcj+0x13 80)[0x7fc7582d7200] /usr/sbin/mysqld(_Z24do_handle_one_connectionP3THD+0x1bd)[0x7fc75837b7a d] /usr/sbin/mysqld(handle_one_connection+0x50)[0x7fc75837b810] /lib/x86_64-linux-gnu/libpthread.so.0(+0x7e9a)[0x7fc757133e9a] /lib/x86_64-linux-gnu/libc.so.6(clone+0x6d)[0x7fc756864cbd] Trying to get some variables. Some pointers may be invalid and cause the dump to abort. Query (7faa4c18e440): is an invalid pointer Connection ID (thread ID): 2286 Status: NOT_KILLED The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains information that should help you find out what is causing the crash. 121120 12:48:48 [Note] Plugin 'FEDERATED' is disabled. 121120 12:48:48 InnoDB: The InnoDB memory heap is disabled 121120 12:48:48 InnoDB: Mutexes and rw_locks use GCC atomic builtins 121120 12:48:48 InnoDB: Compressed tables use zlib 1.2.3.4 121120 12:48:48 InnoDB: Initializing buffer pool, size = 96.0G 121120 12:48:56 InnoDB: Completed initialization of buffer pool 121120 12:48:57 InnoDB: highest supported file format is Barracuda. InnoDB: Log scan progressed past the checkpoint lsn 1341738337497 121120 12:48:58 InnoDB: Database was not shut down normally! InnoDB: Starting crash recovery. InnoDB: Reading tablespace information from the .ibd files... InnoDB: Restoring possible half-written data pages from the doublewrite InnoDB: buffer... InnoDB: Doing recovery: scanned up to log
Re: Innodb, MySQL 5.5.28 - Would an incorrect setting in my.cnf cause mysqld to randomly crash on high load?
Hi Tom, I am assuming nothing relevant shows up in dmesg, right? I have experienced random crashes like that and most of them turned to be HW issues - hard disk and memory banks related. Is it a HW RAID? Have you tried looking at the controller logs? (Megacli). And yes, corrupted tables would fail when restoring them (or even when backuping them). Good luck! Manuel 2012/11/26, Rick James rja...@yahoo-inc.com: Nothing looks bad. 96G for the buffer_pool is bigger than I have experienced, but I know of no reason for it to fail (given that you have 128GB of RAM). -Original Message- From: Tom [mailto:livefortheda...@gmail.com] Sent: Wednesday, November 21, 2012 5:17 PM To: mysql@lists.mysql.com Subject: Innodb, MySQL 5.5.28 - Would an incorrect setting in my.cnf cause mysqld to randomly crash on high load? We have a high-end server, 128GB RAM, 32 Core , Xeon, SSD RAID 10 - running Ubuntu 12.04 with MySQL 5.5.28 . Doing random imports to large InnoDB tables, over 50+ gigs, randomly after a few hours of heavy load, mysql does a Signal 11 and crashes. We have tried to move hardware. Doing a full dump (but not a restore yet) gives no issues. Usually on corrupted tables, a dump would fail no? Below is the crash log and my.cnf . --- 12:45:4 UTC - mysqld got signal 11 ; This could be because you hit a bug. It is also possible that this binary or one of the libraries it was linked against is corrupt, improperly built, or misconfigured. This error can also be caused by malfunctioning hardware. We will try our best to scrape up some info that will hopefully help diagnose the problem, but since we have already crashed, something is definitely wrong and this may fail. key_buffer_size=536870912 read_buffer_size=131072 max_used_connections=324 max_threads=200 thread_count=308 connection_count=308 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 965187 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. Thread pointer: 0x7fc7eb1b5040 Attempting backtrace. You can use the following information to find out where mysqld died. If you see no messages after this, something went terribly wrong... stack_bottom = 7fadf6abfe60 thread_stack 0x3 /usr/sbin/mysqld(my_print_stacktrace+0x29)[0x7fc758522759] /usr/sbin/mysqld(handle_fatal_signal+0x483)[0x7fc7583e9ae3] /lib/x86_64-linux-gnu/libpthread.so.0(+0xfcb0)[0x7fc75713bcb0] /usr/sbin/mysqld(+0x6671b0)[0x7fc75863a1b0] /usr/sbin/mysqld(+0x61d6b9)[0x7fc7585f06b9] /usr/sbin/mysqld(+0x630d12)[0x7fc758603d12] /usr/sbin/mysqld(+0x6319c2)[0x7fc7586049c2] /usr/sbin/mysqld(+0x631d85)[0x7fc758604d85] /usr/sbin/mysqld(+0x626e7d)[0x7fc7585f9e7d] /usr/sbin/mysqld(+0x633cea)[0x7fc758606cea] /usr/sbin/mysqld(+0x6347e2)[0x7fc7586077e2] /usr/sbin/mysqld(+0x624426)[0x7fc7585f7426] /usr/sbin/mysqld(+0x610871)[0x7fc7585e3871] /usr/sbin/mysqld(+0x5d4cb0)[0x7fc7585a7cb0] /usr/sbin/mysqld(+0x5b7c9c)[0x7fc75858ac9c] /usr/sbin/mysqld(_ZN7handler21read_multi_range_nextEPP18st_key_multi_ra nge+0x24)[0x7fc7583e9fe4] /usr/sbin/mysqld(_ZN18QUICK_RANGE_SELECT8get_nextEv+0x3c)[0x7fc7584a3c8 c] /usr/sbin/mysqld(+0x4e9195)[0x7fc7584bc195] /usr/sbin/mysqld(_Z10sub_selectP4JOINP13st_join_tableb+0x71)[0x7fc7582f 1741] /usr/sbin/mysqld(+0x32f025)[0x7fc758302025] /usr/sbin/mysqld(_ZN4JOIN4execEv+0x4a5)[0x7fc758311155] /usr/sbin/mysqld(_Z12mysql_selectP3THDPPP4ItemP10TABLE_LISTjR4ListIS1_E S2_jP8st_orderSB_S2_SB_yP13select_resultP18st_select_lex_unitP13st_sele ct_lex+0x130)[0x7fc75830d000] /usr/sbin/mysqld(_Z13handle_selectP3THDP3LEXP13select_resultm+0x17c)[0x 7fc758312f5c] /usr/sbin/mysqld(+0x2f66b4)[0x7fc7582c96b4] /usr/sbin/mysqld(_Z21mysql_execute_commandP3THD+0x16d8)[0x7fc7582d1118] /usr/sbin/mysqld(_Z11mysql_parseP3THDPcjP12Parser_state+0x10f)[0x7fc758 2d5daf] /usr/sbin/mysqld(_Z16dispatch_command19enum_server_commandP3THDPcj+0x13 80)[0x7fc7582d7200] /usr/sbin/mysqld(_Z24do_handle_one_connectionP3THD+0x1bd)[0x7fc75837b7a d] /usr/sbin/mysqld(handle_one_connection+0x50)[0x7fc75837b810] /lib/x86_64-linux-gnu/libpthread.so.0(+0x7e9a)[0x7fc757133e9a] /lib/x86_64-linux-gnu/libc.so.6(clone+0x6d)[0x7fc756864cbd] Trying to get some variables. Some pointers may be invalid and cause the dump to abort. Query (7faa4c18e440): is an invalid pointer Connection ID (thread ID): 2286 Status: NOT_KILLED The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains information that should help you find out what is causing the crash. 121120 12:48:48 [Note] Plugin 'FEDERATED' is disabled. 121120 12:48:48 InnoDB: The InnoDB memory heap is disabled 121120 12:48:48 InnoDB: Mutexes and rw_locks use GCC atomic builtins 121120 12:48:48 InnoDB: Compressed tables use zlib 1.2.3.4 121120 12:48:48 InnoDB: Initializing buffer pool, size = 96.0G 121120 12:48:56 InnoDB: Completed initialization of buffer pool 121120 12:48:57
mysqld cannot start.
Hi, guys, I'm new to MySQL. I installed MySQL step-by-step according to the manual from source code. The version is mysql-5.5.28. When I start the server using: #bin/mysqld_safe --user=mysql The server failed to start with the following message in the log (attached below). There're two problems according to the log messages: 1. 121112 13:00:59 [ERROR] Can't read from messagefile '/usr/local/mysql/data/errmsg.sys I'm confused because I do have this file which is owned by user mysql: #ll /usr/local/mysql/data/errmsg.sys -rw-r--r-- 1 mysql mysql 0 Nov 12 12:35 /usr/local/mysql/data/errmsg.sys 2. 121112 13:00:59 [ERROR] An old style --language value with language specific part detected: /usr/local/mysql/data/ I commented the lc-messages-dir configuration entry in the my.cnf, but the error still exists... Could anyone take a look at the error log? Thanks a lot! T -- 121112 13:00:59 mysqld_safe Starting mysqld daemon with databases from /usr/local/mysql/data 121112 13:00:59 [ERROR] An old style --language value with language specific part detected: /usr/local/mysql/data/ 121112 13:00:59 [ERROR] Use --lc-messages-dir without language specific part instead. 121112 13:00:59 [ERROR] Can't read from messagefile '/usr/local/mysql/data/errmsg.sys' 121112 13:00:59 InnoDB: The InnoDB memory heap is disabled 121112 13:00:59 InnoDB: Mutexes and rw_locks use GCC atomic builtins 121112 13:00:59 InnoDB: Compressed tables use zlib 1.2.3.4 121112 13:00:59 InnoDB: Initializing buffer pool, size = 128.0M 121112 13:00:59 InnoDB: Completed initialization of buffer pool 121112 13:00:59 InnoDB: highest supported file format is Barracuda. 121112 13:00:59 InnoDB: Waiting for the background threads to start 121112 13:01:00 InnoDB: 1.1.8 started; log sequence number 1595675 121112 13:01:00 [ERROR] Aborting 121112 13:01:00 InnoDB: Starting shutdown... 121112 13:01:00 InnoDB: Shutdown completed; log sequence number 1595675 121112 13:01:00 [Note] 121112 13:01:00 mysqld_safe mysqld from pid file /var/run/mysqld/mysqld.pid ended 121112 13:03:49 mysqld_safe Starting mysqld daemon with databases from /usr/local/mysql/data 121112 13:03:49 [ERROR] Can't find messagefile '/usr/share/errmsg.sys' 121112 13:03:49 InnoDB: The InnoDB memory heap is disabled 121112 13:03:49 InnoDB: Mutexes and rw_locks use GCC atomic builtins 121112 13:03:49 InnoDB: Compressed tables use zlib 1.2.3.4 121112 13:03:49 InnoDB: Initializing buffer pool, size = 128.0M 121112 13:03:49 InnoDB: Completed initialization of buffer pool 121112 13:03:49 InnoDB: highest supported file format is Barracuda. 121112 13:03:49 InnoDB: Waiting for the background threads to start 121112 13:03:50 InnoDB: 1.1.8 started; log sequence number 1595675 121112 13:03:50 [ERROR] Aborting 121112 13:03:50 InnoDB: Starting shutdown... 121112 13:03:50 InnoDB: Shutdown completed; log sequence number 1595675 121112 13:03:50 [Note] 121112 13:03:50 mysqld_safe mysqld from pid file /var/run/mysqld/mysqld.pid ended -- Tianyin XU, http://cseweb.ucsd.edu/~tixu/
Re: mysqld cannot start.
On Mon, Nov 12, 2012 at 2:11 PM, Tianyin Xu t...@cs.ucsd.edu wrote: Hi, guys, I'm new to MySQL. I installed MySQL step-by-step according to the manual from source code. The version is mysql-5.5.28. When I start the server using: #bin/mysqld_safe --user=mysql The server failed to start with the following message in the log (attached below). There're two problems according to the log messages: 1. 121112 13:00:59 [ERROR] Can't read from messagefile '/usr/local/mysql/data/errmsg.sys I'm confused because I do have this file which is owned by user mysql: #ll /usr/local/mysql/data/errmsg.sys -rw-r--r-- 1 mysql mysql 0 Nov 12 12:35 /usr/local/mysql/data/errmsg.sys Check the permissions of all the dirs in that path: /usr, /usr/local, /usr/local/mysql, /usr/local/mysql/data. The mysql user will need r-x access to all of them. 2. 121112 13:00:59 [ERROR] An old style --language value with language specific part detected: /usr/local/mysql/data/ I commented the lc-messages-dir configuration entry in the my.cnf, but the error still exists... Don't know what platform you're on, but on my Mac I had this issue, and I got around it by starting the server with: --lc-messages-dir=/usr/local/mysql/share/ On CentOS and RHEL I did not have this issue. HTH- larry -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql
Re: mysqld cannot start.
Hi, Larry, Thanks a lot for the reply! On Mon, Nov 12, 2012 at 1:27 PM, Larry Martell larry.mart...@gmail.comwrote: On Mon, Nov 12, 2012 at 2:11 PM, Tianyin Xu t...@cs.ucsd.edu wrote: Hi, guys, I'm new to MySQL. I installed MySQL step-by-step according to the manual from source code. The version is mysql-5.5.28. When I start the server using: #bin/mysqld_safe --user=mysql The server failed to start with the following message in the log (attached below). There're two problems according to the log messages: 1. 121112 13:00:59 [ERROR] Can't read from messagefile '/usr/local/mysql/data/errmsg.sys I'm confused because I do have this file which is owned by user mysql: #ll /usr/local/mysql/data/errmsg.sys -rw-r--r-- 1 mysql mysql 0 Nov 12 12:35 /usr/local/mysql/data/errmsg.sys Check the permissions of all the dirs in that path: /usr, /usr/local, /usr/local/mysql, /usr/local/mysql/data. The mysql user will need r-x access to all of them. I already did so. It's weird... From the log, it seems that mysqld encountered some problem when reading the messagefile. But the file does exist with permission. 2. 121112 13:00:59 [ERROR] An old style --language value with language specific part detected: /usr/local/mysql/data/ I commented the lc-messages-dir configuration entry in the my.cnf, but the error still exists... Don't know what platform you're on, but on my Mac I had this issue, and I got around it by starting the server with: --lc-messages-dir=/usr/local/mysql/share/ I'm working on Ubuntu-12.04. Yes, the configuration parameter is set as /usr/local/mysql/data/ (see the error message). I tried your setting but this time mysqld tells me 121112 13:46:28 [ERROR] bin/mysqld: unknown variable 'lc-message-dir=/usr/local/mysql/share/' 121112 13:46:28 [ERROR] Aborting What a mess... On CentOS and RHEL I did not have this issue. HTH- larry Probably I shall go to GDB to understand what's happening here... Great thanks! T -- Tianyin XU, http://cseweb.ucsd.edu/~tixu/
Re: mysqld cannot start.
On Mon, Nov 12, 2012 at 1:47 PM, Tianyin Xu t...@cs.ucsd.edu wrote: Hi, Larry, Thanks a lot for the reply! On Mon, Nov 12, 2012 at 1:27 PM, Larry Martell larry.mart...@gmail.comwrote: On Mon, Nov 12, 2012 at 2:11 PM, Tianyin Xu t...@cs.ucsd.edu wrote: Hi, guys, I'm new to MySQL. I installed MySQL step-by-step according to the manual from source code. The version is mysql-5.5.28. When I start the server using: #bin/mysqld_safe --user=mysql The server failed to start with the following message in the log (attached below). There're two problems according to the log messages: 1. 121112 13:00:59 [ERROR] Can't read from messagefile '/usr/local/mysql/data/errmsg.sys I'm confused because I do have this file which is owned by user mysql: #ll /usr/local/mysql/data/errmsg.sys -rw-r--r-- 1 mysql mysql 0 Nov 12 12:35 /usr/local/mysql/data/errmsg.sys Check the permissions of all the dirs in that path: /usr, /usr/local, /usr/local/mysql, /usr/local/mysql/data. The mysql user will need r-x access to all of them. I already did so. It's weird... From the log, it seems that mysqld encountered some problem when reading the messagefile. But the file does exist with permission. 2. 121112 13:00:59 [ERROR] An old style --language value with language specific part detected: /usr/local/mysql/data/ I commented the lc-messages-dir configuration entry in the my.cnf, but the error still exists... Don't know what platform you're on, but on my Mac I had this issue, and I got around it by starting the server with: --lc-messages-dir=/usr/local/mysql/share/ I'm working on Ubuntu-12.04. Yes, the configuration parameter is set as /usr/local/mysql/data/ (see the error message). I tried your setting but this time mysqld tells me 121112 13:46:28 [ERROR] bin/mysqld: unknown variable 'lc-message-dir=/usr/local/mysql/share/' 121112 13:46:28 [ERROR] Aborting What a mess... Oh, the above error message is caused by my typo. Yes, I set --lc-messages-dir=/usr/local/mysql/share/, and everything's ok... The latter error message (i.e., messagefile) is the chain reaction caused by the previous one (lc-messages-dir) which confused me. Thanks a lot, Larry! Tianyin On CentOS and RHEL I did not have this issue. HTH- larry Probably I shall go to GDB to understand what's happening here... Great thanks! T -- Tianyin XU, http://cseweb.ucsd.edu/~tixu/ -- Tianyin XU, http://cseweb.ucsd.edu/~tixu/
most mysqld instances running with 100% CPU
i notice since this night all mysqld instances suing innodb are running at very high CPU, there is nothing in the mysqld-log and after restarting the service the same again i do not think this has to to with the reason taking back 5.5.25 becasue no disk-IO, i more doubt this has to do with the time-correction-second (not sure how to translate Schaltsekunde to english) because it started late at night __ http://dev.mysql.com/doc/refman/5.5/en/news-5-5-25a.html BTW: since there are announcements of new versions of mysqld it is very rude take them back without any announcement and put after weeks some lines in the old changelog which nobody reads after rollout however, as said, i doubt this is not the problem signature.asc Description: OpenPGP digital signature
Re: most mysqld instances running with 100% CPU
Hi, * On Sun, Jul 01, 2012 at 12:44:42PM +0200, Reindl Harald h.rei...@thelounge.net wrote: i notice since this night all mysqld instances suing innodb are running at very high CPU, there is nothing in the mysqld-log and after restarting the service the same again i do not think this has to to with the reason taking back 5.5.25 becasue no disk-IO, i more doubt this has to do with the time-correction-second (not sure how to translate Schaltsekunde to english) because it started late at night __ http://dev.mysql.com/doc/refman/5.5/en/news-5-5-25a.html BTW: since there are announcements of new versions of mysqld it is very rude take them back without any announcement and put after weeks some lines in the old changelog which nobody reads after rollout however, as said, i doubt this is not the problem It has to do with http://bugs.mysql.com/bug.php?id=65778 More analysis here: http://blog.mozilla.org/it/2012/06/30/mysql-and-the-leap-second-high-cpu-and-the-fix/ http://serverfault.com/questions/403732/anyone-else-experiencing-high-rates-of-linux-server-crashes-during-a-leap-second It is more of a linux kernel bug (affecting RHEL =6 in the enterprise kernels category). Regards, -- Raghavendra D Prabhu (TZ: GMT + 530) Call: +91 96118 00062 mailto:raghavendra.pra...@percona.com Percona, Inc. - http://www.percona.com / Blog: http://www.mysqlperformanceblog.com/ Skype: percona.raghavendrap GPG: 0xD72BE977 pgpSaCsut4xRn.pgp Description: PGP signature
Re: most mysqld instances running with 100% CPU
thank you very much, leap second was the translation i missed for our german word Schaltsekunde so i will reboot our infrastrcuture and rollout a kernel update within which was timed for tomorrow after my vacation which is now supsended :-) P.S.: named DNS showas also interesting CPU spikes, but not permamently Am 01.07.2012 12:52, schrieb Raghavendra D Prabhu: * On Sun, Jul 01, 2012 at 12:44:42PM +0200, Reindl Harald h.rei...@thelounge.net wrote: i notice since this night all mysqld instances suing innodb are running at very high CPU, there is nothing in the mysqld-log and after restarting the service the same again i do not think this has to to with the reason taking back 5.5.25 becasue no disk-IO, i more doubt this has to do with the time-correction-second (not sure how to translate Schaltsekunde to english) because it started late at night __ http://dev.mysql.com/doc/refman/5.5/en/news-5-5-25a.html BTW: since there are announcements of new versions of mysqld it is very rude take them back without any announcement and put after weeks some lines in the old changelog which nobody reads after rollout however, as said, i doubt this is not the problem It has to do with http://bugs.mysql.com/bug.php?id=65778 More analysis here: http://blog.mozilla.org/it/2012/06/30/mysql-and-the-leap-second-high-cpu-and-the-fix/ http://serverfault.com/questions/403732/anyone-else-experiencing-high-rates-of-linux-server-crashes-during-a-leap-second It is more of a linux kernel bug (affecting RHEL =6 in the enterprise kernels category) signature.asc Description: OpenPGP digital signature
Re: mysqld got signal 6 (problem why bigger than I initially realised)
I'll disagree with your disagreement. Many web servers maintain persistent connections. This leads to eventually exceeding max_connections, even if connections are rare. Once he hits 41, he will be issuing 404s, or other bad stuff. Also, having 1000 http threads hanging around is a waste when you rarely have 10 active at once. Or do your threads somehow take a long time without taking much in resources (CPU, I/O, MySQL, etc)? If each of 1000 threads took only 1% of the CPU, the CPU would be overloaded, even on an 8-core box. On 3/27/12 10:38 PM, Reindl Harald wrote: Am 27.03.2012 23:24, schrieb Rick James: MaxClients 1000 could overwhelm max_connections = 41 . Strongly recommend you decrease MaxClients to less than max_connections (not the other way around). totally wrong! not every http-connection implies a myql-connection a website typically contains a lot of static files like images, javascripts, stylesheets and you bring down your httpd if MaxClients is set too low and you are unable to serve waiting clients additionally if KeepAlive is used there are open httpd-connections with NO db-connection after serving a dynamic page using one out of MaxClients for a timewindow based on KeepAliveTimeout MaxClients on httpd should never be lower than max_connections max_connections is primary a question of RAM and typical load mysqltuner.pl: [--] Total buffers: 2.4G global + 3.2M per thread (200 max threads) [OK] Maximum possible memory usage: 3.0G (37% of installed RAM) _ however - 1000 is much too high if we are speak about a preforked server on most hardware - keep in mind that a worker process with mod_php consumes some MB of memory in a typical environment but this is all not mysql related -- Rick James - MySQL Geek -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql
Re: mysqld got signal 6 (problem why bigger than I initially realised)
Am 29.03.2012 19:20, schrieb Rick James: I'll disagree with your disagreement. Many web servers maintain persistent connections. this is a stupid idea for most workloads i thought we are speaking about useful configured servers persistent connections will not work on machines with many websites / db-users, you describe the result of using them - they are only useful on dedicated servers with only one db-user This leads to eventually exceeding max_connections, even if connections are rare. Once he hits 41, he will be issuing 404s, or other bad stuff. that is why you have to find out a typical workload my software is using a self written db-abstraction which will try again if connect fails up to 10 times this does usually not happen often Also, having 1000 http threads hanging around is a waste when you rarely have 10 active at once. Or do your threads somehow take a long time without taking much in resources (CPU, I/O, MySQL, etc)? If each of 1000 threads took only 1% of the CPU, the CPU would be overloaded, even on an 8-core box. what exactly did you not understadn in my last paragraph? however - 1000 is much too high if we are speak about a preforked server on most hardware - keep in mind that a worker process with mod_php consumes some MB of memory in a typical environment with enough memory even this would be possible i had a prjoect last year with 400 active httpd-workers on a high dynamic webpage on a virtaul machine while the host serves 10 other different guests with a mixed workload of some webservers with 500 domains, mail, spamfirewall and vpn-gateway and the host did never get higher than 70% CPU ok, all the 500 domains are using a highly optimized CMS which was inhouse developed and is maintained and optimized since 10 years, but you see the workload is possible without problems On 3/27/12 10:38 PM, Reindl Harald wrote: Am 27.03.2012 23:24, schrieb Rick James: MaxClients 1000 could overwhelm max_connections = 41 . Strongly recommend you decrease MaxClients to less than max_connections (not the other way around). totally wrong! not every http-connection implies a myql-connection a website typically contains a lot of static files like images, javascripts, stylesheets and you bring down your httpd if MaxClients is set too low and you are unable to serve waiting clients additionally if KeepAlive is used there are open httpd-connections with NO db-connection after serving a dynamic page using one out of MaxClients for a timewindow based on KeepAliveTimeout MaxClients on httpd should never be lower than max_connections max_connections is primary a question of RAM and typical load mysqltuner.pl: [--] Total buffers: 2.4G global + 3.2M per thread (200 max threads) [OK] Maximum possible memory usage: 3.0G (37% of installed RAM) _ however - 1000 is much too high if we are speak about a preforked server on most hardware - keep in mind that a worker process with mod_php consumes some MB of memory in a typical environment but this is all not mysql related -- Mit besten Grüßen, Reindl Harald the lounge interactive design GmbH A-1060 Vienna, Hofmühlgasse 17 CTO / software-development / cms-solutions p: +43 (1) 595 3999 33, m: +43 (676) 40 221 40 icq: 154546673, http://www.thelounge.net/ http://www.thelounge.net/signature.asc.what.htm signature.asc Description: OpenPGP digital signature
Mysqld remote dont stop
Hello: We have a problem when we try to stop the mysql service (mysql Ver 14.14 Distrib 5.5.12, for Linux (x86_64) using readline 5.1) on a remote server throught SSH. The problem is that mysql_safe, start again mysqld before that mysql kill all the connection and stop the process. So cannot stop properly the server. Attached the log of .err when we send the command ssh server service mysql stop Thanks for your help. Muchas gracias y un saludo. ADMSA - Administración de Sistemas Abiertos - Diego Servicio de Sistemas Informáticos - División de Tecnologías de la Información Oficina Española de Patentes y Marcas - Mº. Industria, Turismo y Comercio DTI - Servicio de Sistemas Informáticos ad...@oepm.esmailto:ad...@oepm.es 91 34 95361 Francisco Nievas 91 34 93091 Roberto Toledo 91 34 93092 Diego Martín Oficina Española de Patentes y Marcas ** Este mensaje y los ficheros adjuntos pueden contener información confidencial destinada solamente a la(s) persona(s) mencionadas anteriormente pueden estar protegidos por secreto profesional. Si usted recibe este correo electrónico por error, gracias por informar inmediatamente al remitente y destruir el mensaje. Al no estar asegurada la integridad de este mensaje sobre la red, la Oficina Española de Patentes y Marcas no se hace responsable por su contenido. Su contenido no constituye ningún compromiso para la Oficina Española de Patentes y Marcas. salvo ratificación escrita por ambas partes. Aunque se esfuerza al máximo por mantener su red libre de virus, el emisor no puede garantizar nada al respecto y no será responsable de cualesquiera daños que puedan resultar de una transmisión de virus. **120328 6:00:38 [Note] /usr/sbin/mysqld: Normal shutdown 120328 6:00:38 [Note] Event Scheduler: Purging the queue. 0 events 120328 6:00:40 [Warning] /usr/sbin/mysqld: Forcing close of thread 13859 user: xxx 120328 6:00:40 [Warning] /usr/sbin/mysqld: Forcing close of thread 13853 user: xxx 120328 6:00:40 [Warning] /usr/sbin/mysqld: Forcing close of thread 229 user: xxx 120328 6:00:40 [Warning] /usr/sbin/mysqld: Forcing close of thread 46 user: xxx InnoDB: Error: trying to free a corrupt fetch buffer. InnoDB: Apparent memory corruption: mem dump len 500; hex 709c001dd0e3001d21007078692f6a7078695f6461746131235023503033210048ea031d682a15ed3f0020004110b307952d773073656c2e6300880c01009083001d9083001d30103010301078001bc3053700f2fbae00a00f003c003f0078006d006c002000760065007200730069006f006e003d00270031002e00300027003f003e003c004a0050005800490044004f00430053004b004c00200044004f004300490044003d002700310031003400360037003700360032002700200045005800540044004f004300490044003d002700450031002000200020002000200030003100330035004600310041003900430036004600450050003100200027003e003c0053004b004c004f0042004a002000490044003d0027003100270020004f00460046003d0027003000270020004c0045004e003d0027003900330030003800370027002000; asc p ! pxi/jpxi_data1#P#P03! H h* ? A -w0sel.c 0 0 0 x 7 ? x m l v e r s i o n = ' 1 . 0 ' ? J P X I D O C S K L D O C I D = ' 1 1 4 6 7 7 6 2 ' E X T D O C I D = ' E 1 0 1 3 5 F 1 A 9 C 6 F E P 1 ' S K L O B J I D = ' 1 ' O F F = ' 0 ' L E N = ' 9 3 0 8 7 ' ; InnoDB: Scanning backward trying to find previous allocated mem blocks Mem block at - 124, file w0sel.c, line 3208 Mem block at - 572, file t0mem.c, line 74 Freed mem block at - 2940, file mysql.c, line 677 Mem block at - 7068, file w0sel.c, line 3208 Mem block at - 10204, file w0sel.c, line 3208 Mem block at - 13340, file w0sel.c, line 3208 Mem block at - 16476, file w0sel.c, line 3208 Mem block at - 19612, file w0sel.c, line 3208 Mem block at - 22748, file w0sel.c, line 3208 Mem block at - 25884, file w0sel.c, line 3208 InnoDB: Scanning forward trying to find next allocated mem blocks Mem block at + 20596, file t0mem.c, line 74 Mem block at + 22436, file t0mem.c, line 266 Mem block at + 22676, file t0mem.c, line 266 Mem block at + 23252, file t0mem.c, line 266 Mem block at + 24660, file mysql.c, line 677 Mem block at + 25652, file mysql.c, line 677 Mem block at + 27476, file 0pcur.c, line 46 Mem block at + 28196, file t0mem.c
Re: Mysqld remote dont stop
- Original Message - From: AdmSA ad...@oepm.es We have a problem when we try to stop the mysql service (mysql Ver 14.14 Distrib 5.5.12, for Linux (x86_64) using readline 5.1) on a remote server throught SSH. The problem is that mysql_safe, start again mysqld before that mysql kill all the connection and stop the process. So cannot stop properly the server. Attached the log of .err when we send the command “ ssh server service mysql stop ” Hmm, smelly stuff. My first guess would've been that the init script kills the daemon before it has a chance to clean up (InnoDB in particular can take a while). To test that, try shutting down using mysqladmin shutdown instead. However, your error log also points at possible memory corruption - if you can get a maintenance window, take the machine down and run memtest86 (or appropriate vendor tools) to verify if there's no hardware problem. -- Bier met grenadyn Is als mosterd by den wyn Sy die't drinkt, is eene kwezel Hy die't drinkt, is ras een ezel
mysqld got signal 6 (problem why bigger than I initially realised)
Hey Guys Yesterday I sent an email, about '1 client is using or hasn't closed the table properly', but the problem is actually bigger than I realised. We run Mysql replication, and on the second node, Mysql is crashing with 'mysqld got signal 6' every so often. Other than the drives, we have replaced the hardware, and still the problem persists. Googling, I thought it was a memory exhaustion issue, so I started playing with the following variables and values. key_buffer_size=8384512 max_connections=41 But it still crashes Mar 27 12:36:53 xyz-web02 mysqld: key_buffer_size=8384512 Mar 27 12:36:53 xyz-web02 mysqld: read_buffer_size=131072 Mar 27 12:36:53 xyz-web02 mysqld: max_used_connections=3 Mar 27 12:36:53 xyz-web02 mysqld: max_threads=41 Mar 27 12:36:53 xyz-web02 mysqld: thread_count=1 Mar 27 12:36:53 xyz-web02 mysqld: connection_count=1 Mar 27 12:36:53 xyz-web02 mysqld: It is possible that mysqld could use up to Mar 27 12:36:53 xyz-web02 mysqld: key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 97828 K bytes of memory xyz-web02:# free -m total used free sharedbuffers cached Mem: 12038 11966 71 0117 11378 -/+ buffers/cache:469 11568 Swap: 2047 0 2047 We running Debian Squeeze 64bit. I have attached the full crash message. If anyone can help, I would be *most* grateful (If you are in South Africa, I will buy you a meal, let alone a beer :) Kindest Regards Brent Clark *** glibc detected *** /usr/sbin/mysqld: double free or corruption (!prev): 0x7f5e38003b60 *** === Backtrace: = /lib/libc.so.6(+0x71bd6)[0x7f5e4575dbd6] /lib/libc.so.6(cfree+0x6c)[0x7f5e4576294c] /usr/sbin/mysqld(_ZN15Query_log_eventD0Ev+0x20)[0x7f5e474f2ed0] /usr/sbin/mysqld(handle_slave_sql+0x835)[0x7f5e47567255] /lib/libpthread.so.0(+0x68ca)[0x7f5e46c738ca] /lib/libc.so.6(clone+0x6d)[0x7f5e457bb86d] === Memory map: 7f5e3000-7f5e30021000 rw-p 00:00 0 7f5e30021000-7f5e3400 ---p 00:00 0 7f5e3800-7f5e38158000 rw-p 00:00 0 7f5e38158000-7f5e3c00 ---p 00:00 0 7f5e3e019000-7f5e3e01a000 ---p 00:00 0 7f5e3e01a000-7f5e3e81a000 rw-p 00:00 0 7f5e3e81a000-7f5e3e81b000 ---p 00:00 0 7f5e3e81b000-7f5e3f01b000 rw-p 00:00 0 7f5e3f01b000-7f5e3f01c000 ---p 00:00 0 7f5e3f01c000-7f5e3f81c000 rw-p 00:00 0 7f5e3f81c000-7f5e3f81d000 ---p 00:00 0 7f5e3f81d000-7f5e4001d000 rw-p 00:00 0 7f5e4001d000-7f5e4001e000 ---p 00:00 0 7f5e4001e000-7f5e40a24000 rw-p 00:00 0 7f5e40c47000-7f5e40c48000 ---p 00:00 0 7f5e40c48000-7f5e41448000 rw-p 00:00 0 7f5e41448000-7f5e41449000 ---p 00:00 0 7f5e41449000-7f5e41c49000 rw-p 00:00 0 7f5e41c49000-7f5e41c4a000 ---p 00:00 0 7f5e41c4a000-7f5e448c4000 rw-p 00:00 0 7f5e448c4000-7f5e448d r-xp fd:00 328894 /lib/libnss_files-2.11.3.so 7f5e448d-7f5e44acf000 ---p c000 fd:00 328894 /lib/libnss_files-2.11.3.so 7f5e44acf000-7f5e44ad r--p b000 fd:00 328894 /lib/libnss_files-2.11.3.so 7f5e44ad-7f5e44ad1000 rw-p c000 fd:00 328894 /lib/libnss_files-2.11.3.so 7f5e44ad1000-7f5e44adb000 r-xp fd:00 328896 /lib/libnss_nis-2.11.3.so 7f5e44adb000-7f5e44cda000 ---p a000 fd:00 328896 /lib/libnss_nis-2.11.3.so 7f5e44cda000-7f5e44cdb000 r--p 9000 fd:00 328896 /lib/libnss_nis-2.11.3.so 7f5e44cdb000-7f5e44cdc000 rw-p a000 fd:00 328896 /lib/libnss_nis-2.11.3.so 7f5e44cdc000-7f5e44ce3000 r-xp fd:00 328892 /lib/libnss_compat-2.11.3.so 7f5e44ce3000-7f5e44ee2000 ---p 7000 fd:00 328892 /lib/libnss_compat-2.11.3.so 7f5e44ee2000-7f5e44ee3000 r--p 6000 fd:00 328892 /lib/libnss_compat-2.11.3.so 7f5e44ee3000-7f5e44ee4000 rw-p 7000 fd:00 328892 /lib/libnss_compat-2.11.3.so 7f5e44eeb000-7f5e44eec000 ---p 00:00 0 7f5e44eec000-7f5e456ec000 rw-p 00:00 0 7f5e456ec000-7f5e45845000 r-xp fd:00 328847 /lib/libc-2.11.3.so 7f5e45845000-7f5e45a44000 ---p 00159000 fd:00 328847 /lib/libc-2.11.3.so 7f5e45a44000-7f5e45a48000 r--p 00158000 fd:00 328847 /lib/libc-2.11.3.so 7f5e45a48000-7f5e45a49000 rw-p 0015c000 fd:00 328847 /lib/libc-2.11.3.so 7f5e45a49000-7f5e45a4e000 rw-p 00:00 0 7f5e45a4e000-7f5e45a64000 r-xp fd:00 328801 /lib/libgcc_s.so.1 7f5e45a64000-7f5e45c63000 ---p 00016000 fd:00 328801 /lib/libgcc_s.so.1 7f5e45c63000-7f5e45c64000 rw-p 00015000 fd:00 328801 /lib/libgcc_s.so
Re: mysqld got signal 6 (problem why bigger than I initially realised)
HI Brent, Can you please paste your configuration file settings (my.cnf) ? It will help to identify where things went wrong. Is there any other memory consuming application running on the server beyond mysql ? Regards, KarthiK.P.R On Tue, Mar 27, 2012 at 4:17 PM, Brent Clark brentgclarkl...@gmail.comwrote: Hey Guys Yesterday I sent an email, about '1 client is using or hasn't closed the table properly', but the problem is actually bigger than I realised. We run Mysql replication, and on the second node, Mysql is crashing with 'mysqld got signal 6' every so often. Other than the drives, we have replaced the hardware, and still the problem persists. Googling, I thought it was a memory exhaustion issue, so I started playing with the following variables and values. key_buffer_size=8384512 max_connections=41 But it still crashes Mar 27 12:36:53 xyz-web02 mysqld: key_buffer_size=8384512 Mar 27 12:36:53 xyz-web02 mysqld: read_buffer_size=131072 Mar 27 12:36:53 xyz-web02 mysqld: max_used_connections=3 Mar 27 12:36:53 xyz-web02 mysqld: max_threads=41 Mar 27 12:36:53 xyz-web02 mysqld: thread_count=1 Mar 27 12:36:53 xyz-web02 mysqld: connection_count=1 Mar 27 12:36:53 xyz-web02 mysqld: It is possible that mysqld could use up to Mar 27 12:36:53 xyz-web02 mysqld: key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 97828 K bytes of memory xyz-web02:# free -m total used free sharedbuffers cached Mem: 12038 11966 71 0117 11378 -/+ buffers/cache:469 11568 Swap: 2047 0 2047 We running Debian Squeeze 64bit. I have attached the full crash message. If anyone can help, I would be *most* grateful (If you are in South Africa, I will buy you a meal, let alone a beer :) Kindest Regards Brent Clark -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql
Re: mysqld got signal 6 (problem why bigger than I initially realised)
Good day KarthiK.P.R Other than the replication settings in '/etc/mysql/conf.d/replication.cnf' and our /etc/mysql/conf.d/custom.cnf xyz-web02:/data# cat /etc/mysql/conf.d/custom.cnf [mysqld] innodb_file_per_table bind-address = 0.0.0.0 datadir = /data binlog_format=mixed key_buffer_size=8384512 max_connections=41 The original /etc/mysql/my.cnf is untouched. The only other service we have running is DRBD (active / active) and apache, nothing is hitting apache as this is the standby node. And there is no load, or anything consuming resources. Thanks Brent On 27/03/2012 14:04, P.R.Karthik wrote: HI Brent, Can you please paste your configuration file settings (my.cnf) ? It will help to identify where things went wrong. Is there any other memory consuming application running on the server beyond mysql ? Regards, KarthiK.P.R On Tue, Mar 27, 2012 at 4:17 PM, Brent Clark brentgclarkl...@gmail.com mailto:brentgclarkl...@gmail.com wrote: Hey Guys Yesterday I sent an email, about '1 client is using or hasn't closed the table properly', but the problem is actually bigger than I realised. We run Mysql replication, and on the second node, Mysql is crashing with 'mysqld got signal 6' every so often. Other than the drives, we have replaced the hardware, and still the problem persists. Googling, I thought it was a memory exhaustion issue, so I started playing with the following variables and values. key_buffer_size=8384512 max_connections=41 But it still crashes Mar 27 12:36:53 xyz-web02 mysqld: key_buffer_size=8384512 Mar 27 12:36:53 xyz-web02 mysqld: read_buffer_size=131072 Mar 27 12:36:53 xyz-web02 mysqld: max_used_connections=3 Mar 27 12:36:53 xyz-web02 mysqld: max_threads=41 Mar 27 12:36:53 xyz-web02 mysqld: thread_count=1 Mar 27 12:36:53 xyz-web02 mysqld: connection_count=1 Mar 27 12:36:53 xyz-web02 mysqld: It is possible that mysqld could use up to Mar 27 12:36:53 xyz-web02 mysqld: key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 97828 K bytes of memory xyz-web02:# free -m total used free sharedbuffers cached Mem: 12038 11966 71 0117 11378 -/+ buffers/cache:469 11568 Swap: 2047 0 2047 We running Debian Squeeze 64bit. I have attached the full crash message. If anyone can help, I would be *most* grateful (If you are in South Africa, I will buy you a meal, let alone a beer :) Kindest Regards Brent Clark -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/mysql -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql
Re: mysqld got signal 6 (problem why bigger than I initially realised)
Do you have 12GB of RAM? Is this a 64-bit mysqld? Let's see SHOW VARIABLES LIKE '%buffer%'; SHOW GLOBAL STATUS LIKE 'Max%'; SHOW GLOBAL STATUS LIKE 'Up%'; What is Apache's MaxClients? On 3/27/12 6:25 AM, Brent Clark wrote: Good day KarthiK.P.R Other than the replication settings in '/etc/mysql/conf.d/replication.cnf' and our /etc/mysql/conf.d/custom.cnf xyz-web02:/data# cat /etc/mysql/conf.d/custom.cnf [mysqld] innodb_file_per_table bind-address = 0.0.0.0 datadir = /data binlog_format=mixed key_buffer_size=8384512 max_connections=41 The original /etc/mysql/my.cnf is untouched. The only other service we have running is DRBD (active / active) and apache, nothing is hitting apache as this is the standby node. And there is no load, or anything consuming resources. Thanks Brent On 27/03/2012 14:04, P.R.Karthik wrote: HI Brent, Can you please paste your configuration file settings (my.cnf) ? It will help to identify where things went wrong. Is there any other memory consuming application running on the server beyond mysql ? Regards, KarthiK.P.R On Tue, Mar 27, 2012 at 4:17 PM, Brent Clarkbrentgclarkl...@gmail.commailto:brentgclarkl...@gmail.com wrote: Hey Guys Yesterday I sent an email, about '1 client is using or hasn't closed the table properly', but the problem is actually bigger than I realised. We run Mysql replication, and on the second node, Mysql is crashing with 'mysqld got signal 6' every so often. Other than the drives, we have replaced the hardware, and still the problem persists. Googling, I thought it was a memory exhaustion issue, so I started playing with the following variables and values. key_buffer_size=8384512 max_connections=41 But it still crashes Mar 27 12:36:53 xyz-web02 mysqld: key_buffer_size=8384512 Mar 27 12:36:53 xyz-web02 mysqld: read_buffer_size=131072 Mar 27 12:36:53 xyz-web02 mysqld: max_used_connections=3 Mar 27 12:36:53 xyz-web02 mysqld: max_threads=41 Mar 27 12:36:53 xyz-web02 mysqld: thread_count=1 Mar 27 12:36:53 xyz-web02 mysqld: connection_count=1 Mar 27 12:36:53 xyz-web02 mysqld: It is possible that mysqld could use up to Mar 27 12:36:53 xyz-web02 mysqld: key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 97828 K bytes of memory xyz-web02:# free -m total used free sharedbuffers cached Mem: 12038 11966 71 0117 11378 -/+ buffers/cache:469 11568 Swap: 2047 0 2047 We running Debian Squeeze 64bit. I have attached the full crash message. If anyone can help, I would be *most* grateful (If you are in South Africa, I will buy you a meal, let alone a beer :) Kindest Regards Brent Clark -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/mysql -- Rick James - MySQL Geek -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql
Re: mysqld got signal 6 (problem why bigger than I initially realised)
Hi Rick Thank you for replying. Please see my answers to your questions. On Tue, Mar 27, 2012 at 7:58 PM, Rick James rja...@yahoo-inc.com wrote: Do you have 12GB of RAM? total used free sharedbuffers cached Mem: 12038 11959 78 0139 11234 -/+ buffers/cache:586 11451 Swap: 2047 0 2047 Is this a 64-bit mysqld? Linux hostname 2.6.32-5-amd64 #1 SMP Mon Jan 16 16:22:28 UTC 2012 x86_64 GNU/Linux Let's see SHOW VARIABLES LIKE '%buffer%'; +-+-+ | Variable_name | Value | +-+-+ | bulk_insert_buffer_size | 8388608 | | innodb_buffer_pool_size | 8388608 | | innodb_log_buffer_size | 1048576 | | join_buffer_size| 131072 | | key_buffer_size | 8384512 | | myisam_sort_buffer_size | 8388608 | | net_buffer_length | 16384 | | preload_buffer_size | 32768 | | read_buffer_size| 131072 | | read_rnd_buffer_size| 262144 | | sort_buffer_size| 2097144 | | sql_buffer_result | OFF | +-+-+ SHOW GLOBAL STATUS LIKE 'Max%'; +--+---+ | Variable_name| Value | +--+---+ | Max_used_connections | 3 | +--+---+ SHOW GLOBAL STATUS LIKE 'Up%'; +---+---+ | Variable_name | Value | +---+---+ | Uptime| 18492 | | Uptime_since_flush_status | 18492 | +---+---+ What is Apache's MaxClients? MaxClients 1000 Thank you again. Brent On 3/27/12 6:25 AM, Brent Clark wrote: Good day KarthiK.P.R Other than the replication settings in '/etc/mysql/conf.d/replication.cnf' and our /etc/mysql/conf.d/custom.cnf xyz-web02:/data# cat /etc/mysql/conf.d/custom.cnf [mysqld] innodb_file_per_table bind-address = 0.0.0.0 datadir = /data binlog_format=mixed key_buffer_size=8384512 max_connections=41 The original /etc/mysql/my.cnf is untouched. The only other service we have running is DRBD (active / active) and apache, nothing is hitting apache as this is the standby node. And there is no load, or anything consuming resources. Thanks Brent On 27/03/2012 14:04, P.R.Karthik wrote: HI Brent, Can you please paste your configuration file settings (my.cnf) ? It will help to identify where things went wrong. Is there any other memory consuming application running on the server beyond mysql ? Regards, KarthiK.P.R On Tue, Mar 27, 2012 at 4:17 PM, Brent Clarkbrentgclarkl...@gmail.commailto:brentgclarkl...@gmail.com wrote: Hey Guys Yesterday I sent an email, about '1 client is using or hasn't closed the table properly', but the problem is actually bigger than I realised. We run Mysql replication, and on the second node, Mysql is crashing with 'mysqld got signal 6' every so often. Other than the drives, we have replaced the hardware, and still the problem persists. Googling, I thought it was a memory exhaustion issue, so I started playing with the following variables and values. key_buffer_size=8384512 max_connections=41 But it still crashes Mar 27 12:36:53 xyz-web02 mysqld: key_buffer_size=8384512 Mar 27 12:36:53 xyz-web02 mysqld: read_buffer_size=131072 Mar 27 12:36:53 xyz-web02 mysqld: max_used_connections=3 Mar 27 12:36:53 xyz-web02 mysqld: max_threads=41 Mar 27 12:36:53 xyz-web02 mysqld: thread_count=1 Mar 27 12:36:53 xyz-web02 mysqld: connection_count=1 Mar 27 12:36:53 xyz-web02 mysqld: It is possible that mysqld could use up to Mar 27 12:36:53 xyz-web02 mysqld: key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 97828 K bytes of memory xyz-web02:# free -m total used free shared buffers cached Mem: 12038 11966 71 0 117 11378 -/+ buffers/cache: 469 11568 Swap: 2047 0 2047 We running Debian Squeeze 64bit. I have attached the full crash message. If anyone can help, I would be *most* grateful (If you are in South Africa, I will buy you a meal, let alone a beer :) Kindest Regards Brent Clark -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/mysql -- Rick James - MySQL Geek -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/mysql -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql
Re: mysqld got signal 6 (problem why bigger than I initially realised)
MaxClients 1000 could overwhelm max_connections = 41 . Strongly recommend you decrease MaxClients to less than max_connections (not the other way around). Uptime| 18492 Not very long to see stuff. | innodb_buffer_pool_size | 8388608 | | key_buffer_size | 8384512 | Much too small for a 12GB machine. See http://mysql.rjweb.org/doc.php/memory for tuning advice. Back to signal 6 (Abort) -- was anything useful in mysqld.err ? On 3/27/12 2:06 PM, Brent Clark wrote: Hi Rick Thank you for replying. Please see my answers to your questions. On Tue, Mar 27, 2012 at 7:58 PM, Rick Jamesrja...@yahoo-inc.com wrote: Do you have 12GB of RAM? total used free sharedbuffers cached Mem: 12038 11959 78 0139 11234 -/+ buffers/cache:586 11451 Swap: 2047 0 2047 Is this a 64-bit mysqld? Linux hostname 2.6.32-5-amd64 #1 SMP Mon Jan 16 16:22:28 UTC 2012 x86_64 GNU/Linux Let's see SHOW VARIABLES LIKE '%buffer%'; +-+-+ | Variable_name | Value | +-+-+ | bulk_insert_buffer_size | 8388608 | | innodb_buffer_pool_size | 8388608 | | innodb_log_buffer_size | 1048576 | | join_buffer_size| 131072 | | key_buffer_size | 8384512 | | myisam_sort_buffer_size | 8388608 | | net_buffer_length | 16384 | | preload_buffer_size | 32768 | | read_buffer_size| 131072 | | read_rnd_buffer_size| 262144 | | sort_buffer_size| 2097144 | | sql_buffer_result | OFF | +-+-+ SHOW GLOBAL STATUS LIKE 'Max%'; +--+---+ | Variable_name| Value | +--+---+ | Max_used_connections | 3 | +--+---+ SHOW GLOBAL STATUS LIKE 'Up%'; +---+---+ | Variable_name | Value | +---+---+ | Uptime| 18492 | | Uptime_since_flush_status | 18492 | +---+---+ What is Apache's MaxClients? MaxClients 1000 Thank you again. Brent On 3/27/12 6:25 AM, Brent Clark wrote: Good day KarthiK.P.R Other than the replication settings in '/etc/mysql/conf.d/replication.cnf' and our /etc/mysql/conf.d/custom.cnf xyz-web02:/data# cat /etc/mysql/conf.d/custom.cnf [mysqld] innodb_file_per_table bind-address = 0.0.0.0 datadir = /data binlog_format=mixed key_buffer_size=8384512 max_connections=41 The original /etc/mysql/my.cnf is untouched. The only other service we have running is DRBD (active / active) and apache, nothing is hitting apache as this is the standby node. And there is no load, or anything consuming resources. Thanks Brent On 27/03/2012 14:04, P.R.Karthik wrote: HI Brent, Can you please paste your configuration file settings (my.cnf) ? It will help to identify where things went wrong. Is there any other memory consuming application running on the server beyond mysql ? Regards, KarthiK.P.R On Tue, Mar 27, 2012 at 4:17 PM, Brent Clarkbrentgclarkl...@gmail.commailto:brentgclarkl...@gmail.comwrote: Hey Guys Yesterday I sent an email, about '1 client is using or hasn't closed the table properly', but the problem is actually bigger than I realised. We run Mysql replication, and on the second node, Mysql is crashing with 'mysqld got signal 6' every so often. Other than the drives, we have replaced the hardware, and still the problem persists. Googling, I thought it was a memory exhaustion issue, so I started playing with the following variables and values. key_buffer_size=8384512 max_connections=41 But it still crashes Mar 27 12:36:53 xyz-web02 mysqld: key_buffer_size=8384512 Mar 27 12:36:53 xyz-web02 mysqld: read_buffer_size=131072 Mar 27 12:36:53 xyz-web02 mysqld: max_used_connections=3 Mar 27 12:36:53 xyz-web02 mysqld: max_threads=41 Mar 27 12:36:53 xyz-web02 mysqld: thread_count=1 Mar 27 12:36:53 xyz-web02 mysqld: connection_count=1 Mar 27 12:36:53 xyz-web02 mysqld: It is possible that mysqld could use up to Mar 27 12:36:53 xyz-web02 mysqld: key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 97828 K bytes of memory xyz-web02:# free -m total used free sharedbuffers cached Mem: 12038 11966 71 0117 11378 -/+ buffers/cache:469 11568 Swap: 2047 0 2047 We running Debian Squeeze 64bit. I have attached the full crash message. If anyone can help, I would be *most* grateful (If you are in South Africa, I will buy you a meal, let alone a beer :) Kindest Regards Brent Clark -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql
Re: mysqld got signal 6 (problem why bigger than I initially realised)
Am 27.03.2012 23:24, schrieb Rick James: MaxClients 1000 could overwhelm max_connections = 41 . Strongly recommend you decrease MaxClients to less than max_connections (not the other way around). totally wrong! not every http-connection implies a myql-connection a website typically contains a lot of static files like images, javascripts, stylesheets and you bring down your httpd if MaxClients is set too low and you are unable to serve waiting clients additionally if KeepAlive is used there are open httpd-connections with NO db-connection after serving a dynamic page using one out of MaxClients for a timewindow based on KeepAliveTimeout MaxClients on httpd should never be lower than max_connections max_connections is primary a question of RAM and typical load mysqltuner.pl: [--] Total buffers: 2.4G global + 3.2M per thread (200 max threads) [OK] Maximum possible memory usage: 3.0G (37% of installed RAM) _ however - 1000 is much too high if we are speak about a preforked server on most hardware - keep in mind that a worker process with mod_php consumes some MB of memory in a typical environment but this is all not mysql related signature.asc Description: OpenPGP digital signature
Re: help! mysqld cannot start!
It doesn't particularly say, but this: 120116 19:15:29 120116 19:15:29 InnoDB: 1.1.8 started; log sequence number 1595675 suggests to me that there's still junk from a previous install around. You might want to clean that up. - Original Message - From: mantianyu mantia...@gmail.com To: mysql@lists.mysql.com Sent: Monday, 16 January, 2012 12:37:07 PM Subject: help! mysqld cannot start! I have download the Linux - Generic 2.6 (x86, 32-bit), Compressed TAR Archive binary edition and I installed it all followed the INSTALL_BINARY but at last step I start the service by run sudo bin/mysqld_safe --user=mysql I got following error message cifer@Pig:/usr/local/mysql$ 120116 19:15:28 mysqld_safe Logging to '/var/log/mysql/error.log'. 120116 19:15:28 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql 120116 19:15:30 mysqld_safe mysqld from pid file /var/lib/mysql/Pig.pid ended and I check the error.log file it shows that 120116 19:15:28 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql 120116 19:15:28 [ERROR] Can't find messagefile '/usr/share/errmsg.sys' 120116 19:15:28 [Note] Plugin 'FEDERATED' is disabled. 120116 19:15:28 InnoDB: The InnoDB memory heap is disabled 120116 19:15:28 InnoDB: Mutexes and rw_locks use InnoDB's own implementation 120116 19:15:28 InnoDB: Compressed tables use zlib 1.2.3 120116 19:15:28 InnoDB: Using Linux native AIO 120116 19:15:28 InnoDB: Initializing buffer pool, size = 128.0M 120116 19:15:28 InnoDB: Completed initialization of buffer pool 120116 19:15:28 InnoDB: highest supported file format is Barracuda. 120116 19:15:28 InnoDB: Waiting for the background threads to start 120116 19:15:29 InnoDB: 1.1.8 started; log sequence number 1595675 120116 19:15:29 [ERROR] Aborting 120116 19:15:29 InnoDB: Starting shutdown... 120116 19:15:30 InnoDB: Shutdown completed; log sequence number 1595675 120116 19:15:30 [Note] 120116 19:15:30 mysqld_safe mysqld from pid file /var/lib/mysql/Pig.pid ended every step I followed the INSTALL_BINARY file why it still can't start? who can help me? thanks! -- Bier met grenadyn Is als mosterd by den wyn Sy die't drinkt, is eene kwezel Hy die't drinkt, is ras een ezel -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql
Re: help! mysqld cannot start!
2012/01/16 19:37 +0800, mantianyu but at last step I start the service by run sudo bin/mysqld_safe --user=mysql I got following error message cifer@Pig:/usr/local/mysql$ 120116 19:15:28 mysqld_safe Logging to '/var/log/mysql/error.log'. Your means of starting does not show where the MySQL own files are. The flag -b (--basedir) is used for that. It works also to start mysqld in the directory where the default my.cnf was left. If that has everything that MySQL needs, it works also to start with --defaults-file=/my.cnf--the four dots stand for the rest of the full pathname. -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql
Re: help! mysqld cannot start!
On Mon, Jan 16, 2012 at 4:37 AM, mantianyu mantia...@gmail.com wrote: I have download the Linux - Generic 2.6 (x86, 32-bit), Compressed TAR Archive binary edition and I installed it all followed the INSTALL_BINARY but at last step I start the service by run sudo bin/mysqld_safe --user=mysql I got following error message cifer@Pig:/usr/local/mysql$ 120116 19:15:28 mysqld_safe Logging to '/var/log/mysql/error.log'. 120116 19:15:28 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql 120116 19:15:30 mysqld_safe mysqld from pid file /var/lib/mysql/Pig.pid ended and I check the error.log file it shows that 120116 19:15:28 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql 120116 19:15:28 [ERROR] Can't find messagefile '/usr/share/errmsg.sys' 120116 19:15:28 [Note] Plugin 'FEDERATED' is disabled. 120116 19:15:28 InnoDB: The InnoDB memory heap is disabled 120116 19:15:28 InnoDB: Mutexes and rw_locks use InnoDB's own implementation 120116 19:15:28 InnoDB: Compressed tables use zlib 1.2.3 120116 19:15:28 InnoDB: Using Linux native AIO 120116 19:15:28 InnoDB: Initializing buffer pool, size = 128.0M 120116 19:15:28 InnoDB: Completed initialization of buffer pool 120116 19:15:28 InnoDB: highest supported file format is Barracuda. 120116 19:15:28 InnoDB: Waiting for the background threads to start 120116 19:15:29 InnoDB: 1.1.8 started; log sequence number 1595675 120116 19:15:29 [ERROR] Aborting 120116 19:15:29 InnoDB: Starting shutdown... 120116 19:15:30 InnoDB: Shutdown completed; log sequence number 1595675 120116 19:15:30 [Note] 120116 19:15:30 mysqld_safe mysqld from pid file /var/lib/mysql/Pig.pid ended every step I followed the INSTALL_BINARY file why it still can't start? who can help me? thanks! I had the same issue, and I solved it by starting the server with this command line option: --lc-messages-dir=/usr/local/mysql/share/ HTH, -larry -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql
[ERROR] /usr/sbin/mysqld: Can't find file: './mysql/user.frm'
Dear all, I am facing the below problem while installing mysql in a debian based system from the last 2 days. I tried the command apt-get install mysql-server but the server doesn't start properly due to below exception in /var/log/syslog 41 [ERROR] /usr/sbin/mysqld: Can't find file: './mysql/user.frm' (errno: 13) Mar 14 10:36:41 sun-cloud mysqld[3500]: ERROR: 1017 Can't find file: './mysql/user.frm' (errno: 13) Mar 14 10:36:41 sun-cloud mysqld[3500]: 110314 10:36:41 [ERROR] Aborting Mar 14 10:36:41 sun-cloud mysqld[3500]: Don't know what is the reason behind this. I attached my debian.cnf file also. Please guide me how to resolve this permanently and also I need to access the mysql server from many client servers. My /var/lib/mysql permissions are : root@sun-cloud:/var/lib# ls -ls | grep mysql 4 drwx-- 3 mysql mysql 4096 2011-03-14 10:36 mysql Thanks best Regards, Adarsh Sharma # Automatically generated for Debian scripts. DO NOT TOUCH! [client] host = localhost user = debian-sys-maint password = l7MZwYyF45QH8wrY socket = /var/run/mysqld/mysqld.sock [mysql_upgrade] host = localhost user = debian-sys-maint password = l7MZwYyF45QH8wrY socket = /var/run/mysqld/mysqld.sock basedir = /usr -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql?unsub=arch...@jab.org
Re: [ERROR] /usr/sbin/mysqld: Can't find file: './mysql/user.frm'
errono:13 is Permission Denied. Check permissions for mysql data dir. On Mon, Mar 14, 2011 at 11:02 AM, Adarsh Sharma adarsh.sha...@orkash.comwrote: Dear all, I am facing the below problem while installing mysql in a debian based system from the last 2 days. I tried the command apt-get install mysql-server but the server doesn't start properly due to below exception in /var/log/syslog 41 [ERROR] /usr/sbin/mysqld: Can't find file: './mysql/user.frm' (errno: 13) Mar 14 10:36:41 sun-cloud mysqld[3500]: ERROR: 1017 Can't find file: './mysql/user.frm' (errno: 13) Mar 14 10:36:41 sun-cloud mysqld[3500]: 110314 10:36:41 [ERROR] Aborting Mar 14 10:36:41 sun-cloud mysqld[3500]: Don't know what is the reason behind this. I attached my debian.cnf file also. Please guide me how to resolve this permanently and also I need to access the mysql server from many client servers. My /var/lib/mysql permissions are : root@sun-cloud:/var/lib# ls -ls | grep mysql 4 drwx-- 3 mysql mysql 4096 2011-03-14 10:36 mysql Thanks best Regards, Adarsh Sharma # Automatically generated for Debian scripts. DO NOT TOUCH! [client] host = localhost user = debian-sys-maint password = l7MZwYyF45QH8wrY socket = /var/run/mysqld/mysqld.sock [mysql_upgrade] host = localhost user = debian-sys-maint password = l7MZwYyF45QH8wrY socket = /var/run/mysqld/mysqld.sock basedir = /usr -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql?unsub=nilnan...@gmail.com
RE: Any way to change timezone WITHOUT mysqld restart?
Trust me, I read it. We had an I18N product at my last company and all our time was stored in UTC in mySQL and we'd alter it on the fly for each user. This isn't rocket science. It's done every day in probably many of the sites you visit and don't even know it. To clarify for you (again): * Per-connection time zones. Each client that connects has its own time zone setting, given by the session http://dev.mysql.com/doc/refman/5.1/en/server-system-variables.html#sysvar _time_zone time_zone variable. Initially, the session variable takes its value from the global http://dev.mysql.com/doc/refman/5.1/en/server-system-variables.html#sysvar _time_zone time_zone variable, but the client can change its own time zone with this statement: mysql SET time_zone = timezone; The current session time zone setting affects display and storage of time values that are zone-sensitive. This includes the values displayed by functions such as http://dev.mysql.com/doc/refman/5.1/en/date-and-time-functions.html#functi on_now NOW() or http://dev.mysql.com/doc/refman/5.1/en/date-and-time-functions.html#functi on_curtime CURTIME(), and values stored in and retrieved from http://dev.mysql.com/doc/refman/5.1/en/datetime.html TIMESTAMP columns. Values for http://dev.mysql.com/doc/refman/5.1/en/datetime.html TIMESTAMP columns are converted from the current time zone to UTC for storage, and from UTC to the current time zone for retrieval. Don't forget to do this stuff too: http://dev.mysql.com/doc/refman/5.1/en/mysql-tzinfo-to-sql.html So if it's not clear by now, you store all your dates/times in UTC (convert them via some script if you didn't start out that way). Then per web page connection, you read the user's profile TZ (presumably from the user session object or some other persistent means), execute that SQL statement above as one of the first things on the page, and FM ensues. All your properly saved mysql rows will display in the LOCAL timezone instead of UTC. You ALSO have to set the TZ in PHP too don't forget or you'll get whacky discrepencies. http://php.net/manual/en/function.date-default-timezone-set.php There's plenty of info on this out there for using PHP MySQL if that's what you're using too... http://www.ferdychristant.com/blog//archive/DOMM-84NEJN _ From: Bryan Cantwell [mailto:bcantw...@firescope.com] Sent: Saturday, October 02, 2010 5:18 AM To: Daevid Vincent Cc: mysql@lists.mysql.com Subject: RE: Any way to change timezone WITHOUT mysqld restart? As a matter of fact I did, the real question is : Did you even read my email? I said WITHOUT a restart... The manual states that a restart of the mysqld is required. The reason for the post to such a list is because on many occasions, user have suggestions on some workaround for things that do work in spite of what the manual says. On Fri, 2010-10-01 at 15:42 -0700, Daevid Vincent wrote: Did you even look at the manual? http://lmgtfy.com/?q=mysql+set+timezone First link. -Original Message- From: Bryan Cantwell [mailto:bcantw...@firescope.com] Sent: Friday, October 01, 2010 10:25 AM To: mysql@lists.mysql.com Subject: Any way to change timezone WITHOUT mysqld restart? Any way to change timezone WITHOUT mysqld restart? It would be a lifesaver if there were some way for me not to have to restart because if mysql restarts then I have to go through a lot of other issues with my other apps.
Re: Any way to change timezone WITHOUT mysqld restart?
I suggest you put your glasses on, then. Getting of that horse might help, too. default-time-zone='*timezone*' If you have the SUPERhttp://dev.mysql.com/doc/refman/5.1/en/privileges-provided.html#priv_superprivilege, you can set the global server time zone value at runtime with this statement: On Sat, Oct 2, 2010 at 2:18 PM, Bryan Cantwell bcantw...@firescope.comwrote: As a matter of fact I did, the real question is : Did you even read my email? I said WITHOUT a restart... The manual states that a restart of the mysqld is required. The reason for the post to such a list is because on many occasions, user have suggestions on some workaround for things that do work in spite of what the manual says. On Fri, 2010-10-01 at 15:42 -0700, Daevid Vincent wrote: Did you even look at the manual? http://lmgtfy.com/?q=mysql+set+timezone First link. -Original Message- From: Bryan Cantwell [mailto:bcantw...@firescope.com] Sent: Friday, October 01, 2010 10:25 AM To: mysql@lists.mysql.com Subject: Any way to change timezone WITHOUT mysqld restart? Any way to change timezone WITHOUT mysqld restart? It would be a lifesaver if there were some way for me not to have to restart because if mysql restarts then I have to go through a lot of other issues with my other apps. -- Bier met grenadyn Is als mosterd by den wyn Sy die't drinkt, is eene kwezel Hy die't drinkt, is ras een ezel
RE: Any way to change timezone WITHOUT mysqld restart?
As a matter of fact I did, the real question is : Did you even read my email? I said WITHOUT a restart... The manual states that a restart of the mysqld is required. The reason for the post to such a list is because on many occasions, user have suggestions on some workaround for things that do work in spite of what the manual says. On Fri, 2010-10-01 at 15:42 -0700, Daevid Vincent wrote: Did you even look at the manual? http://lmgtfy.com/?q=mysql+set+timezone First link. -Original Message- From: Bryan Cantwell [mailto:bcantw...@firescope.com] Sent: Friday, October 01, 2010 10:25 AM To: mysql@lists.mysql.com Subject: Any way to change timezone WITHOUT mysqld restart? Any way to change timezone WITHOUT mysqld restart? It would be a lifesaver if there were some way for me not to have to restart because if mysql restarts then I have to go through a lot of other issues with my other apps.
Any way to change tinezone WITHOUT mysqld restart?
Any way to change timezone WITHOUT mysqld restart? It would be a lifesaver if there were some way for me not to have to restart because if mysql restarts then I have to go through a lot of other issues with my other apps.
RE: Any way to change tinezone WITHOUT mysqld restart?
Did you even look at the manual? http://lmgtfy.com/?q=mysql+set+timezone First link. -Original Message- From: Bryan Cantwell [mailto:bcantw...@firescope.com] Sent: Friday, October 01, 2010 10:25 AM To: mysql@lists.mysql.com Subject: Any way to change tinezone WITHOUT mysqld restart? Any way to change timezone WITHOUT mysqld restart? It would be a lifesaver if there were some way for me not to have to restart because if mysql restarts then I have to go through a lot of other issues with my other apps. -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql?unsub=arch...@jab.org
Re: Responsibilities of the main mysqld thread?
Couple of thoughts ... lsof -p pid of mysql process may give some clue of what files/tables it's reading/writing. From that you may be able to deduce something useful. Check the slow query log and see if any of the queries are CPU-intensive (by doing an EXPLAIN) and are the bottleneck. - Ashish On Fri, Aug 20, 2010 at 10:09 PM, Tom Kleinpeter tomkleinpe...@gmail.comwrote: I've been watching our mysqld procs in htop and the root thread is using 75-100% of a CPU most of the time. I'm trying to understand what that is being used for, and so I was hoping someone could tell me what that thread does that might be using a lot of CPU. We are using 5.5.4-m3, we use MyISAM tables with full text indexes, do around 1500-2000 queries per second, accept around 150 connections per second, and at the moment both our key cache and our query cache are disabled (I was curious if that contention was an issue). CPU usage didn't really change with the caches disabled. The server is doing around 2 megabytes of traffic per second. We store a bunch of data compressed, and use uncompress(columnName) in queries to get it back out. None of these things set off any red flags for me, but it has been a number of years since I've tuned MySQL, so I don't really trust myself. Thanks, Tom -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/mysql?unsub=ashish.mukher...@gmail.com
Responsibilities of the main mysqld thread?
I've been watching our mysqld procs in htop and the root thread is using 75-100% of a CPU most of the time. I'm trying to understand what that is being used for, and so I was hoping someone could tell me what that thread does that might be using a lot of CPU. We are using 5.5.4-m3, we use MyISAM tables with full text indexes, do around 1500-2000 queries per second, accept around 150 connections per second, and at the moment both our key cache and our query cache are disabled (I was curious if that contention was an issue). CPU usage didn't really change with the caches disabled. The server is doing around 2 megabytes of traffic per second. We store a bunch of data compressed, and use uncompress(columnName) in queries to get it back out. None of these things set off any red flags for me, but it has been a number of years since I've tuned MySQL, so I don't really trust myself. Thanks, Tom -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql?unsub=arch...@jab.org
mysqld freeze at 100% load
As soon as mysqld starts it goes 100% cpu. I can stop it, there is no mysql_safe running, and I ran mysqlcheck -A -a -c -o -g --auto-repair -u root -p all is ok, syslog shows nothing important but I can't login to any account with mysql client it just sits there, using php it times out. I don't know how to fix the urgent situation... How-To-Repeat: Looks like it has been started after a release update. I don't know if this bug is related since is mysql_safe https://bugs.launchpad.net/ubuntu/+source/mysql-dfsg-5.0/+bug/105457/ Fix: I don't know Submitter-Id: submitter ID Originator:root Organization: organization of PR author (multiple lines) MySQL support: [none | licence | email support | extended email support ] Synopsis: synopsis of the problem (one line) Severity: [ non-critical | serious | critical ] (one line) Priority: [ low | medium | high ] (one line) Category: mysql Class: [ sw-bug | doc-bug | change-request | support ] (one line) Release: mysql-5.1.41-3ubuntu12.6 ((Ubuntu)) C compiler:gcc-4.4.real (Ubuntu 4.4.3-4ubuntu5) 4.4.3 C++ compiler: g++-4.4.real (Ubuntu 4.4.3-4ubuntu5) 4.4.3 Environment: machine, os, target, libraries (multiple lines) System: Linux mail.campiaperti.org 2.6.32.16-linode28 #1 SMP Sun Jul 25 21:32:42 UTC 2010 i686 GNU/Linux Some paths: /usr/bin/perl /usr/bin/make /usr/bin/gcc /usr/bin/cc GCC: Using built-in specs. Target: i486-linux-gnu Configured with: ../src/configure -v --with-pkgversion='Ubuntu 4.4.3-4ubuntu5' --with-bugurl=file:///usr/share/doc/gcc-4.4/R Thread model: posix gcc version 4.4.3 (Ubuntu 4.4.3-4ubuntu5) Compilation info (call): CC='gcc' CFLAGS='-O3 -DBIG_JOINS=1 -fno-strict-aliasing' CXX='g++' CXXFLAGS='-O3 -DBIG_JOINS=1 -- ~ Eli ~
Mysqld crashes. Stack Trace Attached.
Hi My mysql server suddenly crashed. Not it does not start and dumps the following stack trace. I suspect some table corruption. Please help me to start it. mysql@lists.mysql.comstack_bottom = (nil) thread_stack 0x4 /usr/sbin/mysqld(my_print_stacktrace+0x24) [0x84fd84] /usr/sbin/mysqld(handle_segfault+0x320) [0x58a870] /lib/libpthread.so.0 [0x7fe50b3145f0] /lib/libc.so.6(gsignal+0x35) [0x7fe50a7f9c85] /lib/libc.so.6(abort+0x10e) [0x7fe50a7fafee] /usr/sbin/mysqld [0x785ebd] /usr/sbin/mysqld [0x77442f] /usr/sbin/mysqld [0x77579d] /usr/sbin/mysqld [0x72aef7] /usr/sbin/mysqld [0x7366c1] /usr/sbin/mysqld [0x736c06] /usr/sbin/mysqld [0x72e9d2] /usr/sbin/mysqld [0x762d31] /usr/sbin/mysqld [0x7eaf6d] /usr/sbin/mysqld [0x7c3800] /usr/sbin/mysqld [0x70bde5] /usr/sbin/mysqld(ha_initialize_handlerton(st_plugin_int*)+0x31) [0x679a31] /usr/sbin/mysqld [0x6f214a] /usr/sbin/mysqld(plugin_init(int*, char**, int)+0x812) [0x6f5682] /usr/sbin/mysqld [0x58bc8b] /usr/sbin/mysqld(main+0x405) [0x58ef25] /lib/libc.so.6(__libc_start_main+0xf4) [0x7fe50a7e6ff4] /usr/sbin/mysqld [0x4c9a39] Things I tried: 1. Start with inndb_force_recovery = 4, but it failed with the same stack trace. 2. Took backup of all data files and put them on other machine. There also it did not start and gave the same error. Any idea what is going wrong? Thanks Garima
Re: libexec/mysqld: unknown option '--skip-bdb'
Jörg, thanks again for your help and your patience with this issue. You also caught oversights with strace and clarified that this is not a PATH issue. I've filed it at: http://bugs.mysql.com/bug.php?id=53667 You don't state it explicitly, but I take your text to mean If the MySQL tools are compiled using --prefix, --basedir, or other such settings, they should not read system-wide configuration files. That is a possible request, different from the current MySQL policy. I am not saying MySQL should not read system-wide configuration files. I'm saying that if one defines a --sysconfdir directory, then that directory should be consulted first. The bottom line is that the MySQL behavior is non-standard. A lot of software allow reading their configuration files from anywhere. -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql?unsub=arch...@jab.org
libexec/mysqld: unknown option '--skip-bdb'
Hello, I am trying to produce an automated, reliable, and repeatable way of testing mysql releases, and I am finding an error that makes this impossible to accomplish. I am trying to compile mysql and install it in a non-standard directory. I do notwant mysql installed in /usr or /usr/local. For example, I am trying to install it in /tmp/msource with the configure line: ./configure --prefix=/tmp/msource --exec-prefix=/tmp/msource --bindir=/tmp/msource/bin --sbindir=/tmp/msource/sbin --localstatedir=/tmp/msource/lib --sysconfdir=/tmp/msource --enable-assembler --with-mysqld-ldflags=-all-static --with-client-ldflags=-all-static --with-mysqld-user=tester --with-unix-socket-path=/tmp/msource/var/run/mysql.sock 'make' and 'make install' succeed. I have also created a custom my.cnf file installed in /tmp/msource/etc/my.cnf. However, installing the database tables fails: $ /tmp/msource/bin/mysql_install_db --basedir=/tmp/msource --datadir=/tmp/msource/data Installing MySQL system tables... 100513 21:53:35 [ERROR] /tmp/msource/libexec/mysqld: unknown option '--skip-bdb' 100513 21:53:35 [ERROR] Aborting 100513 21:53:35 [Note] /tmp/msource/libexec/mysqld: Shutdown complete Installation of system tables failed! Examine the logs in /tmp/msource/data for more information. You can try to start the mysqld daemon with: shell /tmp/msource/libexec/mysqld --skip-grant and use the command line tool /tmp/msource/bin/mysql to connect to the mysql database and look at the grant tables: shell /tmp/msource/bin/mysql -u root mysql mysql show tables Try 'mysqld --help' if you have problems with paths. Using --log gives you a log in /tmp/msource/data that may be helpful. Please consult the MySQL manual section 'Problems running mysql_install_db', and the manual section that describes problems on your OS. Another information source are the MySQL email archives available at http://lists.mysql.com/. Please check all of the above before mailing us! And remember, if you do mail us, you MUST use the /tmp/msource/scripts/mysqlbug script! The following error just won't go away: 100513 21:53:35 [ERROR] /tmp/msource/libexec/mysqld: unknown option '--skip-bdb' ... even after I manually search for the location where this flag is passed, and manually edit that source to never issue it. [mysql-5.1.45-source]$ grep -irnH -- '--skip-bdb' * mysql-test/mtr:4229: mtr_add_arg($args, --skip-bdb); mysql-test/mysql-test-run:4229: mtr_add_arg($args, --skip-bdb); mysql-test/lib/v1/mysql-test-run.pl:3925: mtr_add_arg($args, % s--skip-bdb, $prefix); mysql-test/mysql-test-run.pl:4229: mtr_add_arg($args, --skip-bdb); scripts/mysql_install_db.pl.in:422: --skip-bdb, Clearly something is wrong here. I don't know if mysql is accidentally linking against some other, existing mysql library already present on my test machine. In any case, it shouldn't be doing that. I suspected that that somehow /usr/bin/mysql_install_db (for my existing MySQL installation) was being called (which contains --skip-bdb). But even after removing the --skip-bdb from that file the error persisted. Any ideas on what the error might be, and how to fix it ? Thanks for any help. -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql?unsub=arch...@jab.org
Re: libexec/mysqld: unknown option '--skip-bdb'
Hi Kris, all, what you describe here seems to be related to MySQL bug# 50336 http://bugs.mysql.com/bug.php?id=50336 : Kris wrote: [[...]] I am trying to compile mysql and install it in a non-standard directory. I do notwant mysql installed in /usr or /usr/local. For example, I am trying to install it in /tmp/msource with the configure line: [[...]] 'make' and 'make install' succeed. I have also created a custom my.cnf file installed in /tmp/msource/etc/my.cnf. However, installing the database tables fails: [[...]] The following error just won't go away: 100513 21:53:35 [ERROR] /tmp/msource/libexec/mysqld: unknown option '--skip-bdb' ... even after I manually search for the location where this flag is passed, and manually edit that source to never issue it. [[...]] I am surprised to see that option still occurring in a file in 5.1, that looks wrong. But I doubt this is really the problem, because in that case many more users would suffer from it, internal tests included. Are you really sure that this option does not show up in your my.cnf, or any other config file read by the server? It was still used and supported in 5.0, so any remnant 5.0 config file read by your 5.1 server might cause this problem. HTH, Jörg -- Joerg Bruehe, MySQL Build Team, joerg.bru...@sun.com Sun Microsystems GmbH, Komturstrasse 18a, D-12099 Berlin Geschaeftsfuehrer: Juergen Kunz Amtsgericht Muenchen: HRB161028 -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql?unsub=arch...@jab.org
Re: libexec/mysqld: unknown option '--skip-bdb'
On Fri, 2010-05-14 at 10:28 +0200, Joerg Bruehe wrote: The following error just won't go away: 100513 21:53:35 [ERROR] /tmp/msource/libexec/mysqld: unknown option '--skip-bdb' ... even after I manually search for the location where this flag is passed, and manually edit that source to never issue it. [[...]] I am surprised to see that option still occurring in a file in 5.1, that looks wrong. But I doubt this is really the problem, because in that case many more users would suffer from it, internal tests included. I doubt many more users try to create a clean test installation of MySQL, in a specific directory, on a machine that already has MySQL installed. Are you really sure that this option does not show up in your my.cnf, or any other config file read by the server? It was still used and supported in 5.0, so any remnant 5.0 config file read by your 5.1 server might cause this problem. Well, that's precisely the problem: I am doing a clean ./configure; make; make install cycle, and I am producing a clean my.cnf, but somehow the mysql tools are trying to execute something else (which must pick up my existing 5.0 installation. They must be picking up something from the path. This is just wrong. I should be able to build a clean MySQL and start it independently, even if I already have a previous, pre-packaged MySQL instance on the test machine. I believe the problem is in the MySQL tools. I shouldn't have to remove my existing MySQL installation just to build and test some other MySQL installation. That's exactly the whole rationale behind having a --prefix in ./configure, a --basedir, and so forth. -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql?unsub=arch...@jab.org
Re: libexec/mysqld: unknown option '--skip-bdb'
Kris wrote: Hello, I am trying to produce an automated, reliable, and repeatable way of testing mysql releases, and I am finding an error that makes this impossible to accomplish. I am trying to compile mysql and install it in a non-standard directory. I do notwant mysql installed in /usr or /usr/local. For example, I am trying to install it in /tmp/msource with the configure line: Do not install software in /tmp in Linux. /tmp is not guaranteed to survive a reboot. -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql?unsub=arch...@jab.org
Re: libexec/mysqld: unknown option '--skip-bdb'
Kris, all, Kris wrote: On Fri, 2010-05-14 at 10:28 +0200, Joerg Bruehe wrote: The following error just won't go away: 100513 21:53:35 [ERROR] /tmp/msource/libexec/mysqld: unknown option '--skip-bdb' ... even after I manually search for the location where this flag is passed, and manually edit that source to never issue it. [[...]] I am surprised to see that option still occurring in a file in 5.1, that looks wrong. But I doubt this is really the problem, because in that case many more users would suffer from it, internal tests included. I doubt many more users try to create a clean test installation of MySQL, in a specific directory, on a machine that already has MySQL installed. Correct - but if really the occurrence in mysql_install_db were the issue, then it would also occur with a single install. Are you really sure that this option does not show up in your my.cnf, or any other config file read by the server? It was still used and supported in 5.0, so any remnant 5.0 config file read by your 5.1 server might cause this problem. Well, that's precisely the problem: I am doing a clean ./configure; make; make install cycle, and I am producing a clean my.cnf, but somehow the mysql tools are trying to execute something else (which must pick up my existing 5.0 installation. They must be picking up something from the path. I fear so, too. You didn't exactly specify your platform, I can just tell it is some Unix. I propose you check for all existing my.cnf and do a ls -lu on them, then start your new server, then do that ls -lu again. I suspect one (or more) of them will be read by the new server upon startup. This is just wrong. I should be able to build a clean MySQL and start it independently, even if I already have a previous, pre-packaged MySQL instance on the test machine. I believe the problem is in the MySQL tools. I shouldn't have to remove my existing MySQL installation just to build and test some other MySQL installation. That's exactly the whole rationale behind having a --prefix in ./configure, a --basedir, and so forth. It is a question of policies and preferences. MySQL traditionally supports both global, system-wide configuration files and local ones, by instance. Changing that might affect existing installations, so it can't be done lightly and needs decent design and announcement. Regards, Jörg -- Joerg Bruehe, MySQL Build Team, joerg.bru...@sun.com Sun Microsystems GmbH, Komturstrasse 18a, D-12099 Berlin Geschaeftsfuehrer: Juergen Kunz Amtsgericht Muenchen: HRB161028 -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql?unsub=arch...@jab.org
Re: libexec/mysqld: unknown option '--skip-bdb'
Joerg, thanks again for the help. I disagree with you. I doubt many more users try to create a clean test installation of MySQL, in a specific directory, on a machine that already has MySQL installed. Correct - but if really the occurrence in mysql_install_db were the issue, then it would also occur with a single install. True, for a single install in a non-standard directory (try using a --prefix, --basedir, --datadir, all the flags I've shown), not for a single install that installs in /var and /usr/bin and uses /etc/mysql/my.cnf. mysql_install_db does not work as expected for 5.1 (probably previous versions, too), and I will show this next. The problem is that mysql_install_db, somehow always reads /etc/mysql/my.cnf. That's wrong. It should read @sysconfdir@/my.cnf. You didn't exactly specify your platform, I can just tell it is some Unix. I propose you check for all existing my.cnf and do a ls -lu on them, then start your new server, then do that ls -lu again. I suspect one (or more) of them will be read by the new server upon startup. It's Debian 5.0. $ uname -a Linux syd.mkgnu.net 2.6.18-6-686 #1 SMP Sat Dec 27 09:31:05 UTC 2008 i686 GNU/Linux I've just run: # find / | grep -i my.cnf And deleted every single my.cnf file, except from: /tmp/msource/etc/my.cnf /etc/mysql/my.cnf I still get the same error, because /etc/mysql/my.cnf is still there. This is just wrong. I should be able to build a clean MySQL and start it independently, even if I already have a previous, pre-packaged MySQL instance on the test machine. I believe the problem is in the MySQL tools. I shouldn't have to remove my existing MySQL installation just to build and test some other MySQL installation. That's exactly the whole rationale behind having a --prefix in ./configure, a --basedir, and so forth. It is a question of policies and preferences. MySQL traditionally supports both global, system-wide configuration files and local ones, by instance. Changing that might affect existing installations, so it can't be done lightly and needs decent design and announcement. If this was a PATH issue, meaning I'm calling different mysql (5.0) binaries, I should be able to: export PATH=/tmp/msource/bin:$PATH ... then run: /tmp/msource/bin/mysql_install_db --basedir=/tmp/msource --datadir=/tmp/msource/data ... and get the tables installed. I still get the same error though. I suspect that there are hardcoded paths in mysql that ALWAYS call the mysql tools from /usr/bin, or ALWAYS use /etc/mysql/my.cnf. It does not appear to me to be a question of policies, but a bug. I am attaching the output of: $ strace /tmp/msource/bin/mysql_install_db --basedir=/tmp/msource --datadir=/tmp/msource/data /tmp/trace 21 The output observes: # mysql_install_db is opened on fd 3 open(/tmp/msource/bin/mysql_install_db, O_RDONLY|O_LARGEFILE) = 3 # From fd 3 one uses parameters that don't make sense. I did not specify --user=mysql. And I did not specify the pid file to be in /var/run. read(3, --user=mysql\n--pid-file=/var/run/..., 128) = 128 # Further down, I did not install mysql in /var/lib, but in /tmp/msource read(3, /var/lib/mysql\n..., 128) = 15 It seems that mysql first consults hard-coded defaults that are *different* from the paths one specifies in the ./configure line. To me this seems wrong. To verify this, after I remove /etc/mysql/my.cnf, installing the tables works: +++= $ /tmp/msource/bin/mysql_install_db --basedir=/tmp/msource --datadir=/tmp/msource/data Installing MySQL system tables... OK Filling help tables... OK To start mysqld at boot time you have to copy support-files/mysql.server to the right place for your system PLEASE REMEMBER TO SET A PASSWORD FOR THE MySQL root USER ! To do so, start the server, then issue the following commands: /tmp/msource/bin/mysqladmin -u root password 'new-password' /tmp/msource/bin/mysqladmin -u root -h syd.mkgnu.net password 'new-password' Alternatively you can run: /tmp/msource/bin/mysql_secure_installation which will also give you the option of removing the test databases and anonymous user created by default. This is strongly recommended for production servers. See the manual for more instructions. You can start the MySQL daemon with: cd /tmp/msource ; /tmp/msource/bin/mysqld_safe You can test the MySQL daemon with mysql-test-run.pl cd /tmp/msource/mysql-test ; perl mysql-test-run.pl Please report any problems with the /tmp/msource/scripts/mysqlbug script! + Restoring /etc/mysql/my.cnf results in mysql_install_db to fail again. This suggests that any mysql test build will ALWAYS consult /etc/mysql/my.cnf, even if one already specified a different sysconfdir to ./configure. To me, this seems like a bug. execve(/tmp/msource/bin/mysql_install_db, [/tmp/msource/bin/mysql_install_d..., --basedir=/tmp/msource, --datadir=/tmp/msource/data], [/* 51 vars */]) = 0 brk(0
Re: libexec/mysqld: unknown option '--skip-bdb'
Do not install software in /tmp in Linux. /tmp is not guaranteed to survive a reboot. Thank you for the heads up. Well... there is *another* bug where if one specifies in their my.cnf filepaths that are over 100 characters, the filenames are truncated at 100, hence making it impossible to really install mysql anywhere you want for reliable testing... I hope someone can look into that, too. -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql?unsub=arch...@jab.org
Re: libexec/mysqld: unknown option '--skip-bdb'
Hi Kris, all, Kris wrote: Joerg, thanks again for the help. I disagree with you. that's perfectly fine - combining our two different viewpoints, we will be able to show more of the issue at hand than from one point alone. I doubt many more users try to create a clean test installation of MySQL, in a specific directory, on a machine that already has MySQL installed. Correct - but if really the occurrence in mysql_install_db were the issue, then it would also occur with a single install. True, for a single install in a non-standard directory (try using a --prefix, --basedir, --datadir, all the flags I've shown), not for a single install that installs in /var and /usr/bin and uses /etc/mysql/my.cnf. mysql_install_db does not work as expected for 5.1 (probably previous versions, too), and I will show this next. The problem is that mysql_install_db, somehow always reads /etc/mysql/my.cnf. That's wrong. It should read @sysconfdir@/my.cnf. Well, you explicitly say it is *not* a problem of mysql_install_db issuing this option all by itself, but rather by taking it from a system-wide config file. That knowledge is helpful. I won't take any position which config file mysql_install_db should read: True, you can argue it should take just the specific one for its installation, but you can also argue that a system-wide config file which may be read by the server should also be read by the script. I will readily admit I am no expert on this, so please don't debate with me which component should behave in which way. You didn't exactly specify your platform, I can just tell it is some Unix. I propose you check for all existing my.cnf and do a ls -lu on them, then start your new server, then do that ls -lu again. I suspect one (or more) of them will be read by the new server upon startup. It's Debian 5.0. I asked for the platform just because on Linux I would recommend locate for finding those config files, whereas this tool is not available on other Unixes AFAIK. $ uname -a Linux syd.mkgnu.net 2.6.18-6-686 #1 SMP Sat Dec 27 09:31:05 UTC 2008 i686 GNU/Linux I've just run: # find / | grep -i my.cnf And deleted every single my.cnf file, except from: /tmp/msource/etc/my.cnf /etc/mysql/my.cnf I still get the same error, because /etc/mysql/my.cnf is still there. In such cases, I prefer doing ls -lu twice, to show the file was read. Your approach of using strace is of course more exact, but also more effort. This is just wrong. I should be able to build a clean MySQL and start it independently, even if I already have a previous, pre-packaged MySQL instance on the test machine. I believe the problem is in the MySQL tools. I shouldn't have to remove my existing MySQL installation just to build and test some other MySQL installation. That's exactly the whole rationale behind having a --prefix in ./configure, a --basedir, and so forth. It is a question of policies and preferences. MySQL traditionally supports both global, system-wide configuration files and local ones, by instance. Changing that might affect existing installations, so it can't be done lightly and needs decent design and announcement. If this was a PATH issue, meaning I'm calling different mysql (5.0) binaries, I should be able to: export PATH=/tmp/msource/bin:$PATH ... then run: /tmp/msource/bin/mysql_install_db --basedir=/tmp/msource --datadir=/tmp/msource/data I never claimed it to be a PATH issue - config files are not covered by PATH. And obviously the concept of having global config files, which is meant to make it easy to have system-wide settings for multiple instances, implies that these config files must be compatible with all versions used on that system - which causes your problem, as the --skip-bdb option is not compatible with 5.1. Whether the advantage (system wide settings) or the disadvantage (read from all versions) has the stronger weight - that differs by type of usage. In your case, the compatibility requirement doesn't fit your use. You don't state it explicitly, but I take your text to mean If the MySQL tools are compiled using --prefix, --basedir, or other such settings, they should not read system-wide configuration files. That is a possible request, different from the current MySQL policy. I do not think it is easy to implement that. Seen from the MySQL policy, the fault is with you: You should not have a global /etc/my.cnf if you are dealing with multiple versions. ... and get the tables installed. I still get the same error though. I suspect that there are hardcoded paths in mysql that ALWAYS call the mysql tools from /usr/bin, or ALWAYS use /etc/mysql/my.cnf. It does not appear to me to be a question of policies, but a bug. Did I claim that a policy always is perfect? A ls -lu on the mysql tools from /usr/bin and /etc/mysql/my.cnf should tell you whether one of these tools gets called (I sincerely hope none is) and/or the config
problem with mysqld process
Hi * mysqld process consuming more 100% of cpu usage and execution time also very high. 1. how to reduce CPU? 2. why mysqld process consuming high cpu utilization? 3. Wether need to fine tune sql application. then how to use plan table in mysql? 4. which storage engine is better for transaction? innodb or myisam. my current production, some tables are in myisam and some tables are in innodb. is there any changes required here... 5. what is the use of left outer join. this will downgrade the db performance.. please proived the answer. my current db give more performance related issue. i was increase the instance memory but still problem not solved. i don't have much idea in mysql.. thank in advance.. Cheers Faizal S GSM : 9840118673 Blog: http://oradbapro.blogspot.com
Re: mysqld occupies 100$ cpu
what is your my.cnf setting. Also did u check slowquery.log for any sql's not using index or not using the right index. On Mon, Jan 11, 2010 at 1:21 PM, F.A.I.Z.A.L sac.fai...@gmail.com wrote: Hi mysqld process taking high cpu utilization (100%), how to reduce the cup utilization it is running under solaris 8 with 16GB ram and 1 multicore cpu (2 core) anyone help please? Cheers Faizal S GSM : 9840118673 Blog: http://oradbapro.blogspot.com
Re: mysqld occupies 100$ cpu
Hi Kumar, thanks for your reply.. here is my my.cnf file. i don't see anything here. what is this slowquery.log?, where it will be? --- [mysqld] datadir=/var/lib/mysql socket=/var/lib/mysql/mysql.sock # Default to using old password format for compatibility with mysql 3.x # clients (those using the mysqlclient10 compatibility package). old_passwords=1 [mysql.server] user=mysql basedir=/var/lib [mysqld_safe] log-error=/var/log/mysqld.log pid-file=/var/run/mysqld/mysqld.pid - Cheers Faizal S GSM : 9840118673 Blog: http://oradbapro.blogspot.com On Mon, Jan 11, 2010 at 2:17 PM, Ananda Kumar anan...@gmail.com wrote: what is your my.cnf setting. Also did u check slowquery.log for any sql's not using index or not using the right index. On Mon, Jan 11, 2010 at 1:21 PM, F.A.I.Z.A.L sac.fai...@gmail.com wrote: Hi mysqld process taking high cpu utilization (100%), how to reduce the cup utilization it is running under solaris 8 with 16GB ram and 1 multicore cpu (2 core) anyone help please? Cheers Faizal S GSM : 9840118673 Blog: http://oradbapro.blogspot.com
Re: mysqld occupies 100$ cpu
looks like u have not setup slow query log parameter. If this is a non-production db, shut it down and add this parameter, unser [mysqld] log-slow-queries = /var/lib/slowqueries.log. Or execute SHOW ENGINE STATUS\G; You will get to know what all activities are going on ur db and check if there is any IO contention happening On Mon, Jan 11, 2010 at 2:47 PM, F.A.I.Z.A.L sac.fai...@gmail.com wrote: Hi Kumar, thanks for your reply.. here is my my.cnf file. i don't see anything here. what is this slowquery.log?, where it will be? --- [mysqld] datadir=/var/lib/mysql socket=/var/lib/mysql/mysql.sock # Default to using old password format for compatibility with mysql 3.x # clients (those using the mysqlclient10 compatibility package). old_passwords=1 [mysql.server] user=mysql basedir=/var/lib [mysqld_safe] log-error=/var/log/mysqld.log pid-file=/var/run/mysqld/mysqld.pid - Cheers Faizal S GSM : 9840118673 Blog: http://oradbapro.blogspot.com On Mon, Jan 11, 2010 at 2:17 PM, Ananda Kumar anan...@gmail.com wrote: what is your my.cnf setting. Also did u check slowquery.log for any sql's not using index or not using the right index. On Mon, Jan 11, 2010 at 1:21 PM, F.A.I.Z.A.L sac.fai...@gmail.comwrote: Hi mysqld process taking high cpu utilization (100%), how to reduce the cup utilization it is running under solaris 8 with 16GB ram and 1 multicore cpu (2 core) anyone help please? Cheers Faizal S GSM : 9840118673 Blog: http://oradbapro.blogspot.com
Re: mysqld occupies 100$ cpu
i try this mysql SHOW ENGINE STATUS\G; ERROR 1286 (42000): Unknown table engine 'STATUS' ERROR: No query specified after setting the parameter in my.cnf which u provided. it is not showing mysql show engine status; ERROR 1286 (42000): Unknown table engine 'status' what i have to do now? Cheers Faizal S GSM : 9840118673 Blog: http://oradbapro.blogspot.com On Mon, Jan 11, 2010 at 3:27 PM, Ananda Kumar anan...@gmail.com wrote: looks like u have not setup slow query log parameter. If this is a non-production db, shut it down and add this parameter, unser [mysqld] log-slow-queries = /var/lib/slowqueries.log. Or execute SHOW ENGINE STATUS\G; You will get to know what all activities are going on ur db and check if there is any IO contention happening On Mon, Jan 11, 2010 at 2:47 PM, F.A.I.Z.A.L sac.fai...@gmail.com wrote: Hi Kumar, thanks for your reply.. here is my my.cnf file. i don't see anything here. what is this slowquery.log?, where it will be? --- [mysqld] datadir=/var/lib/mysql socket=/var/lib/mysql/mysql.sock # Default to using old password format for compatibility with mysql 3.x # clients (those using the mysqlclient10 compatibility package). old_passwords=1 [mysql.server] user=mysql basedir=/var/lib [mysqld_safe] log-error=/var/log/mysqld.log pid-file=/var/run/mysqld/mysqld.pid - Cheers Faizal S GSM : 9840118673 Blog: http://oradbapro.blogspot.com On Mon, Jan 11, 2010 at 2:17 PM, Ananda Kumar anan...@gmail.comwrote: what is your my.cnf setting. Also did u check slowquery.log for any sql's not using index or not using the right index. On Mon, Jan 11, 2010 at 1:21 PM, F.A.I.Z.A.L sac.fai...@gmail.comwrote: Hi mysqld process taking high cpu utilization (100%), how to reduce the cup utilization it is running under solaris 8 with 16GB ram and 1 multicore cpu (2 core) anyone help please? Cheers Faizal S GSM : 9840118673 Blog: http://oradbapro.blogspot.com
Re: mysqld occupies 100$ cpu
SHOW ENGINE innodb STATUS\G On Mon, Jan 11, 2010 at 3:35 PM, F.A.I.Z.A.L sac.fai...@gmail.com wrote: i try this mysql SHOW ENGINE STATUS\G; ERROR 1286 (42000): Unknown table engine 'STATUS' ERROR: No query specified after setting the parameter in my.cnf which u provided. it is not showing mysql show engine status; ERROR 1286 (42000): Unknown table engine 'status' what i have to do now? Cheers Faizal S GSM : 9840118673 Blog: http://oradbapro.blogspot.com On Mon, Jan 11, 2010 at 3:27 PM, Ananda Kumar anan...@gmail.com wrote: looks like u have not setup slow query log parameter. If this is a non-production db, shut it down and add this parameter, unser [mysqld] log-slow-queries = /var/lib/slowqueries.log. Or execute SHOW ENGINE STATUS\G; You will get to know what all activities are going on ur db and check if there is any IO contention happening On Mon, Jan 11, 2010 at 2:47 PM, F.A.I.Z.A.L sac.fai...@gmail.comwrote: Hi Kumar, thanks for your reply.. here is my my.cnf file. i don't see anything here. what is this slowquery.log?, where it will be? --- [mysqld] datadir=/var/lib/mysql socket=/var/lib/mysql/mysql.sock # Default to using old password format for compatibility with mysql 3.x # clients (those using the mysqlclient10 compatibility package). old_passwords=1 [mysql.server] user=mysql basedir=/var/lib [mysqld_safe] log-error=/var/log/mysqld.log pid-file=/var/run/mysqld/mysqld.pid - Cheers Faizal S GSM : 9840118673 Blog: http://oradbapro.blogspot.com On Mon, Jan 11, 2010 at 2:17 PM, Ananda Kumar anan...@gmail.comwrote: what is your my.cnf setting. Also did u check slowquery.log for any sql's not using index or not using the right index. On Mon, Jan 11, 2010 at 1:21 PM, F.A.I.Z.A.L sac.fai...@gmail.comwrote: Hi mysqld process taking high cpu utilization (100%), how to reduce the cup utilization it is running under solaris 8 with 16GB ram and 1 multicore cpu (2 core) anyone help please? Cheers Faizal S GSM : 9840118673 Blog: http://oradbapro.blogspot.com
RE: mysqld occupies 100$ cpu
Regards, Jerry Schwartz The Infoshop by Global Information Incorporated 195 Farmington Ave. Farmington, CT 06032 860.674.8796 / FAX: 860.674.8341 www.the-infoshop.com -Original Message- From: F.A.I.Z.A.L [mailto:sac.fai...@gmail.com] Sent: Monday, January 11, 2010 2:51 AM To: mysql@lists.mysql.com Subject: mysqld occupies 100$ cpu Hi mysqld process taking high cpu utilization (100%), how to reduce the cup utilization it is running under solaris 8 with 16GB ram and 1 multicore cpu (2 core) anyone help please? Cheers Faizal S GSM : 9840118673 Blog: http://oradbapro.blogspot.com -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql?unsub=arch...@jab.org
mysqld occupies 100$ cpu
Hi mysqld process taking high cpu utilization (100%), how to reduce the cup utilization it is running under solaris 8 with 16GB ram and 1 multicore cpu (2 core) anyone help please? Cheers Faizal S GSM : 9840118673 Blog: http://oradbapro.blogspot.com
Can't initialize mysqld data dir
I'm trying to get started with running mysqld but I can't set up the data directory. Any hints? Thanks in advance. Details follow: $ uname -a Linux hammer.csail.mit.edu 2.6.27.35-170.2.94.fc10.x86_64 #1 SMP Thu Oct 1 14:41:38 EDT 2009 x86_64 x86_64 x86_64 GNU/Linux $ mysql/bin/mysqld --version mysql/bin/mysqld Ver 5.4.3-beta for unknown-linux-gnu on x86_64 (MySQL Community Server (GPL)) $ cat my.cnf [mysqld] port=3307 datadir=./data-mysql basedir=mysql $ mkdir data-mysql $ mysql/scripts/mysql_install_db --basedir=mysql --datadir=./data-mysql Installing MySQL system tables... 091213 13:45:13 [ERROR] Can't find messagefile '/local-home/yang/packdb/mysql/share/mysql/share/english/errmsg.sys' 091213 13:45:13 [ERROR] Aborting 091213 13:45:13 [Note] Installation of system tables failed! Examine the logs in ./data-mysql/ for more information. You can try to start the mysqld daemon with: shell mysql//bin/mysqld --skip-grant and use the command line tool mysql//bin/mysql to connect to the mysql database and look at the grant tables: shell mysql//bin/mysql -u root mysql mysql show tables Try 'mysqld --help' if you have problems with paths. Using --log gives you a log in ./data-mysql/ that may be helpful. The latest information about MySQL is available on the web at http://www.mysql.com/. Please consult the MySQL manual section 'Problems running mysql_install_db', and the manual section that describes problems on your OS. Another information source are the MySQL email archives available at http://lists.mysql.com/. Please check all of the above before mailing us! And remember, if you do mail us, you MUST use the mysql//scripts/mysqlbug script! $ mysql//bin/mysqld --defaults-file=my.cnf --skip-grant 091213 14:04:18 [Note] Plugin 'FEDERATED' is disabled. InnoDB: The InnoDB memory heap is disabled InnoDB: Mutexes and rw_locks use GCC atomic builtins. 091213 14:04:18 InnoDB: highest supported file format is Barracuda. 091213 14:04:19 InnoDB Plugin 1.0.4 started; log sequence number 44254 091213 14:04:19 [Warning] Can't open and lock time zone table: Table 'mysql.time_zone_leap_second' doesn't exist trying to live without them 091213 14:04:19 [ERROR] Can't open and lock privilege tables: Table 'mysql.servers' doesn't exist 091213 14:04:19 [Note] mysql//bin/mysqld: ready for connections. Version: '5.4.3-beta' socket: '/tmp/mysql.sock' port: 3307 MySQL Community Server (GPL) $ mysql//bin/mysql -u root mysql -e 'show tables;' -- Yang Zhang http://www.mit.edu/~y_z/ -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql?unsub=arch...@jab.org
[ERROR] /usr/sbin/mysqld: unknown option '--ndbcluster'
Dear All, Can anyone brief me about this error. I am unable to start the mysql so please suggest me work around on how to fix this error. I am installing mysql Ver 14.14 Distrib 5.1.38, for pc-linux-gnu (i686) using readline 5.1 [ERROR] /usr/sbin/mysqld: unknown option '--ndbcluster' -- Manoj M. Burande, Artificial Machines Pvt Ltd, System Administrator. -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql?unsub=arch...@jab.org
RE: [ERROR] /usr/sbin/mysqld: unknown option '--ndbcluster'
Edit your /etc/my.cnf file and remove the option. Regards, Gavin Towey -Original Message- From: Manoj Burande [mailto:manoj.bura...@artificialmachines.com] Sent: Friday, September 18, 2009 7:17 AM To: mysql@lists.mysql.com Subject: [ERROR] /usr/sbin/mysqld: unknown option '--ndbcluster' Dear All, Can anyone brief me about this error. I am unable to start the mysql so please suggest me work around on how to fix this error. I am installing mysql Ver 14.14 Distrib 5.1.38, for pc-linux-gnu (i686) using readline 5.1 [ERROR] /usr/sbin/mysqld: unknown option '--ndbcluster' -- Manoj M. Burande, Artificial Machines Pvt Ltd, System Administrator. -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql?unsub=gto...@ffn.com The information contained in this transmission may contain privileged and confidential information. It is intended only for the use of the person(s) named above. If you are not the intended recipient, you are hereby notified that any review, dissemination, distribution or duplication of this communication is strictly prohibited. If you are not the intended recipient, please contact the sender by reply email and destroy all copies of the original message. -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql?unsub=arch...@jab.org
Where does mysqld write a core file?
I've been trying to make mysqld write a coredump following a crash, and this morning I finally succeeded - according to mysqld.log anyway. It clearly says Writing a core file - but where to? I've checked the datadir /var/lib/mysql, whereelse might it be? /Per Jessen, Zürich -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql?unsub=arch...@jab.org
mysqld not writing to err-log
Hi, mysqld is not writing to err-log and i do not see any log generated upon mysql service restart. In my.cnf = [safe_mysqld] err-log=/var/log/mysqld.log pid-file=/var/lib/mysql/mysql.pid open_files_limit=16384 r...@server[~]# ll /var/log/mysqld.log -rw-r--r-- 1 mysql root 0 Nov 24 2008 /var/log/mysqld.log r...@server[~]# Please advise what i can look for to fix this issue.
Re: mysqld not writing to err-log
It is probably writing to syslog. Try cat /var/log/messages | grep -i mysqld to search for entries made by mysqld. Walter On Tue, Jun 16, 2009 at 11:48 AM, Madan Thapamadan.feedb...@gmail.com wrote: Hi, mysqld is not writing to err-log and i do not see any log generated upon mysql service restart. In my.cnf = [safe_mysqld] err-log=/var/log/mysqld.log pid-file=/var/lib/mysql/mysql.pid open_files_limit=16384 r...@server[~]# ll /var/log/mysqld.log -rw-r--r-- 1 mysql root 0 Nov 24 2008 /var/log/mysqld.log r...@server[~]# Please advise what i can look for to fix this issue. -- Walter Heck, Engineer @ Open Query (http://openquery.com) Affordable Training and ProActive Support for MySQL related technologies Follow our blog at http://openquery.com/blog/ OurDelta: free enhanced builds for MySQL @ http://ourdelta.org -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql?unsub=arch...@jab.org
Re: mysqld not writing to err-log
Hi Rick, It was't a permission issue though. I did compare with another server, that had the same thing working. [r...@server1 mysql]# ls -lh /var/log/mysqld.log -rw-r--r-- 1 mysql root 60M Jun 16 18:40 /var/log/mysqld.log [r...@server1 mysql]# grep err-log /etc/my.cnf err-log=/var/log/mysqld.log [r...@server1 mysql]# On this server now, I have commented err-log and use log_error , which happily writes to the log file r...@server [~]# grep err-log /etc/my.cnf #err-log=/var/log/mysqld.log r...@server [~]# r...@server [~]# ls -lh /var/log/mysqld.log -rw-r--r-- 1 mysql root 728 Jun 16 17:51 /var/log/mysqld.log r...@server [~]# err-log was under safe_mysqld, so neither any fault in its position in my.cnf ( http://mysqldatabaseadministration.blogspot.com/2006/07/err-log-or-log-error.html) [safe_mysqld] #err-log=/var/log/mysqld.log On Wed, Jun 17, 2009 at 12:21 AM, lists-mysql replies-lists-b3z1-my...@listmail.innovate.net wrote: This might be an issue of permissions (/var/log is controlled by root). So, you might try touch-ing /var/log/mysqld.log and setting ownership to mysql.mysql. Then [re-]start mysqld and see if the log gets written to. Related, the logging entry in my my.cnf is log-error= not your err-log=. I haven't looked in the documentation to see if your version should work, but mine does, so you might want to try it. - Rick Original Message Date: Tuesday, June 16, 2009 11:18:25 PM +0530 From: Madan Thapa madan.feedb...@gmail.com To: mysql@lists.mysql.com Subject: mysqld not writing to err-log Hi, mysqld is not writing to err-log and i do not see any log generated upon mysql service restart. In my.cnf = [safe_mysqld] err-log=/var/log/mysqld.log pid-file=/var/lib/mysql/mysql.pid open_files_limit=16384 r...@server[~]# ll /var/log/mysqld.log -rw-r--r-- 1 mysql root 0 Nov 24 2008 /var/log/mysqld.log r...@server[~]# Please advise what i can look for to fix this issue. End Original Message
Re: mysqld not writing to err-log
Thanks Eric, it worked. = On Tue, Jun 16, 2009 at 11:55 PM, Eric Bergen eric.ber...@gmail.com wrote: Madan, Try: [mysqld] log_error=/var/log/mysqld.log On Tue, Jun 16, 2009 at 10:48 AM, Madan Thapamadan.feedb...@gmail.com wrote: Hi, mysqld is not writing to err-log and i do not see any log generated upon mysql service restart. In my.cnf = [safe_mysqld] err-log=/var/log/mysqld.log pid-file=/var/lib/mysql/mysql.pid open_files_limit=16384 r...@server[~]# ll /var/log/mysqld.log -rw-r--r-- 1 mysql root 0 Nov 24 2008 /var/log/mysqld.log r...@server[~]# Please advise what i can look for to fix this issue.
Call a routine on mysqld startup
Hi, I must call a routine when mysqld start (to populate a heap table). I did not find any related options in mysqld --help --verbose. Is there a way to achieve this, without modifying the startup script ? Thanks in advance. -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql?unsub=arch...@jab.org
Re: Call a routine on mysqld startup
There's an option called init-file that will invoke an sql script on start up. That would probably work for you. On Mon, Jun 15, 2009 at 5:17 AM, Gabriel Linder lin...@jeuxvideo.comwrote: Hi, I must call a routine when mysqld start (to populate a heap table). I did not find any related options in mysqld --help --verbose. Is there a way to achieve this, without modifying the startup script ? Thanks in advance. -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql?unsub=jlyons4...@gmail.com -- Jim Lyons Web developer / Database administrator http://www.weblyons.com
Re: Call a routine on mysqld startup
On Mon, 15 Jun 2009 10:00:00 -0400 Jim Lyons jlyons4...@gmail.com wrote: There's an option called init-file that will invoke an sql script on start up. That would probably work for you. Thanks you, that is what I was searching for. I guess I should clean my glasses :) -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql?unsub=arch...@jab.org
Re: CentOS 4.4 mysqld crash
I have opened a bug about this issue: http://bugs.mysql.com/bug.php?id=44914 Joel On Tue, May 12, 2009 at 10:55 PM, Joel Heenan jo...@planetjoel.com wrote: Mysql List, I have a crash that has occured a number of times on a production CentOS 4.4 machine. It occurs when using a product called Interspire Email Marketer and doing an import of some 30,000 email addresses. Unfortunately, I have not been able to reproduce the crash myself (I have tried numerous times). MySQL is version 4.1.22, latest for this version of CentOS. Should I open a bug report about this? Since it is production I can't do too much on the host itself and I have limited ability to reproduce. Here is what the crash looks like: Version: '4.1.22' socket: '/var/lib/mysql/mysql.sock' port: 3306 Source distribution mysqld got signal 11; This could be because you hit a bug. It is also possible that this binary or one of the libraries it was linked against is corrupt, improperly built, or misconfigured. This error can also be caused by malfunctioning hardware. We will try our best to scrape up some info that will hopefully help diagnose the problem, but since we have already crashed, something is definitely wrong and this may fail. key_buffer_size=402653184 read_buffer_size=1044480 max_used_connections=82 max_connections=500 threads_connected=44 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 1927212 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. thd=0x950dc9c8 Attempting backtrace. You can use the following information to find out where mysqld died. If you see no messages after this, something went terribly wrong... Cannot determine thread, fp=0x961626b4, backtrace may not be correct. Stack range sanity check OK, backtrace follows: 0x8139eec 0x4f6e67 0x831b884 0x81c22a7 0x81c3150 0x81b5f53 0x814f934 0x8151b3c 0x815255a 0x8152db5 0x815375b 0x4f5371 0x3f5ffe New value of fp=(nil) failed sanity check, terminating stack trace! Please read http://dev.mysql.com/doc/mysql/en/Using_stack_trace.html and follow instructions on how to resolve the stack trace. Resolved stack trace is much more helpful in diagnosing the problem, so please do resolve it Trying to get some variables. Some pointers may be invalid and cause the dump to abort... thd-query at 0x9c20480 = SAVEPOINT interspire4a00f4b153ccf thd-thread_id=108208 The manual page at http://www.mysql.com/doc/en/Crashing.html contains information that should help you find out what is causing the crash. Number of processes running now: 0 090506 11:23:45 mysqld restarted Here is what the /etc/my.cnf file looks like: [mysqld] datadir=/var/lib/mysql socket=/var/lib/mysql/mysql.sock old_passwords=1 back_log = 75 skip-innodb max_connections = 500 key_buffer = 384M myisam_sort_buffer_size = 64M join_buffer_size = 1M read_buffer_size = 1M sort_buffer_size = 2M table_cache = 1800 thread_cache_size = 384 wait_timeout = 7200 connect_timeout = 10 tmp_table_size = 64M max_heap_table_size = 64M max_allowed_packet = 64M max_connect_errors = 1000 read_rnd_buffer_size = 524288 bulk_insert_buffer_size = 8M query_cache_limit = 4M query_cache_size =128M query_cache_type = 1 query_prealloc_size = 65536 query_alloc_block_size = 131072 default-storage-engine = MyISAM [mysql.server] user=mysql basedir=/var/lib [mysqld_safe] err-log=/var/log/mysqld.log pid-file=/var/run/mysqld/mysqld.pid nice = -5 open_files_limit = 8192 [myisamchk] tmpdir=/home/mysqltmp key_buffer = 64M sort_buffer = 64M read_buffer = 16M write_buffer = 16M [mysqldump] quick max_allowed_packet = 16M Thanks Joel
CentOS 4.4 mysqld crash
Mysql List, I have a crash that has occured a number of times on a production CentOS 4.4 machine. It occurs when using a product called Interspire Email Marketer and doing an import of some 30,000 email addresses. Unfortunately, I have not been able to reproduce the crash myself (I have tried numerous times). MySQL is version 4.1.22, latest for this version of CentOS. Should I open a bug report about this? Since it is production I can't do too much on the host itself and I have limited ability to reproduce. Here is what the crash looks like: Version: '4.1.22' socket: '/var/lib/mysql/mysql.sock' port: 3306 Source distribution mysqld got signal 11; This could be because you hit a bug. It is also possible that this binary or one of the libraries it was linked against is corrupt, improperly built, or misconfigured. This error can also be caused by malfunctioning hardware. We will try our best to scrape up some info that will hopefully help diagnose the problem, but since we have already crashed, something is definitely wrong and this may fail. key_buffer_size=402653184 read_buffer_size=1044480 max_used_connections=82 max_connections=500 threads_connected=44 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 1927212 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. thd=0x950dc9c8 Attempting backtrace. You can use the following information to find out where mysqld died. If you see no messages after this, something went terribly wrong... Cannot determine thread, fp=0x961626b4, backtrace may not be correct. Stack range sanity check OK, backtrace follows: 0x8139eec 0x4f6e67 0x831b884 0x81c22a7 0x81c3150 0x81b5f53 0x814f934 0x8151b3c 0x815255a 0x8152db5 0x815375b 0x4f5371 0x3f5ffe New value of fp=(nil) failed sanity check, terminating stack trace! Please read http://dev.mysql.com/doc/mysql/en/Using_stack_trace.html and follow instructions on how to resolve the stack trace. Resolved stack trace is much more helpful in diagnosing the problem, so please do resolve it Trying to get some variables. Some pointers may be invalid and cause the dump to abort... thd-query at 0x9c20480 = SAVEPOINT interspire4a00f4b153ccf thd-thread_id=108208 The manual page at http://www.mysql.com/doc/en/Crashing.html contains information that should help you find out what is causing the crash. Number of processes running now: 0 090506 11:23:45 mysqld restarted Here is what the /etc/my.cnf file looks like: [mysqld] datadir=/var/lib/mysql socket=/var/lib/mysql/mysql.sock old_passwords=1 back_log = 75 skip-innodb max_connections = 500 key_buffer = 384M myisam_sort_buffer_size = 64M join_buffer_size = 1M read_buffer_size = 1M sort_buffer_size = 2M table_cache = 1800 thread_cache_size = 384 wait_timeout = 7200 connect_timeout = 10 tmp_table_size = 64M max_heap_table_size = 64M max_allowed_packet = 64M max_connect_errors = 1000 read_rnd_buffer_size = 524288 bulk_insert_buffer_size = 8M query_cache_limit = 4M query_cache_size =128M query_cache_type = 1 query_prealloc_size = 65536 query_alloc_block_size = 131072 default-storage-engine = MyISAM [mysql.server] user=mysql basedir=/var/lib [mysqld_safe] err-log=/var/log/mysqld.log pid-file=/var/run/mysqld/mysqld.pid nice = -5 open_files_limit = 8192 [myisamchk] tmpdir=/home/mysqltmp key_buffer = 64M sort_buffer = 64M read_buffer = 16M write_buffer = 16M [mysqldump] quick max_allowed_packet = 16M Thanks Joel
Re: mysqld memory usage
Quoth Walter Heck li...@olindata.com: You could bring it down, but the real question is if you really want to do that? Making the buffers and caches smaller will reduce the memory used, but it also reduces performance. Noted. Could you tell us what you are hoping to use MySQL for and why you wanna bring the memory usage down? WordPress blogs. Why, because my VPS is very low-powered. I have PostgreSQL installed as well and it uses less than 1.5% of memory when idle. Sebastian -- Emacs' AlsaPlayer - Music Without Jolts Lightweight, full-featured and mindful of your idyllic happiness. http://home.gna.org/eap -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql?unsub=arch...@jab.org
Re: mysqld memory usage
Quoth wult...@gmail.com: Through your conf file(s) you have told MySQL how much memory it may consume. As long as the server does not go beyond what it is told it may consume it is not doing anything wrong. Thanks. I'll have a look in the conf file. At the moment it's running as it came out of the box. The server will not return all memory when idle because various things will be held in several caches. Start hacking your configuration file if you wish to decrease idle consumption. Noted. Also, 5.0 is very broad. Somerhing like 5.0.67 on 64 bit intel is way more informitive. Most people have not migrated to 5.1 yet, and many people are using versions older than 5.0 . Fair enough. It's 5.0.51a-21 on 32 bit Intel Xeon. Sebastian -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql?unsub=arch...@jab.org
Re: mysqld memory usage
So I assume you have a terabyte of RAM in the server, since you didn't say... OMG, it's using 143GB of RAM when it's idle? Wow.. :-) You need to provide some more details here. I can't judge whether there is any issue at all. Baron On Sun, Feb 1, 2009 at 8:35 AM, Sebastian Tennant seb...@smolny.plus.com wrote: Hi all, I recently installed MySQL (version 5.0) on my Debian Lenny VPS and mysqld uses 14.3% of memory when idle. Is this a known issue? I'm aware that version 5.0 is not the latest version but it's the one currently shipped by Debian Lenny (testing) so I'm loathe to 'manually' install a later version. Is there anything I can do to bring this figure down? Any advice/tips/pointers much appreciated. Regards, Sebastian -- Emacs' AlsaPlayer - Music Without Jolts Lightweight, full-featured and mindful of your idyllic happiness. http://home.gna.org/eap -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql?unsub=ba...@xaprb.com -- Baron Schwartz, Director of Consulting, Percona Inc. Our Blog: http://www.mysqlperformanceblog.com/ Our Services: http://www.percona.com/services.html -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql?unsub=arch...@jab.org
Re: mysqld memory usage
Quoth Baron Schwartz ba...@xaprb.com: So I assume you have a terabyte of RAM in the server, since you didn't say... OMG, it's using 143GB of RAM when it's idle? Wow.. :-) You need to provide some more details here. I can't judge whether there is any issue at all. Sorry. My VPS has 144 MB of RAM so mysqld is using about ~ 21 MB when idle. Sebastian -- Emacs' AlsaPlayer - Music Without Jolts Lightweight, full-featured and mindful of your idyllic happiness. http://home.gna.org/eap -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql?unsub=arch...@jab.org
mysqld memory usage
Hi all, I recently installed MySQL (version 5.0) on my Debian Lenny VPS and mysqld uses 14.3% of memory when idle. Is this a known issue? I'm aware that version 5.0 is not the latest version but it's the one currently shipped by Debian Lenny (testing) so I'm loathe to 'manually' install a later version. Is there anything I can do to bring this figure down? Any advice/tips/pointers much appreciated. Regards, Sebastian -- Emacs' AlsaPlayer - Music Without Jolts Lightweight, full-featured and mindful of your idyllic happiness. http://home.gna.org/eap -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql?unsub=arch...@jab.org
Re: mysqld memory usage
You could bring it down, but the real question is if you really want to do that? Making the buffers and caches smaller will reduce the memory used, but it also reduces performance. Could you tell us what you are hoping to use MySQL for and why you wanna bring the memory usage down? Walter OlinData: Professional services for MySQL Support * Consulting * Administration http://www.olindata.com On Sun, Feb 1, 2009 at 2:35 PM, Sebastian Tennant seb...@smolny.plus.com wrote: Hi all, I recently installed MySQL (version 5.0) on my Debian Lenny VPS and mysqld uses 14.3% of memory when idle. Is this a known issue? I'm aware that version 5.0 is not the latest version but it's the one currently shipped by Debian Lenny (testing) so I'm loathe to 'manually' install a later version. Is there anything I can do to bring this figure down? Any advice/tips/pointers much appreciated. Regards, Sebastian -- Emacs' AlsaPlayer - Music Without Jolts Lightweight, full-featured and mindful of your idyllic happiness. http://home.gna.org/eap -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql?unsub=li...@olindata.com -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql?unsub=arch...@jab.org
Mysqld fails to start
Hello List, mysqld fails to start, and emits the following error messages in /var/log/mysqld.log 090127 10:00:30 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql /usr/libexec/mysqld: Table 'mysql.plugin' doesn't exist 090127 10:00:30 [ERROR] Can't open the mysql.plugin table. Please run mysql_upgrade to create it. 090127 10:00:30 InnoDB: Operating system error number 13 in a file operation. InnoDB: The error means mysqld does not have the access rights to InnoDB: the directory. InnoDB: File name ./ibdata1 InnoDB: File operation call: 'open'. InnoDB: Cannot continue operation. 090127 10:00:30 mysqld_safe mysqld from pid file /var/run/mysqld/mysqld.pid ended So, I tried to run mysql_upgrade: # mysql_upgrade Looking for 'mysql' as: mysql Looking for 'mysqlcheck' as: mysqlcheck Running 'mysqlcheck'... mysqlcheck: Got error: 2002: Can't connect to local MySQL server through socket '/var/lib/mysql/mysql.sock' (2) when trying to connect FATAL ERROR: Upgrade failed So, it seems like a chicken and egg thing??? Cannot run mysql_upgrade bcause the server is not running. Cannot run the server because I must first run mysql_upgrade. PS: I know nothing about configuring and setting up mysql. Amarok2 needs a running mysqld in order to organize music tracks collections ... etc. I need help to get mysqld started and running and to add users that are allowed to access and modify their databases. Could someone send me a set of user commands to get thing going? These are all the mysql related packages on my system: mysql-5.1.30-1.fc7.remi mysql-libs-5.1.30-1.fc7.remi sqlite-3.4.2-1.fc7 libdbi-dbd-pgsql-0.8.1a-2.fc7 sqlite-3.4.2-1.fc7 postgresql-libs-8.2.9-1.fc7 hsqldb-1.8.0.8-1jpp.5.fc7 postgresql-libs-8.2.9-1.fc7 mysql-server-5.1.30-1.fc7.remi mysqlclient15-5.0.67-1.fc7.remi mod_auth_mysql-3.0.0-3.1 mysqlclient15-5.0.67-1.fc7.remi sqlite2-2.8.17-1.fc6 php-pgsql-5.2.8-1.fc7.remi sqlite-devel-3.4.2-1.fc7 postgresql-python-8.2.9-1.fc7 postgresql-8.2.9-1.fc7 postgresql-server-8.2.9-1.fc7 mono-data-sqlite-1.2.3-5.fc7 mysql-devel-5.1.30-1.fc7.remi mysqlclient15-devel-5.0.67-1.fc7.remi mod_auth_pgsql-2.0.3-3 mysql-connector-odbc-3.51.12-2.2 libdbi-dbd-mysql-0.8.1a-2.fc7 mysqlclient15-devel-5.0.67-1.fc7.remi php-mysql-5.2.8-1.fc7.remi Cheers, JD -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql?unsub=arch...@jab.org
Re: Mysqld fails to start
Hello JD, You need to look beyond the first error messages: /usr/libexec/mysqld: Table 'mysql.plugin' doesn't exist 090127 10:00:30 [ERROR] Can't open the mysql.plugin table. Please run mysql_upgrade to create it. but keep reading: 090127 10:00:30 InnoDB: Operating system error number 13 in a file operation. InnoDB: The error means mysqld does not have the access rights to InnoDB: the directory. InnoDB: File name ./ibdata1 InnoDB: File operation call: 'open'. InnoDB: Cannot continue operation. That's what is really keeping mysqld from starting. You just need to chown/chmod the data directory or run mysqld as the proper user. -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql?unsub=arch...@jab.org
Re: Mysqld fails to start
Hi JD, I believe the error about mysql.plugin is a red herring - it needs fixing, but it's not the reason MySQL isn't starting. The second error is the one about InnoDB not having access rights to the directory. Check that /var/lib/mysql is writeable by the MySQL user (usually MySQL.) Make sure this is done, then MySQL will start, then you can run mysql_upgrade. HTH, Andy JD wrote: Hello List, mysqld fails to start, and emits the following error messages in /var/log/mysqld.log 090127 10:00:30 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql /usr/libexec/mysqld: Table 'mysql.plugin' doesn't exist 090127 10:00:30 [ERROR] Can't open the mysql.plugin table. Please run mysql_upgrade to create it. 090127 10:00:30 InnoDB: Operating system error number 13 in a file operation. InnoDB: The error means mysqld does not have the access rights to InnoDB: the directory. InnoDB: File name ./ibdata1 InnoDB: File operation call: 'open'. InnoDB: Cannot continue operation. 090127 10:00:30 mysqld_safe mysqld from pid file /var/run/mysqld/mysqld.pid ended So, I tried to run mysql_upgrade: # mysql_upgrade Looking for 'mysql' as: mysql Looking for 'mysqlcheck' as: mysqlcheck Running 'mysqlcheck'... mysqlcheck: Got error: 2002: Can't connect to local MySQL server through socket '/var/lib/mysql/mysql.sock' (2) when trying to connect FATAL ERROR: Upgrade failed So, it seems like a chicken and egg thing??? Cannot run mysql_upgrade bcause the server is not running. Cannot run the server because I must first run mysql_upgrade. PS: I know nothing about configuring and setting up mysql. Amarok2 needs a running mysqld in order to organize music tracks collections ... etc. I need help to get mysqld started and running and to add users that are allowed to access and modify their databases. Could someone send me a set of user commands to get thing going? These are all the mysql related packages on my system: mysql-5.1.30-1.fc7.remi mysql-libs-5.1.30-1.fc7.remi sqlite-3.4.2-1.fc7 libdbi-dbd-pgsql-0.8.1a-2.fc7 sqlite-3.4.2-1.fc7 postgresql-libs-8.2.9-1.fc7 hsqldb-1.8.0.8-1jpp.5.fc7 postgresql-libs-8.2.9-1.fc7 mysql-server-5.1.30-1.fc7.remi mysqlclient15-5.0.67-1.fc7.remi mod_auth_mysql-3.0.0-3.1 mysqlclient15-5.0.67-1.fc7.remi sqlite2-2.8.17-1.fc6 php-pgsql-5.2.8-1.fc7.remi sqlite-devel-3.4.2-1.fc7 postgresql-python-8.2.9-1.fc7 postgresql-8.2.9-1.fc7 postgresql-server-8.2.9-1.fc7 mono-data-sqlite-1.2.3-5.fc7 mysql-devel-5.1.30-1.fc7.remi mysqlclient15-devel-5.0.67-1.fc7.remi mod_auth_pgsql-2.0.3-3 mysql-connector-odbc-3.51.12-2.2 libdbi-dbd-mysql-0.8.1a-2.fc7 mysqlclient15-devel-5.0.67-1.fc7.remi php-mysql-5.2.8-1.fc7.remi Cheers, JD -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql?unsub=arch...@jab.org
Re: Mysqld fails to start
JD wrote: Hello List, mysqld fails to start, and emits the following error messages in /var/log/mysqld.log 090127 10:00:30 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql /usr/libexec/mysqld: Table 'mysql.plugin' doesn't exist 090127 10:00:30 [ERROR] Can't open the mysql.plugin table. Please run mysql_upgrade to create it. 090127 10:00:30 InnoDB: Operating system error number 13 in a file operation. InnoDB: The error means mysqld does not have the access rights to InnoDB: the directory. That's most likely to be the real error. Or, at least, the most important one. InnoDB: File name ./ibdata1 InnoDB: File operation call: 'open'. InnoDB: Cannot continue operation. 090127 10:00:30 mysqld_safe mysqld from pid file /var/run/mysqld/mysqld.pid ended So, I tried to run mysql_upgrade: # mysql_upgrade Looking for 'mysql' as: mysql Looking for 'mysqlcheck' as: mysqlcheck Running 'mysqlcheck'... mysqlcheck: Got error: 2002: Can't connect to local MySQL server through socket '/var/lib/mysql/mysql.sock' (2) when trying to connect FATAL ERROR: Upgrade failed So, it seems like a chicken and egg thing??? Cannot run mysql_upgrade bcause the server is not running. Cannot run the server because I must first run mysql_upgrade. I think you're being misled by the fact that there are two errors: A missing table and a file system that mysqld doesn't have access to. Fix the file permissions first, and then try starting mysqld. You'll then be able to run mysql_upgrade to fix the missing table problem (which is a warning, not a fatal error, hence why you need to have the server running to be able to fix it). Mark -- http://www.good-stuff.co.uk - Stuff, some of it good -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql?unsub=arch...@jab.org
Re: Mysqld fails to start
I am running as root. I dont understand what rights or permissions mysqld needs beyond those of root. Also, ./ibdata1 is relative to what path? I get this message no matter what dir is my current working dir. I searched in my home dir and in /root home dir. There is no such file or directory called ./ibdata1 nor is there any file or dir called mysql.plugin Wasnt mysqld supposed to create all that at startup?? This is what the top of the log file says: 071215 15:36:09 mysqld started InnoDB: The first specified data file ./ibdata1 did not exist: InnoDB: a new database to be created! 071215 15:36:09 InnoDB: Setting file ./ibdata1 size to 10 MB InnoDB: Database physically writes the file full: wait... 071215 15:36:10 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... 071215 15:36:10 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 071215 15:36:10 InnoDB: Started; log sequence number 0 0 071215 15:36:10 [Note] /usr/libexec/mysqld: ready for connections. Version: '5.0.45' socket: '/var/lib/mysql/mysql.sock' port: 3306 Source distribution 071215 15:47:01 [Note] /usr/libexec/mysqld: Normal shutdown 071215 15:47:01 InnoDB: Starting shutdown... 071215 15:47:02 InnoDB: Shutdown completed; log sequence number 0 43655 071215 15:47:02 [Note] /usr/libexec/mysqld: Shutdown complete 071215 15:47:02 mysqld ended Then at re-start: 071215 15:47:17 mysqld started 071215 15:47:17 InnoDB: Started; log sequence number 0 43655 071215 15:47:17 [Note] /usr/libexec/mysqld: ready for connections. Version: '5.0.45' socket: '/var/lib/mysql/mysql.sock' port: 3306 Source distribution 071217 0:03:27 [Note] /usr/libexec/mysqld: Normal shutdown 071217 0:03:28 InnoDB: Starting shutdown... 071217 0:03:29 InnoDB: Shutdown completed; log sequence number 0 43655 071217 0:03:29 [Note] /usr/libexec/mysqld: Shutdown complete 071217 00:03:29 mysqld ended 090121 09:32:40 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql /usr/libexec/mysqld: Table 'mysql.plugin' doesn't exist 090121 9:32:41 [ERROR] Can't open the mysql.plugin table. Please run mysql_upgrade to create it. 090121 9:32:41 InnoDB: Operating system error number 13 in a file operation. InnoDB: The error means mysqld does not have the access rights to InnoDB: the directory. InnoDB: File name ./ibdata1 InnoDB: File operation call: 'open'. InnoDB: Cannot continue operation. 090121 09:32:41 mysqld_safe mysqld from pid file /var/run/mysqld/mysqld.pid ended 090121 09:33:41 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql /usr/libexec/mysqld: Table 'mysql.plugin' doesn't exist 090121 9:33:41 [ERROR] Can't open the mysql.plugin table. Please run mysql_upgrade to create it. So, how are ibdata1 and mysql.plugin are supposed to be created? Baron Schwartz wrote: Hello JD, You need to look beyond the first error messages: /usr/libexec/mysqld: Table 'mysql.plugin' doesn't exist 090127 10:00:30 [ERROR] Can't open the mysql.plugin table. Please run mysql_upgrade to create it. but keep reading: 090127 10:00:30 InnoDB: Operating system error number 13 in a file operation. InnoDB: The error means mysqld does not have the access rights to InnoDB: the directory. InnoDB: File name ./ibdata1 InnoDB: File operation call: 'open'. InnoDB: Cannot continue operation. That's what is really keeping mysqld from starting. You just need to chown/chmod the data directory or run mysqld as the proper user.
Re: Mysqld fails to start
Deamon runs as root. ls -ld /var/lib/mysql/ drwxr-xr-x 5 mysql mysql 4096 2009-01-27 10:00 /var/lib/mysql/ So what other perms does root need? Andy Shellam wrote: Hi JD, I believe the error about mysql.plugin is a red herring - it needs fixing, but it's not the reason MySQL isn't starting. The second error is the one about InnoDB not having access rights to the directory. Check that /var/lib/mysql is writeable by the MySQL user (usually MySQL.) Make sure this is done, then MySQL will start, then you can run mysql_upgrade. HTH, Andy JD wrote: Hello List, mysqld fails to start, and emits the following error messages in /var/log/mysqld.log 090127 10:00:30 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql /usr/libexec/mysqld: Table 'mysql.plugin' doesn't exist 090127 10:00:30 [ERROR] Can't open the mysql.plugin table. Please run mysql_upgrade to create it. 090127 10:00:30 InnoDB: Operating system error number 13 in a file operation. InnoDB: The error means mysqld does not have the access rights to InnoDB: the directory. InnoDB: File name ./ibdata1 InnoDB: File operation call: 'open'. InnoDB: Cannot continue operation. 090127 10:00:30 mysqld_safe mysqld from pid file /var/run/mysqld/mysqld.pid ended So, I tried to run mysql_upgrade: # mysql_upgrade Looking for 'mysql' as: mysql Looking for 'mysqlcheck' as: mysqlcheck Running 'mysqlcheck'... mysqlcheck: Got error: 2002: Can't connect to local MySQL server through socket '/var/lib/mysql/mysql.sock' (2) when trying to connect FATAL ERROR: Upgrade failed So, it seems like a chicken and egg thing??? Cannot run mysql_upgrade bcause the server is not running. Cannot run the server because I must first run mysql_upgrade. PS: I know nothing about configuring and setting up mysql. Amarok2 needs a running mysqld in order to organize music tracks collections ... etc. I need help to get mysqld started and running and to add users that are allowed to access and modify their databases. Could someone send me a set of user commands to get thing going? These are all the mysql related packages on my system: mysql-5.1.30-1.fc7.remi mysql-libs-5.1.30-1.fc7.remi sqlite-3.4.2-1.fc7 libdbi-dbd-pgsql-0.8.1a-2.fc7 sqlite-3.4.2-1.fc7 postgresql-libs-8.2.9-1.fc7 hsqldb-1.8.0.8-1jpp.5.fc7 postgresql-libs-8.2.9-1.fc7 mysql-server-5.1.30-1.fc7.remi mysqlclient15-5.0.67-1.fc7.remi mod_auth_mysql-3.0.0-3.1 mysqlclient15-5.0.67-1.fc7.remi sqlite2-2.8.17-1.fc6 php-pgsql-5.2.8-1.fc7.remi sqlite-devel-3.4.2-1.fc7 postgresql-python-8.2.9-1.fc7 postgresql-8.2.9-1.fc7 postgresql-server-8.2.9-1.fc7 mono-data-sqlite-1.2.3-5.fc7 mysql-devel-5.1.30-1.fc7.remi mysqlclient15-devel-5.0.67-1.fc7.remi mod_auth_pgsql-2.0.3-3 mysql-connector-odbc-3.51.12-2.2 libdbi-dbd-mysql-0.8.1a-2.fc7 mysqlclient15-devel-5.0.67-1.fc7.remi php-mysql-5.2.8-1.fc7.remi Cheers, JD -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql?unsub=arch...@jab.org
Re: Mysqld fails to start
JD, please post the ouput from: ls -altr /var/lib/mysql thanks Claudio JD wrote: Deamon runs as root. ls -ld /var/lib/mysql/ drwxr-xr-x 5 mysql mysql 4096 2009-01-27 10:00 /var/lib/mysql/ So what other perms does root need? Andy Shellam wrote: Hi JD, I believe the error about mysql.plugin is a red herring - it needs fixing, but it's not the reason MySQL isn't starting. The second error is the one about InnoDB not having access rights to the directory. Check that /var/lib/mysql is writeable by the MySQL user (usually MySQL.) Make sure this is done, then MySQL will start, then you can run mysql_upgrade. HTH, Andy JD wrote: Hello List, mysqld fails to start, and emits the following error messages in /var/log/mysqld.log 090127 10:00:30 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql /usr/libexec/mysqld: Table 'mysql.plugin' doesn't exist 090127 10:00:30 [ERROR] Can't open the mysql.plugin table. Please run mysql_upgrade to create it. 090127 10:00:30 InnoDB: Operating system error number 13 in a file operation. InnoDB: The error means mysqld does not have the access rights to InnoDB: the directory. InnoDB: File name ./ibdata1 InnoDB: File operation call: 'open'. InnoDB: Cannot continue operation. 090127 10:00:30 mysqld_safe mysqld from pid file /var/run/mysqld/mysqld.pid ended So, I tried to run mysql_upgrade: # mysql_upgrade Looking for 'mysql' as: mysql Looking for 'mysqlcheck' as: mysqlcheck Running 'mysqlcheck'... mysqlcheck: Got error: 2002: Can't connect to local MySQL server through socket '/var/lib/mysql/mysql.sock' (2) when trying to connect FATAL ERROR: Upgrade failed So, it seems like a chicken and egg thing??? Cannot run mysql_upgrade bcause the server is not running. Cannot run the server because I must first run mysql_upgrade. PS: I know nothing about configuring and setting up mysql. Amarok2 needs a running mysqld in order to organize music tracks collections ... etc. I need help to get mysqld started and running and to add users that are allowed to access and modify their databases. Could someone send me a set of user commands to get thing going? These are all the mysql related packages on my system: mysql-5.1.30-1.fc7.remi mysql-libs-5.1.30-1.fc7.remi sqlite-3.4.2-1.fc7 libdbi-dbd-pgsql-0.8.1a-2.fc7 sqlite-3.4.2-1.fc7 postgresql-libs-8.2.9-1.fc7 hsqldb-1.8.0.8-1jpp.5.fc7 postgresql-libs-8.2.9-1.fc7 mysql-server-5.1.30-1.fc7.remi mysqlclient15-5.0.67-1.fc7.remi mod_auth_mysql-3.0.0-3.1 mysqlclient15-5.0.67-1.fc7.remi sqlite2-2.8.17-1.fc6 php-pgsql-5.2.8-1.fc7.remi sqlite-devel-3.4.2-1.fc7 postgresql-python-8.2.9-1.fc7 postgresql-8.2.9-1.fc7 postgresql-server-8.2.9-1.fc7 mono-data-sqlite-1.2.3-5.fc7 mysql-devel-5.1.30-1.fc7.remi mysqlclient15-devel-5.0.67-1.fc7.remi mod_auth_pgsql-2.0.3-3 mysql-connector-odbc-3.51.12-2.2 libdbi-dbd-mysql-0.8.1a-2.fc7 mysqlclient15-devel-5.0.67-1.fc7.remi php-mysql-5.2.8-1.fc7.remi Cheers, JD -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql?unsub=arch...@jab.org
Re: Mysqld fails to start
ls -altr /var/lib/mysql total 20548K drwxr-xr-x 2 mysql mysql 4096 2007-12-15 15:36 test/ -rw-r--r-- 1 mysql mysql 5242880 2007-12-15 15:36 ib_logfile1 drwxr-xr-x 2 mysql mysql 4096 2007-12-15 16:10 ampache/ -rw-r--r-- 1 mysql mysql 10485760 2007-12-17 00:03 ibdata1 drwxr-xr-x 2 mysql mysql 4096 2009-01-21 14:12 mysql/ srwxrwxrwx 1 mysql mysql0 2009-01-27 14:13 mysql.sock= -rw-r--r-- 1 mysql mysql 5242880 2009-01-27 14:13 ib_logfile0 drwxr-xr-x 53 root root 4096 2009-01-27 14:14 ../ drwxr-xr-x 5 mysql mysql 4096 2009-01-27 15:48 ./ Claudio Nanni wrote: JD, please post the ouput from: ls -altr /var/lib/mysql thanks Claudio JD wrote: Deamon runs as root. ls -ld /var/lib/mysql/ drwxr-xr-x 5 mysql mysql 4096 2009-01-27 10:00 /var/lib/mysql/ So what other perms does root need? Andy Shellam wrote: Hi JD, I believe the error about mysql.plugin is a red herring - it needs fixing, but it's not the reason MySQL isn't starting. The second error is the one about InnoDB not having access rights to the directory. Check that /var/lib/mysql is writeable by the MySQL user (usually MySQL.) Make sure this is done, then MySQL will start, then you can run mysql_upgrade. HTH, Andy JD wrote: Hello List, mysqld fails to start, and emits the following error messages in /var/log/mysqld.log 090127 10:00:30 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql /usr/libexec/mysqld: Table 'mysql.plugin' doesn't exist 090127 10:00:30 [ERROR] Can't open the mysql.plugin table. Please run mysql_upgrade to create it. 090127 10:00:30 InnoDB: Operating system error number 13 in a file operation. InnoDB: The error means mysqld does not have the access rights to InnoDB: the directory. InnoDB: File name ./ibdata1 InnoDB: File operation call: 'open'. InnoDB: Cannot continue operation. 090127 10:00:30 mysqld_safe mysqld from pid file /var/run/mysqld/mysqld.pid ended So, I tried to run mysql_upgrade: # mysql_upgrade Looking for 'mysql' as: mysql Looking for 'mysqlcheck' as: mysqlcheck Running 'mysqlcheck'... mysqlcheck: Got error: 2002: Can't connect to local MySQL server through socket '/var/lib/mysql/mysql.sock' (2) when trying to connect FATAL ERROR: Upgrade failed So, it seems like a chicken and egg thing??? Cannot run mysql_upgrade bcause the server is not running. Cannot run the server because I must first run mysql_upgrade. PS: I know nothing about configuring and setting up mysql. Amarok2 needs a running mysqld in order to organize music tracks collections ... etc. I need help to get mysqld started and running and to add users that are allowed to access and modify their databases. Could someone send me a set of user commands to get thing going? These are all the mysql related packages on my system: mysql-5.1.30-1.fc7.remi mysql-libs-5.1.30-1.fc7.remi sqlite-3.4.2-1.fc7 libdbi-dbd-pgsql-0.8.1a-2.fc7 sqlite-3.4.2-1.fc7 postgresql-libs-8.2.9-1.fc7 hsqldb-1.8.0.8-1jpp.5.fc7 postgresql-libs-8.2.9-1.fc7 mysql-server-5.1.30-1.fc7.remi mysqlclient15-5.0.67-1.fc7.remi mod_auth_mysql-3.0.0-3.1 mysqlclient15-5.0.67-1.fc7.remi sqlite2-2.8.17-1.fc6 php-pgsql-5.2.8-1.fc7.remi sqlite-devel-3.4.2-1.fc7 postgresql-python-8.2.9-1.fc7 postgresql-8.2.9-1.fc7 postgresql-server-8.2.9-1.fc7 mono-data-sqlite-1.2.3-5.fc7 mysql-devel-5.1.30-1.fc7.remi mysqlclient15-devel-5.0.67-1.fc7.remi mod_auth_pgsql-2.0.3-3 mysql-connector-odbc-3.51.12-2.2 libdbi-dbd-mysql-0.8.1a-2.fc7 mysqlclient15-devel-5.0.67-1.fc7.remi php-mysql-5.2.8-1.fc7.remi Cheers, JD -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql?unsub=arch...@jab.org
Re: Mysqld fails to start
Ah, try this: chmod ug+rw ibdata1 and the same for your iblogfile0 and iblogfile1 files.. Walter OlinData: Professional services for MySQL Support * Consulting * Administration http://www.olindata.com On Wed, Jan 28, 2009 at 12:48 AM, JD jd1...@gmail.com wrote: ls -altr /var/lib/mysql -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql?unsub=arch...@jab.org
Re: Mysqld fails to start
Hi JD, just try a simple thing, rm /var/lib/mysql/ib_logfile1 rm /var/lib/mysql/ib_logfile2 to remove the innodb log files, sometimes you can have this problems, did you copy the database between servers? where are the .pid and .err files? Claudio 2009/1/28 JD jd1...@gmail.com ls -altr /var/lib/mysql total 20548K drwxr-xr-x 2 mysql mysql 4096 2007-12-15 15:36 test/ -rw-r--r-- 1 mysql mysql 5242880 2007-12-15 15:36 ib_logfile1 drwxr-xr-x 2 mysql mysql 4096 2007-12-15 16:10 ampache/ -rw-r--r-- 1 mysql mysql 10485760 2007-12-17 00:03 ibdata1 drwxr-xr-x 2 mysql mysql 4096 2009-01-21 14:12 mysql/ srwxrwxrwx 1 mysql mysql0 2009-01-27 14:13 mysql.sock= -rw-r--r-- 1 mysql mysql 5242880 2009-01-27 14:13 ib_logfile0 drwxr-xr-x 53 root root 4096 2009-01-27 14:14 ../ drwxr-xr-x 5 mysql mysql 4096 2009-01-27 15:48 ./ Claudio Nanni wrote: JD, please post the ouput from: ls -altr /var/lib/mysql thanks Claudio JD wrote: Deamon runs as root. ls -ld /var/lib/mysql/ drwxr-xr-x 5 mysql mysql 4096 2009-01-27 10:00 /var/lib/mysql/ So what other perms does root need? Andy Shellam wrote: Hi JD, I believe the error about mysql.plugin is a red herring - it needs fixing, but it's not the reason MySQL isn't starting. The second error is the one about InnoDB not having access rights to the directory. Check that /var/lib/mysql is writeable by the MySQL user (usually MySQL.) Make sure this is done, then MySQL will start, then you can run mysql_upgrade. HTH, Andy JD wrote: Hello List, mysqld fails to start, and emits the following error messages in /var/log/mysqld.log 090127 10:00:30 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql /usr/libexec/mysqld: Table 'mysql.plugin' doesn't exist 090127 10:00:30 [ERROR] Can't open the mysql.plugin table. Please run mysql_upgrade to create it. 090127 10:00:30 InnoDB: Operating system error number 13 in a file operation. InnoDB: The error means mysqld does not have the access rights to InnoDB: the directory. InnoDB: File name ./ibdata1 InnoDB: File operation call: 'open'. InnoDB: Cannot continue operation. 090127 10:00:30 mysqld_safe mysqld from pid file /var/run/mysqld/mysqld.pid ended So, I tried to run mysql_upgrade: # mysql_upgrade Looking for 'mysql' as: mysql Looking for 'mysqlcheck' as: mysqlcheck Running 'mysqlcheck'... mysqlcheck: Got error: 2002: Can't connect to local MySQL server through socket '/var/lib/mysql/mysql.sock' (2) when trying to connect FATAL ERROR: Upgrade failed So, it seems like a chicken and egg thing??? Cannot run mysql_upgrade bcause the server is not running. Cannot run the server because I must first run mysql_upgrade. PS: I know nothing about configuring and setting up mysql. Amarok2 needs a running mysqld in order to organize music tracks collections ... etc. I need help to get mysqld started and running and to add users that are allowed to access and modify their databases. Could someone send me a set of user commands to get thing going? These are all the mysql related packages on my system: mysql-5.1.30-1.fc7.remi mysql-libs-5.1.30-1.fc7.remi sqlite-3.4.2-1.fc7 libdbi-dbd-pgsql-0.8.1a-2.fc7 sqlite-3.4.2-1.fc7 postgresql-libs-8.2.9-1.fc7 hsqldb-1.8.0.8-1jpp.5.fc7 postgresql-libs-8.2.9-1.fc7 mysql-server-5.1.30-1.fc7.remi mysqlclient15-5.0.67-1.fc7.remi mod_auth_mysql-3.0.0-3.1 mysqlclient15-5.0.67-1.fc7.remi sqlite2-2.8.17-1.fc6 php-pgsql-5.2.8-1.fc7.remi sqlite-devel-3.4.2-1.fc7 postgresql-python-8.2.9-1.fc7 postgresql-8.2.9-1.fc7 postgresql-server-8.2.9-1.fc7 mono-data-sqlite-1.2.3-5.fc7 mysql-devel-5.1.30-1.fc7.remi mysqlclient15-devel-5.0.67-1.fc7.remi mod_auth_pgsql-2.0.3-3 mysql-connector-odbc-3.51.12-2.2 libdbi-dbd-mysql-0.8.1a-2.fc7 mysqlclient15-devel-5.0.67-1.fc7.remi php-mysql-5.2.8-1.fc7.remi Cheers, JD -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/mysql?unsub=claudio.na...@gmail.com
Re: Mysqld fails to start
I did the chmod. Then # ls -latrR /var/lib/mysql /var/lib/mysql: total 20548K drwxrwxr-x 2 mysql mysql 4096 2007-12-15 15:36 test/ -rw-rw-r-- 1 mysql mysql 5242880 2007-12-15 15:36 ib_logfile1 drwxrwxr-x 2 mysql mysql 4096 2007-12-15 16:10 ampache/ drwxrwxr-x 2 mysql mysql 4096 2009-01-21 14:12 mysql/ drwxr-xr-x 53 root root 4096 2009-01-27 14:14 ../ srwxrwxrwx 1 mysql mysql0 2009-01-27 16:35 mysql.sock= -rw-rw-r-- 1 mysql mysql 5242880 2009-01-27 16:35 ib_logfile0 -rw-rw-r-- 1 mysql mysql 10485760 2009-01-27 16:35 ibdata1 drwxrwxr-x 5 mysql mysql 4096 2009-01-27 16:35 ./ /var/lib/mysql/test: total 12K drwxrwxr-x 2 mysql mysql 4096 2007-12-15 15:36 ./ drwxrwxr-x 5 mysql mysql 4096 2009-01-27 16:35 ../ /var/lib/mysql/ampache: total 16K -rw-rw-r-- 1 mysql mysql 65 2007-12-15 16:10 db.opt drwxrwxr-x 2 mysql mysql 4096 2007-12-15 16:10 ./ drwxrwxr-x 5 mysql mysql 4096 2009-01-27 16:35 ../ /var/lib/mysql/mysql: total 788K -rw-rw-r-- 1 mysql mysql 10330 2007-12-15 15:36 user.frm -rw-rw-r-- 1 mysql mysql 1024 2007-12-15 15:36 time_zone_transition_type.MYI -rw-rw-r-- 1 mysql mysql 0 2007-12-15 15:36 time_zone_transition_type.MYD -rw-rw-r-- 1 mysql mysql 8748 2007-12-15 15:36 time_zone_transition_type.frm -rw-rw-r-- 1 mysql mysql 1024 2007-12-15 15:36 time_zone_transition.MYI -rw-rw-r-- 1 mysql mysql 0 2007-12-15 15:36 time_zone_transition.MYD -rw-rw-r-- 1 mysql mysql 8686 2007-12-15 15:36 time_zone_transition.frm -rw-rw-r-- 1 mysql mysql 1024 2007-12-15 15:36 time_zone_name.MYI -rw-rw-r-- 1 mysql mysql 0 2007-12-15 15:36 time_zone_name.MYD -rw-rw-r-- 1 mysql mysql 8606 2007-12-15 15:36 time_zone_name.frm -rw-rw-r-- 1 mysql mysql 1024 2007-12-15 15:36 time_zone.MYI -rw-rw-r-- 1 mysql mysql 0 2007-12-15 15:36 time_zone.MYD -rw-rw-r-- 1 mysql mysql 1024 2007-12-15 15:36 time_zone_leap_second.MYI -rw-rw-r-- 1 mysql mysql 0 2007-12-15 15:36 time_zone_leap_second.MYD -rw-rw-r-- 1 mysql mysql 8624 2007-12-15 15:36 time_zone_leap_second.frm -rw-rw-r-- 1 mysql mysql 8636 2007-12-15 15:36 time_zone.frm -rw-rw-r-- 1 mysql mysql 1024 2007-12-15 15:36 tables_priv.MYI -rw-rw-r-- 1 mysql mysql 0 2007-12-15 15:36 tables_priv.MYD -rw-rw-r-- 1 mysql mysql 8947 2007-12-15 15:36 tables_priv.frm -rw-rw-r-- 1 mysql mysql 1024 2007-12-15 15:36 procs_priv.MYI -rw-rw-r-- 1 mysql mysql 0 2007-12-15 15:36 procs_priv.MYD -rw-rw-r-- 1 mysql mysql 8875 2007-12-15 15:36 procs_priv.frm -rw-rw-r-- 1 mysql mysql 1024 2007-12-15 15:36 proc.MYI -rw-rw-r-- 1 mysql mysql 0 2007-12-15 15:36 proc.MYD -rw-rw-r-- 1 mysql mysql 9691 2007-12-15 15:36 proc.frm -rw-rw-r-- 1 mysql mysql 1024 2007-12-15 15:36 host.MYI -rw-rw-r-- 1 mysql mysql 0 2007-12-15 15:36 host.MYD -rw-rw-r-- 1 mysql mysql 9416 2007-12-15 15:36 host.frm -rw-rw-r-- 1 mysql mysql 17408 2007-12-15 15:36 help_topic.MYI -rw-rw-r-- 1 mysql mysql 333276 2007-12-15 15:36 help_topic.MYD -rw-rw-r-- 1 mysql mysql 8770 2007-12-15 15:36 help_topic.frm -rw-rw-r-- 1 mysql mysql 15360 2007-12-15 15:36 help_relation.MYI -rw-rw-r-- 1 mysql mysql 7281 2007-12-15 15:36 help_relation.MYD -rw-rw-r-- 1 mysql mysql 8630 2007-12-15 15:36 help_relation.frm -rw-rw-r-- 1 mysql mysql 14336 2007-12-15 15:36 help_keyword.MYI -rw-rw-r-- 1 mysql mysql 77815 2007-12-15 15:36 help_keyword.MYD -rw-rw-r-- 1 mysql mysql 8612 2007-12-15 15:36 help_keyword.frm -rw-rw-r-- 1 mysql mysql 3072 2007-12-15 15:36 help_category.MYI -rw-rw-r-- 1 mysql mysql 20916 2007-12-15 15:36 help_category.MYD -rw-rw-r-- 1 mysql mysql 8700 2007-12-15 15:36 help_category.frm -rw-rw-r-- 1 mysql mysql 1024 2007-12-15 15:36 func.MYI -rw-rw-r-- 1 mysql mysql 0 2007-12-15 15:36 func.MYD -rw-rw-r-- 1 mysql mysql 8665 2007-12-15 15:36 func.frm -rw-rw-r-- 1 mysql mysql 9494 2007-12-15 15:36 db.frm -rw-rw-r-- 1 mysql mysql 1024 2007-12-15 15:36 columns_priv.MYI -rw-rw-r-- 1 mysql mysql 0 2007-12-15 15:36 columns_priv.MYD -rw-rw-r-- 1 mysql mysql 8820 2007-12-15 15:36 columns_priv.frm -rw-rw-r-- 1 mysql mysql256 2007-12-15 16:10 user.MYD -rw-rw-r-- 1 mysql mysql 1314 2007-12-15 16:10 db.MYD -rw-rw-r-- 1 mysql mysql 2048 2007-12-17 00:03 user.MYI -rw-rw-r-- 1 mysql mysql 4096 2007-12-17 00:03 db.MYI drwxrwxr-x 2 mysql mysql 4096 2009-01-21 14:12 ./ -rw-rw 1 mysql mysql 12288 2009-01-21 14:12 .swp drwxrwxr-x 5 mysql mysql 4096 2009-01-27 16:35 ../ I restarted mysqld (service mysqld restart) and this is what got written in the mysql.log 090127 16:40:09 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql /usr/libexec/mysqld: Table 'mysql.plugin' doesn't exist 090127 16:40:09 [ERROR] Can't open the mysql.plugin table. Please run mysql_upgrade to create it. 090127 16:40:09 InnoDB: Started; log sequence number 0 43655 090127 16:40:09 [ERROR] Can't open and lock privilege tables: Table 'mysql.servers' doesn't exist 090127 16:40:09 [ERROR] Column count
Re: Mysqld fails to start
I stopped mysqld. I removed those logfiles I did not copy any databe between servers. I only have one machine. I would not even know what to copy, as I know nothing about databases. I have no idea where the .pid and the .err files came from. I restarted the daemon, and this is what it wrote into the /var/messages/mysqd.log 090127 16:54:15 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql /usr/libexec/mysqld: Table 'mysql.plugin' doesn't exist 090127 16:54:15 [ERROR] Can't open the mysql.plugin table. Please run mysql_upgrade to create it. 090127 16:54:15 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... 090127 16:54:15 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: The log sequence number in ibdata files does not match InnoDB: the log sequence number in the ib_logfiles! 090127 16:54:15 InnoDB: Database was not shut down normally! InnoDB: Starting crash recovery. InnoDB: Reading tablespace information from the .ibd files... InnoDB: Restoring possible half-written data pages from the doublewrite InnoDB: buffer... 090127 16:54:15 InnoDB: Started; log sequence number 0 44044 090127 16:54:15 [ERROR] Can't open and lock privilege tables: Table 'mysql.servers' doesn't exist 090127 16:54:15 [ERROR] Column count of mysql.db is wrong. Expected 22, found 20. Created with MySQL 50045, now running 50130. Please use mysql_upgrade to fix this error. 090127 16:54:15 [ERROR] mysql.user has no `Event_priv` column at position 29 090127 16:54:15 [ERROR] Cannot open mysql.event 090127 16:54:15 [ERROR] Event Scheduler: An error occurred when initializing system tables. Disabling the Event Scheduler. 090127 16:54:15 [Note] /usr/libexec/mysqld: ready for connections. Version: '5.1.30' socket: '/var/lib/mysql/mysql.sock' port: 3306 MySQL Community Server (GPL) by Remi Claudio Nanni wrote: Hi JD, just try a simple thing, rm /var/lib/mysql/ib_logfile1 rm /var/lib/mysql/ib_logfile2 to remove the innodb log files, sometimes you can have this problems, did you copy the database between servers? where are the .pid and .err files? Claudio 2009/1/28 JD jd1...@gmail.com mailto:jd1...@gmail.com ls -altr /var/lib/mysql total 20548K drwxr-xr-x 2 mysql mysql 4096 2007-12-15 15:36 test/ -rw-r--r-- 1 mysql mysql 5242880 2007-12-15 15:36 ib_logfile1 drwxr-xr-x 2 mysql mysql 4096 2007-12-15 16:10 ampache/ -rw-r--r-- 1 mysql mysql 10485760 2007-12-17 00:03 ibdata1 drwxr-xr-x 2 mysql mysql 4096 2009-01-21 14:12 mysql/ srwxrwxrwx 1 mysql mysql0 2009-01-27 14:13 mysql.sock= -rw-r--r-- 1 mysql mysql 5242880 2009-01-27 14:13 ib_logfile0 drwxr-xr-x 53 root root 4096 2009-01-27 14:14 ../ drwxr-xr-x 5 mysql mysql 4096 2009-01-27 15:48 ./ Claudio Nanni wrote: JD, please post the ouput from: ls -altr /var/lib/mysql thanks Claudio JD wrote: Deamon runs as root. ls -ld /var/lib/mysql/ drwxr-xr-x 5 mysql mysql 4096 2009-01-27 10:00 /var/lib/mysql/ So what other perms does root need? Andy Shellam wrote: Hi JD, I believe the error about mysql.plugin is a red herring - it needs fixing, but it's not the reason MySQL isn't starting. The second error is the one about InnoDB not having access rights to the directory. Check that /var/lib/mysql is writeable by the MySQL user (usually MySQL.) Make sure this is done, then MySQL will start, then you can run mysql_upgrade. HTH, Andy JD wrote: Hello List, mysqld fails to start, and emits the following error messages in /var/log/mysqld.log 090127 10:00:30 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql /usr/libexec/mysqld: Table 'mysql.plugin' doesn't exist 090127 10:00:30 [ERROR] Can't open the mysql.plugin table. Please run mysql_upgrade to create it. 090127 10:00:30 InnoDB: Operating system error number 13 in a file operation. InnoDB: The error means mysqld does not have the access rights to InnoDB: the directory. InnoDB: File name ./ibdata1 InnoDB: File operation call: 'open'. InnoDB: Cannot continue operation. 090127 10
Re: Mysqld fails to start
OK, I located a weblog on how to change the password and it worked. I then stopped and started the serever, and this is what it belched out in the mysqld.log: 090127 18:17:16 [Note] /usr/libexec/mysqld: Normal shutdown 090127 18:17:16 InnoDB: Starting shutdown... 090127 18:17:17 InnoDB: Shutdown completed; log sequence number 0 44044 090127 18:17:17 [Note] /usr/libexec/mysqld: Shutdown complete 090127 18:17:17 mysqld_safe mysqld from pid file /var/run/mysqld/mysqld.pid ended 090127 18:17:18 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql /usr/libexec/mysqld: Table 'mysql.plugin' doesn't exist 090127 18:17:18 [ERROR] Can't open the mysql.plugin table. Please run mysql_upgrade to create it. 090127 18:17:18 InnoDB: Started; log sequence number 0 44044 090127 18:17:18 [ERROR] Can't open and lock privilege tables: Table 'mysql.servers' doesn't exist 090127 18:17:18 [ERROR] Column count of mysql.db is wrong. Expected 22, found 20. Created with MySQL 50045, now running 50130. Please use mysql_upgrade to fix this error. 090127 18:17:18 [ERROR] mysql.user has no `Event_priv` column at position 29 090127 18:17:18 [ERROR] Cannot open mysql.event 090127 18:17:18 [ERROR] Event Scheduler: An error occurred when initializing system tables. Disabling the Event Scheduler. 090127 18:17:18 [Note] /usr/libexec/mysqld: ready for connections. Version: '5.1.30' socket: '/var/lib/mysql/mysql.sock' port: 3306 MySQL Community Server (GPL) by Remi So, how do I fix those errors about 'mysql.plugin' and mysql.db and mysql.user For that matter why does it even have a mysql.user ??? Should it not be mysql.root? Walter Heck wrote: We're slowly getting there ;) that is the root account for the mysql server, not the linux root account :) when you installed mysql, you chose a root password. If you didn't, look up how to reset your mysql root account's password. Plenty of info on the web :) good luck! Walter OlinData: Professional services for MySQL Support * Consulting * Administration http://www.olindata.com On Wed, Jan 28, 2009 at 1:47 AM, JD jd1...@gmail.com wrote: I did the chmod. Then # ls -latrR /var/lib/mysql /var/lib/mysql: total 20548K drwxrwxr-x 2 mysql mysql 4096 2007-12-15 15:36 test/ -rw-rw-r-- 1 mysql mysql 5242880 2007-12-15 15:36 ib_logfile1 drwxrwxr-x 2 mysql mysql 4096 2007-12-15 16:10 ampache/ drwxrwxr-x 2 mysql mysql 4096 2009-01-21 14:12 mysql/ drwxr-xr-x 53 root root 4096 2009-01-27 14:14 ../ srwxrwxrwx 1 mysql mysql0 2009-01-27 16:35 mysql.sock= -rw-rw-r-- 1 mysql mysql 5242880 2009-01-27 16:35 ib_logfile0 -rw-rw-r-- 1 mysql mysql 10485760 2009-01-27 16:35 ibdata1 drwxrwxr-x 5 mysql mysql 4096 2009-01-27 16:35 ./ /var/lib/mysql/test: total 12K drwxrwxr-x 2 mysql mysql 4096 2007-12-15 15:36 ./ drwxrwxr-x 5 mysql mysql 4096 2009-01-27 16:35 ../ /var/lib/mysql/ampache: total 16K -rw-rw-r-- 1 mysql mysql 65 2007-12-15 16:10 db.opt drwxrwxr-x 2 mysql mysql 4096 2007-12-15 16:10 ./ drwxrwxr-x 5 mysql mysql 4096 2009-01-27 16:35 ../ /var/lib/mysql/mysql: total 788K -rw-rw-r-- 1 mysql mysql 10330 2007-12-15 15:36 user.frm -rw-rw-r-- 1 mysql mysql 1024 2007-12-15 15:36 time_zone_transition_type.MYI -rw-rw-r-- 1 mysql mysql 0 2007-12-15 15:36 time_zone_transition_type.MYD -rw-rw-r-- 1 mysql mysql 8748 2007-12-15 15:36 time_zone_transition_type.frm -rw-rw-r-- 1 mysql mysql 1024 2007-12-15 15:36 time_zone_transition.MYI -rw-rw-r-- 1 mysql mysql 0 2007-12-15 15:36 time_zone_transition.MYD -rw-rw-r-- 1 mysql mysql 8686 2007-12-15 15:36 time_zone_transition.frm -rw-rw-r-- 1 mysql mysql 1024 2007-12-15 15:36 time_zone_name.MYI -rw-rw-r-- 1 mysql mysql 0 2007-12-15 15:36 time_zone_name.MYD -rw-rw-r-- 1 mysql mysql 8606 2007-12-15 15:36 time_zone_name.frm -rw-rw-r-- 1 mysql mysql 1024 2007-12-15 15:36 time_zone.MYI -rw-rw-r-- 1 mysql mysql 0 2007-12-15 15:36 time_zone.MYD -rw-rw-r-- 1 mysql mysql 1024 2007-12-15 15:36 time_zone_leap_second.MYI -rw-rw-r-- 1 mysql mysql 0 2007-12-15 15:36 time_zone_leap_second.MYD -rw-rw-r-- 1 mysql mysql 8624 2007-12-15 15:36 time_zone_leap_second.frm -rw-rw-r-- 1 mysql mysql 8636 2007-12-15 15:36 time_zone.frm -rw-rw-r-- 1 mysql mysql 1024 2007-12-15 15:36 tables_priv.MYI -rw-rw-r-- 1 mysql mysql 0 2007-12-15 15:36 tables_priv.MYD -rw-rw-r-- 1 mysql mysql 8947 2007-12-15 15:36 tables_priv.frm -rw-rw-r-- 1 mysql mysql 1024 2007-12-15 15:36 procs_priv.MYI -rw-rw-r-- 1 mysql mysql 0 2007-12-15 15:36 procs_priv.MYD -rw-rw-r-- 1 mysql mysql 8875 2007-12-15 15:36 procs_priv.frm -rw-rw-r-- 1 mysql mysql 1024 2007-12-15 15:36 proc.MYI -rw-rw-r-- 1 mysql mysql 0 2007-12-15 15:36 proc.MYD -rw-rw-r-- 1 mysql mysql 9691 2007-12-15 15:36 proc.frm -rw-rw-r-- 1 mysql mysql 1024 2007-12-15 15:36 host.MYI -rw-rw-r-- 1 mysql mysql 0 2007-12-15 15:36 host.MYD -rw-rw-r-- 1 mysql mysql 9416 2007-12-15 15:36 host.frm -rw-rw-r-- 1
Re: Mysqld fails to start
mysql.user is a table name, it is in the form of database_name.table_name. Mysql has a system database conveniently called mysql :) 090127 18:17:18 [ERROR] Column count of mysql.db is wrong. Expected 22, found 20. Created with MySQL 50045, now running 50130. Please use mysql_upgrade to fix this error. I don't know how you got to where you are now, but it seems like your system database is from MySQL 5.0.45, while you seem to be running 5.1.30. couple of options: 1) try mysql_upgrade again, using root and it's password this time 2) remove the mysql dir inside /var/lib/mysql and then use mysql_install_db to recreate them properly 3) just remove mysql completely and reinstall from scratch Normally I would recommend 2, but in your case I would probably recommend 3 since you just need mysql to run amarok2 (i would recommend songbird anyway: http://www.getsongbird.com/ ;) ) and are not planning on doing anything serious with mysql. Depending on the distro you are using, it can be as simple as yum remove mysql and yum install mysql (removing /var/lib/mysql in between). Your choice though :) good luck! Walter can you try running mysql_upgrade OlinData: Professional services for MySQL Support * Consulting * Administration http://www.olindata.com On Wed, Jan 28, 2009 at 3:21 AM, JD jd1...@gmail.com wrote: OK, I located a weblog on how to change the password and it worked. I then stopped and started the serever, and this is what it belched out in the mysqld.log: 090127 18:17:16 [Note] /usr/libexec/mysqld: Normal shutdown 090127 18:17:16 InnoDB: Starting shutdown... 090127 18:17:17 InnoDB: Shutdown completed; log sequence number 0 44044 090127 18:17:17 [Note] /usr/libexec/mysqld: Shutdown complete 090127 18:17:17 mysqld_safe mysqld from pid file /var/run/mysqld/mysqld.pid ended 090127 18:17:18 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql /usr/libexec/mysqld: Table 'mysql.plugin' doesn't exist 090127 18:17:18 [ERROR] Can't open the mysql.plugin table. Please run mysql_upgrade to create it. 090127 18:17:18 InnoDB: Started; log sequence number 0 44044 090127 18:17:18 [ERROR] Can't open and lock privilege tables: Table 'mysql.servers' doesn't exist 090127 18:17:18 [ERROR] Column count of mysql.db is wrong. Expected 22, found 20. Created with MySQL 50045, now running 50130. Please use mysql_upgrade to fix this error. 090127 18:17:18 [ERROR] mysql.user has no `Event_priv` column at position 29 090127 18:17:18 [ERROR] Cannot open mysql.event 090127 18:17:18 [ERROR] Event Scheduler: An error occurred when initializing system tables. Disabling the Event Scheduler. 090127 18:17:18 [Note] /usr/libexec/mysqld: ready for connections. Version: '5.1.30' socket: '/var/lib/mysql/mysql.sock' port: 3306 MySQL Community Server (GPL) by Remi So, how do I fix those errors about 'mysql.plugin' and mysql.db and mysql.user For that matter why does it even have a mysql.user ??? Should it not be mysql.root? Walter Heck wrote: We're slowly getting there ;) that is the root account for the mysql server, not the linux root account :) when you installed mysql, you chose a root password. If you didn't, look up how to reset your mysql root account's password. Plenty of info on the web :) good luck! Walter OlinData: Professional services for MySQL Support * Consulting * Administration http://www.olindata.com On Wed, Jan 28, 2009 at 1:47 AM, JD jd1...@gmail.com wrote: I did the chmod. Then # ls -latrR /var/lib/mysql /var/lib/mysql: total 20548K drwxrwxr-x 2 mysql mysql 4096 2007-12-15 15:36 test/ -rw-rw-r-- 1 mysql mysql 5242880 2007-12-15 15:36 ib_logfile1 drwxrwxr-x 2 mysql mysql 4096 2007-12-15 16:10 ampache/ drwxrwxr-x 2 mysql mysql 4096 2009-01-21 14:12 mysql/ drwxr-xr-x 53 root root 4096 2009-01-27 14:14 ../ srwxrwxrwx 1 mysql mysql0 2009-01-27 16:35 mysql.sock= -rw-rw-r-- 1 mysql mysql 5242880 2009-01-27 16:35 ib_logfile0 -rw-rw-r-- 1 mysql mysql 10485760 2009-01-27 16:35 ibdata1 drwxrwxr-x 5 mysql mysql 4096 2009-01-27 16:35 ./ /var/lib/mysql/test: total 12K drwxrwxr-x 2 mysql mysql 4096 2007-12-15 15:36 ./ drwxrwxr-x 5 mysql mysql 4096 2009-01-27 16:35 ../ /var/lib/mysql/ampache: total 16K -rw-rw-r-- 1 mysql mysql 65 2007-12-15 16:10 db.opt drwxrwxr-x 2 mysql mysql 4096 2007-12-15 16:10 ./ drwxrwxr-x 5 mysql mysql 4096 2009-01-27 16:35 ../ /var/lib/mysql/mysql: total 788K -rw-rw-r-- 1 mysql mysql 10330 2007-12-15 15:36 user.frm -rw-rw-r-- 1 mysql mysql 1024 2007-12-15 15:36 time_zone_transition_type.MYI -rw-rw-r-- 1 mysql mysql 0 2007-12-15 15:36 time_zone_transition_type.MYD -rw-rw-r-- 1 mysql mysql 8748 2007-12-15 15:36 time_zone_transition_type.frm -rw-rw-r-- 1 mysql mysql 1024 2007-12-15 15:36 time_zone_transition.MYI -rw-rw-r-- 1 mysql mysql 0 2007-12-15 15:36 time_zone_transition.MYD -rw-rw-r-- 1 mysql mysql 8686 2007-12-15 15:36
Re: Mysqld fails to start
Problem with yum remove mysql is that it will also remove all it's dependents, whereas yum install mysql will not restore the dependents. Also, you are probably right re: 5.0.x and 5.1.x At anywho, I ran: }# mysql_upgrade --user=root --password='theNewPassword' Looking for 'mysql' as: mysql Looking for 'mysqlcheck' as: mysqlcheck Running 'mysqlcheck'... mysql.columns_priv OK mysql.db OK mysql.func OK mysql.help_category error: Table upgrade required. Please do REPAIR TABLE `help_category` to fix it! mysql.help_keyword error: Table upgrade required. Please do REPAIR TABLE `help_keyword` to fix it! mysql.help_relationOK mysql.help_topic error: Table upgrade required. Please do REPAIR TABLE `help_topic` to fix it! mysql.host OK mysql.proc error: Table upgrade required. Please do REPAIR TABLE `proc` to fix it! mysql.procs_priv OK mysql.tables_priv OK mysql.time_zoneOK mysql.time_zone_leap_secondOK mysql.time_zone_name error: Table upgrade required. Please do REPAIR TABLE `time_zone_name` to fix it! mysql.time_zone_transition OK mysql.time_zone_transition_typeOK mysql.user OK Repairing tables mysql.help_categoryOK mysql.help_keyword OK mysql.help_topic OK mysql.proc OK mysql.time_zone_name OK Running 'mysql_fix_privilege_tables'... OK So, you want me to 1. Stop the server 2. Remove /var/lib/mysql/mysql right? 3. Restart the server Correct? Walter Heck wrote: mysql.user is a table name, it is in the form of database_name.table_name. Mysql has a system database conveniently called mysql :) 090127 18:17:18 [ERROR] Column count of mysql.db is wrong. Expected 22, found 20. Created with MySQL 50045, now running 50130. Please use mysql_upgrade to fix this error. I don't know how you got to where you are now, but it seems like your system database is from MySQL 5.0.45, while you seem to be running 5.1.30. couple of options: 1) try mysql_upgrade again, using root and it's password this time 2) remove the mysql dir inside /var/lib/mysql and then use mysql_install_db to recreate them properly 3) just remove mysql completely and reinstall from scratch Normally I would recommend 2, but in your case I would probably recommend 3 since you just need mysql to run amarok2 (i would recommend songbird anyway: http://www.getsongbird.com/ ;) ) and are not planning on doing anything serious with mysql. Depending on the distro you are using, it can be as simple as yum remove mysql and yum install mysql (removing /var/lib/mysql in between). Your choice though :) good luck! Walter can you try running mysql_upgrade OlinData: Professional services for MySQL Support * Consulting * Administration http://www.olindata.com On Wed, Jan 28, 2009 at 3:21 AM, JD jd1...@gmail.com wrote: OK, I located a weblog on how to change the password and it worked. I then stopped and started the serever, and this is what it belched out in the mysqld.log: 090127 18:17:16 [Note] /usr/libexec/mysqld: Normal shutdown 090127 18:17:16 InnoDB: Starting shutdown... 090127 18:17:17 InnoDB: Shutdown completed; log sequence number 0 44044 090127 18:17:17 [Note] /usr/libexec/mysqld: Shutdown complete 090127 18:17:17 mysqld_safe mysqld from pid file /var/run/mysqld/mysqld.pid ended 090127 18:17:18 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql /usr/libexec/mysqld: Table 'mysql.plugin' doesn't exist 090127 18:17:18 [ERROR] Can't open the mysql.plugin table. Please run mysql_upgrade to create it. 090127 18:17:18 InnoDB: Started; log sequence number 0 44044 090127 18:17:18 [ERROR] Can't open and lock privilege tables: Table 'mysql.servers' doesn't exist 090127 18:17:18 [ERROR] Column count of mysql.db is wrong. Expected 22, found 20. Created with MySQL 50045, now running 50130. Please use mysql_upgrade to fix this error. 090127 18:17:18 [ERROR] mysql.user has no `Event_priv` column at position 29 090127 18:17:18 [ERROR] Cannot open mysql.event 090127 18:17:18 [ERROR] Event Scheduler: An error occurred when initializing system tables. Disabling the Event Scheduler. 090127 18:17:18 [Note] /usr/libexec/mysqld: ready for connections. Version: '5.1.30' socket: '/var/lib/mysql/mysql.sock' port: 3306 MySQL Community Server (GPL) by Remi So, how do I fix those errors about 'mysql.plugin' and mysql.db and mysql.user For that matter why does it even have a mysql.user ??? Should it not be mysql.root? Walter Heck
