Re: VERY Urgent!
On Monday, 13. May 2002 06:10, Matthew Hale wrote: > I work on a site called Creature World. We get ~110,000 pageviews per day. > Our server load is constantly at like >10. From investigation...pretty much > all of this load comes from mySQL. How can we optimize mysql to make it run > faster and produce less load? Hello, first take a look of the SHOW STATUS Output and analyze them. Maybe you have to change your values, or if you have slow queries, optimize your queries. Regards Georg - 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: VERY URGENT, possible bug. More on: What does this error message mean: InnoDB: Warning: difficult to find free blocks from the buffer pool..
Hi! MySQL AB and Innobase Oy entry-level support contract costs 3770 euros annually (3250 USD). For corporations with requirements for high availability we have more expensive telephone support options. These are extremely low priced compared against your costs for proprietary database products, and are low even when compared to rates charged by other open-source vendors. So please consider investing in a MySQL/InnoDB support contract. You will be served not by a help desk, but directly by the developers who author MySQL/InnoDB's source code. Information: http://www.mysql.com/support/index.html To Purchase: https://order.mysql.com/ About the buffer pool error: a similar bug in recovery was fixed in 3.23.45: ... November 17, 2001: In recovery InnoDB may go into an infinite loop constantly printing a warning message that it cannot find free blocks from the buffer pool. Fixed in 3.23.45. ... I have also a faint recollection that I then also fixed some additional error in the buffer pool flush algorithm which could cause the error messages to be printed in normal operation, not just recovery. Regards, Heikki Tuuri Innobase Oy - Original Message - From: "JW" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Cc: <[EMAIL PROTECTED]> Sent: Sunday, April 07, 2002 5:04 AM Subject: Re: VERY URGENT, possible bug. More on: What does this error message mean: InnoDB: Warning: difficult to find free blocks from the buffer pool.. > > I belive I have found a bug here, possibly. > The last known commands to be run on the DB that are "suspicious" were a join between 2 tables. > > > This is the info I got from the user who was workign on the DB: > > He was "joining between keyword and billing" > > select distinct(a.customerid) from cpcustomer.customerkeyword a left join cpbilling.billdetail b on a.customerid=b.customerid where b.customerid is null and active='y'; > > For some reason he hit ^c to exit (it didn't seem to be responding or somethign) > > He logged came back on to MySQL and ran: > > alter table add key bdetailcid (customerid); > show create billdetail; > > It crashed (locked up) durning the last query mentioned above. > > > I tried to shut down the server, but it wouldn't die so I ran the init-stop script a second time. > It seems that the init start/stop script gets forceful on the second try. > > Started it back up, it took a _very_ long time recovering (InnoDB), then started in with the error message I first posted. > > Any ideas? I'm currently restoring from backups we'll see how it goes. > > Thanks. > > JW >I forgot to point out that this is InnoDB > JW > > JW >I've searched Google and found the following disquiteing thing: > JW >http://www.innodb.com/oldbugs.html: > JW > > JW >"Closed or old bug reports: Almost all of these bugs have been fixed. There are some old bug reports where the cause of the bug was never found, but because there have been no bug reports for newer versions of InnoDB, these reports are not considered actual any more. " > JW > > JW >August 13, 2001: > JW >The fsync problem which was fixed in 3.23.40b and .41 could cause the following warning message on some Unix flavors: > JW > > JW >Innobase: Warning: difficult to find free blocks from > JW >Innobase: the buffer pool! Consider increasing the > JW >Innobase: buffer pool size. > JW > > JW >If you encounter the above message, upgrade to 3.23.41." > JW > > JW >However, I'm already using a newer vresion than that: > JW > > JW >ccs012:~ # rpm -qa |grep mysql > JW >mysql-shared-3.23.44-5 > JW >mysql-Max-3.23.44-5 > JW >mysql-devel-3.23.44-5 > JW >mysql-navigator-1.2.3-106 > JW >mysql-client-3.23.44-5 > JW >mysql-3.23.44-5 > JW >mysql-bench-3.23.44-5 > JW >ccs012:~ # > JW > > JW >This is a mission critical DB. Am I the lucky un-fortunate to re-dicover this supposedly fixed bug? > JW > > JW >JW >I'm getting this error messge constantly in my error log: > JW >JW > > JW >JW >020406 18:02:50 *** > JW >JW >InnoDB: Warning: difficult to find free blocks from > JW >JW >InnoDB: the buffer pool (200 search iterations)! Consider > JW >JW >InnoDB: increasing the buffer pool size. > JW >JW >InnoDB: It is also possible that in your Unix version > JW >JW >InnoDB: fsync is very slow, or completely frozen inside > JW >JW >InnoDB: the OS kernel. Then upgrading to a newer version > JW >JW >InnoDB: of your operating system may help. Look at the > JW >JW >InnoDB: number of fsyncs in diagnostic info below. > JW >JW
Re: VERY URGENT, possible bug. More on: What does this error message mean: InnoDB: Warning: difficult to find free blocks from the buffer pool..
I belive I have found a bug here, possibly. The last known commands to be run on the DB that are "suspicious" were a join between 2 tables. This is the info I got from the user who was workign on the DB: He was "joining between keyword and billing" select distinct(a.customerid) from cpcustomer.customerkeyword a left join cpbilling.billdetail b on a.customerid=b.customerid where b.customerid is null and active='y'; For some reason he hit ^c to exit (it didn't seem to be responding or somethign) He logged came back on to MySQL and ran: alter table add key bdetailcid (customerid); show create billdetail; It crashed (locked up) durning the last query mentioned above. I tried to shut down the server, but it wouldn't die so I ran the init-stop script a second time. It seems that the init start/stop script gets forceful on the second try. Started it back up, it took a _very_ long time recovering (InnoDB), then started in with the error message I first posted. Any ideas? I'm currently restoring from backups we'll see how it goes. Thanks. JW >I forgot to point out that this is InnoDB JW > JW >I've searched Google and found the following disquiteing thing: JW >http://www.innodb.com/oldbugs.html: JW > JW >"Closed or old bug reports: Almost all of these bugs have been fixed. There are some old bug reports where the cause of the bug was never found, but because there have been no bug reports for newer versions of InnoDB, these reports are not considered actual any more. " JW > JW >August 13, 2001: JW >The fsync problem which was fixed in 3.23.40b and .41 could cause the following warning message on some Unix flavors: JW > JW >Innobase: Warning: difficult to find free blocks from JW >Innobase: the buffer pool! Consider increasing the JW >Innobase: buffer pool size. JW > JW >If you encounter the above message, upgrade to 3.23.41." JW > JW >However, I'm already using a newer vresion than that: JW > JW >ccs012:~ # rpm -qa |grep mysql JW >mysql-shared-3.23.44-5 JW >mysql-Max-3.23.44-5 JW >mysql-devel-3.23.44-5 JW >mysql-navigator-1.2.3-106 JW >mysql-client-3.23.44-5 JW >mysql-3.23.44-5 JW >mysql-bench-3.23.44-5 JW >ccs012:~ # JW > JW >This is a mission critical DB. Am I the lucky un-fortunate to re-dicover this supposedly fixed bug? JW > JW >JW >I'm getting this error messge constantly in my error log: JW >JW > JW >JW >020406 18:02:50 *** JW >JW >InnoDB: Warning: difficult to find free blocks from JW >JW >InnoDB: the buffer pool (200 search iterations)! Consider JW >JW >InnoDB: increasing the buffer pool size. JW >JW >InnoDB: It is also possible that in your Unix version JW >JW >InnoDB: fsync is very slow, or completely frozen inside JW >JW >InnoDB: the OS kernel. Then upgrading to a newer version JW >JW >InnoDB: of your operating system may help. Look at the JW >JW >InnoDB: number of fsyncs in diagnostic info below. JW >JW >InnoDB: Pending flushes (fsync) log: 0; buffer pool: 0 JW >JW >InnoDB: 5703 OS file reads, 502 OS file writes, 82 OS fsyncs JW >JW >InnoDB: Starting InnoDB Monitor to print further JW >JW >InnoDB: diagnostics to the standard output. JW >JW > JW >JW >Running SuSE Linux 7.3: JW >JW > JW >JW >ccs012:/var/lib/mysql # uname -a ; df -h ; free -m JW >JW >Linux ccs012 2.4.10-64GB-SMP #1 SMP Fri Sep 28 17:26:36 GMT 2001 i686 unknown JW >JW >FilesystemSize Used Avail Use% Mounted on JW >JW >/dev/sda7 67G 59G 8.2G 88% / JW >JW >/dev/sda5 63M 36M 26M 58% /boot JW >JW >shmfs1007M 0 1006M 0% /dev/shm JW >JW > total used free sharedbuffers cached JW >JW >Mem: 2013 2008 4 0 10657 JW >JW >-/+ buffers/cache: 1340672 JW >JW >Swap: 1035 0 1035 JW >JW > JW >JW > JW >JW >TIA JW >JW > JW >JW >-- JW >JW > JW >JW > JW >JW >Jonathan Wilson JW >JW >System Administrator JW >JW >Clickpatrol.com JW >JW >Cedar Creek Software http://www.cedarcreeksoftware.com JW >JW > JW >JW > JW >JW > JW >JW >- JW >JW >Before posting, please check: JW >JW > http://www.mysql.com/manual.php (the manual) JW >JW > http://lists.mysql.com/ (the list archive) JW >JW > JW >JW >To request this thread, e-mail <[EMAIL PROTECTED]> JW >JW >To unsubscribe, e-mail <[EMAIL PROTECTED]> JW >JW >Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php JW >JW > JW >JW > JW >JW > JW > JW >-- JW > JW > JW >Jonathan Wilson JW >System Administrator JW >Clickpatrol.com JW >Cedar Creek Software http://www.cedarcreeksoftware.com JW > JW > JW > JW >- JW >Before posting, please check: JW > http://www.mysql.com/manual.php (the manual)
Re: Very Urgent (sic)
Im's sending this to the list, since I got it in a private mail and I don't see myself as a substitute for the combined wisdom, knowledge, and willingness to help that is the MySQL mailing list. SHAM SUNDAR writes: > I won't do sql operations using JDBC like insert,delete,select and update.When i >create connection object it is throwing General argument. > I am able to connect with the same username and password by mysql prompt.But not >using JDBC with the same username and password.Can u pls help it is very urgent.If i >give different password it is throwing authentication failed. -- Carl Troein - Círdan / Istari-PixelMagic - UIN 16353280 [EMAIL PROTECTED] | http://pixelmagic.dyndns.org/~cirdan/ Amiga user since '89, and damned proud of it too. - 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: Very Urgent
SHAM SUNDAR writes: >When i cannect from my java program i use to get > error General Error: 22.Can u pls help in this.My > mysql version is 3.23.46 perror 22 will tell you that error 22 is 'Invalid argument', but since you don't state what you're trying to do that is of little help. Maybe if you post excatly what you're doing and what goes wrong, someone with experience of JDBC (I would guess that that's what you're using) will be able to help you. Oh, and generally: Please use the subject line more wisely. Few people read all the mails on this list, and you risk having all the people who know the answer skip your mail just because they don't know what it's about. A subject like "very urgent" will, at least in me, trigger thoughts along the lines of "So this person is in a hurry, which means he/she hasn't done any research or tried to solve the problem. And probably the problem description is something along the lines of 'it doesn't work'." Not that I haven't made the same mistake myself, but that's all the more reason for me to react, right? Finally, a reminder to everyone: If you have a problem, you should always consider buying a support contract from MySQL AB. Hell, even if you don't have a problem, consider buying one just to support them. After all, without the money they wouldn't be able to do as much developing as they do. //C -- Carl Troein - Círdan / Istari-PixelMagic - UIN 16353280 [EMAIL PROTECTED] | http://pixelmagic.dyndns.org/~cirdan/ Amiga user since '89, and damned proud of it too. - 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: Very Urgent
1. Start the mysqld. 2. Make sure it is opening the socket in /var/lin/mysql 3. Make sure /var/lin/mysql is set mode 775 Balaji Nallathambi wrote: > > Iam Getting the error > "Unable to Connect to Local MySql Server through socket 'var/lin/mysql/ > mysql.sock" > my Version For MySql is 3.22.32. > What is Th solutin For this mail me asap > adieu > Balaji.N > > > Get free email and a permanent address at http://www.netaddress.com/?N=1 > > - > 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
