Re: max_rows query + SegFaulting at inopportune times
Greetings Brent; Many thanks for your input. I decided that I would indeed create the table from scratch, making certain to apply the 'proper' settings, and then reload all of the data. This completed yesterday, with the following results: Row_format: Dynamic Rows: 18866709 Avg_row_length: 224 Data_length: 4236151548 Max_data_length: 4294967295 Index_length: 1141235712 Zero improvement. I used the following CREATE: CREATE TABLE mytable ( id int(11) NOT NULL auto_increment, . . . PRIMARY KEY(id)) AVG_ROW_LENGTH=224, MAX_ROWS=10; Which I believe should have incorporated the appropriate changes - but clearly has not. I've just made a couple of simple tests and verified that the 4GB limit isn't the OS' doing (14GB working tarball packing and unpacking), so I'm beginning to get quite confused as to how my efforts seem to return me to the same problem time and time again. I look forward to any further suggestions you may have; JP On Thu, 15 Mar 2007, Brent Baisley wrote: You probably did not change the max_rows setting when you created the table. If you read the manual under AVG_ROW_LENGTH for create table it says: When you create a MyISAM table, MySQL uses the product of the MAX_ROWS and AVG_ROW_LENGTH options to decide how big the resulting table is. If you do not specify either option, the maximum size for a table is 4GB. The 4GB limit is more a default speed optimization setting. Readup on the myisam_data_pointer_size setting for background information. - Original Message - From: JP Hindin [EMAIL PROTECTED] To: Michael Dykman [EMAIL PROTECTED] Cc: JP Hindin [EMAIL PROTECTED]; mysql@lists.mysql.com Sent: Thursday, March 15, 2007 2:09 PM Subject: Re: max_rows query + SegFaulting at inopportune times On Thu, 15 Mar 2007, Michael Dykman wrote: What host OS are you running? And which file system? MySQL is always limited by the file size that the host file system can handle. Deb Sarge is a Linux distribution, the large file support I mentioned allows files up to 2 TB in size. On 3/15/07, JP Hindin [EMAIL PROTECTED] wrote: Greetings all; I have a quandary regarding table limits, and clearly I am not understanding how this all works together. I have a test database which needs to keep long-term historical data, currently the total dataset in this one table is probably about 5.5GB in size - although since I have a 4GB table limit that I can't seem to shake, I'm not entirely positive yet. First off, I'm running 4.1.11-Debian_4sarge7-log. I'm unsure if you MySQL chaps are willing to help me with this distribution version, but I imagine the primary question is fairly non-specific. The OS is obviously Deb Sarge, running on a recent x86 machine (so it does include the large file support in the kernel). So, when I first received a 'Table is full' error I looked up the MySQL documentation and found the section regarding to altering max_rows on a table. Nice and simple. I ran the following on my DB: mysql ALTER TABLE mytable max_rows=2000; And some four days later when I looked at it, this was on the screen: Segmentation fault I checked the table status, and max_data_length had not changed. I thought perhaps I was being too pushy with the max_rows, so I dropped a zero and tried again - with the same results. About four days in, seg fault. So I figured perhaps it was getting bent out of shape with a 4.0GB table already in place, so I removed all rows, optimised the table, and tried the first query again. Success immediately! The SHOW STATUS gave this: Row_format: Dynamic Rows: 0 Avg_row_length: 0 Data_length: 0 Max_data_length: 281474976710655 Index_length: 1024 Looks good. Nice high max_data_length - so I loaded all the data into the table. Again, four days pass for the data to complete the bulk INSERT, and I run a SHOW STATUS again: Row_format: Dynamic Rows: 18866709 Avg_row_length: 224 Data_length: 4236151548 Max_data_length: 4294967295 Index_length: 1141235712 And suddenly I'm back to square one. Now I'm suspecting that the max_data_length is a combination of a lot of factors, and the avg_row_length plays into this. The documentation suggests setting avg_row_length in the ALTER TABLE, however it also says: You have to specify avg_row_length only for tables with BLOB or TEXT columns, so I didn't bother as this table is a combination of ints, varchars and datetimes. I wanted to check with you wizened lot before I set another query going. I'm going to assume that running an ALTER with the data in the DB is only going to garner me
Re: max_rows query + SegFaulting at inopportune times
Addendum; On Thu, 22 Mar 2007, JP Hindin wrote: Zero improvement. I used the following CREATE: MAX_ROWS=10; At first I thought I had spotted the obvious in the above - the MAX_ROWS I used is smaller than the Max_data_length that resulted, presumably MySQL being smarter than I am. So I changed the MAX_ROWS to use larger numbers, ala: AVG_ROW_LENGTH=224, MAX_ROWS=2000; But after creation the 'SHOW STATUS' gives the following: Create_options: max_rows=4294967295 avg_row_length=224 My guess is that MySQL has decided 4294967295 is the maximum table size and ALTERs nor CREATE options are able to change this imposed limit. This would explain why my ALTERs didn't appear to work, seg fault of the client aside. So I suppose the question now is - if MAX_ROWS doesn't increase the table size, what will? Where is the limit that MySQL is imposing coming from? Again, many thanks for anyone who can enlighten me as to what MySQL is thinking. JP -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: max_rows query + SegFaulting at inopportune times
I have, after further googling, discovered that the 4.2 billion figure that MySQL uses as 'max_rows' is, indeed, max_rows and not a max database size in bytes. In theory I have solved my problem, and wasted however many peoples bandwidth by putting all these eMails to the MySQL list. Mea culpa, mea culpa, mea maxima culpa. I slink to my corner with Google in hand and apologise for wasting your time. Here's hoping, of course, in four days I don't find out I'm wrong about the 4.2b rows part. - JP On Thu, 22 Mar 2007, JP Hindin wrote: Addendum; On Thu, 22 Mar 2007, JP Hindin wrote: Zero improvement. I used the following CREATE: MAX_ROWS=10; At first I thought I had spotted the obvious in the above - the MAX_ROWS I used is smaller than the Max_data_length that resulted, presumably MySQL being smarter than I am. So I changed the MAX_ROWS to use larger numbers, ala: AVG_ROW_LENGTH=224, MAX_ROWS=2000; But after creation the 'SHOW STATUS' gives the following: Create_options: max_rows=4294967295 avg_row_length=224 My guess is that MySQL has decided 4294967295 is the maximum table size and ALTERs nor CREATE options are able to change this imposed limit. This would explain why my ALTERs didn't appear to work, seg fault of the client aside. So I suppose the question now is - if MAX_ROWS doesn't increase the table size, what will? Where is the limit that MySQL is imposing coming from? Again, many thanks for anyone who can enlighten me as to what MySQL is thinking. JP -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: max_rows query + SegFaulting at inopportune times
Micah; In the first eMail I mentioned that I had excluded filesystem size limits by manually producing a 14GB tar file. If it was only that simple :) On Thu, 22 Mar 2007, Micah Stevens wrote: This table size is based on your filesystem limits. This is a limit of the OS, not MySQL. -Micah On 03/22/2007 01:02 PM, JP Hindin wrote: Addendum; On Thu, 22 Mar 2007, JP Hindin wrote: Zero improvement. I used the following CREATE: MAX_ROWS=10; At first I thought I had spotted the obvious in the above - the MAX_ROWS I used is smaller than the Max_data_length that resulted, presumably MySQL being smarter than I am. So I changed the MAX_ROWS to use larger numbers, ala: AVG_ROW_LENGTH=224, MAX_ROWS=2000; But after creation the 'SHOW STATUS' gives the following: Create_options: max_rows=4294967295 avg_row_length=224 My guess is that MySQL has decided 4294967295 is the maximum table size and ALTERs nor CREATE options are able to change this imposed limit. This would explain why my ALTERs didn't appear to work, seg fault of the client aside. So I suppose the question now is - if MAX_ROWS doesn't increase the table size, what will? Where is the limit that MySQL is imposing coming from? Again, many thanks for anyone who can enlighten me as to what MySQL is thinking. JP -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
max_rows query + SegFaulting at inopportune times
Greetings all; I have a quandary regarding table limits, and clearly I am not understanding how this all works together. I have a test database which needs to keep long-term historical data, currently the total dataset in this one table is probably about 5.5GB in size - although since I have a 4GB table limit that I can't seem to shake, I'm not entirely positive yet. First off, I'm running 4.1.11-Debian_4sarge7-log. I'm unsure if you MySQL chaps are willing to help me with this distribution version, but I imagine the primary question is fairly non-specific. The OS is obviously Deb Sarge, running on a recent x86 machine (so it does include the large file support in the kernel). So, when I first received a 'Table is full' error I looked up the MySQL documentation and found the section regarding to altering max_rows on a table. Nice and simple. I ran the following on my DB: mysql ALTER TABLE mytable max_rows=2000; And some four days later when I looked at it, this was on the screen: Segmentation fault I checked the table status, and max_data_length had not changed. I thought perhaps I was being too pushy with the max_rows, so I dropped a zero and tried again - with the same results. About four days in, seg fault. So I figured perhaps it was getting bent out of shape with a 4.0GB table already in place, so I removed all rows, optimised the table, and tried the first query again. Success immediately! The SHOW STATUS gave this: Row_format: Dynamic Rows: 0 Avg_row_length: 0 Data_length: 0 Max_data_length: 281474976710655 Index_length: 1024 Looks good. Nice high max_data_length - so I loaded all the data into the table. Again, four days pass for the data to complete the bulk INSERT, and I run a SHOW STATUS again: Row_format: Dynamic Rows: 18866709 Avg_row_length: 224 Data_length: 4236151548 Max_data_length: 4294967295 Index_length: 1141235712 And suddenly I'm back to square one. Now I'm suspecting that the max_data_length is a combination of a lot of factors, and the avg_row_length plays into this. The documentation suggests setting avg_row_length in the ALTER TABLE, however it also says: You have to specify avg_row_length only for tables with BLOB or TEXT columns, so I didn't bother as this table is a combination of ints, varchars and datetimes. I wanted to check with you wizened lot before I set another query going. I'm going to assume that running an ALTER with the data in the DB is only going to garner me another wasted week and a Seg Fault, so I think what I should probably do is clean the table again, run the following: mysql ALTER TABLE mytable max_rows=2000 avg_row_length=224; And then reload all my data and see if that helps. Can someone explain to me if my guess that avg_row_length is a factor in the max_data_length of the table, and is my above query going to release me from my hovering 4GB table limit? Has anyone seen this blasted SegFault issue before? I appreciate any help I can get with this one, I'm obviously missing something, flame away. Many thanks. - JP -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: max_rows query + SegFaulting at inopportune times
On Thu, 15 Mar 2007, Michael Dykman wrote: What host OS are you running? And which file system? MySQL is always limited by the file size that the host file system can handle. Deb Sarge is a Linux distribution, the large file support I mentioned allows files up to 2 TB in size. On 3/15/07, JP Hindin [EMAIL PROTECTED] wrote: Greetings all; I have a quandary regarding table limits, and clearly I am not understanding how this all works together. I have a test database which needs to keep long-term historical data, currently the total dataset in this one table is probably about 5.5GB in size - although since I have a 4GB table limit that I can't seem to shake, I'm not entirely positive yet. First off, I'm running 4.1.11-Debian_4sarge7-log. I'm unsure if you MySQL chaps are willing to help me with this distribution version, but I imagine the primary question is fairly non-specific. The OS is obviously Deb Sarge, running on a recent x86 machine (so it does include the large file support in the kernel). So, when I first received a 'Table is full' error I looked up the MySQL documentation and found the section regarding to altering max_rows on a table. Nice and simple. I ran the following on my DB: mysql ALTER TABLE mytable max_rows=2000; And some four days later when I looked at it, this was on the screen: Segmentation fault I checked the table status, and max_data_length had not changed. I thought perhaps I was being too pushy with the max_rows, so I dropped a zero and tried again - with the same results. About four days in, seg fault. So I figured perhaps it was getting bent out of shape with a 4.0GB table already in place, so I removed all rows, optimised the table, and tried the first query again. Success immediately! The SHOW STATUS gave this: Row_format: Dynamic Rows: 0 Avg_row_length: 0 Data_length: 0 Max_data_length: 281474976710655 Index_length: 1024 Looks good. Nice high max_data_length - so I loaded all the data into the table. Again, four days pass for the data to complete the bulk INSERT, and I run a SHOW STATUS again: Row_format: Dynamic Rows: 18866709 Avg_row_length: 224 Data_length: 4236151548 Max_data_length: 4294967295 Index_length: 1141235712 And suddenly I'm back to square one. Now I'm suspecting that the max_data_length is a combination of a lot of factors, and the avg_row_length plays into this. The documentation suggests setting avg_row_length in the ALTER TABLE, however it also says: You have to specify avg_row_length only for tables with BLOB or TEXT columns, so I didn't bother as this table is a combination of ints, varchars and datetimes. I wanted to check with you wizened lot before I set another query going. I'm going to assume that running an ALTER with the data in the DB is only going to garner me another wasted week and a Seg Fault, so I think what I should probably do is clean the table again, run the following: mysql ALTER TABLE mytable max_rows=2000 avg_row_length=224; And then reload all my data and see if that helps. Can someone explain to me if my guess that avg_row_length is a factor in the max_data_length of the table, and is my above query going to release me from my hovering 4GB table limit? Has anyone seen this blasted SegFault issue before? I appreciate any help I can get with this one, I'm obviously missing something, flame away. Many thanks. - JP -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED] -- - michael dykman - [EMAIL PROTECTED] - All models are wrong. Some models are useful. -- 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]
Invitación: Webinar MySQL 5.0 - Nuevas funcionalidades para la Empresa
Amigos me llegó este mail, quiza les sea de ayuda. Jorge Paiva Lima - Peru MySQL 5.0 - Nuevas funcionalidades para la Empresa Miércoles 1 de Febrero de 2006 MySQL les invita a participar en el primer webinar en castellano para España y Latinoamérica. En este webinar, en colaboración con nuestro partner Afina, explicaremos: a.. Resúmen de la arquitectura de los diferentes motores de la base de datos b.. Nuevas capacidades de MySQL 5.0, incluyendo Stored Procedures, Triggers, Views, e Information Schema. La versión 5.0 de MySQL se ha descargado más de cuatro millones de veces desde su lanzamiento en Octubre de 2005 c.. Presentación de MySQL Network, paquete de soporte y servicios de la base de datos empresarial todo en uno. d.. Explicación de los servicios que se ofrecerán a través de Afina Para registrarse, visite http://www.mysql.com/news-and-events/web-seminars/mysql-5.0.sp.php Quién: Gerardo Narvaja y Jimmy Guerrero, MySQL AB, y Gustavo La Iglesia, Responsable de Formación y Servicios de Afina. Qué: MySQL 5.0 - Nuevas funcionalidades para la empresa Cuándo: 1 de Febrero de 2006, 4:00 pm CET (Madrid), 11:00 am COT (Caracas) Duración: Aproximadamente una hora. Dónde: Acceso sencillo a través de Internet desde su oficina. Para qué: Conocer las nuevas funcionalidades de MySQL 5.0 y los servicios a los que puede acceder a través de Afina. Atentamente, MySQL AB Si desea informarse acerca de los servicios que Afina ofrece como Partner Gold Certificado de MySQL puede hacerlo llamando al 91 411 47 85 o envie un email a [EMAIL PROTECTED] -- Copyright © 2006 MySQL AB| www.mysql.com
oledb provider with transaction support?
i downloaded oledb provider from mysql.com, i use Delphi's ADO. but i found that this oledb provider does not support transaction. is there any oledb provider that does support transaction? thanks
RE: having trouble killing mysqld to restart and change root
Amendment to that last post I don't think the daemon is starting properly, because I can't run a mysqladmin version - I just get a hung cursor. Does anyone know if there's something that would be stopping mysqld from loading with the --skip-grant-tables option? When I do a ps I can see that it's definitely been started, but the fact that I can't do anything with mysqladmin makes me think that it hasn't loaded the way it needs to. JP Ye, that did the trick. I was able to get the daemon restarted using the --skip-grant-tables option, however now I can't connect to the monitor. Typing in /usr/bin/mysql I just get a hung cursor. Same if I try using /usr/bin/mysql -h hostname mysql Anyone know why I can't get the monitor started? JP At 03:20 PM 2/6/2002 -0600, you wrote: If you need to, use the kill -9 pid -9 is a definite kill and it will work -Original Message- From: JP Audette [mailto:[EMAIL PROTECTED]] Sent: Wednesday, February 06, 2002 2:52 PM To: [EMAIL PROTECTED] Subject: having trouble killing mysqld to restart and change root password Howdy, I'm trying to reset a forgotten password for a MySQL server, and I can't kill mysqld via the method mentioned in the documentation (or by any method for that matter). When I try using the command... kill 'cat /var/lib/mysql/mysqld.pid' ...I get a message saying that there is no such pid (although that's definitely the path specified for the pid when mysqld loads). I've also tried to kill it by running a ps -wax and killing these processes... 643 ?S 0:00 sh /usr/bin/safe_mysqld --datadir=/var/lib/mysql --pid-file=/var/lib/mysql/mysqld.pid 675 ?S 0:00 /usr/sbin/mysqld --basedir=/ --datadir=/var/lib/mysql --user=mysql --pid-file=/var/lib/mysql/mysqld.pid - 709 ?S 0:00 /usr/sbin/mysqld --basedir=/ --datadir=/var/lib/mysql --user=mysql --pid-file=/var/lib/mysql/mysqld.pid - 710 ?S 0:00 /usr/sbin/mysqld --basedir=/ --datadir=/var/lib/mysql --user=mysql --pid-file=/var/lib/mysql/mysqld.pid - I'm not sure if all of these are processes that are actively running, but killing them apparently does nothing because I am unable to load mysqld again so that I can restart it using the --skip-grant-tables option. Can someone help me understand which of the pid's is the actual one, and how I can kill it? Thanks, JP - 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 - 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
RE: having trouble killing mysqld to restart and change root
Ye, that did the trick. I was able to get the daemon restarted using the --skip-grant-tables option, however now I can't connect to the monitor. Typing in /usr/bin/mysql I just get a hung cursor. Same if I try using /usr/bin/mysql -h hostname mysql Anyone know why I can't get the monitor started? JP At 03:20 PM 2/6/2002 -0600, you wrote: If you need to, use the kill -9 pid -9 is a definite kill and it will work -Original Message- From: JP Audette [mailto:[EMAIL PROTECTED]] Sent: Wednesday, February 06, 2002 2:52 PM To: [EMAIL PROTECTED] Subject: having trouble killing mysqld to restart and change root password Howdy, I'm trying to reset a forgotten password for a MySQL server, and I can't kill mysqld via the method mentioned in the documentation (or by any method for that matter). When I try using the command... kill 'cat /var/lib/mysql/mysqld.pid' ...I get a message saying that there is no such pid (although that's definitely the path specified for the pid when mysqld loads). I've also tried to kill it by running a ps -wax and killing these processes... 643 ?S 0:00 sh /usr/bin/safe_mysqld --datadir=/var/lib/mysql --pid-file=/var/lib/mysql/mysqld.pid 675 ?S 0:00 /usr/sbin/mysqld --basedir=/ --datadir=/var/lib/mysql --user=mysql --pid-file=/var/lib/mysql/mysqld.pid - 709 ?S 0:00 /usr/sbin/mysqld --basedir=/ --datadir=/var/lib/mysql --user=mysql --pid-file=/var/lib/mysql/mysqld.pid - 710 ?S 0:00 /usr/sbin/mysqld --basedir=/ --datadir=/var/lib/mysql --user=mysql --pid-file=/var/lib/mysql/mysqld.pid - I'm not sure if all of these are processes that are actively running, but killing them apparently does nothing because I am unable to load mysqld again so that I can restart it using the --skip-grant-tables option. Can someone help me understand which of the pid's is the actual one, and how I can kill it? Thanks, JP - 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 - 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
having trouble killing mysqld to restart and change root password
Howdy, I'm trying to reset a forgotten password for a MySQL server, and I can't kill mysqld via the method mentioned in the documentation (or by any method for that matter). When I try using the command... kill 'cat /var/lib/mysql/mysqld.pid' ...I get a message saying that there is no such pid (although that's definitely the path specified for the pid when mysqld loads). I've also tried to kill it by running a ps -wax and killing these processes... 643 ?S 0:00 sh /usr/bin/safe_mysqld --datadir=/var/lib/mysql --pid-file=/var/lib/mysql/mysqld.pid 675 ?S 0:00 /usr/sbin/mysqld --basedir=/ --datadir=/var/lib/mysql --user=mysql --pid-file=/var/lib/mysql/mysqld.pid - 709 ?S 0:00 /usr/sbin/mysqld --basedir=/ --datadir=/var/lib/mysql --user=mysql --pid-file=/var/lib/mysql/mysqld.pid - 710 ?S 0:00 /usr/sbin/mysqld --basedir=/ --datadir=/var/lib/mysql --user=mysql --pid-file=/var/lib/mysql/mysqld.pid - I'm not sure if all of these are processes that are actively running, but killing them apparently does nothing because I am unable to load mysqld again so that I can restart it using the --skip-grant-tables option. Can someone help me understand which of the pid's is the actual one, and how I can kill it? Thanks, JP - 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: having trouble killing mysqld to restart and change root pass word
Ye, that did the trick. I was able to get the daemon restarted using the --skip-grant-tables option, however now I can't connect to the monitor. Typing in /usr/bin/mysql I just get a hung cursor. Same if I try using /usr/bin/mysql -h hostname mysql Anyone know why I can't get the monitor started? JP At 03:20 PM 2/6/2002 -0600, you wrote: If you need to, use the kill -9 pid -9 is a definite kill and it will work -Original Message- From: JP Audette [mailto:[EMAIL PROTECTED]] Sent: Wednesday, February 06, 2002 2:52 PM To: [EMAIL PROTECTED] Subject: having trouble killing mysqld to restart and change root password Howdy, I'm trying to reset a forgotten password for a MySQL server, and I can't kill mysqld via the method mentioned in the documentation (or by any method for that matter). When I try using the command... kill 'cat /var/lib/mysql/mysqld.pid' ...I get a message saying that there is no such pid (although that's definitely the path specified for the pid when mysqld loads). I've also tried to kill it by running a ps -wax and killing these processes... 643 ?S 0:00 sh /usr/bin/safe_mysqld --datadir=/var/lib/mysql --pid-file=/var/lib/mysql/mysqld.pid 675 ?S 0:00 /usr/sbin/mysqld --basedir=/ --datadir=/var/lib/mysql --user=mysql --pid-file=/var/lib/mysql/mysqld.pid - 709 ?S 0:00 /usr/sbin/mysqld --basedir=/ --datadir=/var/lib/mysql --user=mysql --pid-file=/var/lib/mysql/mysqld.pid - 710 ?S 0:00 /usr/sbin/mysqld --basedir=/ --datadir=/var/lib/mysql --user=mysql --pid-file=/var/lib/mysql/mysqld.pid - I'm not sure if all of these are processes that are actively running, but killing them apparently does nothing because I am unable to load mysqld again so that I can restart it using the --skip-grant-tables option. Can someone help me understand which of the pid's is the actual one, and how I can kill it? Thanks, JP - 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 - 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: having trouble killing mysqld to restart and change root pass word
Amendment to that last post I don't think the daemon is starting properly, because I can't run a mysqladmin version - I just get a hung cursor. Does anyone know if there's something that would be stopping mysqld from loading with the --skip-grant-tables option? When I do a ps I can see that it's definitely been started, but the fact that I can't do anything with mysqladmin makes me think that it hasn't loaded the way it needs to. JP Ye, that did the trick. I was able to get the daemon restarted using the --skip-grant-tables option, however now I can't connect to the monitor. Typing in /usr/bin/mysql I just get a hung cursor. Same if I try using /usr/bin/mysql -h hostname mysql Anyone know why I can't get the monitor started? JP At 03:20 PM 2/6/2002 -0600, you wrote: If you need to, use the kill -9 pid -9 is a definite kill and it will work -Original Message- From: JP Audette [mailto:[EMAIL PROTECTED]] Sent: Wednesday, February 06, 2002 2:52 PM To: [EMAIL PROTECTED] Subject: having trouble killing mysqld to restart and change root password Howdy, I'm trying to reset a forgotten password for a MySQL server, and I can't kill mysqld via the method mentioned in the documentation (or by any method for that matter). When I try using the command... kill 'cat /var/lib/mysql/mysqld.pid' ...I get a message saying that there is no such pid (although that's definitely the path specified for the pid when mysqld loads). I've also tried to kill it by running a ps -wax and killing these processes... 643 ?S 0:00 sh /usr/bin/safe_mysqld --datadir=/var/lib/mysql --pid-file=/var/lib/mysql/mysqld.pid 675 ?S 0:00 /usr/sbin/mysqld --basedir=/ --datadir=/var/lib/mysql --user=mysql --pid-file=/var/lib/mysql/mysqld.pid - 709 ?S 0:00 /usr/sbin/mysqld --basedir=/ --datadir=/var/lib/mysql --user=mysql --pid-file=/var/lib/mysql/mysqld.pid - 710 ?S 0:00 /usr/sbin/mysqld --basedir=/ --datadir=/var/lib/mysql --user=mysql --pid-file=/var/lib/mysql/mysqld.pid - I'm not sure if all of these are processes that are actively running, but killing them apparently does nothing because I am unable to load mysqld again so that I can restart it using the --skip-grant-tables option. Can someone help me understand which of the pid's is the actual one, and how I can kill it? Thanks, JP - 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 - 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
monitor will not start
Hi All, Does anyone know if a hard disk that is mostly full will stop the mysql monitor from starting? When I try to start it up all I get is a hung cursor, and I'm sure that the daemon has been properly started. MySQL isn't logging disk full errors to the .err file, so it seems like maybe that's not the problem (unless the monitor has different disk space needs than the tables). Are there any other reasons why the monitor won't start? I can't get mysqladmin to function properly either (same problem - hung cursor after entering the password). Thanks, JP - 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
need developer to help transfer our site
Hello, We have a site that uses PHP and MySQL on Linux, and we need to get it moved from our own server to a professionally hosted server. Unfortunately no one in our organization has enough Linux and MySQL knowledge to make this happen, so we're looking to hire an experienced developer for this project. The site is not very big, and our new host is already in place, so it should be mostly a matter of transferring files. If anyone on this list is interested in our meager project please reply to me directly at [EMAIL PROTECTED] Thanks, JP - 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
Grant problems
I have successfully installed MySQL 3.23.38. I can start the server and log in as root. When I try to grant new users using: grant insert to test.* for testuser identified by 'testpassword'; It comes back saying 0 rows affected. I can go the the MySQL db and look at the grant table and it will show testuser with proper privlidges but a very scrambled looking password (not sure if that is on purpose for security). But when I try to log that user in using: mysql -u testuser -p and then enter the password: testpassword The login fails everytime. Any help would be appreciated. Thanks!!! Justin Pease - 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
Configuring PHP for MySQL
Thanks for the responses. Unfortunately they didn't work. I tried /usr/local /usr/local/mysql /usr/lib /usr/lib/mysql /usr/var /usr/var/mysql and /usr/bin for the --with-mysql=/. command to configure PHP4. It still says Header files not found at ..Does anyone know what the file names are that would be considered the header files? That way I could just do a search. Also when configuring using the --with-mysql= what is the proper syntax to define more than one directory to search? Or can you not do that? Again this is for MySQL 3.23.38 that I installed using the RPM. Thanks for any help!!! Justin Pease - 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: Configuring PHP for MySQL
Sorry Jorge. I thought that the individuals on this list would be more qualified to answer a question regarding where a specific installation (3.23.38 RPM) of MySQL placed specific files ( header files? ) than would PHP users. Justin Pease On 17 May 2001, at 9:53, Jorge del Conde wrote: Hi, This Q should be asked in the php lists instead, but in the mean time, try configuring php like so: ./configure --with-mysql that usually does the trick when RPM's are installed ... Regards, Jorge MySQL Development Team __ ___ __ __ / |/ /_ __/ __/ __ \/ / Jorge del Conde [EMAIL PROTECTED] / /|_/ / // /\ \/ /_/ / /__ MySQL AB, http://www.mysql.com/ /_/ /_/\_, /___/\___\_\/ Mexico City, Mexico ___/ - Original Message - From: [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Wednesday, May 16, 2001 11:39 PM Subject: Configuring PHP for MySQL I just installed the latest version of MySQL (3.23.38 I believe) from an RPM on Red Hat Linux 7.0. My question is when configuring PHP4 I need to include the --with-mysql= ? statement. Where would the correct file be with the RPM install. I have tried almost every directory I can find that seems related to MySQL and I always get an error when I go to configure saying something like header files not found in __ (whatever directory I tried) Any help would be very appreciated!!! Thanks, and sorry for the newbie question. Justin Pease - 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 Sincerely, Justin Pease N u a n c e N i n e Web Development and Design www.nuance9.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
Re: Configuring PHP for MySQL
Well, thanks to everybody for their replies. I appreciate the help, and sorry to those who thought the question was asked in an inappropriate list. I ended up just configuring using --with-mysql=/* and everything seemed to work. Some how I doubt this was the *right* solution, but oh well. Like I said I'm a newbie. JP - 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
