Re: innodb
I haven't touched the log or the data files before or after I upgraded mysqld... Well, now I recreated the log files and so far that error didn't show up again. let's pray :) thank you very much Heikki Tuuri wrote: Harald, 030923 15:10:14 InnoDB: Error: page 53 log sequence number 6 190415140 InnoDB: is in the future! Current system log sequence number 1 3864837242. InnoDB: Your database may be corrupt. what do you think is the correct log sequence number? How much do you have data? The pages have lsn about 16 GB or 24 GB, while the log files only have lsn about 8 GB. Please send me your whole .err log. That may contain clues of what has happened. Best regards, Heikki Innobase Oy http://www.innodb.com InnoDB - transactions, row level locking, and foreign keys for MySQL InnoDB Hot Backup - a hot backup tool for MySQL Order MySQL support from http://www.mysql.com/support/index.html .. Heikki, many thanks for your reply. I do well understand that I must *never* touch logfiles or datafiles, and I did not do that. The only thing I did was the following: $ mysqladmin shutdown This was 4.0.14. The error log said: InnoDB: Starting shutdown... InnoDB: Shutdown completed /usr/sbin/mysqld: Shutdown Complete $ cp /usr/sbin/mysqld-4.0.15 /usr/sbin/mysqld This is bin/mysqld from mysql-standard-4.0.15-pc-linux-i686.tar.gz $ rcmysql start Now the error log said: 030923 15:10:12 mysqld started 030923 15:10:14 InnoDB: Error: page 45 log sequence number 6 193108436 InnoDB: is in the future! Current system log sequence number 1 3864837242. InnoDB: Your database may be corrupt. 030923 15:10:14 InnoDB: Error: page 52 log sequence number 6 190390477 InnoDB: is in the future! Current system log sequence number 1 3864837242. InnoDB: Your database may be corrupt. 030923 15:10:14 InnoDB: Error: page 53 log sequence number 6 190415140 InnoDB: is in the future! Current system log sequence number 1 3864837242. InnoDB: Your database may be corrupt. 030923 15:10:14 InnoDB: Error: page 54 log sequence number 4 1256304988 InnoDB: is in the future! Current system log sequence number 1 3864837242. InnoDB: Your database may be corrupt. 030923 15:10:14 InnoDB: Error: page 55 log sequence number 6 190440189 InnoDB: is in the future! Current system log sequence number 1 3864837242. InnoDB: Your database may be corrupt. 030923 15:10:14 InnoDB: Error: page 56 log sequence number 6 190464315 InnoDB: is in the future! Current system log sequence number 1 3864837242. InnoDB: Your database may be corrupt. 030923 15:10:14 InnoDB: Error: page 59 log sequence number 4 1253798302 InnoDB: is in the future! Current system log sequence number 1 3864837242. InnoDB: Your database may be corrupt. 030923 15:10:14 InnoDB: Error: page 60 log sequence number 4 1216946799 InnoDB: is in the future! Current system log sequence number 1 3864837242. InnoDB: Your database may be corrupt. 030923 15:10:14 InnoDB: Error: page 61 log sequence number 4 1253798302 InnoDB: is in the future! Current system log sequence number 1 3864837242. InnoDB: Your database may be corrupt. 030923 15:10:14 InnoDB: Started /usr/sbin/mysqld: ready for connections. Version: '4.0.15-standard-log' socket: '/var/lib/mysql/mysql.sock' port: 3306 Now I switched back to 4.0.14: $ mysqladmin shutdown $ cp /usr/sbin/mysqld-max /usr/sbin/mysqld This is the old 4.0.14 binary, compiled by MySQL AB. $ rcmysql start The error log said: 030923 15:10:46 InnoDB: Started /usr/sbin/mysqld: ready for connections. Version: '4.0.14-Max-log' socket: '/var/lib/mysql/mysql.sock' port: 3306 I had 4.0.14 running for quite some time now and neither experienced any problem nor saw anything in the error log. The InnoDB part of my.cnf looks like this: innodb_data_home_dir = innodb_data_file_path = /dev/raw/raw1:6149Mraw;/var/mysql/innodb/ibdata:100M:autoextend innodb_log_group_home_dir = /var/mysql/innodb.log innodb_log_arch_dir = /var/mysql/innodb.log innodb_mirrored_log_groups = 1 innodb_log_files_in_group = 3 innodb_log_file_size= 100M innodb_log_buffer_size = 64M innodb_flush_log_at_trx_commit = 2 innodb_flush_method = O_DSYNC innodb_log_archive = 0 innodb_buffer_pool_size = 128M innodb_additional_mem_pool_size = 16M innodb_file_io_threads = 4 innodb_lock_wait_timeout= 50 Just ask if you need more information. -- -- Gustavo Baratto - Systems Engineer [EMAIL PROTECTED] * (604) 638-2525 ext. 408 Technical support web-site: http://support.superb.net Superb Internet Corp. Ahead of the Rest - -- MySQL General Mailing List For list archives: http
Re: innodb
if you need more information. -- -- Gustavo Baratto - Systems Engineer [EMAIL PROTECTED] * (604) 638-2525 ext. 408 Technical support web-site: http://support.superb.net Superb Internet Corp. Ahead of the Rest - -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
innodb
Does anybody know what this error is all about? and how do to get rid of it... It started when I upgraded 4.0.13 to 4.0.15 --- 030922 5:17:30 InnoDB: Error: page 1 log sequence number 0 768348475 InnoDB: is in the future! Current system log sequence number 0 330400180. InnoDB: Your database may be corrupt. -- -- -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
InnoDB error
Hello, I started getting this error since I upgraded from mysql 4.0.13 to 4.0.15: 030918 7:17:13 InnoDB: Error: page 12412 log sequence number 0 670697749 InnoDB: is in the future! Current system log sequence number 0 186563990. InnoDB: Your database may be corrupt. any idea how to get rid of this? thanks -- -- Gustavo Baratto - Systems Engineer [EMAIL PROTECTED] * (604) 638-2525 ext. 408 Technical support web-site: http://support.superb.net Superb Internet Corp. Ahead of the Rest - -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: Large number of Databases
no problem for me... 1000+ DBs on RH linux (ext3 fs), then moved it to freebsd 5.1 (almost 1500). Linux is probably faster because of the kernel based thread, but I like BSD. You definetely have to tune your my.cnf... use thread and query cache, increase the key buffer, optimize tables very often (I do it every day... takes 7 minutes in a dual xeon 2Ghz), increase sort and join size. good luck Harald Fuchs wrote: In article [EMAIL PROTECTED], Richard [EMAIL PROTECTED] writes: Does anybody know of any issues when have a large (+1000) databases in MySQL? It will be running on RedHat 9. Would there be any problems running backups with this many DBs on one box? Some filesystems become slow if you have +1000 subdirectories. ReiserFS doesn't have that problem. -- -- Gustavo Baratto - Systems Engineer [EMAIL PROTECTED] * (604) 638-2525 ext. 408 Technical support web-site: http://support.superb.net Superb Internet Corp. Ahead of the Rest - -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: optimize tables and innodb
from the manual: - 7.5.12.3 Defragmenting a Table If there are random insertions or deletions in the indexes of a table, the indexes may become fragmented. By fragmentation we mean that the physical ordering of the index pages on the disk is not close to the alphabetical ordering of the records on the pages, or that there are many unused pages in the 64-page blocks which were allocated to the index. It can speed up index scans if you periodically use mysqldump to dump the table to a text file, drop the table, and reload it from the dump. Another way to do the defragmenting is to ALTER the table type to MyISAM and back to InnoDB again. Note that a MyISAM table must fit in a single file on your operating system. If the insertions to and index are always ascending and records are deleted only from the end, then the file space management algorithm of InnoDB guarantees that fragmentation in the index will not occur. Franky wrote: Hi all, for myisam tables we have optimize table that can be cronned to run at night, but is there something like this for the innodb table type as well? Franky -- -- Gustavo Baratto - Systems Engineer [EMAIL PROTECTED] * (604) 638-2525 ext. 408 Technical support web-site: http://support.superb.net Superb Internet Corp. Ahead of the Rest - -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: optimize tables and innodb
from the manual: - 7.5.12.3 Defragmenting a Table If there are random insertions or deletions in the indexes of a table, the indexes may become fragmented. By fragmentation we mean that the physical ordering of the index pages on the disk is not close to the alphabetical ordering of the records on the pages, or that there are many unused pages in the 64-page blocks which were allocated to the index. It can speed up index scans if you periodically use mysqldump to dump the table to a text file, drop the table, and reload it from the dump. Another way to do the defragmenting is to ALTER the table type to MyISAM and back to InnoDB again. Note that a MyISAM table must fit in a single file on your operating system. If the insertions to and index are always ascending and records are deleted only from the end, then the file space management algorithm of InnoDB guarantees that fragmentation in the index will not occur. Franky wrote: Hi all, for myisam tables we have optimize table that can be cronned to run at night, but is there something like this for the innodb table type as well? Franky -- -- Gustavo Baratto - Systems Engineer [EMAIL PROTECTED] * (604) 638-2525 ext. 408 Technical support web-site: http://support.superb.net Superb Internet Corp. Ahead of the Rest - -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: Large number of Databases
I already use linuxthreads for freebsd... Do you think mysql would run well with the new threads for freebsd 5.XX? Did anybody try it? thanks Jeremy Zawodny wrote: On Thu, Sep 18, 2003 at 10:51:49AM -0300, Gustavo A. Baratto wrote: no problem for me... 1000+ DBs on RH linux (ext3 fs), then moved it to freebsd 5.1 (almost 1500). Linux is probably faster because of the kernel based thread, but I like BSD. If you use LinuxThreads on FreeBSD, it's nearly as fast, FWIW. -- -- Gustavo Baratto - Systems Engineer [EMAIL PROTECTED] * (604) 638-2525 ext. 408 Technical support web-site: http://support.superb.net Superb Internet Corp. Ahead of the Rest - -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
deleting old odbc driver
I want to remove the old 2.50 myodbc driver. I installed a new version of myodbc, and the old driver is still being diplayed in the list... I know this is not really a mysql problem, but I'm not much of a windows user and google didn't return good results this time... maybe someone here could give me hint... thanks -- -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: What is a good benchmark?
I got disappointing results compared with the ones posted here:with a dual xeon 2Ghz, 2GB ram, freebsd 5.1, mysql mysql SELECT BENCHMARK(100,ENCODE(hello,goodbye)); +--+ | BENCHMARK(100,ENCODE(hello,goodbye)) | +--+ |0 | +--+ 1 row in set (1.10 sec) Any idea how to improve it? The cpu is 90% idle average. following my.cnf and configure options... my.cnf -- [mysqld] log-bin set-variable = max_connections=700 set-variable = max_connect_errors=100 safe-show-database set-variable = wait_timeout=120 set-variable = interactive_timeout=120 set-variable = myisam-recover=BACKUP,FORCE set-variable = key_buffer_size=500MB set-variable = sort_buffer_size=5M set-variable = read_buffer_size=2M set-variable = table_cache=512 set-variable = max_delayed_threads=0 set-variable = max_user_connections=25 set-variable = query_cache_size=50M set-variable = thread_cache_size=100 # INNODB innodb_data_home_dir = /var/mysql/data/INNODB innodb_buffer_pool_size = 80M innodb_additional_mem_pool_size = 5M innodb_log_buffer_size = 20M -- configure: ./configure \ --enable-static \ --with-innodb \ --without-berkeley-db \ --with-mysqld-user=mysql \ --without-debug \ --without-docs \ --without-gemini \ --without-mit-threads \ --without-perl \ --without-readline \ --without-docs \ --with-mysqld-ldflags=-all-static \ --enable-thread-safe-client \ --enable-local-infile \ --enable-assembler \ --with-extra-charsets=complex \ --with-named-thread-libs='-DHAVE_GLIBC2_STYLE_GETHOSTBYNAME_R -D_THREAD_SAFE -I/usr/local/include/pthread/linuxthreads -L/usr/local/lib -llthread -llgcc_r -llstdc++ -llsupc++' \ --with-comment='Superb Mysql Server' \ --localstatedir=/var/mysql/data \ --prefix=/var/mysql/mysql-4.0.13-2003-jul-08 Thanks for any hint... Andrew Braithwaite wrote: I get the following on dual Athlon MP 1666MHz 1GB RAM which is 40% cpu loaded mysql SELECT BENCHMARK(100,ENCODE(hello,goodbye)); +--+ | BENCHMARK(100,ENCODE(hello,goodbye)) | +--+ |0 | +--+ 1 row in set (0.64 sec) This result doesn't take into account disk speed I/O etc - so this test will only be relevent for cpu speed. However, If you're worried about performance and want to speed it up a bit, use abbreviated english in your queries like this: mysql SELECT BENCHMARK(100,ENCODE(hi,bye)); +---+ | BENCHMARK(100,ENCODE(hi,bye)) | +---+ | 0 | +---+ 1 row in set (0.32 sec) Only kidding about the abbreviations ;) Andrew -Original Message- From: Jake Johnson [mailto:[EMAIL PROTECTED] Sent: Wednesday 23 July 2003 15:34 To: Mysql Subject: What is a good benchmark? I ran this benchmark on my pIII 500 and was wondering what everyone else was getting? mysql SELECT BENCHMARK(100,ENCODE(hello,goodbye)); +--+ | BENCHMARK(100,ENCODE(hello,goodbye)) | +--+ |0 | +--+ 1 row in set (2.59 sec) Regards, Jake Johnson [EMAIL PROTECTED] __ Plutoid - http://www.plutoid.com - Shop Plutoid for the best prices on Rims, Car Audio, and Performance Parts. -- -- Gustavo Baratto - Programming and Technical Support [EMAIL PROTECTED] * (604) 638-2525 ext. 408 Technical support web-site: http://support.superb.net Superb Internet Corp. Ahead of the Rest - -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: stopping innodb engine
having the hability to stop the extra engines is a good candidate to go to the todo list. Stopping the server to do a reliable backup is not good solution... The ideal would be a mysql command that read locks all innodb tables, then we can backup the data file and the log files safely... Something that would suspend the update of the data and log files, saving all queries in memory until an unlock command is executed... Is this possible, or there is a design limitation to do this? I never looked into mysql source before, but if time permits we can always help... Thanks - Original Message - From: Paul DuBois [EMAIL PROTECTED] To: Gustavo A. Baratto [EMAIL PROTECTED]; [EMAIL PROTECTED] Sent: Wednesday, July 09, 2003 11:31 PM Subject: Re: stopping innodb engine At 21:47 + 7/9/03, Gustavo A. Baratto wrote: Greetings, What happens if I use the command below when innodb engine is running? set global have_innodb=0; You can easily find out by trying it. (Go ahead, nothing bad will happen.) I want to stop innodb engine without stopping the whole server for backup (most tables are myisam). Any ideas on how to do that? You can't. Storage engines like InnoDB or BDB can only be disabled or enabled at startup time. have_innodb and have_bdb are indicators of the availability of these engines; they cannot be set while the server is running. Thank all -- Paul DuBois, Senior Technical Writer Madison, Wisconsin, USA MySQL AB, www.mysql.com Are you MySQL certified? http://www.mysql.com/certification/ -- 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]
stopping innodb engine
Greetings, What happens if I use the command below when innodb engine is running? set global have_innodb=0; I want to stop innodb engine without stopping the whole server for backup (most tables are myisam). Any ideas on how to do that? Thank all -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: Hi CPU on FreeBSD
the load average in my freebsd 5.0 (latest releng) compiled statically with linuxthreads decreased 80% after I tunned these variables: set-variable = key_buffer_size=100MB set-variable = read_buffer_size=5M set-variable = table_cache=500 set-variable = max_delayed_threads=0 set-variable = max_user_connections=25 set-variable = query_cache_size=50M set-variable = thread_cache_size=100 The only problem I couldn't solve is that some connections will never die... since most of this connections come from tomcat, I'm restarting it more often. Using query cache and thread cache will definetely give you a boost of performance This machine has lots of memory, so you have to be careful with variables like key_buffer_size, table_cache and query_cache_size... you need memory for that, don't let it swap. Lalo Castro wrote: We had the same problem. Upgrading Freebsd to 4.8 and recompiling MySQL to work with Linux style threads seemed to work. The MySQLd process no longer pops up to ~90% on each request. However, with the application we're running that queries the database (Request Tracker 3), we still get process bloat with certain queries (searches mostly). But, this problem doesn't come up with any other application, or with manual querys of the database, so we think it's a bug in the app. Lalo Gunnar Helliesen wrote: On Sat, 22 Jun 2002 17:43:12 -0700 Jeremy Zawodny wrote: On Sat, Jun 22, 2002 at 07:26:36PM -0500, mos wrote: We've managed to reproduce this pretty reliably at Yahoo and are working to track and fix the bug. If we find a resolution, I'll post a note here. There have been a few threads regarding high CPU utilization on FreeBSD systems. Yeah, I mostly ingored them because I thought it was a fluke. But it happens much more than I had thought. It's still happening on the site I first reported it on. We're currently running max-4.0.11-gamma, but the problem has been present since 3.x. FreeBSD 4.4 and 4.5. -- -- Gustavo Baratto - Programming and Technical Support [EMAIL PROTECTED] * (604) 638-2525 ext. 408 Technical support web-site: http://support.superb.net Superb Internet Corp. Ahead of the Rest - -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: Hi CPU on FreeBSD
CPU usage improved a lot as well... It's always above 90% free and before it was 70-75% idle... here is a snapshot: last pid: 58730; load averages: 0.09, 0.11, 0.08 up 9+20:59:57 17:11:24 216 processes: 1 running, 215 sleeping CPU states: 0.0% user, 1.8% nice, 1.2% system, 0.2% interrupt, 96.9% idle Jeremy Zawodny wrote: On Mon, Jun 09, 2003 at 01:41:00PM +, Gustavo A. Baratto wrote: the load average in my freebsd 5.0 (latest releng) compiled statically with linuxthreads decreased 80% after I tunned these variables: What about actual CPU usage? Did is increase similarly? The load average isn't necessarily a good measure of performance. It's often a good measure of bottlenecks beyond the scheduler's control--suck as poor I/O. Jeremy -- -- Gustavo Baratto - Programming and Technical Support [EMAIL PROTECTED] * (604) 638-2525 ext. 408 Technical support web-site: http://support.superb.net Superb Internet Corp. Ahead of the Rest - -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
threads not being killed
Greetings, we running mysql 4.0.13 compiled statically with linuxthreads on freebsd 5.0 (SMP). The problem is that a few connections are not dying after the wait_timeout and interactive_timeout expired. The only pattern we can see here is that mysql clients like jakarta-tomcat (jdbc), and windows (obdc) are the ones not that are not dying. Another thing is that these are the only clients based on 3.XX libmysqlclient... We are not having problem so far with php and perl clients compiled with 4.XX libs. I searched the manual for answers and nothing... The manual does say that we shouldn't have any problem with old 3.XX clients except for using the new privileges provided by 4.XX. I don't really know if this is a freebsd problem as described in http://jeremy.zawodny.com/blog/archives/000697.html or the old mysql client. Any ideas? -- -- Gustavo Baratto - Programming and Technical Support [EMAIL PROTECTED] * (604) 638-2525 ext. 408 Technical support web-site: http://support.superb.net Superb Internet Corp. Ahead of the Rest - -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: threads not being killed
Hail Jeremy!! my kernel is new as releng5_0 (release + security patches). I saw your Yahoo! patch in the source with 4.0.13. My tomcat clients and windows ODBC are all ancient (still 3.XX) Thanks for your help! PS: thnaks for being our guru in mysql/freebsd... Your blogs saved our asses many times :) - Original Message - From: Jeremy Zawodny [EMAIL PROTECTED] To: Gustavo A. Baratto [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Sent: Thursday, June 05, 2003 8:06 PM Subject: Re: threads not being killed On Thu, Jun 05, 2003 at 10:01:23AM +, Gustavo A. Baratto wrote: Greetings, we running mysql 4.0.13 compiled statically with linuxthreads on freebsd 5.0 (SMP). The problem is that a few connections are not dying after the wait_timeout and interactive_timeout expired. The only pattern we can see here is that mysql clients like jakarta-tomcat (jdbc), and windows (obdc) are the ones not that are not dying. Another thing is that these are the only clients based on 3.XX libmysqlclient... We are not having problem so far with php and perl clients compiled with 4.XX libs. I searched the manual for answers and nothing... The manual does say that we shouldn't have any problem with old 3.XX clients except for using the new privileges provided by 4.XX. I don't really know if this is a freebsd problem as described in http://jeremy.zawodny.com/blog/archives/000697.html or the old mysql client. Any ideas? Sounds like the same bug to me. How recent is your 5.0 kernel? I don't recall exactly when the patch went in. 4.0.13 should have an adjustment in vio/vio.c that looks like this: fcntl(sd, F_SETFL, vio-fcntl_mode); /* Yahoo! FreeBSD patch */ That works around the problem to. Jeremy -- Jeremy D. Zawodny | Perl, Web, MySQL, Linux Magazine, Yahoo! [EMAIL PROTECTED] | http://jeremy.zawodny.com/ MySQL 4.0.13: up 2 days, processed 96,077,464 queries (391/sec. avg) -- 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]
Lost connection to MySQL server during query
This old bug reappeared after the upgrading mysql from version 3.23.54a (rpm provided by mysql.com) to version 4.0.8-gamma (binary provided by mysql.com as well). Using redhat 7.1 glibc 2.2.4-31 (which is supposed to fix this problem) This server has glibc 2.2.4-31 installed for quite a while, and mysql 3.23.54a was working just fine with it. Mysql 4.0.8 stopped crashing when I added --skip-name-resolve in the mysql startup... but some tables are getting corrupted very often, and I can't find a reason. It doesn't the tables are getting corrupted because of mysql is crashing, because bin-log index is not increasing, and there is nothing in the logs saying it was restarted. This is one example of check table: alpgrafik_com_1.kent_session_info warning Not used space is supposed to be: 30612 but is: 30404 alpgrafik_com_1.kent_session_info error record delete-link-chain corrupted alpgrafik_com_1.kent_session_info error Corrupt --- I searched for delete-link-chain on google but I didn't have much luck Not all clients (eg, php) have been upgraded to version 4, but the mysql docs say there shouldn't be a problem if we are not using the new features. Ideias? -- -- Gustavo Baratto - Programming and Technical Support [EMAIL PROTECTED] * (604) 638-2525 ext. 408 Technical support web-site: http://support.superb.net Superb Internet Corp. Ahead of the Rest - - 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: Lost connection to MySQL server during query at ... After upgrade to 3.23.54
You can use --skip-name-resolve when starting mysqld, but this is not a real solution. Even doing that,'I'm still having some odd problems I never had before, like table corruption (I'm on 4.0.8 though) - Original Message - From: Patrick de Kievit [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Wednesday, January 15, 2003 2:34 PM Subject: Lost connection to MySQL server during query at ... After upgrade to 3.23.54 Hi all, Pure randomly my server tells me the its Lost connection to MySQL server during query at ... This all happened after my upgrade to version 3.23.54. I searched google and read some threads here. A possible solution is to DOWNGRADE some libc files? Tell me is this the only solution ? Is there a patch ? Thanks, Patrick - 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: mysql.sock??
Hi Mike. Check if you data directory is in: /usr/local/mysql/var as specified in your startup script, or in: /var/lib/mysql On redhat using the binary distribution, the data dir is in /var/lib/mysql -- On December 19, 2001 06:19 pm, Mike Blain wrote: I keep trying to start it and get this: [root@linuxdev1 mysql-3.23.46]# /usr/local/mysql/bin/safe_mysqld --user=mysql [1] 1822 [root@linuxdev1 mysql-3.23.46]# Starting mysqld daemon with databases from /usr/local/mysql/var 011219 18:21:40 mysqld ended It stats and immediately stops. Been combing forums and install instructions for info on this and haven't had much luck. keep trying this to no avail as well: [root@linuxdev1 mysql-3.23.46]# /etc/init.d/mysqld start bash: /etc/init.d/mysqld: No such file or directory -Original Message- From: Quentin Bennett [mailto:[EMAIL PROTECTED]] Sent: Wednesday, December 19, 2001 5:44 PM To: '[EMAIL PROTECTED]'; [EMAIL PROTECTED] Subject: RE: mysql.sock?? Hi, mysqld will create it when it runs - have you started the server? Quentin -Original Message- From: Mike Blain [mailto:[EMAIL PROTECTED]] Sent: Thursday, 20 December 2001 2:07 p.m. To: [EMAIL PROTECTED] Subject: mysql.sock?? I just recently installed MySQL from source. Trying to set the root password and keep getting this error: /usr/local/mysql/bin/mysqladmin: connect to server at 'localhost' failed error: 'Can't connect to local MySQL server through socket '/tmp/mysql.sock' (111)' Check that mysqld is running and that the socket: '/tmp/mysql.sock' exists! How do I create mysql.sock? Thanks, Mike - 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 The information contained in this email is privileged and confidential and intended for the addressee only. If you are not the intended recipient, you are asked to respect that confidentiality and not disclose, copy or make use of its contents. If received in error you are asked to destroy this email and contact the sender immediately. Your assistance is appreciated. - 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
mysql usernames
Hi, I've changed the length of the field 'user' in the table 'user' in the mysql DB, to varchar(128), because we need longer names to identify our users based on their domain names. Something like: each user is identified by a valid domain name. The same thing we are doing with the DB field. The thing is that even though I changed the length of 'user' and 'db' to varchar(128) binary in the tables 'user', 'db' and 'host', I'm getting the login name truncated in the 32th character. If the limitation was 16 character before the changes, why am I getting this 32 characters limitation after the changes? Any ideas? Thanks, Gustavo - 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
myodbc
Greetings, We modified our db, host, and user tables (in mysql db) in order to have bigger db names, users... Just 16 characters is really not enough for us. Now the problem: Some of our users use myODBC to connect to their databases. And that driver does not accept db names with more than 16 characters. Does, anyone have any work around for that? Any ideas will be greatly apreciated. Best Regards, Gustavo - 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: Replication Problem on MySQL 3.23.45/Win32
I'm not sure, But I don't think symbolic links are allowed on win2k... Take a look into this... Regards, gustavo On Fri, 2001-12-07 at 12:04, A. Clausen wrote: I have been using replication for several months between to Win2k machines. Last week I upgraded to MySQL 3.23.45, and everything continued working fine. Yesterday, I put the line use-symbolic-links in the my.cnf file because I've created a very large database that I have another drive reserved for. Since that time, when I enter show processlist the top line shows: |1 | system user | none | NULL | Connect | 88449 | connecting to master | NULL | Of course, the replicating server is not getting through at all. Anybody know what could be causing this? A. Clausen [EMAIL PROTECTED] - 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 -- -- Gustavo Baratto - Programming and Technical Support [EMAIL PROTECTED] * (604) 638-2525 ext. 408 Technical support web-site: http://support.superb.net Superb Internet Corp. Ahead of the Rest - - 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: replication
Thanks for the reply Jeremy... What I need actually is a cluster. We have lots of users using lots of small databases... Our users should send a query to one server, and somehow we must load balance that... I think I'd better get more hardware to that server, until mysql come up with a clustering solution... Thanks, Gustavo On Thu, 2001-12-06 at 23:34, Jeremy Zawodny wrote: On Thu, Dec 06, 2001 at 07:42:29PM -0800, Gustavo A. Baratto wrote: Hi Guys, The documentation in http://www.mysql.com/doc/R/e/Replication.html , is not clear enough regarding using replication for load balancing. I understand that the load balance can just be done on SELECTS. And the documentation says that The extra speed is achieved by sending a part of the non-updating queries to the replica server. My question is: Do we have to send the SELECT explicitly to the slave, or we can send it to the master, and it (the master) will take care of that? You have to send them yourself (explicitly). Assuming you have 1 master and N slaves, you can use various load-balancing techniques (round-robin DNS, LVS, etc) for the SELECTs. Jeremy -- Jeremy D. Zawodny, [EMAIL PROTECTED] Technical Yahoo - Yahoo Finance Desk: (408) 349-7878 Fax: (408) 349-5454 Cell: (408) 685-5936 MySQL 3.23.41-max: up 7 days, processed 170,180,367 queries (249/sec. avg) - 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 -- -- Gustavo Baratto - Programming and Technical Support [EMAIL PROTECTED] * (604) 638-2525 ext. 408 Technical support web-site: http://support.superb.net Superb Internet Corp. Ahead of the Rest - - 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
replication
Hi Guys, The documentation in http://www.mysql.com/doc/R/e/Replication.html , is not clear enough regarding using replication for load balancing. I understand that the load balance can just be done on SELECTS. And the documentation says that The extra speed is achieved by sending a part of the non-updating queries to the replica server. My question is: Do we have to send the SELECT explicitly to the slave, or we can send it to the master, and it (the master) will take care of that? I tried unsuccessfully to find more info regarding load balancing on mysql... If someone can give me a web-site or something else I can read, it would be really appreciated. Thanks Gustavo - 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
