Re: Mysql server not able to stay running on anything but Linux?
Hey everyone, Not trying to beat a dead horse or anything but was wondering if any resolution was found for this on either end. We are about to launch another site and can easily forsee my load getting close to this size within 6 months. Just need to find out any concerns with growth we might have and come up with options. Just trying to plan ahead and keep problems from happening, since I hadn't seen any formal resolution on this thread figured I'd inquire. Thanks everyone Justin Bastedo On 10/12/05, NMH [EMAIL PROTECTED] wrote: --- Greg 'groggy' Lehey [EMAIL PROTECTED] wrote: Note the From: address. On Wednesday, 12 October 2005 at 13:16:22 -0700, NMH wrote: I am stuck with a delema and I feel like a damn troll. But.. I have a Mysql Database that I posted about earlier. It seems that it is only able to not die by running on BSD 4.11 with Linux Threads. My boss is convinced this means that Linux is better for MySQL and wants that installed now. We even got a support contact from Mysql that so far has gotten us nothing for almost a month while our production database server died up to 3 times a day. (and lots of we're looking into it's) One of the reasons why you haven't got much more than we're looking into its is because we haven't been able to reproduce the problem; you acknowledge this in follow-up mail quoted below. As you know from various threads on the FreeBSD lists, including this one, the typical answer is works fine for me. That doesn't mean that we're not taking your problems seriously, but we do have a significant issue just reproducing the problem. We have a number of choices: 1. Try different hardware or a different version of FreeBSD. It's conceivable that there's something about your specific hardware, or about the combination of i386 kernel on amd64 in general, that triggers the problem. Yes possible. However the same hardware was used for the earlier version machine that worked fine. IE Freebsd 5.1-RELEASE-P11 and Mysql 4.0.18 worked on the same hardware. 2. Do debugging on your production servers. This isn't really a choice at all: it would involve even more down time. Yea not really an option. 3. Get you to run a more stable version of FreeBSD while we investigate the problem. This is the method we chose. I haven't heard from you since the weekend, so I hope I'm correct in understanding that you currently don't have stability problems. On our side, we have installed FreeBSD 5.4 on one of our internal machines, and we're trying to reproduce the problem there. So far we have had only one crash that seemed to have been SCSI related. So far it has not happend again. One problem with replication that was a coding issue. We were running fine but a little slow on FreeBSD 5.1-P11 and MySQL 4.0.18.(apperantly before a big Lib change) We had to move quicker than we wanted to a new server running FreeBSD 5.4 and MySQL 4.11 (becouse of a dual HD death) Under production load the new 5.4 server fell over regulary. It has only now become stable by wiping it and running it on FreeBSD 4.11 with Linux Threads. (it regularly has over 400+ threads) Kris obviously understood that by this statement you meant a kernel crash. My understanding is that only the mysqld server is crashing. Is this still correct? Yes only Mysqld would crash. Sometimes brb and autorestart with minimal damage. Other times it would die a horrible death and damage tons of data on its way out. I want to try FreeBSD 5.4 AMD64 (the machines are Opteron) or 6.0 but my boss feels that would be a waste given that MYSQL doesn't support Mysql on AMD64 well enough. I think it would be a good idea to try this. It's one of the things that we intend to do in-house as soon as we can reproduce the problem at all. Yes however as I pointed out.. Just Trying things on a production database is not desirable without some serious indicators that its worthwhile. Last you wrote you said you doubted that would do anything I believe. Also support for amd64 based mysql is listed as Limited. As you said reproducing the problem is the key. However as I suggested I would have thought that if mysql were really into solving the problem, someone would have requested a login on the box to look at our queries to see how they are. Are they 60% reads 40% writes, are they many divergent queries bundled together.. etc. IE come and see our production database in action to see what needs to be replicated. I haven't seen anything like this. Now I don't know much but to me if I can't replicate something it's becouse I don't know enough about it. Can anyone help or offer assistance to help track this down? Perhaps also any annecdotes or examples I can show my boss
Re: Mysql server not able to stay running on anything but Linux?
On 11/9/05, Justin Bastedo [EMAIL PROTECTED] wrote: Hey everyone, Not trying to beat a dead horse or anything but was wondering if any resolution was found for this on either end. We are about to launch another site and can easily forsee my load getting close to this size within 6 months. Just need to find out any concerns with growth we might have and come up with options. Just trying to plan ahead and keep problems from happening, since I hadn't seen any formal resolution on this thread figured I'd inquire. Thanks everyone Justin Bastedo On 10/12/05, NMH [EMAIL PROTECTED] wrote: --- Greg 'groggy' Lehey [EMAIL PROTECTED] wrote: Note the From: address. On Wednesday, 12 October 2005 at 13:16:22 -0700, NMH wrote: I am stuck with a delema and I feel like a damn troll. But.. I have a Mysql Database that I posted about earlier. It seems that it is only able to not die by running on BSD 4.11 with Linux Threads. My boss is convinced this means that Linux is better for MySQL and wants that installed now. We even got a support contact from Mysql that so far has gotten us nothing for almost a month while our production database server died up to 3 times a day. (and lots of we're looking into it's) One of the reasons why you haven't got much more than we're looking into its is because we haven't been able to reproduce the problem; you acknowledge this in follow-up mail quoted below. As you know from various threads on the FreeBSD lists, including this one, the typical answer is works fine for me. That doesn't mean that we're not taking your problems seriously, but we do have a significant issue just reproducing the problem. We have a number of choices: 1. Try different hardware or a different version of FreeBSD. It's conceivable that there's something about your specific hardware, or about the combination of i386 kernel on amd64 in general, that triggers the problem. Yes possible. However the same hardware was used for the earlier version machine that worked fine. IE Freebsd 5.1-RELEASE-P11 and Mysql 4.0.18 worked on the same hardware. 2. Do debugging on your production servers. This isn't really a choice at all: it would involve even more down time. Yea not really an option. 3. Get you to run a more stable version of FreeBSD while we investigate the problem. This is the method we chose. I haven't heard from you since the weekend, so I hope I'm correct in understanding that you currently don't have stability problems. On our side, we have installed FreeBSD 5.4 on one of our internal machines, and we're trying to reproduce the problem there. So far we have had only one crash that seemed to have been SCSI related. So far it has not happend again. One problem with replication that was a coding issue. We were running fine but a little slow on FreeBSD 5.1-P11 and MySQL 4.0.18.(apperantly before a big Lib change) We had to move quicker than we wanted to a new server running FreeBSD 5.4 and MySQL 4.11 (becouse of a dual HD death) Under production load the new 5.4 server fell over regulary. It has only now become stable by wiping it and running it on FreeBSD 4.11 with Linux Threads. (it regularly has over 400+ threads) Kris obviously understood that by this statement you meant a kernel crash. My understanding is that only the mysqld server is crashing. Is this still correct? Yes only Mysqld would crash. Sometimes brb and autorestart with minimal damage. Other times it would die a horrible death and damage tons of data on its way out. I want to try FreeBSD 5.4 AMD64 (the machines are Opteron) or 6.0 but my boss feels that would be a waste given that MYSQL doesn't support Mysql on AMD64 well enough. I think it would be a good idea to try this. It's one of the things that we intend to do in-house as soon as we can reproduce the problem at all. Yes however as I pointed out.. Just Trying things on a production database is not desirable without some serious indicators that its worthwhile. Last you wrote you said you doubted that would do anything I believe. Also support for amd64 based mysql is listed as Limited. As you said reproducing the problem is the key. However as I suggested I would have thought that if mysql were really into solving the problem, someone would have requested a login on the box to look at our queries to see how they are. Are they 60% reads 40% writes, are they many divergent queries bundled together.. etc. IE come and see our production database in action to see what needs to be replicated. I haven't seen anything like this. Now I don't know much but to me if I can't replicate something it's becouse I don't know enough
Re: Mysql server not able to stay running on anything but Linux?
On Oct 12, 2005, at 2:16 PM, NMH wrote: Hi I am stuck with a delema and I feel like a damn troll. But.. I have a Mysql Database that I posted about earlier. It seems that it is only able to not die by running on BSD 4.11 with Linux Threads. My boss is convinced this means that Linux is better for MySQL and wants that installed now. We even got a support contact from Mysql that so far has gotten us nothing for almost a month while our production database server died up to 3 times a day. (and lots of we're looking into it's) does the mysql error log have anything of interest in it related to the crashes? in your mysl/var dir ending in .err Chad --- Chad Leigh -- Shire.Net LLC Your Web App and Email hosting provider [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Mysql server not able to stay running on anything but Linux?
Hi I am stuck with a delema and I feel like a damn troll. But.. I have a Mysql Database that I posted about earlier. It seems that it is only able to not die by running on BSD 4.11 with Linux Threads. My boss is convinced this means that Linux is better for MySQL and wants that installed now. We even got a support contact from Mysql that so far has gotten us nothing for almost a month while our production database server died up to 3 times a day. (and lots of we're looking into it's) We were running fine but a little slow on FreeBSD 5.1-P11 and MySQL 4.0.18.(apperantly before a big Lib change) We had to move quicker than we wanted to a new server running FreeBSD 5.4 and MySQL 4.11 (becouse of a dual HD death) Under production load the new 5.4 server fell over regulary. It has only now become stable by wiping it and running it on FreeBSD 4.11 with Linux Threads. (it regularly has over 400+ threads) MySQL hinted to us that for better support we should move to Linux since that is what they develop on and would somehow better help them solve the problem. I really don't want to run Linux! We have been a FreeBSD only shop for some time and I find it amazing that 5.4 BSD can't support Mysql under a heavy 400+ thread load without Mysql falling over itself and dying. I want to try FreeBSD 5.4 AMD64 (the machines are Opteron) or 6.0 but my boss feels that would be a waste given that MYSQL doesn't support Mysql on AMD64 well enough. Also that given their hints that for the best support we should move our database to Linux to help solve this issue and that so far it has only run with any stability using Linux Threads, So why not just run Linux. That should be even better. Can anyone help or offer assistance to help track this down? Perhaps also any annecdotes or examples I can show my boss that other people have as busy MYSQL databases on BSD 5.X. We paid 3K to Mysql for help and so far they have been unable to offer any clues as to why ours will not stay stable on anything but Linux threads. I feel really sad that so far no one has responded to my posts and it feels like a victory for linux. As I say I only manage the server, I don't program the databases. Is there anything I should/could look for database wise that could trigger such things? The biggest problem with all this is that we have not been able to replicate it. The Mysql Server on 5.4 only dies when under production load. Nothing we or Mysql have been able to simulate seems to have the same effect. Any idea why this could be as well? Not enough randomness? Please help me keep a Freebsd only shop that way. Thanks! NMH The Large Print Giveth And The Small Print Taketh Away -- Anon __ Yahoo! Music Unlimited Access over 1 million songs. Try it free. http://music.yahoo.com/unlimited/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Mysql server not able to stay running on anything but Linux?
On Wed, Oct 12, 2005 at 01:16:22PM -0700, NMH wrote: Hi I am stuck with a delema and I feel like a damn troll. But.. I have a Mysql Database that I posted about earlier. It seems that it is only able to not die by running on BSD 4.11 with Linux Threads. My boss is convinced this means that Linux is better for MySQL and wants that installed now. We even got a support contact from Mysql that so far has gotten us nothing for almost a month while our production database server died up to 3 times a day. (and lots of we're looking into it's) We were running fine but a little slow on FreeBSD 5.1-P11 and MySQL 4.0.18.(apperantly before a big Lib change) We had to move quicker than we wanted to a new server running FreeBSD 5.4 and MySQL 4.11 (becouse of a dual HD death) Under production load the new 5.4 server fell over regulary. It has only now become stable by wiping it and running it on FreeBSD 4.11 with Linux Threads. (it regularly has over 400+ threads) Unfortunately you'll need to provide details of how it fell over (e.g. panic messages + backtraces). You might have better luck with 6.0-RELEASE or 5.4-STABLE, since a number of bugs have been fixed in 5.4-RELEASE..but without more details it's impossible to say whether that will help, or if you're encountering something genuinely new. Can anyone help or offer assistance to help track this down? Perhaps also any annecdotes or examples I can show my boss that other people have as busy MYSQL databases on BSD 5.X. We paid 3K to Mysql for help and so far they have been unable to offer any clues as to why ours will not stay stable on anything but Linux threads. I feel really sad that so far no one has responded to my posts and it feels like a victory for linux. If I was your boss I'd be asking why mysql hasn't delivered on their support contract. Kris pgpr0c6Dz3iRx.pgp Description: PGP signature
Re: Mysql server not able to stay running on anything but Linux?
Here at my work we are running a mysql 5.0 server on FreeBSD 5.4 using the AMD Dual Core 64 chips. current load is as follows: [MYSQL] Uptime: 1338832 Threads: 2 Questions: 15846788 Slow queries: 0 Opens: 0 Flush tables: 16 Open tables: 58 Queries per second avg: 11.836 [FREEBSD TOP] last pid: 29924; load averages: 0.00, 0.00, 0.00 up 35+01:59:20 16:24:01 49 processes: 1 running, 48 sleeping CPU states: 0.5% user, 0.0% nice, 0.5% system, 0.0% interrupt, 99.0% idle Mem: 156M Active, 1250M Inact, 176M Wired, 214M Buf, 2086M Free Swap: 2048M Total, 44K Used, 2048M Free Versions: mysql -V mysql Ver 14.12 Distrib 5.0.12-beta, for portbld-freebsd5.4 (amd64) using 4.3 uname -a FreeBSD db 5.4-RELEASE-p7 FreeBSD 5.4-RELEASE-p7 #0: Wed Sep 7 14:12:34 CDT 2005 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/BLITZ4SMP amd64 Our queries per second avg has been going up consistently and we have yet to have any problems. We haven't had any crashing though I can't quite say how the thread level is comparing to yours. I agree i would look into upgrading to 5.4-STABLE and see how that treats you. As far as my experience the only real advantages I've found that linux has over FreeBSD is the type of file systems. Some of the file systems they support may give better performance to particular types of table types, but that is more if you have a stable db server that is hitting a bottle neck. -- Justin Bastedo At Gmail Dot Com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Mysql server not able to stay running on anything but Linux?
--- Kris Kennaway [EMAIL PROTECTED] wrote: On Wed, Oct 12, 2005 at 01:16:22PM -0700, NMH wrote: Hi I am stuck with a delema and I feel like a damn troll. But.. I have a Mysql Database that I posted about earlier. It seems that it is only able to not die by running on BSD 4.11 with Linux Threads. My boss is convinced this means that Linux is better for MySQL and wants that installed now. We even got a support contact from Mysql that so far has gotten us nothing for almost a month while our production database server died up to 3 times a day. (and lots of we're looking into it's) We were running fine but a little slow on FreeBSD 5.1-P11 and MySQL 4.0.18.(apperantly before a big Lib change) We had to move quicker than we wanted to a new server running FreeBSD 5.4 and MySQL 4.11 (becouse of a dual HD death) Under production load the new 5.4 server fell over regulary. It has only now become stable by wiping it and running it on FreeBSD 4.11 with Linux Threads. (it regularly has over 400+ threads) Unfortunately you'll need to provide details of how it fell over (e.g. panic messages + backtraces). You might have better luck with 6.0-RELEASE or 5.4-STABLE, since a number of bugs have been fixed in 5.4-RELEASE..but without more details it's impossible to say whether that will help, or if you're encountering something genuinely new. Can anyone help or offer assistance to help track this down? Perhaps also any annecdotes or examples I can show my boss that other people have as busy MYSQL databases on BSD 5.X. We paid 3K to Mysql for help and so far they have been unable to offer any clues as to why ours will not stay stable on anything but Linux threads. I feel really sad that so far no one has responded to my posts and it feels like a victory for linux. If I was your boss I'd be asking why mysql hasn't delivered on their support contract. Kris Hi Kris Well I think support has many meanings. I decided to look at what he paid for and it says: We get access to the mysql devlopers... We get access to certified binaries. (none of which are FreeBSD) So, sad as it may seem, if your running on FreeBSD, $3000.00 buys you someone to talk to. It doesn't mean they have to say anything meaningful back or within any reasonable time. :( Also it doesn't cover tuning or code review etc. So if our problem is caused by anything like that.. they don't even have to tell us I would imagine. So.. that is why as always, these lists and fellow FreeBSD people are their own best support. Sadly this is good and bad. Without enough paying users, you don't tend to get as much attention. (this applies to hardware and software) NMH The Large Print Giveth And The Small Print Taketh Away -- Anon __ Start your day with Yahoo! - Make it your home page! http://www.yahoo.com/r/hs ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Mysql server not able to stay running on anything but Linux?
--- Justin Bastedo [EMAIL PROTECTED] wrote: Here at my work we are running a mysql 5.0 server on FreeBSD 5.4 using the AMD Dual Core 64 chips. current load is as follows: [MYSQL] Uptime: 1338832 Threads: 2 Questions: 15846788 Slow queries: 0 Opens: 0 Flush tables: 16 Open tables: 58 Queries per second avg: 11.836 [FREEBSD TOP] last pid: 29924; load averages: 0.00, 0.00, 0.00 up 35+01:59:20 16:24:01 49 processes: 1 running, 48 sleeping CPU states: 0.5% user, 0.0% nice, 0.5% system, 0.0% interrupt, 99.0% idle Mem: 156M Active, 1250M Inact, 176M Wired, 214M Buf, 2086M Free Swap: 2048M Total, 44K Used, 2048M Free Versions: mysql -V mysql Ver 14.12 Distrib 5.0.12-beta, for portbld-freebsd5.4 (amd64) using 4.3 uname -a FreeBSD db 5.4-RELEASE-p7 FreeBSD 5.4-RELEASE-p7 #0: Wed Sep 7 14:12:34 CDT 2005 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/BLITZ4SMP amd64 Our queries per second avg has been going up consistently and we have yet to have any problems. We haven't had any crashing though I can't quite say how the thread level is comparing to yours. I agree i would look into upgrading to 5.4-STABLE and see how that treats you. As far as my experience the only real advantages I've found that linux has over FreeBSD is the type of file systems. Some of the file systems they support may give better performance to particular types of table types, but that is more if you have a stable db server that is hitting a bottle neck. -- Justin Bastedo At Gmail Dot Com Hi Justin Right now here are our stats.. As you can see.. we beat it up pretty good. [MYSQL] Uptime: 174044 Threads: 396 Questions: 140154383 Slow queries: 16 Opens: 2622 Flush tables: 1 Open tables: 1189 Queries per second avg: 805.281 [FREEBSD TOP] (BSD 4.11-STABLE) last pid: 40914; load averages: 0.65, 0.69, 0.74 436 processes: 5 running, 431 sleeping CPU states: 0.5% user, 22.1% nice, 8.1% system, 0.4% interrupt, 69.4% idle Mem: 483M Active, 3046M Inact, 291M Wired, 136M Cache Buf, 6070K Free Swap: 8192M Total, 68K Used, 8192M Free NMH The Large Print Giveth And The Small Print Taketh Away -- Anon __ Start your day with Yahoo! - Make it your home page! http://www.yahoo.com/r/hs ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Mysql server not able to stay running on anything but Linux?
Yeah i still have quite a way to go to catch up on you on actual usage, but would be good to see if the problem persisted on the 5.4-STABLE release. As Kris said a number of bugs have been fixed in 5.4-RELEASE.. it might be a good test. Also does this persist across all the versions of mysql? I know they just launched the RC of 5.0, may be able to leverage that a bit i know they are really pushing to get that released, and might be nice knowing that this problem is fixed in the new release. I'm definately interested to see what the final solution is on this matter. I can easily forsee our db load getting close to that level within the next couple of months depending on how these contracts play out. Justin ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Mysql server not able to stay running on anything but Linux?
--- Justin Bastedo [EMAIL PROTECTED] wrote: Yeah i still have quite a way to go to catch up on you on actual usage, but would be good to see if the problem persisted on the 5.4-STABLE release. As Kris said a number of bugs have been fixed in 5.4-RELEASE.. it might be a good test. Also does this persist across all the versions of mysql? I know they just launched the RC of 5.0, may be able to leverage that a bit i know they are really pushing to get that released, and might be nice knowing that this problem is fixed in the new release. Hi again :) Well we built 3 fairly identical servers for testing and to try replication. At first they all had BSD 5.4-RELEASE. One had -P4 the other 2 had -p6 So they were pretty high up there on the patch levels. Also to stop them from falling over constantly we had to insert: (as it seemed the other threads could not support it at all!) /etc/libmap.conf libpthread.so libthr.so libpthread.so.1 libthr.so.1 Also no one from Mysql seemed to think going to STABLE would do anything. It's a very very tough thing to play lets see what happens if.. On production servers. The time it takes us just to bounce from one machine to another is pretty decent. Let alone downtime etc. Hence my boss's push for Linux. Since MYSQL says it will definatly work on Linux.. We should switch to Linux. I'm definately interested to see what the final solution is on this matter. I can easily forsee our db load getting close to that level within the next couple of months depending on how these contracts play out. Well, I will post whatever happens. As I said the most annoying part to all this is that so far we have been unable to crash the 5.4 servers via any testing means we (and Mysql) could come up with. Yet in production they fell over as soon as the load started to climb and points in between. But never on the slope of decreasing load for the day. (always felt that was odd) IE it would die on the bell curve increases but never at the coresponding downward cycle of the daily busy curve. If anyone knows of any particulary evil testing programs I would love to know. It's tough to simulate 30+ servers asking lots questions and forcing tons of writes. Thanks! NMH Nicole The Large Print Giveth And The Small Print Taketh Away -- Anon __ Yahoo! Mail - PC Magazine Editors' Choice 2005 http://mail.yahoo.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Mysql server not able to stay running on anything but Linux?
Note the From: address. On Wednesday, 12 October 2005 at 13:16:22 -0700, NMH wrote: I am stuck with a delema and I feel like a damn troll. But.. I have a Mysql Database that I posted about earlier. It seems that it is only able to not die by running on BSD 4.11 with Linux Threads. My boss is convinced this means that Linux is better for MySQL and wants that installed now. We even got a support contact from Mysql that so far has gotten us nothing for almost a month while our production database server died up to 3 times a day. (and lots of we're looking into it's) One of the reasons why you haven't got much more than we're looking into its is because we haven't been able to reproduce the problem; you acknowledge this in follow-up mail quoted below. As you know from various threads on the FreeBSD lists, including this one, the typical answer is works fine for me. That doesn't mean that we're not taking your problems seriously, but we do have a significant issue just reproducing the problem. We have a number of choices: 1. Try different hardware or a different version of FreeBSD. It's conceivable that there's something about your specific hardware, or about the combination of i386 kernel on amd64 in general, that triggers the problem. 2. Do debugging on your production servers. This isn't really a choice at all: it would involve even more down time. 3. Get you to run a more stable version of FreeBSD while we investigate the problem. This is the method we chose. I haven't heard from you since the weekend, so I hope I'm correct in understanding that you currently don't have stability problems. On our side, we have installed FreeBSD 5.4 on one of our internal machines, and we're trying to reproduce the problem there. We were running fine but a little slow on FreeBSD 5.1-P11 and MySQL 4.0.18.(apperantly before a big Lib change) We had to move quicker than we wanted to a new server running FreeBSD 5.4 and MySQL 4.11 (becouse of a dual HD death) Under production load the new 5.4 server fell over regulary. It has only now become stable by wiping it and running it on FreeBSD 4.11 with Linux Threads. (it regularly has over 400+ threads) Kris obviously understood that by this statement you meant a kernel crash. My understanding is that only the mysqld server is crashing. Is this still correct? I want to try FreeBSD 5.4 AMD64 (the machines are Opteron) or 6.0 but my boss feels that would be a waste given that MYSQL doesn't support Mysql on AMD64 well enough. I think it would be a good idea to try this. It's one of the things that we intend to do in-house as soon as we can reproduce the problem at all. Can anyone help or offer assistance to help track this down? Perhaps also any annecdotes or examples I can show my boss that other people have as busy MYSQL databases on BSD 5.X. We paid 3K to Mysql for help and so far they have been unable to offer any clues as to why ours will not stay stable on anything but Linux threads. Have you had any kind of crash under 4.x? I don't think that the issue is so much linuxthreads as 5.x. As I say I only manage the server, I don't program the databases. Is there anything I should/could look for database wise that could trigger such things? So far we've had the machine up in-house and have not reproduced the problem. If you have a spare machine that we could run under more typical conditions on your premises, this might help. On Wednesday, 12 October 2005 at 17:07:57 -0400, Kris Kennaway wrote: Unfortunately you'll need to provide details of how it fell over (e.g. panic messages + backtraces). As I mention above, I think this is only a server crash. I mentioned this on the list a couple of weeks ago: all the backtraces I have seen have been a SIGSEGV out of mutex_unlock_common. Can anyone help or offer assistance to help track this down? Perhaps also any annecdotes or examples I can show my boss that other people have as busy MYSQL databases on BSD 5.X. We paid 3K to Mysql for help and so far they have been unable to offer any clues as to why ours will not stay stable on anything but Linux threads. I feel really sad that so far no one has responded to my posts and it feels like a victory for linux. If I was your boss I'd be asking why mysql hasn't delivered on their support contract. Indeed. I think we have, though. There's a certain class of bugs which are almost impossible to fix because they're so hard to chase down. This is one of them. On Wednesday, 12 October 2005 at 14:41:54 -0700, NMH wrote: --- Kris Kennaway [EMAIL PROTECTED] wrote: If I was your boss I'd be asking why mysql hasn't delivered on their support contract. Well I think support has many meanings. I decided to look at what he paid for and it says: We get access to the mysql devlopers... We get access to certified binaries. (none of which are FreeBSD) So, sad as it may seem, if your running
Re: Mysql server not able to stay running on anything but Linux?
--- Greg 'groggy' Lehey [EMAIL PROTECTED] wrote: Note the From: address. On Wednesday, 12 October 2005 at 13:16:22 -0700, NMH wrote: I am stuck with a delema and I feel like a damn troll. But.. I have a Mysql Database that I posted about earlier. It seems that it is only able to not die by running on BSD 4.11 with Linux Threads. My boss is convinced this means that Linux is better for MySQL and wants that installed now. We even got a support contact from Mysql that so far has gotten us nothing for almost a month while our production database server died up to 3 times a day. (and lots of we're looking into it's) One of the reasons why you haven't got much more than we're looking into its is because we haven't been able to reproduce the problem; you acknowledge this in follow-up mail quoted below. As you know from various threads on the FreeBSD lists, including this one, the typical answer is works fine for me. That doesn't mean that we're not taking your problems seriously, but we do have a significant issue just reproducing the problem. We have a number of choices: 1. Try different hardware or a different version of FreeBSD. It's conceivable that there's something about your specific hardware, or about the combination of i386 kernel on amd64 in general, that triggers the problem. Yes possible. However the same hardware was used for the earlier version machine that worked fine. IE Freebsd 5.1-RELEASE-P11 and Mysql 4.0.18 worked on the same hardware. 2. Do debugging on your production servers. This isn't really a choice at all: it would involve even more down time. Yea not really an option. 3. Get you to run a more stable version of FreeBSD while we investigate the problem. This is the method we chose. I haven't heard from you since the weekend, so I hope I'm correct in understanding that you currently don't have stability problems. On our side, we have installed FreeBSD 5.4 on one of our internal machines, and we're trying to reproduce the problem there. So far we have had only one crash that seemed to have been SCSI related. So far it has not happend again. One problem with replication that was a coding issue. We were running fine but a little slow on FreeBSD 5.1-P11 and MySQL 4.0.18.(apperantly before a big Lib change) We had to move quicker than we wanted to a new server running FreeBSD 5.4 and MySQL 4.11 (becouse of a dual HD death) Under production load the new 5.4 server fell over regulary. It has only now become stable by wiping it and running it on FreeBSD 4.11 with Linux Threads. (it regularly has over 400+ threads) Kris obviously understood that by this statement you meant a kernel crash. My understanding is that only the mysqld server is crashing. Is this still correct? Yes only Mysqld would crash. Sometimes brb and autorestart with minimal damage. Other times it would die a horrible death and damage tons of data on its way out. I want to try FreeBSD 5.4 AMD64 (the machines are Opteron) or 6.0 but my boss feels that would be a waste given that MYSQL doesn't support Mysql on AMD64 well enough. I think it would be a good idea to try this. It's one of the things that we intend to do in-house as soon as we can reproduce the problem at all. Yes however as I pointed out.. Just Trying things on a production database is not desirable without some serious indicators that its worthwhile. Last you wrote you said you doubted that would do anything I believe. Also support for amd64 based mysql is listed as Limited. As you said reproducing the problem is the key. However as I suggested I would have thought that if mysql were really into solving the problem, someone would have requested a login on the box to look at our queries to see how they are. Are they 60% reads 40% writes, are they many divergent queries bundled together.. etc. IE come and see our production database in action to see what needs to be replicated. I haven't seen anything like this. Now I don't know much but to me if I can't replicate something it's becouse I don't know enough about it. Can anyone help or offer assistance to help track this down? Perhaps also any annecdotes or examples I can show my boss that other people have as busy MYSQL databases on BSD 5.X. We paid 3K to Mysql for help and so far they have been unable to offer any clues as to why ours will not stay stable on anything but Linux threads. Have you had any kind of crash under 4.x? I don't think that the issue is so much linuxthreads as 5.x. Well. 5.1.. Old lib style No crashes 5.4 .. Crashes like mad 5.4 with libmap.conf to other threads works better.. 4.11 with Linux threads.. No Crashes. So yea.. But thats the other issue that makes it hard. Is it Mysql or is it Freebsd or the interaction and memory sharing going on. I hope that someone here who deals
