Re: Crash after shutdown/restart
On Wednesday 22 January 2014 22:56, you wrote: Hi Jørn, But I must say I'm not very impressed by the speed. I'm running a test on an application that do a lot of reads and writes queries and the general performance has dropped to 50% of the what I had in 5.5.20. I would say that this sort of performance drop is not typical. Some users have reported a smaller performance loss in single threaded workloads in 5.6. But dropping from an average of 1800 jobs per minute down to 300? I don't think that should be expected. A few weeks ago I stopped the test and restored the initial database starting the test over again. Now the performance was back to 1700 jobs per minute, but it slowly went down as the test ran. Yesterday it was down to 300 per minutes and still (but very slowly) dropped. Yesterday I did the following: * stopped the test * dumped all databases * stopped the mysql server 5.6 * Downloaded 5.5.33-log source and installed it * Removed all inodb* and ib_log* files * Removed all databases * Started and initialized mysql * Restored all databases * Started the test where I left it. After a few hours I could see that the performance was back to normal - 1800 - 2000 jobs per minute. There is no sign of drop in performace so far. Please explain. -- 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: Crash after shutdown/restart
Hi Jørn, I would say that this sort of performance drop is not typical. Some users have reported a smaller performance loss in single threaded workloads in 5.6. But dropping from an average of 1800 jobs per minute down to 300? I don't think that should be expected. I would agree with you here. A few weeks ago I stopped the test and restored the initial database starting the test over again. Now the performance was back to 1700 jobs per minute, but it slowly went down as the test ran. Yesterday it was down to 300 per minutes and still (but very slowly) dropped. Yesterday I did the following: * stopped the test * dumped all databases * stopped the mysql server 5.6 * Downloaded 5.5.33-log source and installed it * Removed all inodb* and ib_log* files * Removed all databases * Started and initialized mysql * Restored all databases * Started the test where I left it. After a few hours I could see that the performance was back to normal - 1800 - 2000 jobs per minute. There is no sign of drop in performace so far. Please explain. I want to suspect that there might be a specific query regression (where 5.6 has introduced a new feature, and you fall in an edge case where it is being optimized incorrectly). The way to deduce this is to run EXPLAIN for key queries in MySQL 5.6 and 5.5, and compare for differences: https://dev.mysql.com/doc/refman/5.6/en/explain.html When you have one, there are a lot of people on the list that would be happy to pair this down to a test case, and file a bug. There is also a switch to disable specific optimizations, so you may have an easy work around that would allow you to restore back on 5.6: https://dev.mysql.com/doc/refman/5.6/en/switchable-optimizations.html - Morgan -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql
Re: Crash after shutdown/restart
On Tuesday 14 January 2014 21:51, Jesper Wisborg Krogh wrote: Hi Jørn, On 15/01/2014 04:36, Jørn Dahl-Stamnes wrote: 140114 18:20:08 InnoDB: Error: data file /data/mysql/data/ibdata3 uses page size 1024, 140114 18:20:08 InnoDB: but the only supported page size in this release is=16384 140114 18:20:08 InnoDB: Could not open or create data files. That error is typical for bug http://bugs.mysql.com/bug.php?id=64160 which was present in 5.5.20 and 5.5.21 (see also http://dev.mysql.com/doc/relnotes/mysql/5.5/en/news-5-5-22.html). So try to upgrade to 5.5.22 or later (I'll recommend 5.5.35) and see if that fixes the issue. Thanks a lot :) I installed 5.6.15 from source and things seems to work OK after a restore. But I must say I'm not very impressed by the speed. I'm running a test on an application that do a lot of reads and writes queries and the general performance has dropped to 50% of the what I had in 5.5.20. I have tried misc combination of innodb_xxx settings but without much luck. 5.6.15 is just slow compared 5.5.20. A short description of the application being tested: The application read a lot of data from files with misc formats. The files are read, parsed (based on the format in each file) and then data is written to the database (raw data). Based on the content of each file, computation jobs are created in a queue (implemented as a table in the database). And then a different process will start doing calculation on the raw and create new data which is written to other tables. After eacn calculation job is done, a record is added in the queue log table. All tables involved are innodb. It's the queue log table that I use to find out how many jobs the system is able to process each minute. A full test takes 2 weeks creating over 15 million jobs. Before each test a initial database is restored and then a set of files are feed to the application. With 5.5.20 the application was able to process an average of 1800 jobs per minute (with peeks up to 2000/min). With 5.6.15 it's around 700-800 jobs per minute and never over 1000/min. Except for the database version everything are the same - the same initial database, the same datafiles and the same order of processing (eventually the result after a full test will be the same). The setup show below gave me 677 jobs per minute in average. I later changed innodb_flush_log_at_trx_commit to 2. Thag gave me 753 jobs per minute. Setting it to 1 gave me 695 jobs per minute. Still long way to go to reach the 1800 jobs per minute. So my question is: What's wrong? Is 5.6.15 slower or? The test machine: - Fedora Core 16 (no X-windows) 8 core AMD (FX-8120) at 3100 Mhz. 32 Gb memory 120 Gb SSD disk for the database (mounted with ext4 and defaults) (*) 1 Tb disk for datafiles and bin log files. *: I'm going to change this later to noatime,data=writeback,barrier=0,nobh and test again. Initial my.cnf: y.cnf: [mysqld] port= 3306 socket = /tmp/mysql.sock explicit_defaults_for_timestamp = TRUE skip-external-locking key_buffer_size = 384M max_allowed_packet = 32M table_open_cache = 512 sort_buffer_size = 2M read_buffer_size = 2M read_rnd_buffer_size = 8M myisam_sort_buffer_size = 64M thread_cache_size = 8 query_cache_size = 32M thread_concurrency = 14 max_connections = 50 log-bin=/var/mysql/mysql-bin server-id = 1 binlog_format=mixed # Open files. innodb_open_files = 2048 open_files_limit= 8096 innodb_data_home_dir= /data/mysql/data innodb_data_file_path = ibdata1:20G;ibdata2:20G;ibdata3:20G;ibdata4:20G:autoextend innodb_file_per_table = 0 innodb_log_group_home_dir = /data/mysql/data innodb_buffer_pool_size = 25G innodb_log_file_size= 300M innodb_log_files_in_group = 2 innodb_log_buffer_size = 8M innodb_flush_log_at_trx_commit = 0 innodb_support_xa = 0 innodb_flush_method = O_DIRECT innodb_lock_wait_timeout= 50 innodb_thread_concurrency = 14 innodb_fast_shutdown= 0 -- 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: Crash after shutdown/restart
Hi Jørn, But I must say I'm not very impressed by the speed. I'm running a test on an application that do a lot of reads and writes queries and the general performance has dropped to 50% of the what I had in 5.5.20. I would say that this sort of performance drop is not typical. Some users have reported a smaller performance loss in single threaded workloads in 5.6. It's possible to redeem some of this performance loss by tuning Performance Schema, with the caveat that you will lose some visibility into diagnostics: http://dev.mysql.com/doc/refman/5.6/en/performance-schema-startup-configuration.html It's not clear from your description if the test is run in parallel-threads, but this is something you may want to research. May I also suggest commenting out/assuming some defaults for some of your config settings. 5.6 has much better defaults, and it is always better to 'maintain less customization' yourself: key_buffer_size = 384M table_open_cache = 512 sort_buffer_size = 2M read_buffer_size = 2M read_rnd_buffer_size = 8M myisam_sort_buffer_size = 64M thread_cache_size = 8 query_cache_size = 32M thread_concurrency = 14 I also don't typically recommend these settings, but there will be some cases when they are warranted: innodb_thread_concurrency = 14 innodb_support_xa = 0 innodb_fast_shutdown= 0 - Morgan -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql
Crash after shutdown/restart
Hello, Got a test server with version 5.5.20. I wanted to unmount/mount the disk where the innodb files was located, so I did a shutdown followed by unmount, then a mount before I tried to start the MySQL server. But it did not work as shown in the log below. I wanted to unmount the disk since I wanted to change the 'defaults' in /etc/fstab with 'defaults,noatime,data=writeback,barrier=0,nobh,errors=remount-ro'. What could cause this? Guess I have to recreate the files and start all over again? # Older message from the error file showing the version. Version: '5.5.20-log' socket: '/tmp/mysql.sock' port: 3306 Source distribution # Shutdown messages 140114 18:14:53 [Note] Event Scheduler: Purging the queue. 0 events 140114 18:14:53 InnoDB: Starting shutdown... 140114 18:17:58 InnoDB: Shutdown completed; log sequence number 2230197670580 140114 18:17:58 [Note] /usr/local/mysql/bin/mysqld: Shutdown complete # Restart after umount/mount. 140114 18:17:59 mysqld_safe mysqld from pid file /usr/local/mysql/data/hostname.pid ended 140114 18:20:05 mysqld_safe Starting mysqld daemon with databases from /usr/local/mysql/data 140114 18:20:05 InnoDB: The InnoDB memory heap is disabled 140114 18:20:05 InnoDB: Mutexes and rw_locks use GCC atomic builtins 140114 18:20:05 InnoDB: Compressed tables use zlib 1.2.5 140114 18:20:05 InnoDB: Initializing buffer pool, size = 25.0G 140114 18:20:08 InnoDB: Completed initialization of buffer pool 140114 18:20:08 InnoDB: Error: data file /data/mysql/data/ibdata3 uses page size 1024, 140114 18:20:08 InnoDB: but the only supported page size in this release is=16384 140114 18:20:08 InnoDB: Could not open or create data files. 140114 18:20:08 InnoDB: If you tried to add new data files, and it failed here, 140114 18:20:08 InnoDB: you should now edit innodb_data_file_path in my.cnf back 140114 18:20:08 InnoDB: to what it was, and remove the new ibdata files InnoDB created 140114 18:20:08 InnoDB: in this failed attempt. InnoDB only wrote those files full of 140114 18:20:08 InnoDB: zeros, but did not yet use them in any way. But be careful: do not 140114 18:20:08 InnoDB: remove old data files which contain your precious data! 140114 18:20:08 [ERROR] Plugin 'InnoDB' init function returned error. 140114 18:20:08 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed. 140114 18:20:08 [ERROR] Unknown/unsupported storage engine: InnoDB 140114 18:20:08 [ERROR] Aborting -- 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: Crash after shutdown/restart
Hi Jørn, On 15/01/2014 04:36, Jørn Dahl-Stamnes wrote: 140114 18:20:08 InnoDB: Error: data file /data/mysql/data/ibdata3 uses page size 1024, 140114 18:20:08 InnoDB: but the only supported page size in this release is=16384 140114 18:20:08 InnoDB: Could not open or create data files. That error is typical for bug http://bugs.mysql.com/bug.php?id=64160 which was present in 5.5.20 and 5.5.21 (see also http://dev.mysql.com/doc/relnotes/mysql/5.5/en/news-5-5-22.html). So try to upgrade to 5.5.22 or later (I'll recommend 5.5.35) and see if that fixes the issue. Best regards, Jesper Krogh MySQL Support -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql
is changing my.cnf without restart safe?
Hello MySQL Community, Last Friday I changed /etc/mysql/my.cnf file (at server) accidentally. I set the variable innodb_data_file_path to ibdata1:100M Then I realized that I changed the server copy. Then to get the original value I issued the query : SHOW VARIABLES LIKE 'innodb_data_file_path' I get the following: innodb_data_file_path = ibdata1:4000M;ibdata2:4000M;ibdata3:4000M;ibdata4:4000M:autoextend I wrote this value to my.cnf again. MySQL isn't restarted in these whole process. Whole thing took 5-10 minutes. Here is my questions: if i change something in my.cnf, they are not activated until i restart mysql right? is above scenario safe? Do you think i messed up something? Thank you for your 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: is changing my.cnf without restart safe?
No, this is in and of itself safe. I didn't realise you could change the InnoDB datafiles on the fly, though - thanks for that hint :-) MySQL will never write the config file itself, so you're not at risk of conflict there. You are at risk of putting something in the configfile which messes up your MySQL server at the next restart, however; but that's pretty much the case for any other daemon, too. On Mon, Nov 8, 2010 at 11:06 AM, AHMET ARSLAN aarsl...@anadolu.edu.trwrote: Hello MySQL Community, Last Friday I changed /etc/mysql/my.cnf file (at server) accidentally. I set the variable innodb_data_file_path to ibdata1:100M Then I realized that I changed the server copy. Then to get the original value I issued the query : SHOW VARIABLES LIKE 'innodb_data_file_path' I get the following: innodb_data_file_path = ibdata1:4000M;ibdata2:4000M;ibdata3:4000M;ibdata4:4000M:autoextend I wrote this value to my.cnf again. MySQL isn't restarted in these whole process. Whole thing took 5-10 minutes. Here is my questions: if i change something in my.cnf, they are not activated until i restart mysql right? is above scenario safe? Do you think i messed up something? Thank you for your help. -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql?unsub=vegiv...@tuxera.be -- 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?
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: Need restart mysql when time changed
This is a correct description of behaviour. Did you have a question ? :-) On Fri, Sep 17, 2010 at 5:52 AM, win.a win@gmail.com wrote: I fond my mysql db os time was not correct so i sync with ntpdate ,when testing my app which depend on the date was not the current os time .After restarting Mysql ,the app goes well. All you best What we are struggling for ? The life or the life ? -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql?unsub=vegiv...@tuxera.be -- Bier met grenadyn Is als mosterd by den wyn Sy die't drinkt, is eene kwezel Hy die't drinkt, is ras een ezel
Need restart mysql when time changed
I fond my mysql db os time was not correct so i sync with ntpdate ,when testing my app which depend on the date was not the current os time .After restarting Mysql ,the app goes well. All you best What we are struggling for ? The life or the life ? -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql?unsub=arch...@jab.org
Re: Always corrupted after restart server
How are you shutting down the server during the restart.. have you checked the logs? Might you be issuing a kill and crashing it? MyISAM doesnot dealwith crashes very elegantly. Also, what is some reason? Might thereason you need to restart be related? - michael dykman On Tue, Aug 24, 2010 at 11:13 PM, sangprabv sangpr...@gmail.com wrote: Hi List, I have a very big size MyISAM table. For some reason I need to restart the server periodically. But After restarting the server, the table always get corrupt, and always need to run myisamchk. Don't know what cause the problem. But it will be very helpful if somebody can give me some tips to avoid this problem. Thanks alot. sangprabv sangpr...@gmail.com http://www.petitiononline.com/froyo/ -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/mysql?unsub=mdyk...@gmail.com -- - michael dykman - mdyk...@gmail.com May the Source be with you. -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql?unsub=arch...@jab.org
Re: Always corrupted after restart server
On 25/08/2010 8:05 a, Michael Dykman wrote: How are you shutting down the server during the restart.. have you checked the logs? Might you be issuing a kill and crashing it? MyISAM doesnot dealwith crashes very elegantly. Also, what is some reason? Might thereason you need to restart be related? - michael dykman On Tue, Aug 24, 2010 at 11:13 PM, sangprabvsangpr...@gmail.com wrote: Hi List, I have a very big size MyISAM table. For some reason I need to restart the server periodically. But After restarting the server, the table always get corrupt, and always need to run myisamchk. Don't know what cause the problem. But it will be very helpful if somebody can give me some tips to avoid this problem. Thanks alot. To unsubscribe:http://lists.mysql.com/mysql?unsub=mdyk...@gmail.com Maybe you need to check *why* you have to keep on restarting the server? Cure the disease, not the symptoms? We have a particular mysql server that has been up the last 8 months with no downtime... -- Jangita | +256 76 91 8383 | Y! MSN: jang...@yahoo.com Skype: jangita | GTalk: jangita.nyag...@gmail.com -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql?unsub=arch...@jab.org
Always corrupted after restart server
Hi List, I have a very big size MyISAM table. For some reason I need to restart the server periodically. But After restarting the server, the table always get corrupt, and always need to run myisamchk. Don't know what cause the problem. But it will be very helpful if somebody can give me some tips to avoid this problem. Thanks alot. sangprabv sangpr...@gmail.com http://www.petitiononline.com/froyo/ -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql?unsub=arch...@jab.org
Disable bin-log without restart
Hello, I have a quite loaded server with bin-log enabled. I'd like to disable binary logging globally not for a single session without restarting mysql. Is it possible? Any input is appreciated. Best Regards, George -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql?unsub=arch...@jab.org
RE: Disable bin-log without restart
No George you will need to restart MySQL. From: ext George Chelidze [wr...@geo.net.ge] Sent: 11 June 2010 12:15 To: mysql@lists.mysql.com Subject: Disable bin-log without restart Hello, I have a quite loaded server with bin-log enabled. I'd like to disable binary logging globally not for a single session without restarting mysql. Is it possible? Any input is appreciated. Best Regards, George -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql?unsub=andrew.2.mo...@nokia.com -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql?unsub=arch...@jab.org
do i have to restart the mysql server when i change some global variables?
hi as the title thanks -- - Lin Chun
Re: do i have to restart the mysql server when i change some global variables?
unless and until if the variable is read-only, you don't need Lin. On Mon, May 31, 2010 at 3:17 PM, Lin Chun franks1...@gmail.com wrote: hi as the title thanks -- - Lin Chun -- Thanks Suresh Kuna MySQL DBA
Re: do i have to restart the mysql server when i change some global variables?
Yes and No. Its depend on the type of variable you have changed. If its Dynamic , MySQL restart not required, else its required. System variables can be set at server startup using options on the command line or in an option file. Most of them can be changed dynamically while the server is running by means of the SEThttp://dev.mysql.com/doc/refman/5.1/en/set-option.htmlstatement, which enables you to modify operation of the server without having to stop and restart it. You can refer to system variable values in expressions. Check the complete list of variable. : http://dev.mysql.com/doc/refman/5.1/en/server-system-variables.html Thanks, On Mon, May 31, 2010 at 3:17 PM, Lin Chun franks1...@gmail.com wrote: hi as the title thanks -- - Lin Chun -- Best Regards, Prabhat Kumar MySQL DBA Datavail-India Mumbai Mobile : 91-9987681929 www.datavail.com My Blog: http://adminlinux.blogspot.com My LinkedIn: http://www.linkedin.com/in/profileprabhat
Change clock/timezone time without restart mysql
Hi, I need to change the computer clock (changing the /etc/zoneinfo) but I would not restart de MySQL service. The NOW() still returning the old time... Thanks, Jonas
Re: Change clock/timezone time without restart mysql
Jonas, your information is somewhat incomplete, but still: Jonas Silveira wrote: Hi, I need to change the computer clock (changing the /etc/zoneinfo) but I would From the file name, I assume it is some Unix platform. not restart de MySQL service. The NOW() still returning the old time... Works as designed: A process inherits time zone information when it starts, from the parent and the then valid environment. This also holds for the MySQL server. That is why time zone information contains the info about when daylight saving time starts / ends: A process starting before the change and still running after that will use the correct time only because it got the information (about the change point) already when it started. HTH, Jörg -- Joerg Bruehe, MySQL Build Team, joerg.bru...@sun.com (+49 30) 417 01 487 Sun Microsystems GmbH, Komturstraße 18a, D-12099 Berlin Geschaeftsfuehrer: Thomas Schroeder, Wolfgang Engels, Wolf Frenkel Vorsitzender des Aufsichtsrates: Martin Haering 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: Replication recovery on restart
Before I simulate a total server failure, master1 is using binary file msyql-bin1 position 2231467 and it's slave master2 is following the correct file at the correct position. This is after initial setup. Once I restart master1, it will then start to use msyql-bin2 position 98 and master 2 is still trying to follow msyql-bin1 position 2231467. And since I have this as dual master setup, if I simulate both boxes restarting in a total catastrophe, the masters both change files and the slaves remain trying to follow on the old information. -Original Message- From: Gavin Towey [mailto:gto...@ffn.com] Sent: Thursday, July 30, 2009 5:08 PM To: Cantwell, Bryan; mysql@lists.mysql.com Subject: RE: Replication recovery on restart Hi Bryan, Please define out of whack. Tell us exactly what you're doing when you restart, and what the replication state is before and after, and where the updates are coming from. Regards, Gavin Towey -Original Message- From: Cantwell, Bryan [mailto:bcantw...@firescope.com] Sent: Thursday, July 30, 2009 11:00 AM To: mysql@lists.mysql.com Subject: Replication recovery on restart I have 2 machines 'master' and 'slave'. I have the mysql 5.0.51a-log databases both replicating wonderfully. They are configured in a dual master scenario so that one can take over for the other in my HA environment I've built. All is working great until... If one or the other box reboots or the mysql restarts, the replication gets out of whack. Especially if I simulate both of them crashing in a worst case scenario, they are then both trying to sync from the wrong Master_log_file and Read_Master_Log_Pos... Since catastrpohe WILL happen eventually (heence the need for HA) how do I direct the newly restarted boxes to the right position in the correct files on restart? Thanks -- 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
RE: Replication recovery on restart
Bryan, How are you restarting mysql? In the case a master crashes, it's definitely common for the slave to miss the fact that the master is using a different binlog. The slave advances to a position past the end of the previous binlog, and stops with and error like tried to read impossible position. In this case you do have to intervene, but that's an easy enough case to write a script to handle. When restarting mysql normally, you shouldn't have this problem: i.e. service mysql restart / /etc/ini.d/mysql restart Regards, Gavin Towey -Original Message- From: Cantwell, Bryan [mailto:bcantw...@firescope.com] Sent: Friday, July 31, 2009 10:08 AM To: mysql@lists.mysql.com Subject: RE: Replication recovery on restart Before I simulate a total server failure, master1 is using binary file msyql-bin1 position 2231467 and it's slave master2 is following the correct file at the correct position. This is after initial setup. Once I restart master1, it will then start to use msyql-bin2 position 98 and master 2 is still trying to follow msyql-bin1 position 2231467. And since I have this as dual master setup, if I simulate both boxes restarting in a total catastrophe, the masters both change files and the slaves remain trying to follow on the old information. -Original Message- From: Gavin Towey [mailto:gto...@ffn.com] Sent: Thursday, July 30, 2009 5:08 PM To: Cantwell, Bryan; mysql@lists.mysql.com Subject: RE: Replication recovery on restart Hi Bryan, Please define out of whack. Tell us exactly what you're doing when you restart, and what the replication state is before and after, and where the updates are coming from. Regards, Gavin Towey -Original Message- From: Cantwell, Bryan [mailto:bcantw...@firescope.com] Sent: Thursday, July 30, 2009 11:00 AM To: mysql@lists.mysql.com Subject: Replication recovery on restart I have 2 machines 'master' and 'slave'. I have the mysql 5.0.51a-log databases both replicating wonderfully. They are configured in a dual master scenario so that one can take over for the other in my HA environment I've built. All is working great until... If one or the other box reboots or the mysql restarts, the replication gets out of whack. Especially if I simulate both of them crashing in a worst case scenario, they are then both trying to sync from the wrong Master_log_file and Read_Master_Log_Pos... Since catastrpohe WILL happen eventually (heence the need for HA) how do I direct the newly restarted boxes to the right position in the correct files on restart? Thanks -- 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=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
RE: Replication recovery on restart
Yes I am trying to simulate total failure. In this test case I am using 2 Virtual Machines and I just kill one and then when it comes back I have the challenge described. How can I go about getting the slave back in tune with the newly restarted master? Thanks -Original Message- From: Gavin Towey [mailto:gto...@ffn.com] Sent: Friday, July 31, 2009 1:21 PM To: Cantwell, Bryan; mysql@lists.mysql.com Subject: RE: Replication recovery on restart Bryan, How are you restarting mysql? In the case a master crashes, it's definitely common for the slave to miss the fact that the master is using a different binlog. The slave advances to a position past the end of the previous binlog, and stops with and error like tried to read impossible position. In this case you do have to intervene, but that's an easy enough case to write a script to handle. When restarting mysql normally, you shouldn't have this problem: i.e. service mysql restart / /etc/ini.d/mysql restart Regards, Gavin Towey -Original Message- From: Cantwell, Bryan [mailto:bcantw...@firescope.com] Sent: Friday, July 31, 2009 10:08 AM To: mysql@lists.mysql.com Subject: RE: Replication recovery on restart Before I simulate a total server failure, master1 is using binary file msyql-bin1 position 2231467 and it's slave master2 is following the correct file at the correct position. This is after initial setup. Once I restart master1, it will then start to use msyql-bin2 position 98 and master 2 is still trying to follow msyql-bin1 position 2231467. And since I have this as dual master setup, if I simulate both boxes restarting in a total catastrophe, the masters both change files and the slaves remain trying to follow on the old information. -Original Message- From: Gavin Towey [mailto:gto...@ffn.com] Sent: Thursday, July 30, 2009 5:08 PM To: Cantwell, Bryan; mysql@lists.mysql.com Subject: RE: Replication recovery on restart Hi Bryan, Please define out of whack. Tell us exactly what you're doing when you restart, and what the replication state is before and after, and where the updates are coming from. Regards, Gavin Towey -Original Message- From: Cantwell, Bryan [mailto:bcantw...@firescope.com] Sent: Thursday, July 30, 2009 11:00 AM To: mysql@lists.mysql.com Subject: Replication recovery on restart I have 2 machines 'master' and 'slave'. I have the mysql 5.0.51a-log databases both replicating wonderfully. They are configured in a dual master scenario so that one can take over for the other in my HA environment I've built. All is working great until... If one or the other box reboots or the mysql restarts, the replication gets out of whack. Especially if I simulate both of them crashing in a worst case scenario, they are then both trying to sync from the wrong Master_log_file and Read_Master_Log_Pos... Since catastrpohe WILL happen eventually (heence the need for HA) how do I direct the newly restarted boxes to the right position in the correct files on restart? Thanks -- 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=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
RE: Replication recovery on restart
Bryan, When the slave encounters that error, you can simply set it to replicate from the next binlog file in the sequence starting at position 98. It should be easy to have a script automate this process. Regards, Gavin Towey -Original Message- From: Cantwell, Bryan [mailto:bcantw...@firescope.com] Sent: Friday, July 31, 2009 12:51 PM To: mysql@lists.mysql.com Subject: RE: Replication recovery on restart Yes I am trying to simulate total failure. In this test case I am using 2 Virtual Machines and I just kill one and then when it comes back I have the challenge described. How can I go about getting the slave back in tune with the newly restarted master? Thanks -Original Message- From: Gavin Towey [mailto:gto...@ffn.com] Sent: Friday, July 31, 2009 1:21 PM To: Cantwell, Bryan; mysql@lists.mysql.com Subject: RE: Replication recovery on restart Bryan, How are you restarting mysql? In the case a master crashes, it's definitely common for the slave to miss the fact that the master is using a different binlog. The slave advances to a position past the end of the previous binlog, and stops with and error like tried to read impossible position. In this case you do have to intervene, but that's an easy enough case to write a script to handle. When restarting mysql normally, you shouldn't have this problem: i.e. service mysql restart / /etc/ini.d/mysql restart Regards, Gavin Towey -Original Message- From: Cantwell, Bryan [mailto:bcantw...@firescope.com] Sent: Friday, July 31, 2009 10:08 AM To: mysql@lists.mysql.com Subject: RE: Replication recovery on restart Before I simulate a total server failure, master1 is using binary file msyql-bin1 position 2231467 and it's slave master2 is following the correct file at the correct position. This is after initial setup. Once I restart master1, it will then start to use msyql-bin2 position 98 and master 2 is still trying to follow msyql-bin1 position 2231467. And since I have this as dual master setup, if I simulate both boxes restarting in a total catastrophe, the masters both change files and the slaves remain trying to follow on the old information. -Original Message- From: Gavin Towey [mailto:gto...@ffn.com] Sent: Thursday, July 30, 2009 5:08 PM To: Cantwell, Bryan; mysql@lists.mysql.com Subject: RE: Replication recovery on restart Hi Bryan, Please define out of whack. Tell us exactly what you're doing when you restart, and what the replication state is before and after, and where the updates are coming from. Regards, Gavin Towey -Original Message- From: Cantwell, Bryan [mailto:bcantw...@firescope.com] Sent: Thursday, July 30, 2009 11:00 AM To: mysql@lists.mysql.com Subject: Replication recovery on restart I have 2 machines 'master' and 'slave'. I have the mysql 5.0.51a-log databases both replicating wonderfully. They are configured in a dual master scenario so that one can take over for the other in my HA environment I've built. All is working great until... If one or the other box reboots or the mysql restarts, the replication gets out of whack. Especially if I simulate both of them crashing in a worst case scenario, they are then both trying to sync from the wrong Master_log_file and Read_Master_Log_Pos... Since catastrpohe WILL happen eventually (heence the need for HA) how do I direct the newly restarted boxes to the right position in the correct files on restart? Thanks -- 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=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=gto...@ffn.com The information contained in this transmission may contain privileged and confidential information. It is intended only for the use
Replication recovery on restart
I have 2 machines 'master' and 'slave'. I have the mysql 5.0.51a-log databases both replicating wonderfully. They are configured in a dual master scenario so that one can take over for the other in my HA environment I've built. All is working great until... If one or the other box reboots or the mysql restarts, the replication gets out of whack. Especially if I simulate both of them crashing in a worst case scenario, they are then both trying to sync from the wrong Master_log_file and Read_Master_Log_Pos... Since catastrpohe WILL happen eventually (heence the need for HA) how do I direct the newly restarted boxes to the right position in the correct files on restart? Thanks -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql?unsub=arch...@jab.org
RE: Replication recovery on restart
Hi Bryan, Please define out of whack. Tell us exactly what you're doing when you restart, and what the replication state is before and after, and where the updates are coming from. Regards, Gavin Towey -Original Message- From: Cantwell, Bryan [mailto:bcantw...@firescope.com] Sent: Thursday, July 30, 2009 11:00 AM To: mysql@lists.mysql.com Subject: Replication recovery on restart I have 2 machines 'master' and 'slave'. I have the mysql 5.0.51a-log databases both replicating wonderfully. They are configured in a dual master scenario so that one can take over for the other in my HA environment I've built. All is working great until... If one or the other box reboots or the mysql restarts, the replication gets out of whack. Especially if I simulate both of them crashing in a worst case scenario, they are then both trying to sync from the wrong Master_log_file and Read_Master_Log_Pos... Since catastrpohe WILL happen eventually (heence the need for HA) how do I direct the newly restarted boxes to the right position in the correct files on restart? Thanks -- 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
mk-slave-restart
Hi Baron, I want to use mk-slave-restart (maatkit tool) to restart the slave if 1048 errors comes up. [r...@linux18 ~]# mk-slave-restart --always --daemonize --defaults-file=/etc/my1.cnf --error-numbers=1048 --host=localhost --port 3307 --user=root [r...@linux18 ~]# ps aux | grep mk-slave-restart root 22006 0.0 0.0 4004 700 pts/2S+ 14:51 0:00 grep mk-slave-restart Can you tell me whats wrong in the above syntax. It's not working. Please tell me the complete syntax. -- Krishna Chandra Prajapati
Re: mk-slave-restart
Hi, On Mon, Jan 12, 2009 at 4:28 AM, Krishna Chandra Prajapati prajapat...@gmail.com wrote: Hi Baron, I want to use mk-slave-restart (maatkit tool) to restart the slave if 1048 errors comes up. [r...@linux18 ~]# mk-slave-restart --always --daemonize --defaults-file=/etc/my1.cnf --error-numbers=1048 --host=localhost --port 3307 --user=root [r...@linux18 ~]# ps aux | grep mk-slave-restart root 22006 0.0 0.0 4004 700 pts/2S+ 14:51 0:00 grep mk-slave-restart Can you tell me whats wrong in the above syntax. It's not working. Please tell me the complete syntax. It's great that you want to use it, but just as a note -- if this becomes a long thread, please move it to the Maatkit mailing list. I would remove the --daemonize argument first so you can see standard output and standard error easily. Baron -- 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: Unable to restart after crash
Show you results of ps aux | grep mysql | grep -v grep On Jan 14, 2008 11:41 PM, [EMAIL PROTECTED] wrote: Or maybe the pid is still existing? -Original Message- From: Ross Crawford [mailto:[EMAIL PROTECTED] Sent: Saturday, January 12, 2008 5:13 PM To: mysql@lists.mysql.com Subject: Unable to restart after crash Hi, My mysql server crashed last night, and when it rebooted, was unable to restart. Here is the error log: Jan 13 00:12:54 localhost mysqld_safe[1324]: started Jan 13 00:12:55 localhost mysqld[1327]: 080113 0:12:55 InnoDB: Database was not shut down normally! Jan 13 00:12:55 localhost mysqld[1327]: InnoDB: Starting crash recovery. Jan 13 00:12:55 localhost mysqld[1327]: InnoDB: Reading tablespace information from the .ibd files... Jan 13 00:12:55 localhost mysqld[1327]: InnoDB: Restoring possible half-written data pages from the doublewrite Jan 13 00:12:55 localhost mysqld[1327]: InnoDB: buffer... Jan 13 00:12:56 localhost mysqld[1327]: 080113 0:12:56 InnoDB: Starting log scan based on checkpoint at Jan 13 00:12:56 localhost mysqld[1327]: InnoDB: log sequence number 0 111349. Jan 13 00:12:56 localhost mysqld[1327]: InnoDB: Doing recovery: scanned up to log sequence number 0 111349 Jan 13 00:12:56 localhost mysqld[1327]: InnoDB: Last MySQL binlog file position 0 3587, file name /var/log/mysql/mysql-bin.000489 Jan 13 00:12:56 localhost mysqld[1327]: 080113 0:12:56 InnoDB: Started; log sequence number 0 111349 Jan 13 00:12:56 localhost mysqld[1327]: 080113 0:12:56 [Note] Recovering after a crash using /var/log/mysql/mysql-bin Jan 13 00:12:56 localhost mysqld[1327]: 080113 0:12:56 [Note] Starting crash recovery... Jan 13 00:12:56 localhost mysqld[1327]: 080113 0:12:56 [Note] Crash recovery finished. Jan 13 00:12:57 localhost mysqld[1327]: 080113 0:12:57 [ERROR] Can't start server: Bind on TCP/IP port: Cannot assign requested address Jan 13 00:12:57 localhost mysqld[1327]: 080113 0:12:57 [ERROR] Do you already have another mysqld server running on port: 3306 ? Jan 13 00:12:57 localhost mysqld[1327]: 080113 0:12:57 [ERROR] Aborting Jan 13 00:12:57 localhost mysqld[1327]: Jan 13 00:12:57 localhost mysqld[1327]: 080113 0:12:57 InnoDB: Starting shutdown... Jan 13 00:12:59 localhost mysqld[1327]: 080113 0:12:59 InnoDB: Shutdown completed; log sequence number 0 111349 Jan 13 00:12:59 localhost mysqld[1327]: 080113 0:12:59 [Note] /usr/sbin/mysqld: Shutdown complete Jan 13 00:12:59 localhost mysqld[1327]: Jan 13 00:12:59 localhost mysqld_safe[1374]: ended And since then I am unable to start it. mysqld_safe aborts with: Starting mysqld daemon with databases from /var/lib/mysql mysqld_safe[3150]: started STOPPING server from pid file /var/run/mysqld/mysqld.pid mysqld_safe[3164]: ended And error file: Jan 13 06:03:06 localhost mysqld_safe[1318]: started Jan 13 06:03:08 localhost mysqld[1321]: 080113 6:03:08 InnoDB: Started; log sequence number 0 111349 Jan 13 06:03:08 localhost mysqld[1321]: 080113 6:03:08 [ERROR] Can't start server: Bind on TCP/IP port: Cannot assign requested address Jan 13 06:03:08 localhost mysqld[1321]: 080113 6:03:08 [ERROR] Do you already have another mysqld server running on port: 3306 ? Jan 13 06:03:08 localhost mysqld[1321]: 080113 6:03:08 [ERROR] Aborting Jan 13 06:03:08 localhost mysqld[1321]: Jan 13 06:03:08 localhost mysqld[1321]: 080113 6:03:08 InnoDB: Starting shutdown... Jan 13 06:03:11 localhost mysqld[1321]: 080113 6:03:11 InnoDB: Shutdown completed; log sequence number 0 111349 Jan 13 06:03:11 localhost mysqld[1321]: 080113 6:03:11 [Note] /usr/sbin/mysqld: Shutdown complete Jan 13 06:03:11 localhost mysqld[1321]: Jan 13 06:03:11 localhost mysqld_safe[1368]: ended Nothing is running on port 3306, telnet gets connection refused. No mysql processes are running. Does anyone have any ideas what might be wrong? Thanks ROSCO -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED] This message and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom it is addressed. It may contain sensitive and private proprietary or legally privileged information. No confidentiality or privilege is waived or lost by any mistransmission. If you are not the intended recipient, please immediately delete it and all copies of it from your system, destroy any hard copies of it and notify the sender. You must not, directly or indirectly, use, disclose, distribute, print, or copy any part of this message if you are not the intended recipient. FXDirectDealer, LLC reserves the right to monitor all e-mail communications through its networks. Any views expressed in this message are those of the individual sender, except where
RE: Unable to restart after crash
Or maybe the pid is still existing? -Original Message- From: Ross Crawford [mailto:[EMAIL PROTECTED] Sent: Saturday, January 12, 2008 5:13 PM To: mysql@lists.mysql.com Subject: Unable to restart after crash Hi, My mysql server crashed last night, and when it rebooted, was unable to restart. Here is the error log: Jan 13 00:12:54 localhost mysqld_safe[1324]: started Jan 13 00:12:55 localhost mysqld[1327]: 080113 0:12:55 InnoDB: Database was not shut down normally! Jan 13 00:12:55 localhost mysqld[1327]: InnoDB: Starting crash recovery. Jan 13 00:12:55 localhost mysqld[1327]: InnoDB: Reading tablespace information from the .ibd files... Jan 13 00:12:55 localhost mysqld[1327]: InnoDB: Restoring possible half-written data pages from the doublewrite Jan 13 00:12:55 localhost mysqld[1327]: InnoDB: buffer... Jan 13 00:12:56 localhost mysqld[1327]: 080113 0:12:56 InnoDB: Starting log scan based on checkpoint at Jan 13 00:12:56 localhost mysqld[1327]: InnoDB: log sequence number 0 111349. Jan 13 00:12:56 localhost mysqld[1327]: InnoDB: Doing recovery: scanned up to log sequence number 0 111349 Jan 13 00:12:56 localhost mysqld[1327]: InnoDB: Last MySQL binlog file position 0 3587, file name /var/log/mysql/mysql-bin.000489 Jan 13 00:12:56 localhost mysqld[1327]: 080113 0:12:56 InnoDB: Started; log sequence number 0 111349 Jan 13 00:12:56 localhost mysqld[1327]: 080113 0:12:56 [Note] Recovering after a crash using /var/log/mysql/mysql-bin Jan 13 00:12:56 localhost mysqld[1327]: 080113 0:12:56 [Note] Starting crash recovery... Jan 13 00:12:56 localhost mysqld[1327]: 080113 0:12:56 [Note] Crash recovery finished. Jan 13 00:12:57 localhost mysqld[1327]: 080113 0:12:57 [ERROR] Can't start server: Bind on TCP/IP port: Cannot assign requested address Jan 13 00:12:57 localhost mysqld[1327]: 080113 0:12:57 [ERROR] Do you already have another mysqld server running on port: 3306 ? Jan 13 00:12:57 localhost mysqld[1327]: 080113 0:12:57 [ERROR] Aborting Jan 13 00:12:57 localhost mysqld[1327]: Jan 13 00:12:57 localhost mysqld[1327]: 080113 0:12:57 InnoDB: Starting shutdown... Jan 13 00:12:59 localhost mysqld[1327]: 080113 0:12:59 InnoDB: Shutdown completed; log sequence number 0 111349 Jan 13 00:12:59 localhost mysqld[1327]: 080113 0:12:59 [Note] /usr/sbin/mysqld: Shutdown complete Jan 13 00:12:59 localhost mysqld[1327]: Jan 13 00:12:59 localhost mysqld_safe[1374]: ended And since then I am unable to start it. mysqld_safe aborts with: Starting mysqld daemon with databases from /var/lib/mysql mysqld_safe[3150]: started STOPPING server from pid file /var/run/mysqld/mysqld.pid mysqld_safe[3164]: ended And error file: Jan 13 06:03:06 localhost mysqld_safe[1318]: started Jan 13 06:03:08 localhost mysqld[1321]: 080113 6:03:08 InnoDB: Started; log sequence number 0 111349 Jan 13 06:03:08 localhost mysqld[1321]: 080113 6:03:08 [ERROR] Can't start server: Bind on TCP/IP port: Cannot assign requested address Jan 13 06:03:08 localhost mysqld[1321]: 080113 6:03:08 [ERROR] Do you already have another mysqld server running on port: 3306 ? Jan 13 06:03:08 localhost mysqld[1321]: 080113 6:03:08 [ERROR] Aborting Jan 13 06:03:08 localhost mysqld[1321]: Jan 13 06:03:08 localhost mysqld[1321]: 080113 6:03:08 InnoDB: Starting shutdown... Jan 13 06:03:11 localhost mysqld[1321]: 080113 6:03:11 InnoDB: Shutdown completed; log sequence number 0 111349 Jan 13 06:03:11 localhost mysqld[1321]: 080113 6:03:11 [Note] /usr/sbin/mysqld: Shutdown complete Jan 13 06:03:11 localhost mysqld[1321]: Jan 13 06:03:11 localhost mysqld_safe[1368]: ended Nothing is running on port 3306, telnet gets connection refused. No mysql processes are running. Does anyone have any ideas what might be wrong? Thanks ROSCO -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED] This message and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom it is addressed. It may contain sensitive and private proprietary or legally privileged information. No confidentiality or privilege is waived or lost by any mistransmission. If you are not the intended recipient, please immediately delete it and all copies of it from your system, destroy any hard copies of it and notify the sender. You must not, directly or indirectly, use, disclose, distribute, print, or copy any part of this message if you are not the intended recipient. FXDirectDealer, LLC reserves the right to monitor all e-mail communications through its networks. Any views expressed in this message are those of the individual sender, except where the message states otherwise and the sender is authorized to state them. Unless otherwise stated, any pricing information given in this message is indicative only
Unable to restart after crash
Hi, My mysql server crashed last night, and when it rebooted, was unable to restart. Here is the error log: Jan 13 00:12:54 localhost mysqld_safe[1324]: started Jan 13 00:12:55 localhost mysqld[1327]: 080113 0:12:55 InnoDB: Database was not shut down normally! Jan 13 00:12:55 localhost mysqld[1327]: InnoDB: Starting crash recovery. Jan 13 00:12:55 localhost mysqld[1327]: InnoDB: Reading tablespace information from the .ibd files... Jan 13 00:12:55 localhost mysqld[1327]: InnoDB: Restoring possible half-written data pages from the doublewrite Jan 13 00:12:55 localhost mysqld[1327]: InnoDB: buffer... Jan 13 00:12:56 localhost mysqld[1327]: 080113 0:12:56 InnoDB: Starting log scan based on checkpoint at Jan 13 00:12:56 localhost mysqld[1327]: InnoDB: log sequence number 0 111349. Jan 13 00:12:56 localhost mysqld[1327]: InnoDB: Doing recovery: scanned up to log sequence number 0 111349 Jan 13 00:12:56 localhost mysqld[1327]: InnoDB: Last MySQL binlog file position 0 3587, file name /var/log/mysql/mysql-bin.000489 Jan 13 00:12:56 localhost mysqld[1327]: 080113 0:12:56 InnoDB: Started; log sequence number 0 111349 Jan 13 00:12:56 localhost mysqld[1327]: 080113 0:12:56 [Note] Recovering after a crash using /var/log/mysql/mysql-bin Jan 13 00:12:56 localhost mysqld[1327]: 080113 0:12:56 [Note] Starting crash recovery... Jan 13 00:12:56 localhost mysqld[1327]: 080113 0:12:56 [Note] Crash recovery finished. Jan 13 00:12:57 localhost mysqld[1327]: 080113 0:12:57 [ERROR] Can't start server: Bind on TCP/IP port: Cannot assign requested address Jan 13 00:12:57 localhost mysqld[1327]: 080113 0:12:57 [ERROR] Do you already have another mysqld server running on port: 3306 ? Jan 13 00:12:57 localhost mysqld[1327]: 080113 0:12:57 [ERROR] Aborting Jan 13 00:12:57 localhost mysqld[1327]: Jan 13 00:12:57 localhost mysqld[1327]: 080113 0:12:57 InnoDB: Starting shutdown... Jan 13 00:12:59 localhost mysqld[1327]: 080113 0:12:59 InnoDB: Shutdown completed; log sequence number 0 111349 Jan 13 00:12:59 localhost mysqld[1327]: 080113 0:12:59 [Note] /usr/sbin/mysqld: Shutdown complete Jan 13 00:12:59 localhost mysqld[1327]: Jan 13 00:12:59 localhost mysqld_safe[1374]: ended And since then I am unable to start it. mysqld_safe aborts with: Starting mysqld daemon with databases from /var/lib/mysql mysqld_safe[3150]: started STOPPING server from pid file /var/run/mysqld/mysqld.pid mysqld_safe[3164]: ended And error file: Jan 13 06:03:06 localhost mysqld_safe[1318]: started Jan 13 06:03:08 localhost mysqld[1321]: 080113 6:03:08 InnoDB: Started; log sequence number 0 111349 Jan 13 06:03:08 localhost mysqld[1321]: 080113 6:03:08 [ERROR] Can't start server: Bind on TCP/IP port: Cannot assign requested address Jan 13 06:03:08 localhost mysqld[1321]: 080113 6:03:08 [ERROR] Do you already have another mysqld server running on port: 3306 ? Jan 13 06:03:08 localhost mysqld[1321]: 080113 6:03:08 [ERROR] Aborting Jan 13 06:03:08 localhost mysqld[1321]: Jan 13 06:03:08 localhost mysqld[1321]: 080113 6:03:08 InnoDB: Starting shutdown... Jan 13 06:03:11 localhost mysqld[1321]: 080113 6:03:11 InnoDB: Shutdown completed; log sequence number 0 111349 Jan 13 06:03:11 localhost mysqld[1321]: 080113 6:03:11 [Note] /usr/sbin/mysqld: Shutdown complete Jan 13 06:03:11 localhost mysqld[1321]: Jan 13 06:03:11 localhost mysqld_safe[1368]: ended Nothing is running on port 3306, telnet gets connection refused. No mysql processes are running. Does anyone have any ideas what might be wrong? Thanks ROSCO -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: Unable to restart after crash
Have you looked at the results of netstat -an ? -Grant - Original Message - From: Ross Crawford To: mysql@lists.mysql.com Sent: Saturday, January 12, 2008 5:12 PM Subject: Unable to restart after crash Hi, My mysql server crashed last night, and when it rebooted, was unable to restart. Here is the error log: Jan 13 00:12:54 localhost mysqld_safe[1324]: started Jan 13 00:12:55 localhost mysqld[1327]: 080113 0:12:55 InnoDB: Database was not shut down normally! Jan 13 00:12:55 localhost mysqld[1327]: InnoDB: Starting crash recovery. Jan 13 00:12:55 localhost mysqld[1327]: InnoDB: Reading tablespace information from the .ibd files... Jan 13 00:12:55 localhost mysqld[1327]: InnoDB: Restoring possible half-written data pages from the doublewrite Jan 13 00:12:55 localhost mysqld[1327]: InnoDB: buffer... Jan 13 00:12:56 localhost mysqld[1327]: 080113 0:12:56 InnoDB: Starting log scan based on checkpoint at Jan 13 00:12:56 localhost mysqld[1327]: InnoDB: log sequence number 0 111349. Jan 13 00:12:56 localhost mysqld[1327]: InnoDB: Doing recovery: scanned up to log sequence number 0 111349 Jan 13 00:12:56 localhost mysqld[1327]: InnoDB: Last MySQL binlog file position 0 3587, file name /var/log/mysql/mysql-bin.000489 Jan 13 00:12:56 localhost mysqld[1327]: 080113 0:12:56 InnoDB: Started; log sequence number 0 111349 Jan 13 00:12:56 localhost mysqld[1327]: 080113 0:12:56 [Note] Recovering after a crash using /var/log/mysql/mysql-bin Jan 13 00:12:56 localhost mysqld[1327]: 080113 0:12:56 [Note] Starting crash recovery... Jan 13 00:12:56 localhost mysqld[1327]: 080113 0:12:56 [Note] Crash recovery finished. Jan 13 00:12:57 localhost mysqld[1327]: 080113 0:12:57 [ERROR] Can't start server: Bind on TCP/IP port: Cannot assign requested address Jan 13 00:12:57 localhost mysqld[1327]: 080113 0:12:57 [ERROR] Do you already have another mysqld server running on port: 3306 ? Jan 13 00:12:57 localhost mysqld[1327]: 080113 0:12:57 [ERROR] Aborting Jan 13 00:12:57 localhost mysqld[1327]: Jan 13 00:12:57 localhost mysqld[1327]: 080113 0:12:57 InnoDB: Starting shutdown... Jan 13 00:12:59 localhost mysqld[1327]: 080113 0:12:59 InnoDB: Shutdown completed; log sequence number 0 111349 Jan 13 00:12:59 localhost mysqld[1327]: 080113 0:12:59 [Note] /usr/sbin/mysqld: Shutdown complete Jan 13 00:12:59 localhost mysqld[1327]: Jan 13 00:12:59 localhost mysqld_safe[1374]: ended And since then I am unable to start it. mysqld_safe aborts with: Starting mysqld daemon with databases from /var/lib/mysql mysqld_safe[3150]: started STOPPING server from pid file /var/run/mysqld/mysqld.pid mysqld_safe[3164]: ended And error file: Jan 13 06:03:06 localhost mysqld_safe[1318]: started Jan 13 06:03:08 localhost mysqld[1321]: 080113 6:03:08 InnoDB: Started; log sequence number 0 111349 Jan 13 06:03:08 localhost mysqld[1321]: 080113 6:03:08 [ERROR] Can't start server: Bind on TCP/IP port: Cannot assign requested address Jan 13 06:03:08 localhost mysqld[1321]: 080113 6:03:08 [ERROR] Do you already have another mysqld server running on port: 3306 ? Jan 13 06:03:08 localhost mysqld[1321]: 080113 6:03:08 [ERROR] Aborting Jan 13 06:03:08 localhost mysqld[1321]: Jan 13 06:03:08 localhost mysqld[1321]: 080113 6:03:08 InnoDB: Starting shutdown... Jan 13 06:03:11 localhost mysqld[1321]: 080113 6:03:11 InnoDB: Shutdown completed; log sequence number 0 111349 Jan 13 06:03:11 localhost mysqld[1321]: 080113 6:03:11 [Note] /usr/sbin/mysqld: Shutdown complete Jan 13 06:03:11 localhost mysqld[1321]: Jan 13 06:03:11 localhost mysqld_safe[1368]: ended Nothing is running on port 3306, telnet gets connection refused. No mysql processes are running. Does anyone have any ideas what might be wrong? Thanks ROSCO -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED] -- Total Control Panel Login To: [EMAIL PROTECTED] From: [EMAIL PROTECTED] Remove lists.mysql.com from my allow list You received this message because the domain lists.mysql.com is on your allow list.
Error restart mysqld after network broken
Here is my errors in my locahost.locaodomain.err: 071217 14:02:12 mysqld_safe Starting mysqld daemon with databases from /usr/local/mysql/data/ 2 071217 14:02:12 InnoDB: Started; log sequence number 0 46429 3 071217 14:02:13 [Warning] NDB: server id set to zero will cause any other mysqld with bin log to log with wrong server id 4 071217 14:02:13 [Note] Starting MySQL Cluster Binlog Thread 5 071217 14:02:13 [Note] Event Scheduler: Loaded 0 events 6 071217 14:02:13 [Note] /usr/local/mysql/bin/mysqld: ready for connections. 7 Version: '5.1.21-beta' socket: '/tmp/mysql.sock' port: 3306 MySQL Community Server (GPL) 8 071217 14:02:14 - mysqld got signal 6; 9 This could be because you hit a bug. It is also possible that this binary 10 or one of the libraries it was linked against is corrupt, improperly built, 11 or misconfigured. This error can also be caused by malfunctioning hardware. 12 We will try our best to scrape up some info that will hopefully help diagnose 13 the problem, but since we have already crashed, something is definitely wrong 14 and this may fail. 15 16 key_buffer_size=8388600 17 read_buffer_size=131072 18 max_used_connections=2 19 max_threads=151 20 threads_connected=0 21 It is possible that mysqld could use up to 22 key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 337618 K 23 bytes of memory 24 Hope that's ok; if not, decrease some variables in the equation. 25 26 thd: 0x0 27 Attempting backtrace. You can use the following information to find out 28 where mysqld died. If you see no messages after this, something went 29 terribly wrong... 30 Cannot determine thread, fp=0xb7ff3b28, backtrace may not be correct. 31 Stack range sanity check OK, backtrace follows: 32 0x81fe0c9 33 0xad9402 34 0x4bf07451 35 0x8465f7f 36 0x8452aa4 37 0x8451929 38 0x84adb92 39 0x84b6d58 40 0x84b549d 41 0x84ae0cd 42 0x84adfb7 43 0x849d6b8 44 0x4c0502db 45 0x4bfaa12e 46 New value of fp=(nil) failed sanity check, terminating stack trace! 47 Please read http://dev.mysql.com/doc/refman/5.1/en/resolve-stack-dump.html 48 and follow instructions on how to resolve the stack trace. 49 Resolved stack trace is much more helpful in diagnosing the 50 problem, so please do resolve it 51 The manual page at http://www.mysql.com/doc/en/Crashing.htmlcontains 52 information that should help you find out what is causing the crash. 53 071217 14:02:14 mysqld_safe Number of processes running now: 0 [EMAIL PROTECTED] ~]# service mysqld status ERROR! MySQL is not running, but lock exists [EMAIL PROTECTED] ~]# ps aux | grep mysql root 2232 0.1 0.1 4596 1320 ?S13:52 0:00 /bin/sh /usr/local/mysql//bin/mysqld_safe --datadir=/usr/local/mysql/data/ --pid-file=/usr/local/mysql/data//localhost.localdomain.pid nobody4873 1.3 1.4 114512 14452 ?Sl 13:58 0:00 /usr/local/mysql/bin/mysqld --basedir=/usr/local/mysql/ --datadir=/usr/local/mysql/data/ --user=nobody --log-error=/usr/local/mysql/data//localhost.localdomain.err --pid-file=/usr/local/mysql/data//localhost.localdomain.pid --socket=/tmp/mysql.sock --port=3306 root 4889 0.0 0.0 4124 660 pts/0D+ 13:58 0:00 grep mysql I don't know how to solve this,anybody can help me,thanks.
adding plugin_dir to my.cfg returns error on mysql restart
I'm trying to setup and use User Defined Functions (UDF) in MySQL. First of all, typing: show variables like 'plugin'; in order to get the mysql plugin path returns an empty result set for me. I tried specifying the plugin directory directly in my.cnf, under [mysqld], by adding: plugin_dir=/usr/lib/mysql (note: i created the above directory and chown'ed it to mysql:mysql). After that MySQL could not restart any more. Looking in syslog, I found the following: Jul 25 10:29:09 gx200 mysqld_safe[14480]: started Jul 25 10:29:09 gx200 mysqld[14483]: 070725 10:29:09 [ERROR] /usr/sbin/mysqld: unknown variable 'plugin_dir=/usr/lib/mysql' Jul 25 10:29:09 gx200 mysqld[14483]: Jul 25 10:29:09 gx200 mysqld_safe[14485]: ended I'm using debian etch. Thanks for any help. Take the Internet to Go: Yahoo!Go puts the Internet in your pocket: mail, news, photos more. http://mobile.yahoo.com/go?refer=1GNXIC -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
mysqld-max: segfault at and auto restart mysql
Dear All, I have problem that API node on cluster always auto restart mysql (every 30, 20, 15 or just 5 minutes). I see many error messages at message log file: Jun 20 15:27:18 PrivateData1 sshd(pam_unix)[30280]: session opened for user root by root(uid=0) Jun 20 15:51:24 PrivateData1 kernel: mysqld-max[24953]: segfault at 416c7fe8 rip 003d45d68900 rsp 416c8018 error 6 Jun 20 16:03:34 PrivateData1 kernel: mysqld-max[3171]: segfault at 41541fe8 rip 003d45d68900 rsp 41542018 error 6 Jun 20 16:08:50 PrivateData1 kernel: mysqld-max[22925]: segfault at 40de4fe8 rip 003d45d68900 rsp 40de5018 error 6 Jun 20 17:40:56 PrivateData1 kernel: mysqld-max[25183]: segfault at 41d61fe8 rip 003d45d68900 rsp 41d62018 error 6 Jun 20 17:43:59 PrivateData1 kernel: mysqld-max[2592]: segfault at 40e66fe8 rip 003d45d68900 rsp 40e67018 error 6 Jun 20 17:44:14 PrivateData1 kernel: mysqld-max[3047]: segfault at 40b9bfe8 rip 003d45d68900 rsp 40b9c018 error 6 Jun 20 18:53:28 PrivateData1 kernel: mysqld-max[28016]: segfault at 41992fe8 rip 003d45d68900 rsp 41993018 error 6 Jun 20 19:00:55 PrivateData1 kernel: mysqld-max[16842]: segfault at 412b7fe8 rip 003d45d68900 rsp 412b8018 error 6 Jun 20 19:01:40 PrivateData1 kernel: mysqld-max[19158]: segfault at 40fecfe8 rip 003d45d68900 rsp 40fed018 error 6 Jun 21 08:25:35 PrivateData1 kernel: mysqld-max[17855]: segfault at 41febfe8 rip 003d45d68900 rsp 41fec018 error 6 Jun 21 08:30:20 PrivateData1 kernel: mysqld-max[28280]: segfault at 40b5afe8 rip 003d45d68900 rsp 40b5b018 error 6 Jun 21 08:31:33 PrivateData1 kernel: mysqld-max[30318]: segfault at 41276fe8 rip 003d45d68900 rsp 41277018 error 6 but there is no error on the database log file, only restarted messages. My cluser have: 1 MGM node, 1 API node and 2 data nodes. Version: 5.0.37-max | version_bdb | Sleepycat Software: Berkeley DB 4.1.24: (March 2, 2007) | | version_comment | MySQL Community Edition - Experimental (GPL) | | version_compile_machine: CentOS 4.4 x86_64, kernel: 2.6.9-34.EL Please help me Thanks so much. Toan Dang
how would mysqld restart affect dynamically set global variables?
Hi, We're running mysql 4.1.20. If I understand the manual correctly, I can change max_connections while mysqld is running without restart mysqld to make the change take effect. But what if mysqld restarts later in some other situations, like machine reboot, would my (global) change on max_connections remain? I'm just very clear when to make dynamic changes and when is better to put changes in my.cnf. Please advise. Thanks in advance, Bing -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: how would mysqld restart affect dynamically set global variables?
I believe it would revert back to the settings in your my.cnf file. If you want the change to be permanent, then set it there. Steve Musumeche CIO, Internet Retail Connection [EMAIL PROTECTED] Bing Du wrote: Hi, We're running mysql 4.1.20. If I understand the manual correctly, I can change max_connections while mysqld is running without restart mysqld to make the change take effect. But what if mysqld restarts later in some other situations, like machine reboot, would my (global) change on max_connections remain? I'm just very clear when to make dynamic changes and when is better to put changes in my.cnf. Please advise. Thanks in advance, Bing -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: how would mysqld restart affect dynamically set global variables?
On Wed, March 14, 2007 9:35, Bing Du said: Hi, We're running mysql 4.1.20. If I understand the manual correctly, I can change max_connections while mysqld is running without restart mysqld to make the change take effect. But what if mysqld restarts later in some other situations, like machine reboot, would my (global) change on max_connections remain? I'm just very clear when to make dynamic changes and when is better to put changes in my.cnf. Please advise. Thanks in advance, Bing Put the changes in dynamically. If they work change the my.cnf to make them survive the next time mysql is restarted (for example on a reboot). --- William R. Mussatto, Senior Systems Engineer http://www.csz.com Ph. 909-920-9154 ext. 27 FAX. 909-608-7061 -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: how would mysqld restart affect dynamically set global variables?
We're running mysql 4.1.20. If I understand the manual correctly, I can change max_connections while mysqld is running without restart mysqld to make the change take effect Correct. But what if mysqld restarts later in some other situations, like machine reboot, would my (global) change on max_connections remain? No; you'll need to put it in my.cnf in order for it to persist after mysqld is shut down. -- Alex -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: how would mysqld restart affect dynamically set global variables?
dude try put it on var/my.cf set-variable = max_connections = 1024 set-variable = max_user_connections = 128 set-variable = table_cache=1200 :wq! i have this working with a mysql3x should be similar to mysql4/5x On 3/14/07, Bing Du [EMAIL PROTECTED] wrote: Hi, We're running mysql 4.1.20. If I understand the manual correctly, I can change max_connections while mysqld is running without restart mysqld to make the change take effect. But what if mysqld restarts later in some other situations, like machine reboot, would my (global) change on max_connections remain? I'm just very clear when to make dynamic changes and when is better to put changes in my.cnf. Please advise. Thanks in advance, Bing -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED] -- -- Thiago LPS C.E.S.A.R - Administrador de Sistemas msn: [EMAIL PROTECTED] 0xx 81 8735 2591 --
Re: mysql/syslog - 100,000s of log messages on restart
Hi, In ur cnf file mention the log file path as log=/mysql/logs/mysqllog/qry.log . log-slow-queries=/mysql/logs/mysqllog/slowqry.log and restart mysql. Thanks Regards Dilipkumar - Original Message - From: Adam Rosi-Kessel [EMAIL PROTECTED] To: mysql@lists.mysql.com Sent: Sunday, July 23, 2006 1:58 AM Subject: mysql/syslog - 100,000s of log messages on restart I'm running MySQL 4.0.23 on a Debian Sarge system. Often, when I reboot twice in a short time period, MySQL doesn't seem to shut down gracefully -- it takes a long time for it to come up fully, and if I reboot before that, I get a lot of log messages. I think it takes about an hour to come up fully, although the system is an Athlon XP 2200+ CPU with 2G RAM and not a huge amount of other activity. My first concern is figuring out how to avoid getting hundreds of thousands of messages in syslog -- right now grep mysql /var/log/syslog | wc -l gives 366635 and counting just for today. The log messages look like this: Jul 22 16:29:01 bostoncoop mysqld[1993]: mysql tables in use 1, locked 0 Jul 22 16:29:01 bostoncoop mysqld[1993]: MySQL thread id 252, query id 8143 localhost tpryor statistics Jul 22 16:29:01 bostoncoop mysqld[1993]: /* LinkCache::addLinkObj */ SELECT page_id FROM `page` WHERE page_namespace = '0' AND page_title = 'Zwijnaarde' LIMIT 1 Jul 22 16:29:01 bostoncoop mysqld[1993]: ---TRANSACTION 0 0, not started, process no 1992, OS thread id 2954361776 waiting in InnoDB queue There's also a bunch of INNODB MONITOR OUTPUT. I'd like these messages not to get logged at all -- it's far too many to be useful. Second, I'd like to have MySQL log to /var/log/mysql/mysql.log rather than syslog. my.cnf seems to be very poorly documented on this issue. It says it is a performance killer to log to a specific file -- presumably, using the syslog facility gives better performance. But I can't find any way to filter the syslog logging back to a separate log file -- for example, by setting the syslog facility for MySQL as you can in PostgreSQL. The only documentation in MySQL relating to syslog facility configuration is in the clustering section, which I don't believe has anything to do with what I'm doing. Third, I'd like to figure out why it's taking so long for MySQL to come up; why it doesn't go down gracefully; and why there are so many log messages generated as it is coming up. My my.cnf is attached -- it's fairly standard. Thanks for any tips. -- Adam Rosi-Kessel http://adam.rosi-kessel.org -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED] ** DISCLAIMER ** Information contained and transmitted by this E-MAIL is proprietary to Sify Limited and is intended for use only by the individual or entity to which it is addressed, and may contain information that is privileged, confidential or exempt from disclosure under applicable law. If this is a forwarded message, the content of this E-MAIL may not have been sent with the authority of the Company. If you are not the intended recipient, an agent of the intended recipient or a person responsible for delivering the information to the named recipient, you are notified that any use, distribution, transmission, printing, copying or dissemination of this information in any way or in any manner is strictly prohibited. If you have received this communication in error, please delete this mail notify us immediately at [EMAIL PROTECTED] Watch the latest updates on Mumbai, with video coverage of news, events, Bollywood, live darshan from Siddhivinayak temple and more, only on www.mumbailive.in Watch the hottest videos from Bollywood, Fashion, News and more only on www.sifymax.com -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
mysql/syslog - 100,000s of log messages on restart
I'm running MySQL 4.0.23 on a Debian Sarge system. Often, when I reboot twice in a short time period, MySQL doesn't seem to shut down gracefully -- it takes a long time for it to come up fully, and if I reboot before that, I get a lot of log messages. I think it takes about an hour to come up fully, although the system is an Athlon XP 2200+ CPU with 2G RAM and not a huge amount of other activity. My first concern is figuring out how to avoid getting hundreds of thousands of messages in syslog -- right now grep mysql /var/log/syslog | wc -l gives 366635 and counting just for today. The log messages look like this: Jul 22 16:29:01 bostoncoop mysqld[1993]: mysql tables in use 1, locked 0 Jul 22 16:29:01 bostoncoop mysqld[1993]: MySQL thread id 252, query id 8143 localhost tpryor statistics Jul 22 16:29:01 bostoncoop mysqld[1993]: /* LinkCache::addLinkObj */ SELECT page_id FROM `page` WHERE page_namespace = '0' AND page_title = 'Zwijnaarde' LIMIT 1 Jul 22 16:29:01 bostoncoop mysqld[1993]: ---TRANSACTION 0 0, not started, process no 1992, OS thread id 2954361776 waiting in InnoDB queue There's also a bunch of INNODB MONITOR OUTPUT. I'd like these messages not to get logged at all -- it's far too many to be useful. Second, I'd like to have MySQL log to /var/log/mysql/mysql.log rather than syslog. my.cnf seems to be very poorly documented on this issue. It says it is a performance killer to log to a specific file -- presumably, using the syslog facility gives better performance. But I can't find any way to filter the syslog logging back to a separate log file -- for example, by setting the syslog facility for MySQL as you can in PostgreSQL. The only documentation in MySQL relating to syslog facility configuration is in the clustering section, which I don't believe has anything to do with what I'm doing. Third, I'd like to figure out why it's taking so long for MySQL to come up; why it doesn't go down gracefully; and why there are so many log messages generated as it is coming up. My my.cnf is attached -- it's fairly standard. Thanks for any tips. -- Adam Rosi-Kessel http://adam.rosi-kessel.org # # The MySQL database server configuration file. # # You can copy this to one of: # - /etc/mysql/my.cnf to set global options, # - /var/lib/mysql/my.cnf to set server-specific options or # - ~/.my.cnf to set user-specific options. # # One can use all long options that the program supports. # Run program with --help to get a list of available options and with # --print-defaults to see which it would actually understand and use. # # For explanations see # http://dev.mysql.com/doc/mysql/en/server-system-variables.html # This will be passed to all mysql clients # It has been reported that passwords should be enclosed with ticks/quotes # escpecially if they contain # chars... # Remember to edit /etc/mysql/debian.cnf when changing the socket location. [client] port= 3306 socket = /var/run/mysqld/mysqld.sock # Here is entries for some specific programs # The following values assume you have at least 32M ram # This was formally known as [safe_mysqld]. Both versions are currently parsed. [mysqld_safe] socket = /var/run/mysqld/mysqld.sock nice= 0 [mysqld] user= mysql pid-file= /var/run/mysqld/mysqld.pid socket = /var/run/mysqld/mysqld.sock port= 3306 # Both location gets rotated by the cronjob. # Be aware that this log type is a performance killer. #log= /var/log/mysql.log #log= /var/log/mysql/mysql.log #err-log= /var/log/mysql/mysql.err basedir = /usr datadir = /var/lib/mysql tmpdir = /tmp language= /usr/share/mysql/english max_connections = 200 default-table-type = innodb skip-external-locking # # Instead of skip-networking the default is now to listen only on # localhost which is more compatible and is not less secure. bind-address= 127.0.0.1 key_buffer = 16M max_allowed_packet = 16M thread_stack= 128K # # Query Cache Configuration # query_cache_limit = 1048576 query_cache_size= 16777216 query_cache_type= 1 # # Here you can see queries with especially long duration #log-slow-queries = /var/log/mysql/mysql-slow.log # # The following can be used as easy to replay backup logs or for replication. #server-id = 1 log-bin = /var/log/mysql/mysql-bin.log # See /etc/mysql/debian-log-rotate.conf for the number of files kept. max_binlog_size = 104857600 #binlog-do-db = include_database_name #binlog-ignore-db = include_database_name # # # InnoDB is enabled by default with a 10MB datafile in /var/lib/mysql/. # Read the manual for more InnoDB related options. There are many! # # Read the manual, too, if you want chroot! # chroot = /var/lib/mysql/ # # If you want to enable SSL support (recommended) read the manual or my # HOWTO in
Re: how to restart mysql and apache?
Hi, If it is your default apache /usr/sbin/apachectl start and mysql /etc/init.d/mysql.server start This might help you out. Daniel da Veiga wrote: On 5/9/06, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: found this: /etc/rc.d/init.d/mysqld restart /etc/rc.d/init.d/httpd2 restart I think it should work? Yeah, different systems, different locations, but the same purpose... -- Daniel da Veiga Computer Operator - RS - Brazil -BEGIN GEEK CODE BLOCK- Version: 3.1 GCM/IT/P/O d-? s:- a? C++$ UBLA++ P+ L++ E--- W+++$ N o+ K- w O M- V- PS PE Y PGP- t+ 5 X+++ R+* tv b+ DI+++ D+ G+ e h+ r+ y++ --END GEEK CODE BLOCK-- -- Thanks Regards, Dilipkumar DBA Support ** DISCLAIMER ** Information contained and transmitted by this E-MAIL is proprietary to Sify Limited and is intended for use only by the individual or entity to which it is addressed, and may contain information that is privileged, confidential or exempt from disclosure under applicable law. If this is a forwarded message, the content of this E-MAIL may not have been sent with the authority of the Company. If you are not the intended recipient, an agent of the intended recipient or a person responsible for delivering the information to the named recipient, you are notified that any use, distribution, transmission, printing, copying or dissemination of this information in any way or in any manner is strictly prohibited. If you have received this communication in error, please delete this mail notify us immediately at [EMAIL PROTECTED] Watch India vs. England LIVE, Hot videos and more only on Sify Max! Click Here. www.sifymax.com Get to see what's happening in your favourite City on Bangalore Live! www.bangalorelive.in -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
how to restart mysql and apache
hi again, I have to restart as soon as possible mysql and apache on our web server (mandrake cooker 10) - since our admin is out of office for today. if someone can ive me some instructions, please? 1. what I have to restart first apaceh or mysql - or desn't matter? 2. I have sudo access (if I understand it correct, I have root privilages even I loged in as regular user) to web server - enough or I have to have root access to do restart? Thanks for any help. -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
how to restart mysql and apache?
hi again, I have to restart as soon as possible mysql and apache on our web server (mandrake cooker 10) - since our admin is out of office for today. if someone can ive me some instructions, please? 1. what I have to restart first apaceh or mysql - or desn't matter? 2. I have sudo access (if I understand it correct, I have root privilages even I loged in as regular user) to web server - enough or I have to have root access to do restart? Thanks for any help. -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: how to restart mysql and apache?
found this: /etc/rc.d/init.d/mysqld restart /etc/rc.d/init.d/httpd2 restart I think it should work? -afan On 5/9/06, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: hi again, I have to restart as soon as possible mysql and apache on our web server (mandrake cooker 10) - since our admin is out of office for today. if someone can ive me some instructions, please? 1. what I have to restart first apaceh or mysql - or desn't matter? 2. I have sudo access (if I understand it correct, I have root privilages even I loged in as regular user) to web server - enough or I have to have root access to do restart? Thanks for any help. -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED] -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: how to restart mysql and apache?
On 5/9/06, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: hi again, I have to restart as soon as possible mysql and apache on our web server (mandrake cooker 10) - since our admin is out of office for today. Are you sure you MUST restart those services? AFAIK you run Linux exactly because you don't wanna do that ;) if someone can ive me some instructions, please? 1. what I have to restart first apaceh or mysql - or desn't matter? Anyway: /etc/init.d/mysql restart /etc/init.d/apache2 restart (or apache, depends on your version) 2. I have sudo access (if I understand it correct, I have root privilages even I loged in as regular user) to web server - enough or I have to have root access to do restart? If you have enough privileges using sudo (all privileges to be exact), you can run sudo su and become root, but that's just a security flaw and you should blame your admin for that! Try it: sudo su -c /etc/init.d/mysql restart or simply sudo su and performe the commands listed for your first question. If it succeed, you restart the server, but then you have an insecure and bad configured system. Thanks for any help. -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED] -- Daniel da Veiga Computer Operator - RS - Brazil -BEGIN GEEK CODE BLOCK- Version: 3.1 GCM/IT/P/O d-? s:- a? C++$ UBLA++ P+ L++ E--- W+++$ N o+ K- w O M- V- PS PE Y PGP- t+ 5 X+++ R+* tv b+ DI+++ D+ G+ e h+ r+ y++ --END GEEK CODE BLOCK-- -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: how to restart mysql and apache?
On 5/9/06, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: found this: /etc/rc.d/init.d/mysqld restart /etc/rc.d/init.d/httpd2 restart I think it should work? Yeah, different systems, different locations, but the same purpose... -- Daniel da Veiga Computer Operator - RS - Brazil -BEGIN GEEK CODE BLOCK- Version: 3.1 GCM/IT/P/O d-? s:- a? C++$ UBLA++ P+ L++ E--- W+++$ N o+ K- w O M- V- PS PE Y PGP- t+ 5 X+++ R+* tv b+ DI+++ D+ G+ e h+ r+ y++ --END GEEK CODE BLOCK-- -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: how to restart mysql and apache?
On 5/9/06, Edward Vermillion [EMAIL PROTECTED] wrote: On May 9, 2006, at 1:50 PM, Daniel da Veiga wrote: On 5/9/06, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: hi again, I have to restart as soon as possible mysql and apache on our web server (mandrake cooker 10) - since our admin is out of office for today. Are you sure you MUST restart those services? AFAIK you run Linux exactly because you don't wanna do that ;) Um... you run linux because you *can* do that. IE. you don't have to reboot the server to restart the services... ;) From another point of view, Yeah, true! :) -- Daniel da Veiga Computer Operator - RS - Brazil -BEGIN GEEK CODE BLOCK- Version: 3.1 GCM/IT/P/O d-? s:- a? C++$ UBLA++ P+ L++ E--- W+++$ N o+ K- w O M- V- PS PE Y PGP- t+ 5 X+++ R+* tv b+ DI+++ D+ G+ e h+ r+ y++ --END GEEK CODE BLOCK-- -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: how to restart mysql and apache?
Thanks Daniel! -afan On 5/9/06, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: found this: /etc/rc.d/init.d/mysqld restart /etc/rc.d/init.d/httpd2 restart I think it should work? Yeah, different systems, different locations, but the same purpose... -- Daniel da Veiga Computer Operator - RS - Brazil -BEGIN GEEK CODE BLOCK- Version: 3.1 GCM/IT/P/O d-? s:- a? C++$ UBLA++ P+ L++ E--- W+++$ N o+ K- w O M- V- PS PE Y PGP- t+ 5 X+++ R+* tv b+ DI+++ D+ G+ e h+ r+ y++ --END GEEK CODE BLOCK-- -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED] -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: MySQL 4.1.11 innodb cache can't be flushed after restart ?
2006/4/7, Charles Q. Shen [EMAIL PROTECTED]: Hi all, I am running MySQL 4.1.11 with an innoDB table holding about 17GB of records. I took a few hundreds of randomly selected records from the table and measured the average access time: 1st test: average access time is 600ms 2nd test: average access time is 30ms 3rd test: average access time is 15ms Stop and restart MySQL 4th test: average access time is 15ms Note that I stopped and restarted mysql between the 3rd and 4th test but the average access time does not change. What OS do you use ? It's quiet likely you hit the FS cache, not the MySQL one. -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
RE: MySQL 4.1.11 innodb cache can't be flushed after restart ?
The OS used are Mandriva and Fedora. Can you explain more? Thanks. Charles -Original Message- From: Philippe Poelvoorde [mailto:[EMAIL PROTECTED] Sent: Friday, April 07, 2006 2:43 AM To: MySQL General Subject: Re: MySQL 4.1.11 innodb cache can't be flushed after restart ? 2006/4/7, Charles Q. Shen [EMAIL PROTECTED]: Hi all, I am running MySQL 4.1.11 with an innoDB table holding about 17GB of records. I took a few hundreds of randomly selected records from the table and measured the average access time: 1st test: average access time is 600ms 2nd test: average access time is 30ms 3rd test: average access time is 15ms Stop and restart MySQL 4th test: average access time is 15ms Note that I stopped and restarted mysql between the 3rd and 4th test but the average access time does not change. What OS do you use ? It's quiet likely you hit the FS cache, not the MySQL one. -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED] -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: MySQL 4.1.11 innodb cache can't be flushed after restart ?
2006/4/7, Charles Q. Shen [EMAIL PROTECTED]: The OS used are Mandriva and Fedora. Can you explain more? I'll make it quick, there is plenty of doc on a web that will explain this better than I can. Once you read few things from your hard drive (let's say the index file for your table), it's kept in memory. Next time you access it it's directly retrived from memory, not the hard drive, thus low response time. shutting down MySQL won't clear that cache. If you want to circumvent that, you need to umount the partition where data and index are stored. HIMH http://www.tldp.org/LDP/tlk/fs/filesystem.html -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
MySQL 4.1.11 innodb cache can't be flushed after restart ?
Hi all, I am running MySQL 4.1.11 with an innoDB table holding about 17GB of records. I took a few hundreds of randomly selected records from the table and measured the average access time: 1st test: average access time is 600ms 2nd test: average access time is 30ms 3rd test: average access time is 15ms Stop and restart MySQL 4th test: average access time is 15ms Note that I stopped and restarted mysql between the 3rd and 4th test but the average access time does not change. I also tried another set of random records that are not in the table, the average access time is about 2s for the first test and 115ms for the second test. After stop and restart MySQL, I still got the 115ms access time. Clearly MySQL have both positive and negtive caching. But does anyone know why the cache is not flushed after MySQL restart?? I understand that MySQL has a query_cache, but it is turned off by default and I do NOT have it on. There is also an innodb_buffer_pool_size variable, which in my case is at the default value 1048576 (and can't seem to be set smaller). My data file path in my.cnf file is: # Configure the datafile to be auto expanding innodb_data_file_path = ibdata1:10M:autoextend Thanks a lot! Charles -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Cannot restart service MySQL
Please help, I can't start my server!! I was running a query, and it seemed to be hanging. After waiting about 15 minutes, I finally did a 'CTRL+BREAK' to abort the process. This happened about 3 times, and finally I decided to restart the MySQL service to see if that would help. Well, when I did that, the service wouldn't stop. Now when I go into the Services manager in Windows, the MySQL service is listed as 'Stopping,' and all the control buttons (stop, start, restart) are all grayed out. The problem is, the service is NOT stopping and I can't restart it doing a 'mysqld --console' either. What do I do? -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: Cannot restart service MySQL
In Windows, you have 3 alternatives: 1 - wait untill it stops the service (can take very long time). 2 - restart the server (your users might cry a bit). 3 - Try to kill the task using Task Manager (this might not work, depending on the service). /Johan Sara Woglom wrote: Please help, I can't start my server!! I was running a query, and it seemed to be hanging. After waiting about 15 minutes, I finally did a 'CTRL+BREAK' to abort the process. This happened about 3 times, and finally I decided to restart the MySQL service to see if that would help. Well, when I did that, the service wouldn't stop. Now when I go into the Services manager in Windows, the MySQL service is listed as 'Stopping,' and all the control buttons (stop, start, restart) are all grayed out. The problem is, the service is NOT stopping and I can't restart it doing a 'mysqld --console' either. What do I do? -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
RE: Cannot restart service MySQL
Sorry, I should have been more specific. I tried 'mysqladmin -u root shutdown -p' and that did not work. The service is hung up in a pending state and I cannot control it. It is Net Error 2189: 'The service could not be controlled in its present state.' There has to be some way I can fix this without bouncing the server, because I really can't do that. -Original Message- From: Ariel Sánchez Mora [mailto:[EMAIL PROTECTED] Sent: Friday, March 31, 2006 4:10 PM To: Sara Woglom Subject: RE: Cannot restart service MySQL Have you tried Command line: mysqladmin -u root shutdown -p Without the . If it has a password, it will ask for it. If it doesn't, remove the -p. If that doesn't work, tell the mailing list what you did, any error messages you may get, and they'll tell you what the problem is. I'm not a MySQL guru so I would restart the machine (but I imagine you can't do that?) and try starting it again, or make a new install. It may be your computer is overloaded at the moment, or some program doesn't let your server exit. Good luck! ariel -Mensaje original- De: Sara Woglom [mailto:[EMAIL PROTECTED] Enviado el: viernes, 31 de marzo de 2006 15:05 Para: MySQL List Asunto: Cannot restart service MySQL Please help, I can't start my server!! I was running a query, and it seemed to be hanging. After waiting about 15 minutes, I finally did a 'CTRL+BREAK' to abort the process. This happened about 3 times, and finally I decided to restart the MySQL service to see if that would help. Well, when I did that, the service wouldn't stop. Now when I go into the Services manager in Windows, the MySQL service is listed as 'Stopping,' and all the control buttons (stop, start, restart) are all grayed out. The problem is, the service is NOT stopping and I can't restart it doing a 'mysqld --console' either. What do I do? -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: mysql restart error
hi Dhandapani, The 3306 port is not listening. But there are some connection whose state is FIN_WAIT_2 as you can see in my first letter. After about 10 minutes I shutdowned mysql, I restarted mysql as root using: /usr/local/mysql/bin/mysqld_safe . It worked. Before it, I did this as mysql and I got the error. Regards, Leo Huang 2006/3/28, [S] Dhandapani [EMAIL PROTECTED] : Hi Leo, check for cnf file for which port you have configured the port .If it is in 3306 port then do netstat -an|grep LIST ,check for 3306 port is listening on your system .If yes you mysql process has not shutdown properly. shutdown the mysql process completely and start the mysql process by specifying your datadirectory. /usr/local/mysql/bin/mysqld_safe --defaults-file=/etc/my.cnf --datadir=/usr/local/mysql/data/ --user=mysql port= 3306 socket = /tmp/mysql.sock Regards, Dhandapani leo huang wrote: hi, Lakshmi The mysql process had ended. I get it from both mysql err log and ps output. regards, Leo Huang 2006/3/28, Lakshmi M P [EMAIL PROTECTED] [EMAIL PROTECTED]: Run ps -ef | grep mysql and see any mysql process is running and if so kill the same and try to start mysql.It may help. leo huang wrote: hi, I met the MySQL restart error today. First, I stopped the running mysql server using /usr/local/mysql/bin/mysqladmin -uroot shutdown. After the server shutdowned, I restarted it using /usr/local/mysql/bin/mysqld_safe . Then, I got this error: [ERROR] Can't start server: Bind on TCP/IP port: Address already in use. There was no other process that was using the port 3306 which mysql server use. But there were some mysql connect did not release because the shutdown. The error log is followed: 060328 8:20:45 [Note] /usr/local/mysql/libexec/mysqld: Normal shutdown 060328 8:20:47 InnoDB: Starting shutdown... 060328 8:20:49 InnoDB: Shutdown completed; log sequence number 120 2134241340 060328 8:20:49 [Note] /usr/local/mysql/libexec/mysqld: Shutdown complete 060328 08:20:49 mysqld ended 060328 08:21:15 mysqld started 060328 8:21:15 [ERROR] Can't start server: Bind on TCP/IP port: Address already in use 060328 8:21:15 [ERROR] Do you already have another mysqld server running on port: 3306 ? 060328 8:21:15 [ERROR] Aborting 060328 8:21:15 [Note] /usr/local/mysql/libexec/mysqld: Shutdown complete 060328 08:21:15 mysqld ended The netstat outputs are followed: $ netstat -al Active Internet connections (including servers) Proto Recv-Q Send-Q Local Address Foreign Address(state) tcp4 0 0 bj.3306 s4.9405 FIN_WAIT_2 tcp4 0 0 bj.3306 s4.5168 FIN_WAIT_2 tcp4 0 0 bj.3306 s4.25007 FIN_WAIT_2 tcp4 0 0 bj.3306 s4.9940 FIN_WAIT_2 tcp4 0 0 bj.3306 s4.3916 FIN_WAIT_2 tcp4 0 0 bj.3306 s4.15229 FIN_WAIT_2 tcp4 0 0 bj.3306 s4.6479 FIN_WAIT_2 tcp4 0 0 bj.3306 s4.7873 FIN_WAIT_2 Our mysql version is 4.1.18. It is running on FreeBSD 4.9-RELEASE. Any comment will be great thankful! Regards, Leo Huang -- regards, Lakshmi.M.P. DBA-Support Sify Limited. Ext:4134 ** DISCLAIMER ** Information contained and transmitted by this E-MAIL is proprietary to Sify Limited and is intended for use only by the individual or entity to which it is addressed, and may contain information that is privileged, confidential or exempt from disclosure under applicable law. If this is a forwarded message, the content of this E-MAIL may not have been sent with the authority of the Company. If you are not the intended recipient, an agent of the intended recipient or a person responsible for delivering the information to the named recipient, you are notified that any use, distribution, transmission, printing, copying or dissemination of this information in any way or in any manner is strictly prohibited. If you have received this communication in error, please delete this mail notify us immediately at [EMAIL PROTECTED] www.sify.com - your homepage on the internet for news, sports, finance, astrology, movies, entertainment, food, languages etc
mysql restart error
hi, I met the MySQL restart error today. First, I stopped the running mysql server using /usr/local/mysql/bin/mysqladmin -uroot shutdown. After the server shutdowned, I restarted it using /usr/local/mysql/bin/mysqld_safe . Then, I got this error: [ERROR] Can't start server: Bind on TCP/IP port: Address already in use. There was no other process that was using the port 3306 which mysql server use. But there were some mysql connect did not release because the shutdown. The error log is followed: 060328 8:20:45 [Note] /usr/local/mysql/libexec/mysqld: Normal shutdown 060328 8:20:47 InnoDB: Starting shutdown... 060328 8:20:49 InnoDB: Shutdown completed; log sequence number 120 2134241340 060328 8:20:49 [Note] /usr/local/mysql/libexec/mysqld: Shutdown complete 060328 08:20:49 mysqld ended 060328 08:21:15 mysqld started 060328 8:21:15 [ERROR] Can't start server: Bind on TCP/IP port: Address already in use 060328 8:21:15 [ERROR] Do you already have another mysqld server running on port: 3306 ? 060328 8:21:15 [ERROR] Aborting 060328 8:21:15 [Note] /usr/local/mysql/libexec/mysqld: Shutdown complete 060328 08:21:15 mysqld ended The netstat outputs are followed: $ netstat -al Active Internet connections (including servers) Proto Recv-Q Send-Q Local Address Foreign Address(state) tcp4 0 0 bj.3306 s4.9405 FIN_WAIT_2 tcp4 0 0 bj.3306 s4.5168 FIN_WAIT_2 tcp4 0 0 bj.3306 s4.25007 FIN_WAIT_2 tcp4 0 0 bj.3306 s4.9940 FIN_WAIT_2 tcp4 0 0 bj.3306 s4.3916 FIN_WAIT_2 tcp4 0 0 bj.3306 s4.15229 FIN_WAIT_2 tcp4 0 0 bj.3306 s4.6479 FIN_WAIT_2 tcp4 0 0 bj.3306 s4.7873 FIN_WAIT_2 Our mysql version is 4.1.18. It is running on FreeBSD 4.9-RELEASE. Any comment will be great thankful! Regards, Leo Huang
Re: mysql restart error
hi, Lakshmi The mysql process had ended. I get it from both mysql err log and ps output. regards, Leo Huang 2006/3/28, Lakshmi M P [EMAIL PROTECTED]: Run ps -ef | grep mysql and see any mysql process is running and if so kill the same and try to start mysql.It may help. leo huang wrote: hi, I met the MySQL restart error today. First, I stopped the running mysql server using /usr/local/mysql/bin/mysqladmin -uroot shutdown. After the server shutdowned, I restarted it using /usr/local/mysql/bin/mysqld_safe . Then, I got this error: [ERROR] Can't start server: Bind on TCP/IP port: Address already in use. There was no other process that was using the port 3306 which mysql server use. But there were some mysql connect did not release because the shutdown. The error log is followed: 060328 8:20:45 [Note] /usr/local/mysql/libexec/mysqld: Normal shutdown 060328 8:20:47 InnoDB: Starting shutdown... 060328 8:20:49 InnoDB: Shutdown completed; log sequence number 120 2134241340 060328 8:20:49 [Note] /usr/local/mysql/libexec/mysqld: Shutdown complete 060328 08:20:49 mysqld ended 060328 08:21:15 mysqld started 060328 8:21:15 [ERROR] Can't start server: Bind on TCP/IP port: Address already in use 060328 8:21:15 [ERROR] Do you already have another mysqld server running on port: 3306 ? 060328 8:21:15 [ERROR] Aborting 060328 8:21:15 [Note] /usr/local/mysql/libexec/mysqld: Shutdown complete 060328 08:21:15 mysqld ended The netstat outputs are followed: $ netstat -al Active Internet connections (including servers) Proto Recv-Q Send-Q Local Address Foreign Address(state) tcp4 0 0 bj.3306 s4.9405 FIN_WAIT_2 tcp4 0 0 bj.3306 s4.5168 FIN_WAIT_2 tcp4 0 0 bj.3306 s4.25007 FIN_WAIT_2 tcp4 0 0 bj.3306 s4.9940 FIN_WAIT_2 tcp4 0 0 bj.3306 s4.3916 FIN_WAIT_2 tcp4 0 0 bj.3306 s4.15229 FIN_WAIT_2 tcp4 0 0 bj.3306 s4.6479 FIN_WAIT_2 tcp4 0 0 bj.3306 s4.7873 FIN_WAIT_2 Our mysql version is 4.1.18. It is running on FreeBSD 4.9-RELEASE. Any comment will be great thankful! Regards, Leo Huang -- regards, Lakshmi.M.P. DBA-Support Sify Limited. Ext:4134 ** DISCLAIMER ** Information contained and transmitted by this E-MAIL is proprietary to Sify Limited and is intended for use only by the individual or entity to which it is addressed, and may contain information that is privileged, confidential or exempt from disclosure under applicable law. If this is a forwarded message, the content of this E-MAIL may not have been sent with the authority of the Company. If you are not the intended recipient, an agent of the intended recipient or a person responsible for delivering the information to the named recipient, you are notified that any use, distribution, transmission, printing, copying or dissemination of this information in any way or in any manner is strictly prohibited. If you have received this communication in error, please delete this mail notify us immediately at [EMAIL PROTECTED] www.sify.com - your homepage on the internet for news, sports, finance, astrology, movies, entertainment, food, languages etc
Server Shutdown, Start Restart
FreeBSD / UNIX platform, MySQL ver.4.0.16 Prob. of growing /tmp file, solved by introducing a cron job to clean up the folder intermittently. Prob.solve but new one created - mysql socket wiped out. Could not restart the server with all the standard methods. Complained of other running processes. Killed the orphaned processes runining. But still can't restart. So can't do a dump or any other back up action, so created a tar file of the data etc. Now I wanted to try an upgrade to a newer version but concerned about ability to restore data from the tarball. Does anyone have any idea of how I can effect a restart before running to do an Upgrade? Thanks -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: Server Shutdown, Start Restart
Joseph E. Maxwell wrote: FreeBSD / UNIX platform, MySQL ver.4.0.16 Prob. of growing /tmp file, solved by introducing a cron job to clean up the folder intermittently. Prob.solve but new one created - mysql socket wiped out. Could not restart the server with all the standard methods. Complained of other running processes. Killed the orphaned processes runining. Aparently not. kill any process containing 'mysql' in the process name and restart the server. Alternatively: re-boot the server. But still can't restart. -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Reload mysqld configuration without restart?
Is it possible for mysqld to reload its configuration files without doing an explicit stop/start? I've searched the online documentation plus my copy of the DuBois book to no avail. The fact that the Debian init scripts don't do a proper config reload (just the GRANT tables) does not give me lots of hope. Thanks, J. Trammell -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
RE: Reload mysqld configuration without restart?
Thanks for replying. Some doc pages pertaining to this are: http://dev.mysql.com/doc/mysql/en/dynamic-system-variables.html http://dev.mysql.com/doc/mysql/en/system-variables.html Unfortunately I need to change some that are not dynamic. Many (most?) servers offer this functionality; it would be nice if MySQL had it. -Original Message- From: Gleb Paharenko [mailto:[EMAIL PROTECTED] Sent: Monday, July 18, 2005 1:10 PM To: mysql@lists.mysql.com Subject: Re: Reload mysqld configuration without restart? Hello. I don't know a general way to force MySQL Server to reread it's configuration file, however you could dynamically change lots of variables using SET @@global.xx syntax. FLUSH command could be helpful as well. See: http://dev.mysql.com/doc/mysql/en/system-variables.html http://dev.mysql.com/doc/mysql/en/flush.html John Trammell [EMAIL PROTECTED] wrote: Is it possible for mysqld to reload its configuration files without doing an explicit stop/start? I've searched the online documentation plus my copy of the DuBois book to no avail. The fact that the Debian init scripts don't do a proper config reload (just the GRANT tables) does not give me lots of hope. Thanks, J. Trammell -- For technical support contracts, goto https://order.mysql.com/?ref=ensita This email is sponsored by Ensita.NET http://www.ensita.net/ __ ___ ___ __ / |/ /_ __/ __/ __ \/ /Gleb Paharenko / /|_/ / // /\ \/ /_/ / /__ [EMAIL PROTECTED] /_/ /_/\_, /___/\___\_\___/ MySQL AB / Ensita.NET ___/ www.mysql.com -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED] -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: Reload mysqld configuration without restart?
Hello. I don't know a general way to force MySQL Server to reread it's configuration file, however you could dynamically change lots of variables using SET @@global.xx syntax. FLUSH command could be helpful as well. See: http://dev.mysql.com/doc/mysql/en/system-variables.html http://dev.mysql.com/doc/mysql/en/flush.html John Trammell [EMAIL PROTECTED] wrote: Is it possible for mysqld to reload its configuration files without doing an explicit stop/start? I've searched the online documentation plus my copy of the DuBois book to no avail. The fact that the Debian init scripts don't do a proper config reload (just the GRANT tables) does not give me lots of hope. Thanks, J. Trammell -- For technical support contracts, goto https://order.mysql.com/?ref=ensita This email is sponsored by Ensita.NET http://www.ensita.net/ __ ___ ___ __ / |/ /_ __/ __/ __ \/ /Gleb Paharenko / /|_/ / // /\ \/ /_/ / /__ [EMAIL PROTECTED] /_/ /_/\_, /___/\___\_\___/ MySQL AB / Ensita.NET ___/ www.mysql.com -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
stop and restart mysql on freebsd?
I made a change to my.cnf and want it to restart mysqld_safe so it will re-read my.cnf. How do I do this? Thanks, Chip -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: stop and restart mysql on freebsd?
Someone else may have to chime in, but I think this will work: mysqladmin -u root -p refresh According to the help refresh will Flush all tables and close and open logfiles. You may have to try it. Worst case just issue a shutdown and then start it up again. Scott Chip Wiegand wrote: I made a change to my.cnf and want it to restart mysqld_safe so it will re-read my.cnf. How do I do this? Thanks, Chip -- Scott Baker Canby Telephone - Network Administrator - RHCE Ph: 503.266.8253 -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: stop and restart mysql on freebsd?
In the last episode (Mar 04), Chip Wiegand said: I made a change to my.cnf and want it to restart mysqld_safe so it will re-read my.cnf. How do I do this? /usr/local/etc/rc.d/mysql-server.sh restart -- Dan Nelson [EMAIL PROTECTED] -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
updates after restart MySQL 4.0.18
Hi everyone, Our server crashed the Two questions : 1) is it normal to have a dramatic amount of UPDATES after a MySQL restart after crash ? 2) how to get valuable information from the following? ; Crash from 20/12/04 at 20.10(?) from server.err : 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=838860800 read_buffer_size=104853504 max_used_connections=63 max_connections=400 threads_connected=17 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 3930556 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. thd=0xb478f518 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=0xb57c2c0c, backtrace may not be correct. Stack range sanity check OK, backtrace follows: 0x80f7893 0x40094e48 0x4690f068 0x82302c1 0x819f373 0x815d4e2 0x8105657 0x810868d 0x8103321 0x8102eb8 0x810280d 0x4008edac 0x40254a8a New value of fp=(nil) failed sanity check, terminating stack trace! Please read http://www.mysql.com/doc/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 0xb507fe68 is invalid pointer thd-thread_id=5725700 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. 041220 20:10:52 InnoDB: Database was not shut down normally. InnoDB: Starting recovery from log files... InnoDB: Starting log scan based on checkpoint at InnoDB: log sequence number 9 2043063838 InnoDB: Doing recovery: scanned up to log sequence number 9 2047101097 041220 20:10:53 InnoDB: Starting an apply batch of log records to the database... InnoDB: Progress in percents: 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 InnoDB: Apply batch completed 041220 20:10:55 InnoDB: Flushing modified pages from the buffer pool... 041220 20:10:57 InnoDB: Started /var/lib/mysql/MySQL4.0.18/libexec/mysqld: ready for connections. Version: '4.0.18-log' socket: '/var/lib/mysql/MySQL4.0.18/var/mysql4.0.18.sock' port: 3306 Resolve stack : [EMAIL PROTECTED] ~mysql/tmp]# resolve_stack_dump -s /tmp/mysqld.sym -n mysqld.stack 0x80f7893 handle_segfault + 399 0x40094e48 _end + 936804128 0x4690f068 _end + 1046356288 0x82302c1 lock_print_info + 1573 0x819f373 srv_sprintf_innodb_monitor + 507 0x815d4e2 _Z18innodb_show_statusP3THD + 138 0x8105657 _Z21mysql_execute_commandv + 5999 0x810868d _Z11mysql_parseP3THDPcj + 329 0x8103321 _Z16dispatch_command19enum_server_commandP3THDPcj + 1069 0x8102eb8 _Z10do_commandP3THD + 100 0x810280d handle_one_connection + 841 0x4008edac _end + 936779396 0x40254a8a _end + 938638178 [EMAIL PROTECTED] ~mysql/tmp]# Thanks in advance. -- Dilipan Sebastiampillai London -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Restart of Mysql and tomcat error
Hello Since that list is wonderfull to solve my problem, I will try again. But this might not be the best place since the problem concerns mysql access througt tomcat (jakarta-tomcat-5.0.28). The java application we have, when start after a mysql restart (night backup) , will give an error (reset of the connection) for the first person that log in. Then all subsequent logging will be fine until a mysql restart. How can I prevent that? Johanne Duhaime IRCM
Re: Restart of Mysql and tomcat error
Duhaime Johanne wrote: Hello Since that list is wonderfull to solve my problem, I will try again. But this might not be the best place since the problem concerns mysql access througt tomcat (jakarta-tomcat-5.0.28). The java application we have, when start after a mysql restart (night backup) , will give an error (reset of the connection) for the first person that log in. Then all subsequent logging will be fine until a mysql restart. How can I prevent that? Johanne Duhaime IRCM Johanne, It sounds like tomcat thing. You could get around it by setting up replication and taking the slave db off line instead of the main db. It'd probably be a good idea anyway since your only cost is a little bit of time and some cheap hardware. walt -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
RE: Restart of Mysql and tomcat error
Johanne, There are numerous questions about connection methods, pooling etc that would be better asked in the tomcat list and would require work in your web application. However, putting on my pragmatic system integrator hat, could you get round this by simply doing a request to your application using wget at the end of your MySQL backup script? Worth considering, Andy -Original Message- From: Duhaime Johanne [mailto:[EMAIL PROTECTED] Sent: 15 December 2004 19:22 To: [EMAIL PROTECTED] Subject: Restart of Mysql and tomcat error Hello Since that list is wonderfull to solve my problem, I will try again. But this might not be the best place since the problem concerns mysql access througt tomcat (jakarta-tomcat-5.0.28). The java application we have, when start after a mysql restart (night backup) , will give an error (reset of the connection) for the first person that log in. Then all subsequent logging will be fine until a mysql restart. How can I prevent that? Johanne Duhaime IRCM -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
prepared statements and server restart
I tried to browse through the documentation to figure out what happens with prepared statements if the server is restarted while the prepared statement is assigned an ID and is being used repeatedly. The client then silently reconnects (reconnect flag is set). Is the expected behaviour for the client application to re-prepare the statements or should the client library silently re-send the statement to the server? Pete -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
warming the cache after restart
Good Afternoon. I'm interested if any DBAs on the list have a set of scripts they run after a server restart to pull commonly accessed data into the the query and key caches. I'm currently working on a script that will run various queries from our application against the database servers after restart, in hopes that it will shorten the amount of time it takes for the caches to fill and stabalize. I'm excited to see that MySQL 4.1.1 will have direct commands to do some of this, (see http://dev.mysql.com/doc/mysql/en/LOAD_INDEX.html), but that doesn't help me now... Is there anyone else on this list who has looked at this issue or can point me in the direction of more information about it? thanks a bunch, jenni -- Jennifer Snyder Database Administrator Tribe Networks, Inc. www.tribe.net -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
MySQL 5.0.1 won't restart
I'm running Windows 2000 and MySQL 5.0.1. When I tried to restart the service, it won't start up again, error message saying to try again in 30 minutes. After waiting for 30 minutes, it still bring up same error message. What might be the cause? Scott -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
mysqld process hanging -- can't restart
Hi, I'm having a problem every so often with the following error message: 040718 15:21:59 InnoDB: Started /usr/sbin/mysqld: ready for connections. Version: '4.0.16-standard' socket: '/var/lib/mysql/mysql.sock' port: 3306 Number of processes running now: 1 mysqld process hanging, pid 12141 - killed 040719 17:35:54 mysqld restarted 040719 17:35:54 Can't start server: Bind on TCP/IP port: Address already in use 040719 17:35:54 Do you already have another mysqld server running on port: 3306 ? 040719 17:35:54 Aborting 040719 17:35:54 /usr/sbin/mysqld: Shutdown Complete 040719 17:35:54 mysqld ended 040719 23:09:12 mysqld started As you can see, I didn't notice the server was down until a couple hours later. A lot of people have said I should check to see what process it running on port 3306 but I'm never there when this happens. In any case, it seems pretty clear to me that MySQL isn't all the way shutdown when it tries to start back up again. When I manually have to restart the server it usually takes 10-20 seconds depending on it's current load; the above error message only seems to give a fraction of a second for the server to shutdown. What I can I do to fix this? -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Please HELP !!! Can not restart server
Hi, MySQL Gurus, Version of mysql is Distrib 3.23.54, for redhat-linux-gnu (i386). I started mysql server with 'safe_mysqld --user=root ' . Then I found some variables needs to be optimized. SO I shut it down with 'mysqladmin -p shutdown' using root. But I was connected to the mysql server at the moment as ginger thru another connection. But the server is down all right (at least to me). Then I logged out in my connection as ginger to mysql server. Then I changed the variables in /etc/my.cnf and try to bring up the server using 'safe_mysqld --user=root '. Here is what I got: /usr/usr/bin/safe_mysqld --user=root /usrStarting mysqld daemon with databases from /var/lib/mysql 040408 08:00:06 mysqld ended [1]+ Done/usr/bin/safe_mysqld --user=root I moved the old mysql under datadir to another place and run 'mysql_install_db'. Then I run 'safe_mysqld --user=root '. Still the same thing. I even tried to restart the server again but it does not work either. I have also tried to restore the my.cnf file and there is no effect. Please help me. I need it to be fixed as soon as I can. Thank you so much ginger -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
RE: Please HELP !!! Can not restart server
Please look in your data directory and post the contents of the host name.ERR file that you find there. That will give folks the information they need to help solve your problem. -Original Message- From: Ginger Cheng [mailto:[EMAIL PROTECTED] Sent: Thursday, April 08, 2004 10:21 AM To: [EMAIL PROTECTED] Subject: Please HELP !!! Can not restart server Hi, MySQL Gurus, Version of mysql is Distrib 3.23.54, for redhat-linux-gnu (i386). I started mysql server with 'safe_mysqld --user=root ' . Then I found some variables needs to be optimized. SO I shut it down with 'mysqladmin -p shutdown' using root. But I was connected to the mysql server at the moment as ginger thru another connection. But the server is down all right (at least to me). Then I logged out in my connection as ginger to mysql server. Then I changed the variables in /etc/my.cnf and try to bring up the server using 'safe_mysqld --user=root '. Here is what I got: /usr/usr/bin/safe_mysqld --user=root /usrStarting mysqld daemon with databases from /var/lib/mysql 040408 08:00:06 mysqld ended [1]+ Done/usr/bin/safe_mysqld --user=root I moved the old mysql under datadir to another place and run 'mysql_install_db'. Then I run 'safe_mysqld --user=root '. Still the same thing. I even tried to restart the server again but it does not work either. I have also tried to restore the my.cnf file and there is no effect. Please help me. I need it to be fixed as soon as I can. Thank you so much ginger -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
RE: Please HELP !!! Can not restart server
What information is being logged in *.err? -Original Message- From: Ginger Cheng To: [EMAIL PROTECTED] Sent: 4/8/04 10:20 AM Subject: Please HELP !!! Can not restart server Hi, MySQL Gurus, Version of mysql is Distrib 3.23.54, for redhat-linux-gnu (i386). I started mysql server with 'safe_mysqld --user=root ' . Then I found some variables needs to be optimized. SO I shut it down with 'mysqladmin -p shutdown' using root. But I was connected to the mysql server at the moment as ginger thru another connection. But the server is down all right (at least to me). Then I logged out in my connection as ginger to mysql server. Then I changed the variables in /etc/my.cnf and try to bring up the server using 'safe_mysqld --user=root '. Here is what I got: /usr/usr/bin/safe_mysqld --user=root /usrStarting mysqld daemon with databases from /var/lib/mysql 040408 08:00:06 mysqld ended [1]+ Done/usr/bin/safe_mysqld --user=root I moved the old mysql under datadir to another place and run 'mysql_install_db'. Then I run 'safe_mysqld --user=root '. Still the same thing. I even tried to restart the server again but it does not work either. I have also tried to restore the my.cnf file and there is no effect. Please help me. I need it to be fixed as soon as I can. Thank you so much ginger -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED] -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
RE: Please HELP !!! Can not restart server
I don't have such files. Unfortunately. Am I hopeless? -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
RE: Please HELP !!! Can not restart server
Here is the error msg: 040408 08:47:14 mysqld started Cannot initialize InnoDB as 'innodb_data_file_path' is not set. If you do not want to use transactional InnoDB tables, add a line skip-innodb to the [mysqld] section of init parameters in your my.cnf or my.ini. If you want to use InnoDB tables, add to the [mysqld] section, for example, innodb_data_file_path = ibdata1:10M:autoextend But to get good performance you should adjust for your hardware the InnoDB startup options listed in section 2 at http://www.innodb.com/ibman.html 040408 8:47:14 /usr/libexec/mysqld: Table 'mysql.host' doesn't exist 040408 08:47:14 mysqld ended But I am not sure how to fix it. Could anyone help. Thanks ginger -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
RE: Please HELP !!! Can not restart server
I got it fixed with the msg from --err-log. THank you so much for all your help. I couldn't have made it without your hints. ALl the best ginger -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: Please HELP !!! Can not restart server
Ginger Cheng [EMAIL PROTECTED] wrote: Here is the error msg: 040408 08:47:14 mysqld started Cannot initialize InnoDB as 'innodb_data_file_path' is not set. If you do not want to use transactional InnoDB tables, add a line skip-innodb to the [mysqld] section of init parameters in your my.cnf or my.ini. If you want to use InnoDB tables, add to the [mysqld] section, for example, innodb_data_file_path = ibdata1:10M:autoextend But to get good performance you should adjust for your hardware the InnoDB startup options listed in section 2 at http://www.innodb.com/ibman.html 040408 8:47:14 /usr/libexec/mysqld: Table 'mysql.host' doesn't exist 040408 08:47:14 mysqld ended But I am not sure how to fix it. Could anyone help. If you didn't install privilege tables you must run mysql_install_db script. Otherwise check permissions on the MySQL data dir. -- For technical support contracts, goto https://order.mysql.com/?ref=ensita This email is sponsored by Ensita.net http://www.ensita.net/ __ ___ ___ __ / |/ /_ __/ __/ __ \/ /Victoria Reznichenko / /|_/ / // /\ \/ /_/ / /__ [EMAIL PROTECTED] /_/ /_/\_, /___/\___\_\___/ MySQL AB / Ensita.net ___/ www.mysql.com -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: MySql died a hard death after using grant and won't restart
perror 145 145 = Table was marked as crashed and should be repaired. Run myisamchk on it. David Rankin wrote: I can't figure this out. I'm setting privileges for access on a local net to a user [EMAIL PROTECTED] using grant and all of a sudden mysql is dead. I'm running 3.23.31 on Mandrake 7.2. I haven't had any problems in years. Anybody got any thoughts on this? Please reply to [EMAIL PROTECTED] What in the heck could cause a Bogus stack limit or frame pointer, aborting backtrace ?? The applicable part of the .err log is: mysqld got signal 11; The manual section 'Debugging a MySQL server' tells you how to use a stack trace and/or the core file to produce a readable backtrace that may help in finding out why mysqld died Attemping backtrace. You can use the following information to find out where mysqld died. If you see no messages after this, something went terribly wrong Bogus stack limit or frame pointer, aborting backtrace Number of processes running now: 0 031211 20:38:21 mysqld restarted 031211 20:38:21 Found invalid password for user: '[EMAIL PROTECTED]'; Ignoring user /usr/sbin/mysqld: ready for connections 031211 21:40:40 /usr/sbin/mysqld: Normal shutdown 031211 21:40:40 /usr/sbin/mysqld: Shutdown Complete 031211 21:40:40 mysqld ended 031211 21:40:47 mysqld started 031211 21:40:47 /usr/sbin/mysqld: Can't open file: 'user.MYD'. (errno: 145) 031211 21:40:47 mysqld ended next I mv /datadir/mysql /datadir/mysql-old then do a mysql_install_db and try again. Same error results mysqld got signal 11; The manual section 'Debugging a MySQL server' tells you how to use a stack trace and/or the core file to produce a readable backtrace that may help in finding out why mysqld died Attemping 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, ebp=0xb, backtrace may not be correct Bogus stack limit or frame pointer, aborting backtrace -- David C. Rankin, J.D., P.E. Rankin * Bertin, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 (936) 715-9333 (936) 715-9339 fax -- -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: MySql died a hard death after using grant and won't restart
Thanks for the reply Gerald. I took your advise and tried myisamchk with the following results: [EMAIL PROTECTED] mysql]# myisamchk -r user.* myisamchk: error: 'user.frm' doesn't have a correct index definition. You need to recreate it before you can do a repair - myisamchk: error: 'user.MYD' doesn't have a correct index definition. You need to recreate it before you can do a repair - - recovering (with sort) MyISAM-table 'user.MYI' Data records: 6 - Fixing index 1 Being relatively new to mysql, I am just getting my actual databases/tables set up so wiping out the entire mysql database and starting over is an option. Any thoughts on where I go from here?? I tried the -o option same results. Here are the results from myisamchk -r for the entire mysql directory. The results don't make sense to me. How could everything need to be rebuilt?? [EMAIL PROTECTED] mysql]# myisamchk -r *.* myisamchk: error: 'columns_priv.frm' doesn't have a correct index definition. You need to recreate it before you can do a repair - myisamchk: error: -1 when opening MyISAM-table 'columns_priv.MYD' - - recovering (with keycache) MyISAM-table 'columns_priv.MYI' Data records: 0 - myisamchk: error: 'db.frm' doesn't have a correct index definition. You need to recreate it before you can do a repair - myisamchk: error: 'db.MYD' doesn't have a correct index definition. You need to recreate it before you can do a repair - - recovering (with sort) MyISAM-table 'db.MYI' Data records: 3 - Fixing index 1 - Fixing index 2 - myisamchk: error: 'func.frm' doesn't have a correct index definition. You need to recreate it before you can do a repair - myisamchk: error: -1 when opening MyISAM-table 'func.MYD' - - recovering (with keycache) MyISAM-table 'func.MYI' Data records: 0 - myisamchk: error: 'host.frm' doesn't have a correct index definition. You need to recreate it before you can do a repair - myisamchk: error: -1 when opening MyISAM-table 'host.MYD' - - recovering (with keycache) MyISAM-table 'host.MYI' Data records: 0 - myisamchk: error: 'tables_priv.frm' doesn't have a correct index definition. You need to recreate it before you can do a repair - myisamchk: error: -1 when opening MyISAM-table 'tables_priv.MYD' - - recovering (with keycache) MyISAM-table 'tables_priv.MYI' Data records: 0 - myisamchk: error: 'user.frm' doesn't have a correct index definition. You need to recreate it before you can do a repair - myisamchk: error: 'user.MYD' doesn't have a correct index definition. You need to recreate it before you can do a repair - - recovering (with sort) MyISAM-table 'user.MYI' Data records: 6 - Fixing index 1 [EMAIL PROTECTED] mysql]# Any help would be appreciated!! -- David C. Rankin, J.D., P.E. RANKIN * BERTIN, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 (936) 715-9333 (936) 715-9339 fax -- - Original Message - From: gerald_clark [EMAIL PROTECTED] To: David Rankin [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Sent: Friday, December 12, 2003 8:37 AM Subject: Re: MySql died a hard death after using grant and won't restart perror 145 145 = Table was marked as crashed and should be repaired. Run myisamchk on it. David Rankin wrote: I can't figure this out. I'm setting privileges for access on a local net to a user [EMAIL PROTECTED] using grant and all of a sudden mysql is dead. I'm running 3.23.31 on Mandrake 7.2. I haven't had any problems in years. Anybody got any thoughts on this? Please reply to [EMAIL PROTECTED] What in the heck could cause a Bogus stack limit or frame pointer, aborting backtrace ?? The applicable part of the .err log is: mysqld got signal 11; The manual section 'Debugging a MySQL server' tells you how to use a stack trace and/or the core file to produce a readable backtrace that may help in finding out why mysqld died Attemping backtrace. You can use the following information to find out where mysqld died. If you see no messages after this, something went terribly wrong Bogus stack limit or frame pointer, aborting backtrace Number of processes running now: 0 031211 20:38:21 mysqld restarted 031211 20:38:21 Found invalid password for user: '[EMAIL PROTECTED]'; Ignoring user /usr/sbin/mysqld: ready for connections 031211 21:40:40 /usr/sbin/mysqld: Normal shutdown 031211 21:40:40 /usr/sbin/mysqld: Shutdown Complete 031211 21:40:40 mysqld ended 031211 21:40:47 mysqld started 031211 21:40:47 /usr/sbin/mysqld: Can't open file: 'user.MYD'. (errno: 145) 031211 21:40:47 mysqld ended next I mv /datadir/mysql /datadir/mysql-old then do a mysql_install_db and try again. Same error results mysqld got signal 11; The manual section 'Debugging a MySQL server' tells you how to use a stack trace and/or the core file to produce a readable
Re: MySql died a hard death after using grant and won't restart
Gerald, I spoke too soon. myisamchk seemed to have worked !!! I now have mysql running again and it seems happy. Now if I can just figure out the privileges to put into the db table to allow my local users to be able to connect though their browsers, I'll really have made progress. Thank you for your help! -- David C. Rankin, J.D., P.E. RANKIN * BERTIN, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 (936) 715-9333 (936) 715-9339 fax -- - Original Message - From: gerald_clark [EMAIL PROTECTED] To: David Rankin [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Sent: Friday, December 12, 2003 8:37 AM Subject: Re: MySql died a hard death after using grant and won't restart perror 145 145 = Table was marked as crashed and should be repaired. Run myisamchk on it. David Rankin wrote: I can't figure this out. I'm setting privileges for access on a local net to a user [EMAIL PROTECTED] using grant and all of a sudden mysql is dead. I'm running 3.23.31 on Mandrake 7.2. I haven't had any problems in years. Anybody got any thoughts on this? Please reply to [EMAIL PROTECTED] What in the heck could cause a Bogus stack limit or frame pointer, aborting backtrace ?? The applicable part of the .err log is: mysqld got signal 11; The manual section 'Debugging a MySQL server' tells you how to use a stack trace and/or the core file to produce a readable backtrace that may help in finding out why mysqld died Attemping backtrace. You can use the following information to find out where mysqld died. If you see no messages after this, something went terribly wrong Bogus stack limit or frame pointer, aborting backtrace Number of processes running now: 0 031211 20:38:21 mysqld restarted 031211 20:38:21 Found invalid password for user: '[EMAIL PROTECTED]'; Ignoring user /usr/sbin/mysqld: ready for connections 031211 21:40:40 /usr/sbin/mysqld: Normal shutdown 031211 21:40:40 /usr/sbin/mysqld: Shutdown Complete 031211 21:40:40 mysqld ended 031211 21:40:47 mysqld started 031211 21:40:47 /usr/sbin/mysqld: Can't open file: 'user.MYD'. (errno: 145) 031211 21:40:47 mysqld ended next I mv /datadir/mysql /datadir/mysql-old then do a mysql_install_db and try again. Same error results mysqld got signal 11; The manual section 'Debugging a MySQL server' tells you how to use a stack trace and/or the core file to produce a readable backtrace that may help in finding out why mysqld died Attemping 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, ebp=0xb, backtrace may not be correct Bogus stack limit or frame pointer, aborting backtrace -- David C. Rankin, J.D., P.E. Rankin * Bertin, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 (936) 715-9333 (936) 715-9339 fax -- -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: MySql died a hard death after using grant and won't restart
You might consider using Grant instead of editing the permissions table manually. Follow this link for the appropriate section of the manual: http://www.mysql.com/doc/en/GRANT.html -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: MySql died a hard death after using grant and won't restart - FIXED!!
Thanks Gerald! I'm replying to my self for the benefit of anyone else who has the mysql user.MYD file get corrupted. As root change to the mysql/mysql directory. run myisamchk -r *.* Ignore the errors. Start mysql. Pray your mysql root password isn't corrupt and your through. My root password was corrupt, but thank God I had created a second super user account and was able to fix the root password in the user table from the second account --- whew.. -- David C. Rankin, J.D., P.E. RANKIN * BERTIN, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 (936) 715-9333 (936) 715-9339 fax -- - Original Message - From: gerald_clark [EMAIL PROTECTED] To: David Rankin [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Sent: Friday, December 12, 2003 8:37 AM Subject: Re: MySql died a hard death after using grant and won't restart perror 145 145 = Table was marked as crashed and should be repaired. Run myisamchk on it. David Rankin wrote: I can't figure this out. I'm setting privileges for access on a local net to a user [EMAIL PROTECTED] using grant and all of a sudden mysql is dead. I'm running 3.23.31 on Mandrake 7.2. I haven't had any problems in years. Anybody got any thoughts on this? Please reply to [EMAIL PROTECTED] What in the heck could cause a Bogus stack limit or frame pointer, aborting backtrace ?? The applicable part of the .err log is: mysqld got signal 11; The manual section 'Debugging a MySQL server' tells you how to use a stack trace and/or the core file to produce a readable backtrace that may help in finding out why mysqld died Attemping backtrace. You can use the following information to find out where mysqld died. If you see no messages after this, something went terribly wrong Bogus stack limit or frame pointer, aborting backtrace Number of processes running now: 0 031211 20:38:21 mysqld restarted 031211 20:38:21 Found invalid password for user: '[EMAIL PROTECTED]'; Ignoring user /usr/sbin/mysqld: ready for connections 031211 21:40:40 /usr/sbin/mysqld: Normal shutdown 031211 21:40:40 /usr/sbin/mysqld: Shutdown Complete 031211 21:40:40 mysqld ended 031211 21:40:47 mysqld started 031211 21:40:47 /usr/sbin/mysqld: Can't open file: 'user.MYD'. (errno: 145) 031211 21:40:47 mysqld ended next I mv /datadir/mysql /datadir/mysql-old then do a mysql_install_db and try again. Same error results mysqld got signal 11; The manual section 'Debugging a MySQL server' tells you how to use a stack trace and/or the core file to produce a readable backtrace that may help in finding out why mysqld died Attemping 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, ebp=0xb, backtrace may not be correct Bogus stack limit or frame pointer, aborting backtrace -- David C. Rankin, J.D., P.E. Rankin * Bertin, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 (936) 715-9333 (936) 715-9339 fax -- -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
MySql died a hard death after using grant and won't restart
I can't figure this out. I'm setting privileges for access on a local net to a user [EMAIL PROTECTED] using grant and all of a sudden mysql is dead. I'm running 3.23.31 on Mandrake 7.2. I haven't had any problems in years. Anybody got any thoughts on this? Please reply to [EMAIL PROTECTED] What in the heck could cause a Bogus stack limit or frame pointer, aborting backtrace ?? The applicable part of the .err log is: mysqld got signal 11; The manual section 'Debugging a MySQL server' tells you how to use a stack trace and/or the core file to produce a readable backtrace that may help in finding out why mysqld died Attemping backtrace. You can use the following information to find out where mysqld died. If you see no messages after this, something went terribly wrong Bogus stack limit or frame pointer, aborting backtrace Number of processes running now: 0 031211 20:38:21 mysqld restarted 031211 20:38:21 Found invalid password for user: '[EMAIL PROTECTED]'; Ignoring user /usr/sbin/mysqld: ready for connections 031211 21:40:40 /usr/sbin/mysqld: Normal shutdown 031211 21:40:40 /usr/sbin/mysqld: Shutdown Complete 031211 21:40:40 mysqld ended 031211 21:40:47 mysqld started 031211 21:40:47 /usr/sbin/mysqld: Can't open file: 'user.MYD'. (errno: 145) 031211 21:40:47 mysqld ended next I mv /datadir/mysql /datadir/mysql-old then do a mysql_install_db and try again. Same error results mysqld got signal 11; The manual section 'Debugging a MySQL server' tells you how to use a stack trace and/or the core file to produce a readable backtrace that may help in finding out why mysqld died Attemping 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, ebp=0xb, backtrace may not be correct Bogus stack limit or frame pointer, aborting backtrace -- David C. Rankin, J.D., P.E. Rankin * Bertin, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 (936) 715-9333 (936) 715-9339 fax -- -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: mysqld shows high cpu usage over extended time, restart = normal
On Wed, Jul 09, 2003 at 01:08:56PM -0400, Dave [Hawk-Systems] wrote: load). Is there a known issue (running on FreeBSD 4.8, MySQL 3.23.55 MyISAM)? its been a known issue for quite a long time use linuxthreaded version and it should work fine. although much of work has been done on threads implementation, there are still such problems with mysql. it happens even on freebsd 5.0 Thanks Terry... gave me enough information to google the following which went into further detail regarding this issue specifically on FreeBSD http://jeremy.zawodny.com/blog/archives/000203.html Yes. LinuxThreads + MySQL + FreeBSD 4.x == Good -- Jeremy D. Zawodny | Perl, Web, MySQL, Linux Magazine, Yahoo! [EMAIL PROTECTED] | http://jeremy.zawodny.com/ MySQL 4.0.13: up 7 days, processed 217,907,314 queries (348/sec. avg) -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
mysqld shows high cpu usage over extended time, restart = normal
Occasionally in checking one of the servers, I noticed that mysql shows 85% + of cpu usage essentially leaving the server at 0% idle. After monitoring it for a few hours, the status did not change. After a stop and start of mysql, things progessed normally. Checking back a few days later I noticed it was once again sitting up there at 95% (or thereabouts) and doing nothing of value from what i could tell. Have restarted MySQL during peak usage times for that server and its database, and it has showed normal loads and CPU usage (approx 20% CPU with .1 to .3 load). Is there a known issue (running on FreeBSD 4.8, MySQL 3.23.55 MyISAM)? Is there something I should check when next I notice the high CPU usage? Thanks Dave -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
RE: mysqld shows high cpu usage over extended time, restart = normal
hi, load). Is there a known issue (running on FreeBSD 4.8, MySQL 3.23.55 MyISAM)? its been a known issue for quite a long time use linuxthreaded version and it should work fine. although much of work has been done on threads implementation, there are still such problems with mysql. it happens even on freebsd 5.0 regards, terry -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: mysqld shows high cpu usage over extended time, restart = normal
On Wed, 2003-07-09 at 10:31, Dave [Hawk-Systems] wrote: Is there a known issue (running on FreeBSD 4.8, MySQL 3.23.55 MyISAM)? Is there something I should check when next I notice the high CPU usage? I used to see the same kind of behavior a while back with a MySQL installation I did for a client. It turned out that what was happening was a poorly designed client/server app was touching off this really huge query (lots of rows and lots of columns across multiple tables) and then disconnecting before the result could be returned. They fixed their app and the problem went away. Drove me nuts troubleshooting it. Anyway. Make sure you don't have something similar going on. -- Peter L. Berghold[EMAIL PROTECTED] Dog event enthusiast, brewer of Belgian (style) Ales. Happiness is having your contented dog at your side and a Belgian Ale in your glass. -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
RE: mysqld shows high cpu usage over extended time, restart = normal
load). Is there a known issue (running on FreeBSD 4.8, MySQL 3.23.55 MyISAM)? its been a known issue for quite a long time use linuxthreaded version and it should work fine. although much of work has been done on threads implementation, there are still such problems with mysql. it happens even on freebsd 5.0 Thanks Terry... gave me enough information to google the following which went into further detail regarding this issue specifically on FreeBSD http://jeremy.zawodny.com/blog/archives/000203.html Cheers, Dave -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
RE: mysqld shows high cpu usage over extended time, restart = normal
Is there a known issue (running on FreeBSD 4.8, MySQL 3.23.55 MyISAM)? Is there something I should check when next I notice the high CPU usage? I used to see the same kind of behavior a while back with a MySQL installation I did for a client. It turned out that what was happening was a poorly designed client/server app was touching off this really huge query (lots of rows and lots of columns across multiple tables) and then disconnecting before the result could be returned. They fixed their app and the problem went away. Drove me nuts troubleshooting it. Anyway. Make sure you don't have something similar going on. Will check again next time it occurs, but I don't recall seeing any other processes running at the time via mysqladmin -u root -p processlist After reading terry's post, I did come across the following resource though; http://jeremy.zawodny.com/blog/archives/000203.html thanks Dave -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
