Re: freebsd 5.1 + mysql 4.0.13
Richard, Welcome to the wonderful world of FreeBSD. FreeBSD-5.1 is not release code. It is alpha quality (thought pretty good quality as Alpha goes). I understand that the website doesn't make this abundantly clear on the homepage. FreeBSD 4.8 is the current production quality code. It will probably be much faster for you as well, since debugging options are turned off by default. You can get from 5.1 to 4.8 without having to reinstall the OS by, well, reinstalling the OS. By following the instructions in the handbook for upgrading you can also downgrade to FreeBSD-4.8 by downgrading your source tree in /usr/src, building and installing world. It's actually not quite as bad as it seems in the docs and I've managed upgrades and downgrades with minimum of downtime. Most of the steps can be done while the system is running. The steps that should be done in single user mode (and I recomend this since your not familiar with FreeBSD yet) are pretty quick. FreeBSD is actually fairly nice once you know what's going on. The Handbook is http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/index.html and the chapter you want is http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/cutting-edge.html Substitude old for cutting edge and your on your way. The CVS tag you would want is RELENG_4_8 I would recomend rebuilding anything you built in ports after you upgrade the system, since this downgrade is considerable, but again much of that compile time will be while the system is running. Your really only looking at the time to do a make install and make installkernel, and rebuilding the database server as your downtime. Much less considerable than reinstalling an entire OS and getting everything installed that you want. If you need more assistance shoot me a line, off the MySQL list (as it's no longer a MySQL issue) and I'll answer what I can. -- Michael Conlen -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: freebsd 5.1 + mysql 4.0.13
On Sat, Jun 28, 2003 at 01:14:37PM +0200, Richard Fuchs wrote: hi! i'm using mysql 4.0.13 from the standard freebsd 5.1 ports distribution, and i keep getting repeated random table corruptions. the same thing happens when building both with the native threading lib, and with linuxthreads. i figured it would be related to threading as it's always happening when the mysql server is loaded, that is has lots of concurrent queries on the same table going on. suddenly the table would get corrupted, and i have to run a repair table on it (this always nukes a few rows from the table). it's reproducable only in the sense that it keeps happening randomly ;) are there any known issues with this combination, or with mysql 4.0.13 or freebsd 5.1 in general? what could be the cause for this, and how could it be fixed? You seem to be the first reporting a problem with FreeBSD 5.1 and MySQL. Do you *need* to use 5.1 or could you try 4.8 to see if the problem goes away? That'd help to narrow it down to eithe MySQL or something specific to FreeBSD 5.1. Jeremy -- Jeremy D. Zawodny | Perl, Web, MySQL, Linux Magazine, Yahoo! [EMAIL PROTECTED] | http://jeremy.zawodny.com/ MySQL 4.0.13: up 25 days, processed 813,050,547 queries (362/sec. avg) -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: freebsd 5.1 + mysql 4.0.13
Jeremy Zawodny wrote: On Sat, Jun 28, 2003 at 01:14:37PM +0200, Richard Fuchs wrote: are there any known issues with this combination, or with mysql 4.0.13 or freebsd 5.1 in general? what could be the cause for this, and how could it be fixed? You seem to be the first reporting a problem with FreeBSD 5.1 and MySQL. Do you *need* to use 5.1 or could you try 4.8 to see if the problem goes away? That'd help to narrow it down to eithe MySQL or something specific to FreeBSD 5.1. no i don't *need* it, but switching os's would mean more downtime while possibly not even fixing the problem. and if i were switching os, i would probably go to linux anyway... i've narrowed the problem down already: i have specified enable-locking and skip-name-resolve in my.cnf now, and i haven't had any corruptions for a whole day now. it looks like one of those two options fixes the problem. i can't really tell which one of them does it, and i don't feel like playing russian roulette trying to find that out, so this is my works-for-me case for now... cheers richard -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: freebsd 5.1 + mysql 4.0.13
On Sun, Jun 29, 2003 at 08:55:30AM +0200, Richard Fuchs wrote: Jeremy Zawodny wrote: On Sat, Jun 28, 2003 at 01:14:37PM +0200, Richard Fuchs wrote: are there any known issues with this combination, or with mysql 4.0.13 or freebsd 5.1 in general? what could be the cause for this, and how could it be fixed? You seem to be the first reporting a problem with FreeBSD 5.1 and MySQL. Do you *need* to use 5.1 or could you try 4.8 to see if the problem goes away? That'd help to narrow it down to eithe MySQL or something specific to FreeBSD 5.1. no i don't *need* it, but switching os's would mean more downtime while possibly not even fixing the problem. and if i were switching os, i would probably go to linux anyway... Well, we have dozens of servers running on 4.8 that haven't had such problems. That's why I suggested it. After all, 4.8 is stable while 5.1 is current. i've narrowed the problem down already: i have specified enable-locking and skip-name-resolve in my.cnf now, and i haven't had any corruptions for a whole day now. it looks like one of those two options fixes the problem. i can't really tell which one of them does it, and i don't feel like playing russian roulette trying to find that out, so this is my works-for-me case for now... Interesting. The skip-name-resolve shouldn't be an issue when using LinuxThreads. As for enable-locking, that sounds suspicious. You weren't running other proceses outside of MySQL that might work with the data files (myisamchk, for example), were you? Jeremy -- Jeremy D. Zawodny | Perl, Web, MySQL, Linux Magazine, Yahoo! [EMAIL PROTECTED] | http://jeremy.zawodny.com/ MySQL 4.0.13: up 26 days, processed 813,480,202 queries (362/sec. avg) -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: freebsd 5.1 + mysql 4.0.13
Jeremy Zawodny wrote: On Sun, Jun 29, 2003 at 08:55:30AM +0200, Richard Fuchs wrote: Jeremy Zawodny wrote: On Sat, Jun 28, 2003 at 01:14:37PM +0200, Richard Fuchs wrote: are there any known issues with this combination, or with mysql 4.0.13 or freebsd 5.1 in general? what could be the cause for this, and how could it be fixed? You seem to be the first reporting a problem with FreeBSD 5.1 and MySQL. Do you *need* to use 5.1 or could you try 4.8 to see if the problem goes away? That'd help to narrow it down to eithe MySQL or something specific to FreeBSD 5.1. no i don't *need* it, but switching os's would mean more downtime while possibly not even fixing the problem. and if i were switching os, i would probably go to linux anyway... Well, we have dozens of servers running on 4.8 that haven't had such problems. That's why I suggested it. After all, 4.8 is stable while 5.1 is current. well it wasn't my choice. personally i'm a linux guy, but right now i'd rather have minimum downtime w/o too much playing around. i've narrowed the problem down already: i have specified enable-locking and skip-name-resolve in my.cnf now, and i haven't had any corruptions for a whole day now. it looks like one of those two options fixes the problem. i can't really tell which one of them does it, and i don't feel like playing russian roulette trying to find that out, so this is my works-for-me case for now... Interesting. The skip-name-resolve shouldn't be an issue when using LinuxThreads. As for enable-locking, that sounds suspicious. You weren't running other proceses outside of MySQL that might work with the data files (myisamchk, for example), were you? no of course not :) unless the default freebsd install comes with some cron jobs or something that do something nasty with the tables behind the scenes (just kidding, but i've actually checked for that). is it possible that the internal locking is broken and doesnt work right, and the use of external locking works as a kind of workaround for this? greets richard -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: freebsd 5.1 + mysql 4.0.13
On Sun, Jun 29, 2003 at 09:38:09AM +0200, Richard Fuchs wrote: well it wasn't my choice. personally i'm a linux guy, but right now i'd rather have minimum downtime w/o too much playing around. Ah, got it. Interesting. The skip-name-resolve shouldn't be an issue when using LinuxThreads. As for enable-locking, that sounds suspicious. You weren't running other proceses outside of MySQL that might work with the data files (myisamchk, for example), were you? no of course not :) unless the default freebsd install comes with some cron jobs or something that do something nasty with the tables behind the scenes (just kidding, but i've actually checked for that). Good. is it possible that the internal locking is broken and doesnt work right, and the use of external locking works as a kind of workaround for this? Yeah, that's what it's starting to sounds like. Jeremy -- Jeremy D. Zawodny | Perl, Web, MySQL, Linux Magazine, Yahoo! [EMAIL PROTECTED] | http://jeremy.zawodny.com/ MySQL 4.0.13: up 26 days, processed 815,367,494 queries (362/sec. avg) -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
