Re: MySQL crashing.
On 07/15/2013 07:54 AM, Luis H. Forchesatto wrote: Greetings. I'm receiving the following error log often on my MySQL database server: [SNIP] I suggest you report a bug as suggested. -- Rares Aioanei -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql
MySQL crashing.
Greetings. I'm receiving the following error log often on my MySQL database server: 130715 8:40:18InnoDB: Assertion failure in thread 2974165904 in file btr0cur.c line 160 InnoDB: Failing assertion: page_is_comp(get_page) == page_is_comp(page) InnoDB: We intentionally generate a memory trap. InnoDB: Submit a detailed bug report to http://bugs.mysql.com. InnoDB: If you get repeated assertion failures or crashes, even InnoDB: immediately after the mysqld startup, there may be InnoDB: corruption in the InnoDB tablespace. Please refer to InnoDB: http://dev.mysql.com/doc/refman/5.0/en/forcing-recovery.html InnoDB: about forcing recovery. 130715 8:40:18 - 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=327155712 read_buffer_size=131072 max_used_connections=19 max_connections=1 threads_connected=6 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 3450801 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. thd=(nil) 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=0xb1460fc8, backtrace may not be correct. Stack range sanity check OK, backtrace follows: 0x81f22d3 0x839fb8a 0x83a0b0f 0x83ab815 0x837208e 0x8372855 0x8373948 0x835690a 0x83b6cfc 0x83397cf 0xb7f644fb 0xb7d78e5e New value of fp=(nil) failed sanity check, terminating stack trace! Please read http://dev.mysql.com/doc/mysql/en/using-stack-trace.html and follow instructions on how to resolve the stack trace. Resolved stack trace is much more helpful in diagnosing the problem, so please do resolve it 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. As it said it seems to be something related to InnoDB databases, but I got no idea on where to start looking for the error. Can someone post a troubleshoot for me to follow or contribute with speculations? -- Att.* *** Luis H. Forchesatto http://br.linkedin.com/pub/luis-henrique-forchesatto/73/684/a67
Re: XAMMP-MySQL crashing
I'm sorry for the delay in thanking those that offered help, I have not been able to look at this problem for a day or so, but thank you. And Thank you Martin for your note. I have not backed up anything on this, however it was really just a practice run, so I will not really lose anything, but a very good lesson. I did find a file that had all of the databases in it, I wonder if I copy all of those if I would be able to save whatever DB's I had. Thanks again and if anyone thinks of anything new, I would love to hear it. Gary ""Gary"" wrote in message news:20090711165227.4655.qm...@lists.mysql.com... >I have an issue that Mysql will not start on my local machine. I noticed a > few days ago on a restart that I got an error saying that Mysqld had > encountered a problem and had to close. I did not pay any attention to it > because I was not working in it for a bit. > > I then tried to start it today and got the same error message saying > mysqld.exe has encountered a problem and had to close. > > + Apache 2.2.11 > + MySQL 5.1.30 (Community Server) > + PHP 5.2.8 + PEAR (Support for PHP 4 has been discontinued) > + PHP-Switch win32 1.0 (use "php-switch.bat" in the xampp main directory) > + XAMPP Control Version 2.5 from www.nat32.com > + XAMPP Security 1.0 > + SQLite 2.8.15 > + OpenSSL 0.9.8i > + phpMyAdmin 3.1.1 > + ADOdb 4.990 > + Mercury Mail Transport System v4.52 > + FileZilla FTP Server 0.9.29 > + Webalizer 2.01-10 > + Zend Optimizer 3.3.0 > + eAccelerator 0.9.5.3 für PHP 5.2.8 (but not activated in the php.ini) > > Anyone have an idea to where I should start to look? > > Thanks > > Gary > > > > __ Information from ESET Smart Security, version of virus > signature database 4241 (20090714) __ > > The message was checked by ESET Smart Security. > > http://www.eset.com > > > __ Information from ESET Smart Security, version of virus signature database 4241 (20090714) __ The message was checked by ESET Smart Security. http://www.eset.com -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql?unsub=arch...@jab.org
Re: XAMMP-MySQL crashing
BTW, this is the error message that windows wanted to send to MS C:\DOCUME~1\GARYPA~1\LOCALS~1\Temp\WERd238.dir00\mysqld.exe.mdmp C:\DOCUME~1\GARYPA~1\LOCALS~1\Temp\WERd238.dir00\appcompat.txt "Carlos Proal" wrote in message news:4a58cb7c.4090...@gmail.com... > > Take a look on the my.ini to see if there is something wrong (maybe a path > pointing to a missing place or memory setting bigger than your actual RAM) > > Carlos > > On 7/11/2009 12:17 PM, Gary wrote: >> Not sure if this is it, it was the only .err file that I have. Also this >> seems to be the latest entry that has a date. >> >> Thanks for your help. >> >> Gary >> >> 090617 21:50:45 - mysqld got exception 0xc005 ; >> 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=16777216 >> read_buffer_size=262144 >> max_used_connections=0 >> max_threads=151 >> threads_connected=0 >> It is possible that mysqld could use up to >> key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = >> 133305 K >> bytes of memory >> Hope that's ok; if not, decrease some variables in the equation. >> >> thd: 0x0 >> 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... >> 006B8853mysqld.exe!??? >> The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html >> contains >> information that should help you find out what is causing the crash. >> 090627 9:35:07 - mysqld got exception 0xc005 ; >> 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. >> "Carlos Proal" wrote in message >> news:4a58c79b.2090...@gmail.com... >> >>> You have to take a look on the error log, a file named hostname.err >>> (hostname=your machine name) and should be located inside >>> the mysql dir on the xammp dir. >>> That file will give an insight about the problem, or you can post the >>> error here to get help. >>> >>> Carlos >>> >>> >>> On 7/11/2009 11:52 AM, Gary wrote: >>> I have an issue that Mysql will not start on my local machine. I noticed a few days ago on a restart that I got an error saying that Mysqld had encountered a problem and had to close. I did not pay any attention to it because I was not working in it for a bit. I then tried to start it today and got the same error message saying mysqld.exe has encountered a problem and had to close. + Apache 2.2.11 + MySQL 5.1.30 (Community Server) + PHP 5.2.8 + PEAR (Support for PHP 4 has been discontinued) + PHP-Switch win32 1.0 (use "php-switch.bat" in the xampp main directory) + XAMPP Control Version 2.5 from www.nat32.com + XAMPP Security 1.0 + SQLite 2.8.15 + OpenSSL 0.9.8i + phpMyAdmin 3.1.1 + ADOdb 4.990 + Mercury Mail Transport System v4.52 + FileZilla FTP Server 0.9.29 + Webalizer 2.01-10 + Zend Optimizer 3.3.0 + eAccelerator 0.9.5.3 für PHP 5.2.8 (but not activated in the php.ini) Anyone have an idea to where I should start to look? Thanks Gary >> >> >> >> > -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql?unsub=arch...@jab.org
Re: XAMMP-MySQL crashing
I dont see anything wrong, but then again I may not know wht to look for, this is the my.ini file # Example MySQL config file for small systems. # # This is for a system with little memory (<= 64M) where MySQL is only used # from time to time and it's important that the mysqld daemon # doesn't use much resources. # # You can copy this file to # C:/xampp/mysql/bin/my.cnf to set global options, # mysql-data-dir/my.cnf to set server-specific options (in this # installation this directory is C:/xampp/mysql/data) or # ~/.my.cnf to set user-specific options. # # In this file, you can use all long options that a program supports. # If you want to know which options a program supports, run the program # with the "--help" option. # The following options will be passed to all MySQL clients [client] # password = removed port= 3306 socket = "C:/xampp/mysql/mysql.sock" # Here follows entries for some specific programs # The MySQL server [mysqld] port= 3306 socket= "C:/xampp/mysql/mysql.sock" basedir="C:/xampp/mysql" tmpdir="C:/xampp/tmp" datadir="C:/xampp/mysql/data" skip-locking key_buffer = 16M max_allowed_packet = 1M table_cache = 64 sort_buffer_size = 512K net_buffer_length = 8K read_buffer_size = 256K read_rnd_buffer_size = 512K myisam_sort_buffer_size = 8M # Don't listen on a TCP/IP port at all. This can be a security enhancement, # if all processes that need to connect to mysqld run on the same host. # All interaction with mysqld must be made via Unix sockets or named pipes. # Note that using this option without enabling named pipes on Windows # (via the "enable-named-pipe" option) will render mysqld useless! # # commented in by lampp security #skip-networking skip-federated # Replication Master Server (default) # binary logging is required for replication # log-bin deactivated by default since XAMPP 1.4.11 #log-bin=mysql-bin # required unique id between 1 and 2^32 - 1 # defaults to 1 if master-host is not set # but will not function as a master if omitted server-id = 1 # Replication Slave (comment out master section to use this) # # To configure this host as a replication slave, you can choose between # two methods : # # 1) Use the CHANGE MASTER TO command (fully described in our manual) - #the syntax is: # #CHANGE MASTER TO MASTER_HOST=, MASTER_PORT=, #MASTER_USER=, MASTER_PASSWORD= ; # #where you replace , , by quoted strings and # by the master's port number (3306 by default). # #Example: # #CHANGE MASTER TO MASTER_HOST='125.564.12.1', MASTER_PORT=3306, #MASTER_USER='joe', MASTER_PASSWORD='secret'; # # OR # # 2) Set the variables below. However, in case you choose this method, then #start replication for the first time (even unsuccessfully, for example #if you mistyped the password in master-password and the slave fails to #connect), the slave will create a master.info file, and any later #change in this file to the variables' values below will be ignored and #overridden by the content of the master.info file, unless you shutdown #the slave server, delete master.info and restart the slaver server. #For that reason, you may want to leave the lines below untouched #(commented) and instead use CHANGE MASTER TO (see above) # # required unique id between 2 and 2^32 - 1 # (and different from the master) # defaults to 2 if master-host is set # but will not function as a slave if omitted #server-id = 2 # # The replication master for this slave - required #master-host = # # The username the slave will use for authentication when connecting # to the master - required #master-user = # # The password the slave will authenticate with when connecting to # the master - required #master-password = # # The port the master is listening on. # optional - defaults to 3306 #master-port = # # binary logging - not required for slaves, but recommended #log-bin=mysql-bin # Point the following paths to different dedicated disks #tmpdir = "C:/xampp/tmp" #log-update = /path-to-dedicated-directory/hostname # Uncomment the following if you are using BDB tables #bdb_cache_size = 4M #bdb_max_lock = 1 # Comment the following if you are using InnoDB tables #skip-innodb innodb_data_home_dir = "C:/xampp/mysql/" innodb_data_file_path = ibdata1:10M:autoextend innodb_log_group_home_dir = "C:/xampp/mysql/" #innodb_log_arch_dir = "C:/xampp/mysql/" ## You can set .._buffer_pool_size up to 50 - 80 % ## of RAM but beware of setting memory usage too high innodb_buffer_pool_size = 16M innodb_additional_mem_pool_size = 2M ## Set .._log_file_size to 25 % of buffer pool size innodb_log_file_size = 5M innodb_log_buffer_size = 8M innodb_flush_log_at_trx_commit = 1 innodb_lock_wait_timeout = 50 [mysqldump] quick max_allowed_packet = 16M [mysql] no-auto-rehash # Remove the next comment character if you are not familiar with SQL #safe-updates [isamchk] key_buffer = 20M sort_buffer_size = 20M read_buffer = 2M write_buffer
Re: XAMMP-MySQL crashing
Take a look on the my.ini to see if there is something wrong (maybe a path pointing to a missing place or memory setting bigger than your actual RAM) Carlos On 7/11/2009 12:17 PM, Gary wrote: Not sure if this is it, it was the only .err file that I have. Also this seems to be the latest entry that has a date. Thanks for your help. Gary 090617 21:50:45 - mysqld got exception 0xc005 ; 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=16777216 read_buffer_size=262144 max_used_connections=0 max_threads=151 threads_connected=0 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 133305 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. thd: 0x0 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... 006B8853mysqld.exe!??? The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains information that should help you find out what is causing the crash. 090627 9:35:07 - mysqld got exception 0xc005 ; 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. "Carlos Proal" wrote in message news:4a58c79b.2090...@gmail.com... You have to take a look on the error log, a file named hostname.err (hostname=your machine name) and should be located inside the mysql dir on the xammp dir. That file will give an insight about the problem, or you can post the error here to get help. Carlos On 7/11/2009 11:52 AM, Gary wrote: I have an issue that Mysql will not start on my local machine. I noticed a few days ago on a restart that I got an error saying that Mysqld had encountered a problem and had to close. I did not pay any attention to it because I was not working in it for a bit. I then tried to start it today and got the same error message saying mysqld.exe has encountered a problem and had to close. + Apache 2.2.11 + MySQL 5.1.30 (Community Server) + PHP 5.2.8 + PEAR (Support for PHP 4 has been discontinued) + PHP-Switch win32 1.0 (use "php-switch.bat" in the xampp main directory) + XAMPP Control Version 2.5 from www.nat32.com + XAMPP Security 1.0 + SQLite 2.8.15 + OpenSSL 0.9.8i + phpMyAdmin 3.1.1 + ADOdb 4.990 + Mercury Mail Transport System v4.52 + FileZilla FTP Server 0.9.29 + Webalizer 2.01-10 + Zend Optimizer 3.3.0 + eAccelerator 0.9.5.3 für PHP 5.2.8 (but not activated in the php.ini) Anyone have an idea to where I should start to look? Thanks Gary -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql?unsub=arch...@jab.org
Re: XAMMP-MySQL crashing
Not sure if this is it, it was the only .err file that I have. Also this seems to be the latest entry that has a date. Thanks for your help. Gary 090617 21:50:45 - mysqld got exception 0xc005 ; 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=16777216 read_buffer_size=262144 max_used_connections=0 max_threads=151 threads_connected=0 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 133305 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. thd: 0x0 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... 006B8853mysqld.exe!??? The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains information that should help you find out what is causing the crash. 090627 9:35:07 - mysqld got exception 0xc005 ; 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. "Carlos Proal" wrote in message news:4a58c79b.2090...@gmail.com... > > > You have to take a look on the error log, a file named hostname.err > (hostname=your machine name) and should be located inside > the mysql dir on the xammp dir. > That file will give an insight about the problem, or you can post the > error here to get help. > > Carlos > > > On 7/11/2009 11:52 AM, Gary wrote: >> I have an issue that Mysql will not start on my local machine. I noticed >> a >> few days ago on a restart that I got an error saying that Mysqld had >> encountered a problem and had to close. I did not pay any attention to it >> because I was not working in it for a bit. >> >> I then tried to start it today and got the same error message saying >> mysqld.exe has encountered a problem and had to close. >> >> + Apache 2.2.11 >> + MySQL 5.1.30 (Community Server) >> + PHP 5.2.8 + PEAR (Support for PHP 4 has been discontinued) >> + PHP-Switch win32 1.0 (use "php-switch.bat" in the xampp main >> directory) >> + XAMPP Control Version 2.5 from www.nat32.com >> + XAMPP Security 1.0 >> + SQLite 2.8.15 >> + OpenSSL 0.9.8i >> + phpMyAdmin 3.1.1 >> + ADOdb 4.990 >> + Mercury Mail Transport System v4.52 >> + FileZilla FTP Server 0.9.29 >> + Webalizer 2.01-10 >> + Zend Optimizer 3.3.0 >> + eAccelerator 0.9.5.3 für PHP 5.2.8 (but not activated in the php.ini) >> >> Anyone have an idea to where I should start to look? >> >> Thanks >> >> Gary >> >> >> >> > -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql?unsub=arch...@jab.org
Re: XAMMP-MySQL crashing
You have to take a look on the error log, a file named hostname.err (hostname=your machine name) and should be located inside the mysql dir on the xammp dir. That file will give an insight about the problem, or you can post the error here to get help. Carlos On 7/11/2009 11:52 AM, Gary wrote: I have an issue that Mysql will not start on my local machine. I noticed a few days ago on a restart that I got an error saying that Mysqld had encountered a problem and had to close. I did not pay any attention to it because I was not working in it for a bit. I then tried to start it today and got the same error message saying mysqld.exe has encountered a problem and had to close. + Apache 2.2.11 + MySQL 5.1.30 (Community Server) + PHP 5.2.8 + PEAR (Support for PHP 4 has been discontinued) + PHP-Switch win32 1.0 (use "php-switch.bat" in the xampp main directory) + XAMPP Control Version 2.5 from www.nat32.com + XAMPP Security 1.0 + SQLite 2.8.15 + OpenSSL 0.9.8i + phpMyAdmin 3.1.1 + ADOdb 4.990 + Mercury Mail Transport System v4.52 + FileZilla FTP Server 0.9.29 + Webalizer 2.01-10 + Zend Optimizer 3.3.0 + eAccelerator 0.9.5.3 für PHP 5.2.8 (but not activated in the php.ini) Anyone have an idea to where I should start to look? Thanks Gary -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql?unsub=arch...@jab.org
XAMMP-MySQL crashing
I have an issue that Mysql will not start on my local machine. I noticed a few days ago on a restart that I got an error saying that Mysqld had encountered a problem and had to close. I did not pay any attention to it because I was not working in it for a bit. I then tried to start it today and got the same error message saying mysqld.exe has encountered a problem and had to close. + Apache 2.2.11 + MySQL 5.1.30 (Community Server) + PHP 5.2.8 + PEAR (Support for PHP 4 has been discontinued) + PHP-Switch win32 1.0 (use "php-switch.bat" in the xampp main directory) + XAMPP Control Version 2.5 from www.nat32.com + XAMPP Security 1.0 + SQLite 2.8.15 + OpenSSL 0.9.8i + phpMyAdmin 3.1.1 + ADOdb 4.990 + Mercury Mail Transport System v4.52 + FileZilla FTP Server 0.9.29 + Webalizer 2.01-10 + Zend Optimizer 3.3.0 + eAccelerator 0.9.5.3 für PHP 5.2.8 (but not activated in the php.ini) Anyone have an idea to where I should start to look? Thanks Gary -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql?unsub=arch...@jab.org
Mysql crashing every now and then
Hello, our mysql 5.0.67 on a AMD Opteron 2218 with 2 GB RAM is crashing from time to time. This what is in the log: 081028 6:37:30 - mysqld got signal 11 ; This could be because you hit a bug. It is also possible that this binary or one of the libraries it was linked against is corrupt, improperly built, or misconfigured. This error can also be caused by malfunctioning hardware. We will try our best to scrape up some info that will hopefully help diagnose the problem, but since we have already crashed, something is definitely wrong and this may fail. key_buffer_size=402653184 read_buffer_size=2097152 max_used_connections=31 max_connections=1 threads_connected=2 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 41353216 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. thd=0x1fa7feb0 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=0x4510b0e0, backtrace may not be correct. Stack range sanity check OK, backtrace follows: (nil) New value of fp=0x1fa7feb0 failed sanity check, terminating stack trace! Please read http://dev.mysql.com/doc/mysql/en/using-stack-trace.html and follow instructions on how to resolve the stack trace. Resolved stack trace is much more helpful in diagnosing the problem, so please do resolve it Trying to get some variables. Some pointers may be invalid and cause the dump to abort... thd->query at 0x201766f0 = SELECT DISTINCT session_id, DATE_FORMAT(access_time,'%Y-%m-%d %H:%i') as fmtDate, substring( access_time, 1, 0 ) AS dd, COUNT(access_time) as cnt FROM curry_stattraq WHERE session_id <> 0 GROUP BY session_id ORDER BY dd DESC LIMIT 0, 1000 thd->thread_id=682597 The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains information that should help you find out what is causing the crash. Number of processes running now: 0 081028 06:37:31 mysqld restarted InnoDB: The log sequence number in ibdata files does not match InnoDB: the log sequence number in the ib_logfiles! 081028 6:37:31 InnoDB: Database was not shut down normally! InnoDB: Starting crash recovery. InnoDB: Reading tablespace information from the .ibd files... InnoDB: Restoring possible half-written data pages from the doublewrite InnoDB: buffer... 081028 6:37:50 InnoDB: Started; log sequence number 0 1081908061 081028 6:37:51 [Note] /vrmd/mysql/mysql-5.0.67/libexec/mysqld: ready for connections. Version: '5.0.67-log' socket: '/tmp/mysql.sock' port: 3306 Source distribution Although the log doesn't state the database name, I found out the specific database. I'm a bit astounded that anything might be wrong with the tables, since we did a rebuild (mysqldump and import) of all tables. To be sure, I started a repair table anyway: mysql> repair table curry_stattraq; +++--+--+ | Table | Op | Msg_type | Msg_text | +++--+--+ | db18841.curry_stattraq | repair | status | OK | +++--+--+ 1 row in set (10.06 sec) Now I was trying to do the sql query: mysql> SELECT DISTINCT session_id, DATE_FORMAT(access_time,'%Y-%m-%d %H:%i') as fmtDate, substring( access_time, 1, 0 ) AS dd, COUNT(access_time) as cnt FROM curry_stattraq WHERE session_id <> 0 GROUP BY session_id ORDER BY dd DESC LIMIT 0, 1000; ERROR 2013 (HY000): Lost connection to MySQL server during query What is mysql doing here? Why does it crash? The table seems to be fine and there is enough RAM and CPU left to process the query. Any ideas? Kind regards Marten -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
MySQL crashing on flush-logs
We have MySQL 5.0.27 running on about 10 different RedHat EL4 boxes, all from the same RPMs. Every night we run mysqladmin flush-logs from crontab (as well as some other things) on most of these servers. One on server, mysqld is dying with signal 11 every single night right during the mysqladmin flush-logs command. None of the others ever do that. This is repeatable. It happens every night. We're investigating possible causes, but in the meantime I'm also curious if anyone else on this list has run into something similar and has some suggestions. Here's the backtrace portion of the error log from the most recent crash: | 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=0x45394f78, backtrace may not be correct. | Stack range sanity check OK, backtrace follows: | 0x5f737400746f6f72 | New value of fp=0x1874230 failed sanity check, terminating stack trace! | Please read http://dev.mysql.com/doc/mysql/en/Using_stack_trace.html and follow instructions on how to resolve the stack | trace. Resolved | stack trace is much more helpful in diagnosing the problem, so please do | resolve it | Trying to get some variables. | Some pointers may be invalid and cause the dump to abort... | thd->query at (nil) is invalid pointer | thd->thread_id=12310 -- Cos -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Need help on mysql crashing.
Hi, My mysql is crashing. Below table has the values it logs in the .err file before restarting. I am using the large.cnf file. The parameters I have changed are below. Rest are default values. #for performance SSR log=/var/log/mysql-queries.log join_buffer_size=1M max_connections=300 query_cache_size=64M query_cache_limit=2M #for performance SSR ERROR LOG TABLE === KBS : key_buffer_size RBS : read_buffer_size MUC : max_used_connections MC : max_connections TC : threads_connected All values are in KB. == TimeKBS RBS MUC MC TC TOTAL == 10:12:17268435456 1044480 251 300 197 875341 10:44:42268435456 1044480 209 300 158 875341 11:38:56268435456 1044480 176 300 124 875341 12:42:32268435456 1044480 187 300 134 875341 13:52:07268435456 1044480 152 300 96 875341 14:44:58268435456 1044480 154 300 106 875341 15:07:00268435456 1044480 150 300 94 875341 15:42:41268435456 1044480 150 300 100 875341 17:01:44268435456 1044480 162 300 101 875341 17:29:32268435456 1044480 133 300 81 875341 01:04:39268435456 1044480 155 300 107 875341 01:44:27268435456 1044480 190 300 139 875341 03:10:32268435456 1044480 185 300 120 875341 04:14:23268435456 1044480 276 300 220 875341 04:33:57268435456 1044480 204 300 152 875341 04:58:44268435456 1044480 233 300 179 875341 05:43:09268435456 1044480 265 300 213 875341 06:13:44268435456 1044480 210 300 155 875341 07:08:56268435456 1044480 186 300 133 875341 07:44:21268435456 1044480 250 250 203 773142 08:43:03268435456 1044480 250 250 195 773142 09:00:13268435456 1044480 193 250 142 773142 09:18:56268435456 1044480 286 300 235 875341 09:38:14268435456 1044480 211 300 152 875341 09:59:23268435456 1044480 181 300 116 875341 10:55:17268435456 1044480 196 300 137 875341 11:17:44268435456 1044480 154 300 99 875341 12:14:36268435456 1044480 147 300 87 875341 12:33:16268435456 1044480 214 300 162 875341 13:06:38268435456 1044480 189 300 124 875341 14:21:07268435456 1044480 164 300 100 875341 14:54:37268435456 1044480 167 300 116 875341 15:43:06268435456 1044480 130 300 69 875341 16:24:04268435456 1044480 134 300 68 875341 17:37:24268435456 1044480 126 300 78 875341 == -Sunil Sunder Raj -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
mysql crashing on osx 10.3.9
I'm running a dual G5 xserve with OSXS 10.3.9. Mysql version 4.0.24 (the version that ships with the OS). For many months now mysql has been stopping/crashing about twice a week. It's primary purpose in life is to provide the database for a minimally used Horde webmail setup. I've looked at the logs, and can find nothing that offers any indication of what is causing it to go down. I can also attest that it is truly dead, it is not present in the process list, and doing mysqladmin ping reports that there is no running server. Can anyone suggest additional steps for troubleshooting? thanks, Eben -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: mysql crashing after restore
Tomas, did you use rsync to copy the ibdata file of a RUNNING mysqld server? http://dev.mysql.com/doc/mysql/en/Backing_up.html Both MyISAM and InnoDB cache their data in memory while mysqld is running. The ibdata files, ib_logfiles, .MYI, .MYD files are not up to date in the file system. Your backup may be severely corrupt. Best regards, Heikki Tuuri Innobase Oy Foreign keys, transactions, and row level locking for MySQL InnoDB Hot Backup - a hot backup tool for InnoDB which also backs up MyISAM tables http://www.innodb.com/order.php Order MySQL technical support from https://order.mysql.com/ - Original Message - From: "Tomas Clements" <[EMAIL PROTECTED]> Newsgroups: mailing.database.myodbc Sent: Sunday, December 26, 2004 6:44 AM Subject: mysql crashing after restore Hello, I have a server that was using raid5. I also did a daily rsync from the machine. The raid5 failed and the data was lost. I recopied all of the data back to the machine from the backup. Most of which was a 133G ibdata1 file. Now when I try to start mysql I get the following: -- enough to kill the drive. 041225 22:19:56 mysqld started 041225 22:19:56 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 90 3664440544 InnoDB: Doing recovery: scanned up to log sequence number 90 3669579776 041225 22:19:56 InnoDB: Assertion failure in thread 16384 in file ../../innobase/in clude/page0page.ic line 482 InnoDB: Failing assertion: offs < UNIV_PAGE_SIZE InnoDB: We intentionally generate a memory trap. InnoDB: Send a detailed bug report to mysql@lists.mysql.com 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=8 read_buffer_size=16773120 max_used_connections=0 max_connections=1000 threads_connected=0 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 3403864 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. thd=0x8381228 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... Bogus stack limit or frame pointer, fp=0xbfffd9a8, stack_bottom=0x59f57c70, thread_s tack=196608, aborting backtrace. Trying to get some variables. Some pointers may be invalid and cause the dump to abort... thd->query at 0x58e0af80 is invalid pointer thd->thread_id=-1398035799 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. 041225 22:19:56 mysqld ended - It told me to submit this so I am. I don't know the cause of this. I believe that because the file was copied while in use (from the rsync) that it was not "closed" correctly. Because of that it's trying to scan the file for errors, but because of it's size it is failing. Any help you can offer would be greatly appreciated. Thanks in advance, -- Tomas Clements http://www.national-net.com NationalNet is committed to the highest level of Customer Service available in the Web Hosting business. If you have any questions, comments or concerns feel free to contact us at 770-471-9075 ext 1 (or toll-free, 877-471-9075 ext 1). -- 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]
mysql crashing after restore
Hello, I have a server that was using raid5. I also did a daily rsync from the machine. The raid5 failed and the data was lost. I recopied all of the data back to the machine from the backup. Most of which was a 133G ibdata1 file. Now when I try to start mysql I get the following: -- enough to kill the drive. 041225 22:19:56 mysqld started 041225 22:19:56 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 90 3664440544 InnoDB: Doing recovery: scanned up to log sequence number 90 3669579776 041225 22:19:56 InnoDB: Assertion failure in thread 16384 in file ../../innobase/in clude/page0page.ic line 482 InnoDB: Failing assertion: offs < UNIV_PAGE_SIZE InnoDB: We intentionally generate a memory trap. InnoDB: Send a detailed bug report to mysql@lists.mysql.com 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=8 read_buffer_size=16773120 max_used_connections=0 max_connections=1000 threads_connected=0 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 3403864 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. thd=0x8381228 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... Bogus stack limit or frame pointer, fp=0xbfffd9a8, stack_bottom=0x59f57c70, thread_s tack=196608, aborting backtrace. Trying to get some variables. Some pointers may be invalid and cause the dump to abort... thd->query at 0x58e0af80 is invalid pointer thd->thread_id=-1398035799 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. 041225 22:19:56 mysqld ended - It told me to submit this so I am. I don't know the cause of this. I believe that because the file was copied while in use (from the rsync) that it was not "closed" correctly. Because of that it's trying to scan the file for errors, but because of it's size it is failing. Any help you can offer would be greatly appreciated. Thanks in advance, -- Tomas Clements http://www.national-net.com NationalNet is committed to the highest level of Customer Service available in the Web Hosting business. If you have any questions, comments or concerns feel free to contact us at 770-471-9075 ext 1 (or toll-free, 877-471-9075 ext 1). -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: MySQL Crashing On Index Creation/Select count(*) statement - InnoDB tables
Frank, We used the 64-bit source to compile 4.0.20, and we used the 32-bit binaries. The problem was tracked down at about 1am - it was the kernel (or the SCSI drivers). We put a 3Ware SATA Raid-5 card in, and all the crashes went away. There are 64-bit binaries, but we had some problems with them (the guy that initially tried them can't remember the exact issue). You need to had a -fPic flag to get them to compile for the Opteron. The PIC flag is for position-independant code. Google it with Opteron and you'll see a bunch of posts on it. David Dr. Frank Ullrich wrote: David, David Griffiths wrote: We are in the process of setting up a new MySQL server. It's a dual-Opteron (Tyan Thunder K8S motherboard) with 6 gig of DDR333 RAM (registered) and an LSI SCSI card with 6 SCSI drives (5 in a RAID-5 array, with one hot-spare) running SuSE Enterprise 8.1 (64-bit). I loaded all our data (about 2 gig) into the database back on Tuesday, and created the indexes without issue, as a test to see how long it would take. Tonight, we were going to cut over to this new machine. I was setting up data as a test run, and started coming across "Database page corruption on disk or a failed file read of page" errors. At first, we were using MySQL 4.0.20 64-bit, compiled from source by us (the -fPic option needs to be included in the Makefile, and for some reason isn't in the binaries - also, no release notes for the AMD64 So you can't use the binaries that MySQL provides and therefore you didn't test them? Or did you? Why is this -fPic option important? I'm curious because we have a dual opteron system too and I wanted to install the 64bit binary (4.0.20-standard) from the MySQL web site. Regards, Frank. platform at http://dev.mysql.com/doc/mysql/en/Linux.html). I could consistently crash the database by creating an index on a column (a varchar(50)). I could also crash it doing a "SELECT COUNT(*)..." from a table with 3 million rows. Unfort, I did not save the crash-log. We rolled back to 4.0.18, also 64-bit. Exactly the same issue. Here's the output. - InnoDB: Database page corruption on disk or a failed InnoDB: file read of page 12244. InnoDB: You may have to recover from a backup. 040624 17:21:59 InnoDB: Page dump in ascii and hex (16384 bytes): ... 040624 17:21:59 InnoDB: Page checksum 1484130208, prior-to-4.0.14-form checksum 1108511089 InnoDB: stored checksum 2958040096, prior-to-4.0.14-form stored checksum 1108511089 InnoDB: Page lsn 0 204702464, low 4 bytes of lsn at page end 204702464 InnoDB: Page may be an index page where index id is 0 24 InnoDB: and table yw/boats2 index PRIMARY InnoDB: Database page corruption on disk or a failed InnoDB: file read of page 12244. InnoDB: You may have to recover from a backup. InnoDB: It is also possible that your operating InnoDB: system has corrupted its own file cache InnoDB: and rebooting your computer removes the InnoDB: error. InnoDB: If the corrupt page is an index page InnoDB: you can also try to fix the corruption InnoDB: by dumping, dropping, and reimporting InnoDB: the corrupt table. You can use CHECK InnoDB: TABLE to scan your table for corruption. InnoDB: Look also at section 6.1 of InnoDB: http://www.innodb.com/ibman.html about InnoDB: forcing recovery. InnoDB: Ending processing because of a corrupt database page. - InnoDB is robust enough to recover, fortunately. Then we thought it might be an issue with the 64-bit version, so we installed the 32-binary version (we didn't compile it) of 4.0.20. I managed to make it crash in exactly the same way - adding an index to a table, dropping an index, or selecting a count from the same large table. - 040624 20:29:07 mysqld restarted 040624 20:29:08 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 0 3576655719 InnoDB: Doing recovery: scanned up to log sequence number 0 3576655719 040624 20:29:08 InnoDB: Flushing modified pages from the buffer pool... 040624 20:29:09 InnoDB: Started /usr/local/mysql/bin/mysqld: ready for connections. Version: '4.0.18-standard-log' socket: '/tmp/mysql.sock' port: 3306 InnoDB: Database page corruption on disk or a failed InnoDB: file read of page 23235. InnoDB: You may have to recover from a backup. 040624 20:29:38 InnoDB: Page dump in ascii and hex (16384 bytes): 040624 20:29:38 InnoDB: Page checksum 1229875638, prior-to-4.0.14-form checksum 4263044155 InnoDB: stored checksum 2727822450, prior-to-4.0.14-form stored checksum 4263044155 InnoDB: Page lsn 0 748566710, low 4 bytes of lsn at page end 748566710
Re: MySQL Crashing On Index Creation/Select count(*) statement - InnoDB tables
David, David Griffiths wrote: We are in the process of setting up a new MySQL server. It's a dual-Opteron (Tyan Thunder K8S motherboard) with 6 gig of DDR333 RAM (registered) and an LSI SCSI card with 6 SCSI drives (5 in a RAID-5 array, with one hot-spare) running SuSE Enterprise 8.1 (64-bit). I loaded all our data (about 2 gig) into the database back on Tuesday, and created the indexes without issue, as a test to see how long it would take. Tonight, we were going to cut over to this new machine. I was setting up data as a test run, and started coming across "Database page corruption on disk or a failed file read of page" errors. At first, we were using MySQL 4.0.20 64-bit, compiled from source by us (the -fPic option needs to be included in the Makefile, and for some reason isn't in the binaries - also, no release notes for the AMD64 So you can't use the binaries that MySQL provides and therefore you didn't test them? Or did you? Why is this -fPic option important? I'm curious because we have a dual opteron system too and I wanted to install the 64bit binary (4.0.20-standard) from the MySQL web site. Regards, Frank. platform at http://dev.mysql.com/doc/mysql/en/Linux.html). I could consistently crash the database by creating an index on a column (a varchar(50)). I could also crash it doing a "SELECT COUNT(*)..." from a table with 3 million rows. Unfort, I did not save the crash-log. We rolled back to 4.0.18, also 64-bit. Exactly the same issue. Here's the output. - InnoDB: Database page corruption on disk or a failed InnoDB: file read of page 12244. InnoDB: You may have to recover from a backup. 040624 17:21:59 InnoDB: Page dump in ascii and hex (16384 bytes): ... 040624 17:21:59 InnoDB: Page checksum 1484130208, prior-to-4.0.14-form checksum 1108511089 InnoDB: stored checksum 2958040096, prior-to-4.0.14-form stored checksum 1108511089 InnoDB: Page lsn 0 204702464, low 4 bytes of lsn at page end 204702464 InnoDB: Page may be an index page where index id is 0 24 InnoDB: and table yw/boats2 index PRIMARY InnoDB: Database page corruption on disk or a failed InnoDB: file read of page 12244. InnoDB: You may have to recover from a backup. InnoDB: It is also possible that your operating InnoDB: system has corrupted its own file cache InnoDB: and rebooting your computer removes the InnoDB: error. InnoDB: If the corrupt page is an index page InnoDB: you can also try to fix the corruption InnoDB: by dumping, dropping, and reimporting InnoDB: the corrupt table. You can use CHECK InnoDB: TABLE to scan your table for corruption. InnoDB: Look also at section 6.1 of InnoDB: http://www.innodb.com/ibman.html about InnoDB: forcing recovery. InnoDB: Ending processing because of a corrupt database page. - InnoDB is robust enough to recover, fortunately. Then we thought it might be an issue with the 64-bit version, so we installed the 32-binary version (we didn't compile it) of 4.0.20. I managed to make it crash in exactly the same way - adding an index to a table, dropping an index, or selecting a count from the same large table. - 040624 20:29:07 mysqld restarted 040624 20:29:08 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 0 3576655719 InnoDB: Doing recovery: scanned up to log sequence number 0 3576655719 040624 20:29:08 InnoDB: Flushing modified pages from the buffer pool... 040624 20:29:09 InnoDB: Started /usr/local/mysql/bin/mysqld: ready for connections. Version: '4.0.18-standard-log' socket: '/tmp/mysql.sock' port: 3306 InnoDB: Database page corruption on disk or a failed InnoDB: file read of page 23235. InnoDB: You may have to recover from a backup. 040624 20:29:38 InnoDB: Page dump in ascii and hex (16384 bytes): 040624 20:29:38 InnoDB: Page checksum 1229875638, prior-to-4.0.14-form checksum 4263044155 InnoDB: stored checksum 2727822450, prior-to-4.0.14-form stored checksum 4263044155 InnoDB: Page lsn 0 748566710, low 4 bytes of lsn at page end 748566710 InnoDB: Page may be an index page where index id is 0 15 InnoDB: and table yw/boats_clobs2 index PRIMARY InnoDB: Database page corruption on disk or a failed InnoDB: file read of page 23235. InnoDB: You may have to recover from a backup. InnoDB: It is also possible that your operating InnoDB: system has corrupted its own file cache InnoDB: and rebooting your computer removes the InnoDB: error. InnoDB: If the corrupt page is an index page InnoDB: you can also try to fix the corruption InnoDB: by dumping, dropping, and reimporting InnoDB: the corrupt table. You can use CHECK InnoDB: T
MySQL Crashing On Index Creation/Select count(*) statement - InnoDB tables
We are in the process of setting up a new MySQL server. It's a dual-Opteron (Tyan Thunder K8S motherboard) with 6 gig of DDR333 RAM (registered) and an LSI SCSI card with 6 SCSI drives (5 in a RAID-5 array, with one hot-spare) running SuSE Enterprise 8.1 (64-bit). I loaded all our data (about 2 gig) into the database back on Tuesday, and created the indexes without issue, as a test to see how long it would take. Tonight, we were going to cut over to this new machine. I was setting up data as a test run, and started coming across "Database page corruption on disk or a failed file read of page" errors. At first, we were using MySQL 4.0.20 64-bit, compiled from source by us (the -fPic option needs to be included in the Makefile, and for some reason isn't in the binaries - also, no release notes for the AMD64 platform at http://dev.mysql.com/doc/mysql/en/Linux.html). I could consistently crash the database by creating an index on a column (a varchar(50)). I could also crash it doing a "SELECT COUNT(*)..." from a table with 3 million rows. Unfort, I did not save the crash-log. We rolled back to 4.0.18, also 64-bit. Exactly the same issue. Here's the output. - InnoDB: Database page corruption on disk or a failed InnoDB: file read of page 12244. InnoDB: You may have to recover from a backup. 040624 17:21:59 InnoDB: Page dump in ascii and hex (16384 bytes): ... 040624 17:21:59 InnoDB: Page checksum 1484130208, prior-to-4.0.14-form checksum 1108511089 InnoDB: stored checksum 2958040096, prior-to-4.0.14-form stored checksum 1108511089 InnoDB: Page lsn 0 204702464, low 4 bytes of lsn at page end 204702464 InnoDB: Page may be an index page where index id is 0 24 InnoDB: and table yw/boats2 index PRIMARY InnoDB: Database page corruption on disk or a failed InnoDB: file read of page 12244. InnoDB: You may have to recover from a backup. InnoDB: It is also possible that your operating InnoDB: system has corrupted its own file cache InnoDB: and rebooting your computer removes the InnoDB: error. InnoDB: If the corrupt page is an index page InnoDB: you can also try to fix the corruption InnoDB: by dumping, dropping, and reimporting InnoDB: the corrupt table. You can use CHECK InnoDB: TABLE to scan your table for corruption. InnoDB: Look also at section 6.1 of InnoDB: http://www.innodb.com/ibman.html about InnoDB: forcing recovery. InnoDB: Ending processing because of a corrupt database page. - InnoDB is robust enough to recover, fortunately. Then we thought it might be an issue with the 64-bit version, so we installed the 32-binary version (we didn't compile it) of 4.0.20. I managed to make it crash in exactly the same way - adding an index to a table, dropping an index, or selecting a count from the same large table. - 040624 20:29:07 mysqld restarted 040624 20:29:08 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 0 3576655719 InnoDB: Doing recovery: scanned up to log sequence number 0 3576655719 040624 20:29:08 InnoDB: Flushing modified pages from the buffer pool... 040624 20:29:09 InnoDB: Started /usr/local/mysql/bin/mysqld: ready for connections. Version: '4.0.18-standard-log' socket: '/tmp/mysql.sock' port: 3306 InnoDB: Database page corruption on disk or a failed InnoDB: file read of page 23235. InnoDB: You may have to recover from a backup. 040624 20:29:38 InnoDB: Page dump in ascii and hex (16384 bytes): 040624 20:29:38 InnoDB: Page checksum 1229875638, prior-to-4.0.14-form checksum 4263044155 InnoDB: stored checksum 2727822450, prior-to-4.0.14-form stored checksum 4263044155 InnoDB: Page lsn 0 748566710, low 4 bytes of lsn at page end 748566710 InnoDB: Page may be an index page where index id is 0 15 InnoDB: and table yw/boats_clobs2 index PRIMARY InnoDB: Database page corruption on disk or a failed InnoDB: file read of page 23235. InnoDB: You may have to recover from a backup. InnoDB: It is also possible that your operating InnoDB: system has corrupted its own file cache InnoDB: and rebooting your computer removes the InnoDB: error. InnoDB: If the corrupt page is an index page InnoDB: you can also try to fix the corruption InnoDB: by dumping, dropping, and reimporting InnoDB: the corrupt table. You can use CHECK InnoDB: TABLE to scan your table for corruption. InnoDB: Look also at section 6.1 of InnoDB: http://www.innodb.com/ibman.html about InnoDB: forcing recovery. InnoDB: Ending processing because of a corrupt database page. - I am pr
Re: compiling mysql and mysql crashing
Michael Stassen wrote: Christine Ross wrote: I had to install a source version of mysql and one of the install docs strongly suggests using CXXFLAGS="03 -felide-constructors -fno-exceptions -fno-rtti" ---8>< It's not a CERO, it's an letter O, the correct syntax is: CXXFLAGS="-O3 -felide-constructors -fno-exceptions-fno-rtti" If you are using a recent intel processor you can even add: "-march=i686 -mcpu=i686" You don't even have to add the "-O3" since it will be automatically added by the mysql configure script. Just export CXXFLAGS with the other optional optims flags, you can check out what they mean by reading them in the gcc man: man gcc When I did that I noticed in the compile a line that said it wasn't supported by gcc (3.3.3). I"m using CXX=gcc. --8>< What distro are you using? What mysql server are you trying to compile? Also when I included it in the build, my statement about --localstatedir=/usr/local/mysql/data It's irrelevant, the localstatedir is where mysql, once compiled and configured will look for data by default, this default can _ALWAYS_ be overriden by changing the configuration file. It's just a default. Once compiled, you must run a script that will create the default databases and tables, _BUT_ once compiled and _INSTALLED_, not before. The script is called: mysql_install_db and it should be (normally i mean) in /usr/bin Best Regards! -- |...| | _ _|Victor Medina M | |\ \ \| | _ \ / \ |Linux - Java - MySQL | | \ \ \ _| | |_) / _ \ |Dpto. Sistemas - Ferreteria EPA | | / / / |___| __/ ___ \ |[EMAIL PROTECTED] | |/_/_/|_|_| /_/ \_\|Tel: +58-241-8507325 - ext. 325 | ||Cel: +58-412-8859934 | ||geek by nature - linux by choice | |...| -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: compiling mysql and mysql crashing
Christine Ross wrote: I had to install a source version of mysql and one of the install docs strongly suggests using CXXFLAGS="03 -felide-constructors -fno-exceptions -fno-rtti" because of some instances of mysql crashing. When I did that I noticed in the compile a line that said it wasn't supported by gcc (3.3.3). I"m using CXX=gcc. It would be helpful if you would tell us what OS you have and which version of mysql you are building, as well as pasting in the message you got from gcc. 1) Has anyone had instances if it crashing without those parameters? I can't have mysql crashing but if the gcc indicates it doesn't support it, do those flags get built in? Also when I included it in the build, my statement about --localstatedir=/usr/local/mysql/data was ignored because it never built the data directory. 2) I just built it with --prefix and --localstatedir. Has anyone had problems with this? That depends on what you mean by build (out of `configure`, `make`, or `make install`). The data directory is created when you install mysql with `make install`. Are you saying that didn't happen when you installed? 3) If I want to recompile mysql, do I also have to recompile all apache, php and mod_ssl? That depends. Did you build php against your build of mysql, or did you keep php's built-in mysql support? Thanks for any suggestions. Michael -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
compiling mysql and mysql crashing
I had to install a source version of mysql and one of the install docs strongly suggests using CXXFLAGS="03 -felide-constructors -fno-exceptions -fno-rtti" because of some instances of mysql crashing. When I did that I noticed in the compile a line that said it wasn't supported by gcc (3.3.3). I"m using CXX=gcc. 1) Has anyone had instances if it crashing without those parameters? I can't have mysql crashing but if the gcc indicates it doesn't support it, do those flags get built in? Also when I included it in the build, my statement about --localstatedir=/usr/local/mysql/data was ignored because it never built the data directory. 2) I just built it with --prefix and --localstatedir. Has anyone had problems with this? 3) If I want to recompile mysql, do I also have to recompile all apache, php and mod_ssl? Thanks for any suggestions. -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: mysql crashing regularly
David, - Original Message - From: "David Bernick" <[EMAIL PROTECTED]> Newsgroups: mailing.database.mysql Sent: Tuesday, July 22, 2003 8:02 PM Subject: mysql crashing regularly > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 your database is corrupt. It is trying to access a page at 8 TB. What Linux distro you are using? What is the complete query? If you resolve the stack dump, what does it say? If the table is not huge, run CHECK TABLE on it, and post the .err log output here. > We're doing a select query on our INNODB database. > Linux 2.4.21 on x86 (Athlon). Mysql is 4.0.13. Anyone seen this problem before? > - - > InnoDB: Error: trying to access page number 538587904 in space 0 > InnoDB: which is outside the tablespace bounds. > InnoDB: Byte offset 0, len 16384, i/o type 10 > 030722 12:49:11 InnoDB: Assertion failure in thread 40970 in file fil0fil.c > line 1176 > InnoDB: Failing assertion: 0 > InnoDB: We intentionally generate a memory trap. > InnoDB: Send a detailed bug report to [EMAIL PROTECTED] > 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=16777216 > read_buffer_size=131072 > sort_buffer_size=524280 > max_used_connections=0 > max_connections=100 > threads_connected=1 > It is possible that mysqld could use up to > key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 80383 K > bytes of memory > Hope that's ok; if not, decrease some variables in the equation. > > > - -- > David Bernick Regards, Heikki > Senior Engineer - Legal Computer Solutions > [EMAIL PROTECTED] > > "The combination of a number of things to make existence worthwhile." > "Yes, the philosophy of 'none,' meaning 'all.'" > -- Spock and Lincoln, "The Savage Curtain", stardate 5906.4 > -BEGIN PGP SIGNATURE- > Version: GnuPG v1.0.7 (GNU/Linux) > Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org > > iD8DBQE/HWypzR9WeS6DURURAmnIAJ9RU+e0/knlSVP1iSPjdNDCnJJ+HQCfdKay > 5JA4S5dFESq4f4HIMkBS8D0= > =ECfl > -END PGP SIGNATURE- > > > -- > 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]
mysql crashing regularly
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 We're doing a select query on our INNODB database. Linux 2.4.21 on x86 (Athlon). Mysql is 4.0.13. Anyone seen this problem before? - - InnoDB: Error: trying to access page number 538587904 in space 0 InnoDB: which is outside the tablespace bounds. InnoDB: Byte offset 0, len 16384, i/o type 10 030722 12:49:11 InnoDB: Assertion failure in thread 40970 in file fil0fil.c line 1176 InnoDB: Failing assertion: 0 InnoDB: We intentionally generate a memory trap. InnoDB: Send a detailed bug report to [EMAIL PROTECTED] 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=16777216 read_buffer_size=131072 sort_buffer_size=524280 max_used_connections=0 max_connections=100 threads_connected=1 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 80383 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. - -- David Bernick Senior Engineer - Legal Computer Solutions [EMAIL PROTECTED] "The combination of a number of things to make existence worthwhile." "Yes, the philosophy of 'none,' meaning 'all.'" -- Spock and Lincoln, "The Savage Curtain", stardate 5906.4 -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.7 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQE/HWypzR9WeS6DURURAmnIAJ9RU+e0/knlSVP1iSPjdNDCnJJ+HQCfdKay 5JA4S5dFESq4f4HIMkBS8D0= =ECfl -END PGP SIGNATURE- -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
mysql crashing
hi, my mysql is crashing from time to time, on nothing more than just count(*) on a table. its 3.23.52 compiled from the sources, running on openbsd 3.1 i have compiled with debug turned on, but there is no backtrace in the log file when it happens,only this: 020918 16:16:20 mysqld restarted /mysql/libexec/mysqld: ready for connections 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 agaist 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=16773120 record_buffer=131072 sort_buffer=524280 max_used_connections=50 max_connections=100 threads_connected=40 It is possible that mysqld could use up to key_buffer_size + (record_buffer + sort_buffer)*max_connections = 80379 K bytes of memory Hope that's ok, if not, decrease some variables in the equation 020919 03:31:48 mysqld restarted i have increased all the limits on memory, stack, opened files etc to no avail. what else can i do to debug the problem or resolve the issue ? regards, terry - Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail <[EMAIL PROTECTED]> To unsubscribe, e-mail <[EMAIL PROTECTED]> Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
Re: Mysql crashing.
[EMAIL PROTECTED] writes: > >Description: > See earlier emails from me. Same problem. > >How-To-Repeat: > >Fix: > >Submitter-Id: [EMAIL PROTECTED] > >Originator: [EMAIL PROTECTED] > >Organization: Auctionwatch.com > >MySQL support: login > >Synopsis:Mysql crashing. > >Severity:critical > >Priority:high > >Category:mysql > >Class: sw-bug > >Release: mysql-3.23.43 (Official MySQL binary) > > >Environment: > System: Linux dbrspare-red.auctionwatch.com 2.4.17-rc2 #1 SMP Thu Dec 20 19:05:16 >PST 2001 i686 unknown > Architecture: i686 > > Some paths: /usr/bin/perl /usr/bin/make /usr/bin/gcc /usr/bin/cc > GCC: Reading specs from /usr/lib/gcc-lib/i386-linux/2.95.4/specs > gcc version 2.95.4 20010703 (Debian prerelease) > Compilation info: CC='gcc' CFLAGS='-O3 -mpentium ' CXX='gcc' CXXFLAGS='-O3 >-mpentium -felide-constructors' LDFLAGS='-static' > LIBC: > lrwxrwxrwx1 root root 13 Dec 14 11:06 /lib/libc.so.6 -> >libc-2.2.3.so > -rwxr-xr-x1 root root 1155720 Jul 27 13:42 /lib/libc-2.2.3.so > -rw-r--r--1 root root 2579358 Jul 25 08:15 /usr/lib/libc.a > -rw-r--r--1 root root 178 Jul 25 08:15 /usr/lib/libc.so > Configure command: ./configure --prefix=/usr/local/mysql '--with-comment=Official >MySQL binary' --with-extra-charsets=complex --with-server-suffix= --enable-assembler >--with-mysqld-ldflags=-all-static --with-client-ldflags=-all-static --disable-shared > > Here is the stack dump: > 0x807b75f handle_segfault__Fi + 383 > 0x812bcaa pthread_sighandler + 154 > 0x815059c chunk_free + 596 > 0x8152573 free + 155 > 0x811579c my_no_flags_free + 16 > 0x80764d5 _._5ilink + 61 > 0x807b48d end_thread__FP3THDb + 53 > 0x80809cc handle_one_connection__FPv + 996 > Hi! The above looks like memory corruption. Can you please take a look at the log file and see if there are any messsages there ?? Beside that, send us also login info at the ususal SupportWizard interface at http://support.mysql.com -- Regards, __ ___ ___ __ / |/ /_ __/ __/ __ \/ /Mr. Sinisa Milivojevic <[EMAIL PROTECTED]> / /|_/ / // /\ \/ /_/ / /__ MySQL AB, Fulltime Developer /_/ /_/\_, /___/\___\_\___/ Larnaca, Cyprus <___/ www.mysql.com - Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail <[EMAIL PROTECTED]> To unsubscribe, e-mail <[EMAIL PROTECTED]> Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
Mysql crashing.
>Description: See earlier emails from me. Same problem. >How-To-Repeat: >Fix: >Submitter-Id: [EMAIL PROTECTED] >Originator:[EMAIL PROTECTED] >Organization: Auctionwatch.com >MySQL support: login >Synopsis: Mysql crashing. >Severity: critical >Priority: high >Category: mysql >Class: sw-bug >Release: mysql-3.23.43 (Official MySQL binary) >Environment: System: Linux dbrspare-red.auctionwatch.com 2.4.17-rc2 #1 SMP Thu Dec 20 19:05:16 PST 2001 i686 unknown Architecture: i686 Some paths: /usr/bin/perl /usr/bin/make /usr/bin/gcc /usr/bin/cc GCC: Reading specs from /usr/lib/gcc-lib/i386-linux/2.95.4/specs gcc version 2.95.4 20010703 (Debian prerelease) Compilation info: CC='gcc' CFLAGS='-O3 -mpentium ' CXX='gcc' CXXFLAGS='-O3 -mpentium -felide-constructors' LDFLAGS='-static' LIBC: lrwxrwxrwx1 root root 13 Dec 14 11:06 /lib/libc.so.6 -> libc-2.2.3.so -rwxr-xr-x1 root root 1155720 Jul 27 13:42 /lib/libc-2.2.3.so -rw-r--r--1 root root 2579358 Jul 25 08:15 /usr/lib/libc.a -rw-r--r--1 root root 178 Jul 25 08:15 /usr/lib/libc.so Configure command: ./configure --prefix=/usr/local/mysql '--with-comment=Official MySQL binary' --with-extra-charsets=complex --with-server-suffix= --enable-assembler --with-mysqld-ldflags=-all-static --with-client-ldflags=-all-static --disable-shared Here is the stack dump: 0x807b75f handle_segfault__Fi + 383 0x812bcaa pthread_sighandler + 154 0x815059c chunk_free + 596 0x8152573 free + 155 0x811579c my_no_flags_free + 16 0x80764d5 _._5ilink + 61 0x807b48d end_thread__FP3THDb + 53 0x80809cc handle_one_connection__FPv + 996 - Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail <[EMAIL PROTECTED]> To unsubscribe, e-mail <[EMAIL PROTECTED]> Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
Re: mysql crashing
Hi Russell, have you applied patches M410-008, M410-012 and most important M410-014? Even after applying the patches there are major thread problems (althought MySQL should 'run' ). My advice to you is to update to 4.2 which seems to fix the threads problems, and apply current patches as there are some security patches (for both 4.1 and 4.2). Best of luck, Ken - Original Message - From: "Russell A. Bell" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Tuesday, September 04, 2001 8:39 PM Subject: mysql crashing > MySQL crashes almost every time we try to use it through a PHP > script. > We use 4.1 BSDI BSD/OS 4.1 Kernel #0 > > - > Before posting, please check: >http://www.mysql.com/manual.php (the manual) >http://lists.mysql.com/ (the list archive) > > To request this thread, e-mail <[EMAIL PROTECTED]> > To unsubscribe, e-mail <[EMAIL PROTECTED]> > Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php > > - Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail <[EMAIL PROTECTED]> To unsubscribe, e-mail <[EMAIL PROTECTED]> Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
mysql crashing
MySQL crashes almost every time we try to use it through a PHP script. We use 4.1 BSDI BSD/OS 4.1 Kernel #0 - Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail <[EMAIL PROTECTED]> To unsubscribe, e-mail <[EMAIL PROTECTED]> Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
Re: MySQL crashing/stopping in ABRIASOFT's installation
You are probably running MySQL version build for different Windows version. Please download and try a latest Windows binary. -- Regards, __ ___ ___ __ / |/ /_ __/ __/ __ \/ /Mr. Sinisa Milivojevic <[EMAIL PROTECTED]> / /|_/ / // /\ \/ /_/ / /__ MySQL AB, FullTime Developer /_/ /_/\_, /___/\___\_\___/ Larnaca, Cyprus <___/ www.mysql.com - Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail <[EMAIL PROTECTED]> To unsubscribe, e-mail <[EMAIL PROTECTED]> Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
MySQL crashing/stopping in ABRIASOFT's installation
Hi, Could some one tell me how to find out what is wrong with the MySQL as it stops working after a minute or two on a machine running Win98SE. the Mysql is installed by the Merlin Server installer of Abriasofts. I include the report if it tells anyone anything, to me it is bit gibberish. This Report was made using the WinMySQLadmin 1.0 Tool 4.9.2001 14:27:45 Description: How-To-Repeat : Fix: Synopsis : Submitter-Id : Originator : Organization : MySQL support : [none | licence | email support | extended email support ] Severity : [non-critical | serious | critical ] Priority : [low | medium | high ] Category : [mysqld, mysql client, C, PHP, PERL, ...] Class : [ sw-bug | doc-bug | change-request | support ] OS Platform: Win 95 or Win 98 detected Machine description: Compiler : VC++ 6.0 Architecture : i686 Total Memory : 130,564 MB RAM My.ini File [mysqld] basedir=C:/OHJELMATIEDOSTOT/ABRIA MERLIN/MYSQL datadir=C:/OHJELMATIEDOSTOT/ABRIA MERLIN/MYSQL/data Server Status Values Server Info3.23.36 Host Info localhost via TCP/IP Client Info3.23.33 Proto Info 10 Aborted_clients1 Aborted_connects 0 Bytes_received 0 Bytes_sent 0 Connections5 Created_tmp_disk_tables0 Created_tmp_tables 0 Created_tmp_files 0 Delayed_insert_threads 0 Delayed_writes 0 Delayed_errors 0 Flush_commands 1 Handler_delete 0 Handler_read_first 1 Handler_read_key 0 Handler_read_next 0 Handler_read_prev 0 Handler_read_rnd 0 Handler_read_rnd_next 9 Handler_update 0 Handler_write 0 Key_blocks_used0 Key_read_requests 0 Key_reads 0 Key_write_requests 0 Key_writes 0 Max_used_connections 2 Not_flushed_key_blocks 0 Not_flushed_delayed_rows 0 Open_tables3 Open_files 6 Open_streams 0 Opened_tables 8 Questions 71 Select_full_join 0 Select_full_range_join 0 Select_range 0 Select_range_check 0 Select_scan0 Slave_running OFF Slave_open_temp_tables 0 Slow_launch_threads0 Slow_queries 0 Sort_merge_passes 0 Sort_range 0 Sort_rows 0 Sort_scan 0 Table_locks_immediate 5 Table_locks_waited 0 Threads_cached 0 Threads_created4 Threads_connected 3 Threads_running1 Uptime 256 Variables Values ansi_mode OFF back_log 50 basedirc:\ohjelmatiedostot\abria merlin\mysql\ binlog_cache_size 32768 character_set latin1 character_sets latin1 big5 czech euc_kr gb2312 gbk sjis tis620 ujis dec8 dos german1 hp8 koi8_ru latin2 swe7 usa7 cp1251 danish hebrew win1251 estonia hungarian koi8_ukr win1251ukr greek win1250 croat cp1257 concurrent_insert ON connect_timeout5 datadirc:\ohjelmatiedostot\abria merlin\mysql\data\ delay_key_writeON delayed_insert_limit 100 delayed_insert_timeout 300 delayed_queue_size 1000 flush OFF flush_time 1800 have_bdb NO have_geminiNO have_innobase NO have_isam YES have_raid NO have_ssl NO init_file interactive_timeout28800 join_buffer_size 131072 key_buffer_size8388600 language c:\ohjelmatiedostot\abria merlin\mysql\share\english\ large_files_supportON logOFF log_update OFF log_binOFF log_slave_updates OFF long_query_time10 low_priority_updates OFF lower_case_table_names 1 max_allowed_packet 1048576
MySQL crashing in abria merlin server
Hi, have met a following problem, I have on my Win32 work machine the Abria softs merlin server package but the MySQL part of it keeps failing. You do not have to do a thing and it fails, does not give out data anymore. I have to close both Mysql and Apache for it to work again for a few moments. Does anyone else have similar troubles with it? Jari Mäkelä - Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail <[EMAIL PROTECTED]> To unsubscribe, e-mail <[EMAIL PROTECTED]> Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
Re: mysql crashing under 100 user loads
David Freeman writes: > I am having a problem with mysql. I am running a php web site that uses a (mysql >Ver 11.15 Disturb 3.23.39 for pc-linux-gnu (i686))database. Whenever i get a load of >about 100 simultaneous users, mysql begins to spawn D stat processes and the site >dies. Everything works very well with smaller loads. > > I am running this on a Quad Proc HP LH4 with 1GB Ram (which isn't being touched much) > > running Slack ware 7.1 upgraded to kernel 2.4-efs > > Apache http/https > > any help would be greatly appreciated. > > > here is a small sample of the spawned processes. HI! You are either running out of file descriptors or you have a lock contention problem. Second problem can be solved by using our binary. -- Regards, __ ___ ___ __ / |/ /_ __/ __/ __ \/ /Mr. Sinisa Milivojevic <[EMAIL PROTECTED]> / /|_/ / // /\ \/ /_/ / /__ MySQL AB, FullTime Developer /_/ /_/\_, /___/\___\_\___/ Larnaca, Cyprus <___/ www.mysql.com - Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail <[EMAIL PROTECTED]> To unsubscribe, e-mail <[EMAIL PROTECTED]> Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
mysql crashing under 100 user loads
I am having a problem with mysql. I am running a php web site that uses a (mysql Ver 11.15 Disturb 3.23.39 for pc-linux-gnu (i686))database. Whenever i get a load of about 100 simultaneous users, mysql begins to spawn D stat processes and the site dies. Everything works very well with smaller loads. I am running this on a Quad Proc HP LH4 with 1GB Ram (which isn't being touched much) running Slack ware 7.1 upgraded to kernel 2.4-efs Apache http/https any help would be greatly appreciated. here is a small sample of the spawned processes. root 104 0.0 0.0 1600 800 ?S12:04 0:00 /bin/sh ./bin/safe_mysqld -u mysql mysql 129 0.0 1.1 51632 10208 ? S12:04 0:00 _ /usr/local/mysql/bin/mysqld --defaults-extra-file=/usr/local/mysq mysql 131 0.0 1.1 51632 10208 ? S12:04 0:00 _ /usr/local/mysql/bin/mysqld --defaults-extra-file=/usr/local/ mysql 132 0.0 1.1 51632 10208 ? S12:04 0:00 _ /usr/local/mysql/bin/mysqld --defaults-extra-file=/usr/lo mysql 133 0.0 1.1 51632 10208 ? S12:04 0:00 _ /usr/local/mysql/bin/mysqld --defaults-extra-file=/usr/lo mysql 149 0.0 1.1 51632 10208 ? S12:05 0:11 _ /usr/local/mysql/bin/mysqld --defaults-extra-file=/usr/lo mysql 152 0.0 1.1 51632 10208 ? S12:06 0:09 _ /usr/local/mysql/bin/mysqld --defaults-extra-file=/usr/lo mysql 153 0.0 1.1 51632 10208 ? S12:06 0:11 _ /usr/local/mysql/bin/mysqld --defaults-extra-file=/usr/lo mysql 154 0.0 1.1 51632 10208 ? S12:06 0:10 _ /usr/local/mysql/bin/mysqld --defaults-extra-file=/usr/lo mysql 155 0.0 1.1 51632 10208 ? S12:06 0:10 _ /usr/local/mysql/bin/mysqld --defaults-extra-file=/usr/lo mysql 156 0.0 1.1 51632 10208 ? D12:06 0:10 _ /usr/local/mysql/bin/mysqld --defaults-extra-file=/usr/lo mysql 157 0.0 1.1 51632 10208 ? S12:06 0:11 _ /usr/local/mysql/bin/mysqld --defaults-extra-file=/usr/lo mysql 158 0.0 1.1 51632 10208 ? S12:06 0:10 _ /usr/local/mysql/bin/mysqld --defaults-extra-file=/usr/lo mysql 159 0.0 1.1 51632 10208 ? D12:06 0:11 _ /usr/local/mysql/bin/mysqld --defaults-extra-file=/usr/lo - Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail <[EMAIL PROTECTED]> To unsubscribe, e-mail <[EMAIL PROTECTED]> Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
Re: MySQL Crashing
Is something run from cron deleting the socket? The second error is just because your PHP script did not check for the first error. David Addison wrote: > I use MySQL with PHP on a BSD server. For the last week or so I've been > getting errors. My problem is that I'm not sure how to read the error code: > > > Warning: MySQL Connection Failed: Can't connect to local MySQL server > through socket '/tmp/mysql.sock' (61) in > /usr/home/thebookc/usr/local/etc/httpd/conf/INIFile on line 22 > > Warning: 0 is not a MySQL link index in > /usr/home/thebookc/usr/local/etc/httpd/conf/INIFile on line 936 > SYSTEM ERROR: Please contact database administrator. > Error: :: > Location: selectLgBanner > > *** > > If I use the kill command and then shutdown and restart the system comes > back up. Then it crashes again... Can anyone tell me how to read this > error message. What's going on? Anywhere that I can read to find out more about >how to diagnose errors? Are there any good MySQL news groups > > Thanks, > David Addison > Transit ID, LLC. -- Gerald L. Clark [EMAIL PROTECTED] - Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail <[EMAIL PROTECTED]> To unsubscribe, e-mail <[EMAIL PROTECTED]> Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
MySQL Crashing
I use MySQL with PHP on a BSD server. For the last week or so I've been getting errors. My problem is that I'm not sure how to read the error code: Warning: MySQL Connection Failed: Can't connect to local MySQL server through socket '/tmp/mysql.sock' (61) in /usr/home/thebookc/usr/local/etc/httpd/conf/INIFile on line 22 Warning: 0 is not a MySQL link index in /usr/home/thebookc/usr/local/etc/httpd/conf/INIFile on line 936 SYSTEM ERROR: Please contact database administrator. Error: :: Location: selectLgBanner *** If I use the kill command and then shutdown and restart the system comes back up. Then it crashes again... Can anyone tell me how to read this error message. What's going on? Anywhere that I can read to find out more about how to diagnose errors? Are there any good MySQL news groups Thanks, David Addison Transit ID, LLC.
