Re: REPOST: MySQL 3.23.54 is a buggy, crashing piece of crap.
The tables I am querying the most are quite small. I just query them a lot. The system processes about 500k requests a day, and each request involves multiple queries. I have just enabled a bunch of logging to try and puzzle out what is going on, but I can't see it being a help.. The same queries execute over and over and over, for 24 hours until eventually they stop working. Perhaps the logs will have some errors messages or something that will be helpful. It really seems to me (as a programmer) that MySQL is running itself out of something internally, and then just finally dying. I am not a big system admin guy, but I am going to get upgraded to .55 in the next few minutes, to see if that helps at all.. Reading the changes list I don't see anything that would affect me, but ya never know. Thanks for the assistance. Cheers, Jason - Original Message - From: "Zak Greant" <[EMAIL PROTECTED]> To: "Jason Maskell" <[EMAIL PROTECTED]> Cc: <[EMAIL PROTECTED]> Sent: Monday, February 17, 2003 2:10 AM Subject: Re: REPOST: MySQL 3.23.54 is a buggy, crashing piece of crap. > On Mon, Feb 17, 2003 at 01:37:59AM -0600, Jason Maskell wrote: > > Perhaps the subject will get someone to actually read this and offer even > > one reply with a suggestion? > > I admit that the topic got my attention - perhaps not in the best way > though. > > I can offer a few suggestions: > > Provide more details: >- How big is the table you are querying? >- What is the query that you are running? >- Do you have logging enabled? If so, does it report any error > messages/slow queries/etc. >- Is this the first time that you have encountered the issue? >- etc... > > Can you upgrade? There have been bug fixes and enhancements in the > versions that have been released since x.54. While I am not sure that > they would fix your issues, this is a fairly quick thing to test - of > course, make sure that you have back ups (just in case)! > > Also, keep in mind that it is the weekend and that this is a volunteer > list. I would guess that our resident FreeBSD guru (Jeremy Z.) is out > working on his latest book. Assuming that you have not pissed him off, > he may help you out. :) > > > Cheers! > -- > Zak Greant <[EMAIL PROTECTED]> > MySQL AB Community Advocate > Personal Blog: http://zak.fooassociates.com > > MySQL Tip: InnoDB in 4.0.8 supports ON UPDATE foreign key constraints > See http://www.mysql.com/doc/en/SEC449.html for more details > - 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
REPOST: MySQL 3.23.54 is a buggy, crashing piece of crap.
Perhaps the subject will get someone to actually read this and offer even one reply with a suggestion? NB: This now kills mysql (process hang) in around 24 hours of uptime. --- I'm hoping someone can help me, I've got a problem with mysql going insane.. I've a quite busy application (avg 700 queries a second right now) - with about 40 odd seperate databases (scalability requirement) Anyway, depending on volume of transactions, it seems to go insane. I am using a mix of InnoDB for the important tables, and MyISAM for the raw data tables. After a while, one of my queries that uses RAND() as an order by simply stops returning any rows, either in the script that's calling it or the mysql shell. Remove the RAND() and it works fine. Then shortly after that, it fails altogether, and I have to kill a mysqld process that's hung and restart. This is on a FreeBSD 4.7 system, with 2gigs of ram. Restarting seems to fix it, so I have to assume that something's leaking. Can php cause mysql to leak resources? I dunno what's going on here, but the script is going to get substantially busier and I don't wanna have to be restarting this damn thing every few hours. Any help? I'll be quite happy to provide any information needed, but the system is currently running, so I can't be too crazy with it, I'd like to be able to diagnose and/or fix the problem without too much (or any) downtime. Cheers, Jason - 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 3.23.54 degrades and eventually hangs/has to be restarted
Reposted from my NG post, I'm hoping someone can help out, this is getting ugly. The problem I am describing is happenning in less than 24 hours now. As volume increases the period is getting shorter. I'm hoping someone can help me, I've got a problem with mysql going insane.. I've a quite busy application (avg 700 queries a second right now) - with about 40 odd seperate databases (scalability requirement) Anyway, depending on volume of transactions, it seems to go insane. I am using a mix of InnoDB for the important tables, and MyISAM for the raw data tables. After a while, one of my queries that uses RAND() as an order by simply stops returning any rows, either in the script that's calling it or the mysql shell. Remove the RAND() and it works fine. Then shortly after that, it fails altogether, and I have to kill a mysqld process that's hung and restart. This is on a FreeBSD 4.7 system, with 2gigs of ram. Restarting seems to fix it, so I have to assume that something's leaking. Can php cause mysql to leak resources? I dunno what's going on here, but the script is going to get substantially busier and I don't wanna have to be restarting this damn thing every few hours. Any help? I'll be quite happy to provide any information needed, but the system is currently running, so I can't be too crazy with it, I'd like to be able to diagnose and/or fix the problem without too much (or any) downtime. Cheers, Jason - 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