Re: connection issue
Thanks, Doug. How did you figure out it's because of "open_files_limit"? Best, Tianyin On Sat, Dec 22, 2012 at 5:51 AM, Doug wrote: > sorry the problem has been resolved. > it's the reason of open_files_limit too small. > I increased it and the problem resolved. > > 2012/12/22 Doug : >> Hello, >> >> When connecting to mysql, sometime I got this error: >> >> # mysql -ucdn -h113.108.22x.xx -p >> Enter password: >> ERROR 2013 (HY000): Lost connection to MySQL server at 'reading >> initial communication packet', system error: 0 >> >> >> But most time it's correct. >> What's the reason? Thanks. >> >> I am running mysql-5.1.37 on Linux, there is no firewall configured on the >> host. > > -- > MySQL General Mailing List > For list archives: http://lists.mysql.com/mysql > To unsubscribe:http://lists.mysql.com/mysql > -- Tianyin XU, http://cseweb.ucsd.edu/~tixu/ -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql
Re: Which test suites are valid for --extern option in mysql-test-run?
Thanks a lot, Eric! Yes, unfortunately, I'm trying to use them to do some specific testing. One thing bugged me is that even testing on a clean mysqld with the default configuration, some "--extern" test fails. I guess it is because these test cases are not supported. By the way, could you explain a little bit about the difference between the test cases in the "r" directory and the ones in the "suite" directory? It seems they are quite different. When running "mysql_test_run" without argument, it uses the ones in the "suite" directory. Best, Tianyin On Mon, Nov 26, 2012 at 6:57 PM, Eric Bergen wrote: > Those tests are typically used by people developing the mysqld server. > The packages distributed have already had the tests ran on them. I'm > not sure how much value it will provide unless you're modifying > mysqld. > > I don't have a great answer but my best guess is that extern can't be > used with tests that start or stop mysqld servers like the replication > tests. > > On Sat, Nov 24, 2012 at 12:16 AM, Tianyin Xu wrote: > > Hi, all, > > > > I wanna test my running MySQL server. According to the README in the > > "mysql-test" directory, "If you want to use an already running MySQL > server > > for specific tests, use the --extern option to mysql-test-run". > > > > For example, mysql-test-run --extern alias > > > > But the README also pointed out that "some tests cannot run with an > > external server". > > > > My question is how to know which test suites in "t" directory are valid > for > > --extern option? Without knowing this, I cannot judge whether a test > fails > > is because it's not supported or "real" problems. > > > > Thanks a lot! > > Tianyin > > > > -- > > Tianyin XU, > > http://cseweb.ucsd.edu/~tixu/ > > > > -- > Eric Bergen > eric.ber...@gmail.com > http://www.ebergen.net > -- Tianyin XU, http://cseweb.ucsd.edu/~tixu/
Re: Why configuration directives are all case sensitive?
Hi, Eric, Thanks a lot for the GREAT explanation! This perfectly answers my question. We can close the threads now :-) Best, T On Sat, Nov 24, 2012 at 8:53 AM, Eric Bergen wrote: > Yes, the missing piece of the puzzle is that configuration files are > turned into command line arguments internally. Programs will parse > configuration files and place them at the beginning of the array for > command line arguments. They are made case sensitive because they are > turned into command line arguments. So the basic process is read all > the configuration files in order of precedence into the beginning of > the command line array. Then send this array to the command line > handling code. This is also how argument precedence works. As the > array is walked through options will override previous options so > things passed on the command line are at the end and override options > in the config file. > > On Fri, Nov 23, 2012 at 10:08 PM, Tianyin Xu wrote: > > Dear Eric, > > > > Thanks a lot for the explanation of argument directives! The concerns are > > very considerate. > > > > Actually, what I'm curious about is the configuration directives in the > > configuration file, i.e., my.cnf. To my experience, MySQL is the very few > > software who treats these directives in a case sensitive manner. > > > > The directives in the configuration file is different from the arguments, > > because we don't have something like --port and -P. So, a directive like > > "Port" clearly indicates that the user specifies "port" (exactly as you > > said). And this's the reason that most apps do not differentiate them. > > > > Could you please explain about the directives in the configuration file? > > > > Thanks a lot! > > > > Happy Thanksgiving!! > > Tianyin > > > > > > > > On Fri, Nov 23, 2012 at 4:20 PM, Eric Bergen > wrote: > >> > >> Anger and OS religious arguments the real answer is that is just how > >> the option parsing code works. It doesn't always have to make sense. > >> There are short and long args to programs. For example on the mysql > >> client there is --port or -P and --pasword or -p. The short options > >> have to be case sensitive because -P and -p mean different things. The > >> short options are case sensitive so the long options may as well be. > >> It keeps things simpler. Who wants to write --Port when --port means > >> not hitting the shift key? > >> > >> There are a few exceptions to this. The option comparison treats _ and > >> - as the same. I realize that isn't case but it just shows the > >> matching isn't exact. So --show_warnings is valid. On the other side > >> of the equal sign comparisons for true, on, false, and off are done > >> case insensitive. So --show_warnings=FaLse is valid but > >> --show_warningS=TruE isn't. > >> > >> If you want to be even more confused consider that mysql allows > >> partial argument names. You don't have to type out the full long arg > >> as long as you type enough that it only matches one option. For > >> example mysql --so is enough to mean socket but mysql --s isn't > >> because it can't be distinguished from 'show' variables. This gets > >> confusing with things like b. mysql --b is batch mode. So is mysql -B > >> but mysql -b is no beep. Confused yet? > >> > >> On Sun, Nov 18, 2012 at 6:42 PM, Tianyin Xu wrote: > >> > On Sun, Nov 18, 2012 at 6:13 PM, Reindl Harald > >> > wrote: > >> > > >> >> > >> >> > >> >> Am 19.11.2012 02:07, schrieb Tianyin Xu: > >> >> > You are saying as long as admins are careful, there's no > >> >> misconfiguration? > >> >> > But why misconfigurations are so pervasive? > >> >> > Simply because the admins are not careful enough? > >> >> > >> >> yes > >> >> > >> >> > >> > That means not only I'm dummy, and that's means you should take care > the > >> > system configuration design if many people are careless. > >> > > >> > > >> > > >> >> > I apologize for my lack of respect. I don't know what's your stuff, > >> >> > but > >> >> > I guess they'll be more popular if you make them more friendly. > >> >> > >> >> it does not need to be more popular > >> >
Which test suites are valid for --extern option in mysql-test-run?
Hi, all, I wanna test my running MySQL server. According to the README in the "mysql-test" directory, "If you want to use an already running MySQL server for specific tests, use the --extern option to mysql-test-run". For example, mysql-test-run --extern alias But the README also pointed out that "some tests cannot run with an external server". My question is how to know which test suites in "t" directory are valid for --extern option? Without knowing this, I cannot judge whether a test fails is because it's not supported or "real" problems. Thanks a lot! Tianyin -- Tianyin XU, http://cseweb.ucsd.edu/~tixu/
Re: Why configuration directives are all case sensitive?
Dear Eric, Thanks a lot for the explanation of argument directives! The concerns are very considerate. Actually, what I'm curious about is the configuration directives in the configuration file, i.e., my.cnf. To my experience, MySQL is the very few software who treats these directives in a case sensitive manner. The directives in the configuration file is different from the arguments, because we don't have something like --port and -P. So, a directive like "Port" clearly indicates that the user specifies "port" (exactly as you said). And this's the reason that most apps do not differentiate them. Could you please explain about the directives in the configuration file? Thanks a lot! Happy Thanksgiving!! Tianyin On Fri, Nov 23, 2012 at 4:20 PM, Eric Bergen wrote: > Anger and OS religious arguments the real answer is that is just how > the option parsing code works. It doesn't always have to make sense. > There are short and long args to programs. For example on the mysql > client there is --port or -P and --pasword or -p. The short options > have to be case sensitive because -P and -p mean different things. The > short options are case sensitive so the long options may as well be. > It keeps things simpler. Who wants to write --Port when --port means > not hitting the shift key? > > There are a few exceptions to this. The option comparison treats _ and > - as the same. I realize that isn't case but it just shows the > matching isn't exact. So --show_warnings is valid. On the other side > of the equal sign comparisons for true, on, false, and off are done > case insensitive. So --show_warnings=FaLse is valid but > --show_warningS=TruE isn't. > > If you want to be even more confused consider that mysql allows > partial argument names. You don't have to type out the full long arg > as long as you type enough that it only matches one option. For > example mysql --so is enough to mean socket but mysql --s isn't > because it can't be distinguished from 'show' variables. This gets > confusing with things like b. mysql --b is batch mode. So is mysql -B > but mysql -b is no beep. Confused yet? > > On Sun, Nov 18, 2012 at 6:42 PM, Tianyin Xu wrote: > > On Sun, Nov 18, 2012 at 6:13 PM, Reindl Harald >wrote: > > > >> > >> > >> Am 19.11.2012 02:07, schrieb Tianyin Xu: > >> > You are saying as long as admins are careful, there's no > >> misconfiguration? > >> > But why misconfigurations are so pervasive? > >> > Simply because the admins are not careful enough? > >> > >> yes > >> > >> > > That means not only I'm dummy, and that's means you should take care the > > system configuration design if many people are careless. > > > > > > > >> > I apologize for my lack of respect. I don't know what's your stuff, > but > >> > I guess they'll be more popular if you make them more friendly. > >> > >> it does not need to be more popular > >> it is better not to be too popular but working clean and safe > >> > >> careless working these days means usually also not care > >> about security which is not acceptable htese days and i > >> know a lot of crap out there which is more popluar like > >> my work but with crappy quality and terrible insecure > >> > >> see all this CMS sytems out there writing hundrets of > >> warnings each request with error_reporting E_STRICT > >> while my whole source code runs clean i know who is right > >> > >> really: > >> if you find it useful to complain why a configuration is > >> case-sensitive instead accept it and correct your fault > >> you are doing the wrong job > >> > >> > > I'm complaining nothing. I just curious about the configuration and want > to > > know you developers' thinking. I apologize if I gave you the impression > of > > complaining by asking questions. > > > > Basically, I'm new to MySQL and find MySQL really take care about lots of > > things to give users an easy job. For example, the unit, the enumeration > > options, all are case insensitive -- "512K" and "512k" means the same > size, > > "MIXED" and "mixed" means the same option, etc. Having such impression, > > when MySQL tells me 'Port' is unknown, it did take me some time to figure > > it out. Maybe simply because all the other servers I used like > PostgreSQL, > > httpd, etc are case insensitive. That's the whole story, and that's why I > > ask on the forum, being curious about the reason. > > > > It's fine that you told me it's simply because you developers assume > nobody > > "came to the idea write options > > not EXACTLY like they are in the documentation", so you simply do not > want > > to do it. But I do not buy this, because MySQL developers do take care a > > lot of things (as unit and options I mentioned). > > > > T > > > > > > -- > > Tianyin XU, > > http://cseweb.ucsd.edu/~tixu/ > > > > -- > Eric Bergen > eric.ber...@gmail.com > http://www.ebergen.net > -- Tianyin XU, http://cseweb.ucsd.edu/~tixu/
Re: Why configuration directives are all case sensitive?
On Sun, Nov 18, 2012 at 6:13 PM, Reindl Harald wrote: > > > Am 19.11.2012 02:07, schrieb Tianyin Xu: > > You are saying as long as admins are careful, there's no > misconfiguration? > > But why misconfigurations are so pervasive? > > Simply because the admins are not careful enough? > > yes > > That means not only I'm dummy, and that's means you should take care the system configuration design if many people are careless. > > I apologize for my lack of respect. I don't know what's your stuff, but > > I guess they'll be more popular if you make them more friendly. > > it does not need to be more popular > it is better not to be too popular but working clean and safe > > careless working these days means usually also not care > about security which is not acceptable htese days and i > know a lot of crap out there which is more popluar like > my work but with crappy quality and terrible insecure > > see all this CMS sytems out there writing hundrets of > warnings each request with error_reporting E_STRICT > while my whole source code runs clean i know who is right > > really: > if you find it useful to complain why a configuration is > case-sensitive instead accept it and correct your fault > you are doing the wrong job > > I'm complaining nothing. I just curious about the configuration and want to know you developers' thinking. I apologize if I gave you the impression of complaining by asking questions. Basically, I'm new to MySQL and find MySQL really take care about lots of things to give users an easy job. For example, the unit, the enumeration options, all are case insensitive -- "512K" and "512k" means the same size, "MIXED" and "mixed" means the same option, etc. Having such impression, when MySQL tells me 'Port' is unknown, it did take me some time to figure it out. Maybe simply because all the other servers I used like PostgreSQL, httpd, etc are case insensitive. That's the whole story, and that's why I ask on the forum, being curious about the reason. It's fine that you told me it's simply because you developers assume nobody "came to the idea write options not EXACTLY like they are in the documentation", so you simply do not want to do it. But I do not buy this, because MySQL developers do take care a lot of things (as unit and options I mentioned). T -- Tianyin XU, http://cseweb.ucsd.edu/~tixu/
Re: Why configuration directives are all case sensitive?
Hi, On Sun, Nov 18, 2012 at 4:35 PM, Reindl Harald wrote: > > > Am 19.11.2012 01:27, schrieb Tianyin Xu: > > I'm not saying the file names but the configuration directives. > > At least for most servers I have managed so far, > > all the configuration directives are case insensitive. Examples? > PostgreSQL, > > Apache httpd, OpenLDAP, Squid, etc. > > That's why I'm curious. (Yes, please tell me there's no other > case-insensitive software) > > i never would came to the idea write options > not EXACTLY like they are in the documentation > > Sometimes people are not aware of their mistakes, otherwise they won't make mistakes. People are different. You cannot assume all your users are the same as you. > > I'm glad most MySQL folks are not like you. I'm happy to see "M" and "m" > refers > > to the same thing, and "K" and "k" also. > > if you work exactly and careful it does not matter > if not do not maintain a server at all > > You are saying as long as admins are careful, there's no misconfiguration? But why misconfigurations are so pervasive? Simply because the admins are not careful enough? > > If you wanna everyone follow your binary-by-binary rule, nobody gonna > use your stuff > > enough people are using my stuff outside the mysql world > and the all are able to enter things like they are in the > documentation, and i am speaking about noobs, not admins > I apologize for my lack of respect. I don't know what's your stuff, but I guess they'll be more popular if you make them more friendly. > > because if this is a problem for you maybe you have the wrong job > > I don't think it's wrong to make your software as friend as possible > > if you are a server admin you have to be careful what > you type or you are doing the wrong job > > sever software does not need to be friendly > it does not need to think what you mean > you have to excactly specify what you mean > > This does not make sense. Taking MySQL as an example, as server software, it's used everywhere by millions of users. Most of them are not admins or developers. > sounds liek you are a windows guy > 1. I really don't think windows guy or linux guy matters. After all, MySQL has windows versions. 2. Unfortunately, I'm not a windows guy. > > try "LS", "DF" or whatever on a unix terminal > you will get error messages as response > > Thanks! I use them regularly. T -- Tianyin XU, http://cseweb.ucsd.edu/~tixu/
Re: Why configuration directives are all case sensitive?
Hi, Reindl, On Sun, Nov 18, 2012 at 3:11 PM, Reindl Harald wrote: > > > Am 18.11.2012 23:59, schrieb Tianyin Xu: > > Hi, > > > > I'm just curious why MySQL parses its configuration directives (i.e., the > > ones in my.cnf) in a case sensitive way? > > > > For example, Having "Port=3309", will receive "unknown variable > 'Port=3309". > > > > I guess there must be some concern for this. Could anyone tell me why? > > because every useable OS on this world is case-sensitive? > > windows and partly MacOSX are the only OS on this world which > are not case-senstivie even for filenames and both are NOT > useable for servers at all > > I'm not saying the file names but the configuration directives. At least for most servers I have managed so far, all the configuration directives are case insensitive. Examples? PostgreSQL, Apache httpd, OpenLDAP, Squid, etc. That's why I'm curious. (Yes, please tell me there's no other case-insensitive software) > because "A" is binary not the same as "a" > because computers are working with binary data > > because "a.txt" is not the same file as "A.txt" > because it is useless overhead to translate every input > because if you maintain a server you should have a working keyboard > because a configuration should be clear and not a guess what you mean > > I'm glad most MySQL folks are not like you. I'm happy to see "M" and "m" refers to the same thing, and "K" and "k" also. If you wanna everyone follow your binary-by-binary rule, nobody gonna use your stuff. > because if this is a problem for you maybe you have the wrong job > > I don't think it's wrong to make your software as friend as possible. T -- Tianyin XU, http://cseweb.ucsd.edu/~tixu/
Why configuration directives are all case sensitive?
Hi, I'm just curious why MySQL parses its configuration directives (i.e., the ones in my.cnf) in a case sensitive way? For example, Having "Port=3309", will receive "unknown variable 'Port=3309". I guess there must be some concern for this. Could anyone tell me why? Thanks, Tianyin -- Tianyin XU, http://cseweb.ucsd.edu/~tixu/
Re: mysqld cannot start.
On Mon, Nov 12, 2012 at 1:47 PM, Tianyin Xu wrote: > Hi, Larry, > > Thanks a lot for the reply! > > > On Mon, Nov 12, 2012 at 1:27 PM, Larry Martell wrote: > >> On Mon, Nov 12, 2012 at 2:11 PM, Tianyin Xu wrote: >> > Hi, guys, >> > >> > I'm new to MySQL. I installed MySQL step-by-step according to the manual >> > from source code. The version is mysql-5.5.28. >> > >> > When I start the server using: >> > #bin/mysqld_safe --user=mysql >> > >> > The server failed to start with the following message in the log >> (attached >> > below). >> > >> > There're two problems according to the log messages: >> > >> > 1. >> > >> > 121112 13:00:59 [ERROR] Can't read from messagefile >> > '/usr/local/mysql/data/errmsg.sys >> > >> > I'm confused because I do have this file which is owned by user "mysql": >> > >> > #ll /usr/local/mysql/data/errmsg.sys >> > -rw-r--r-- 1 mysql mysql 0 Nov 12 12:35 /usr/local/mysql/data/errmsg.sys >> >> Check the permissions of all the dirs in that path: /usr, /usr/local, >> /usr/local/mysql, /usr/local/mysql/data. The mysql user will need r-x >> access to all of them. >> >> > I already did so. It's weird... From the log, it seems that mysqld > encountered some problem when reading the messagefile. But the file does > exist with permission. > > > >> > 2. >> > >> > 121112 13:00:59 [ERROR] An old style --language value with language >> > specific part detected: /usr/local/mysql/data/ >> > >> > I commented the "lc-messages-dir" configuration entry in the my.cnf, but >> > the error still exists... >> >> Don't know what platform you're on, but on my Mac I had this issue, >> and I got around it by starting the server with: >> >> --lc-messages-dir="/usr/local/mysql/share/" >> > > I'm working on Ubuntu-12.04. Yes, the configuration parameter is set as > /usr/local/mysql/data/ (see the error message). I tried your setting but > this time mysqld tells me > > 121112 13:46:28 [ERROR] bin/mysqld: unknown variable > 'lc-message-dir=/usr/local/mysql/share/' > 121112 13:46:28 [ERROR] Aborting > > What a mess... > > > Oh, the above error message is caused by my typo. Yes, I set --lc-messages-dir="/usr/local/mysql/share/", and everything's ok... The latter error message (i.e., messagefile) is the chain reaction caused by the previous one (lc-messages-dir) which confused me. Thanks a lot, Larry! Tianyin > >> On CentOS and RHEL I did not have this issue. >> >> HTH- >> larry >> > > > Probably I shall go to GDB to understand what's happening here... > > Great thanks! > > T > > -- > Tianyin XU, > http://cseweb.ucsd.edu/~tixu/ > -- Tianyin XU, http://cseweb.ucsd.edu/~tixu/
Re: mysqld cannot start.
Hi, Larry, Thanks a lot for the reply! On Mon, Nov 12, 2012 at 1:27 PM, Larry Martell wrote: > On Mon, Nov 12, 2012 at 2:11 PM, Tianyin Xu wrote: > > Hi, guys, > > > > I'm new to MySQL. I installed MySQL step-by-step according to the manual > > from source code. The version is mysql-5.5.28. > > > > When I start the server using: > > #bin/mysqld_safe --user=mysql > > > > The server failed to start with the following message in the log > (attached > > below). > > > > There're two problems according to the log messages: > > > > 1. > > > > 121112 13:00:59 [ERROR] Can't read from messagefile > > '/usr/local/mysql/data/errmsg.sys > > > > I'm confused because I do have this file which is owned by user "mysql": > > > > #ll /usr/local/mysql/data/errmsg.sys > > -rw-r--r-- 1 mysql mysql 0 Nov 12 12:35 /usr/local/mysql/data/errmsg.sys > > Check the permissions of all the dirs in that path: /usr, /usr/local, > /usr/local/mysql, /usr/local/mysql/data. The mysql user will need r-x > access to all of them. > > I already did so. It's weird... From the log, it seems that mysqld encountered some problem when reading the messagefile. But the file does exist with permission. > > 2. > > > > 121112 13:00:59 [ERROR] An old style --language value with language > > specific part detected: /usr/local/mysql/data/ > > > > I commented the "lc-messages-dir" configuration entry in the my.cnf, but > > the error still exists... > > Don't know what platform you're on, but on my Mac I had this issue, > and I got around it by starting the server with: > > --lc-messages-dir="/usr/local/mysql/share/" > I'm working on Ubuntu-12.04. Yes, the configuration parameter is set as /usr/local/mysql/data/ (see the error message). I tried your setting but this time mysqld tells me 121112 13:46:28 [ERROR] bin/mysqld: unknown variable 'lc-message-dir=/usr/local/mysql/share/' 121112 13:46:28 [ERROR] Aborting What a mess... > > On CentOS and RHEL I did not have this issue. > > HTH- > larry > Probably I shall go to GDB to understand what's happening here... Great thanks! T -- Tianyin XU, http://cseweb.ucsd.edu/~tixu/
mysqld cannot start.
Hi, guys, I'm new to MySQL. I installed MySQL step-by-step according to the manual from source code. The version is mysql-5.5.28. When I start the server using: #bin/mysqld_safe --user=mysql The server failed to start with the following message in the log (attached below). There're two problems according to the log messages: 1. 121112 13:00:59 [ERROR] Can't read from messagefile '/usr/local/mysql/data/errmsg.sys I'm confused because I do have this file which is owned by user "mysql": #ll /usr/local/mysql/data/errmsg.sys -rw-r--r-- 1 mysql mysql 0 Nov 12 12:35 /usr/local/mysql/data/errmsg.sys 2. 121112 13:00:59 [ERROR] An old style --language value with language specific part detected: /usr/local/mysql/data/ I commented the "lc-messages-dir" configuration entry in the my.cnf, but the error still exists... Could anyone take a look at the error log? Thanks a lot! T -- 121112 13:00:59 mysqld_safe Starting mysqld daemon with databases from /usr/local/mysql/data 121112 13:00:59 [ERROR] An old style --language value with language specific part detected: /usr/local/mysql/data/ 121112 13:00:59 [ERROR] Use --lc-messages-dir without language specific part instead. 121112 13:00:59 [ERROR] Can't read from messagefile '/usr/local/mysql/data/errmsg.sys' 121112 13:00:59 InnoDB: The InnoDB memory heap is disabled 121112 13:00:59 InnoDB: Mutexes and rw_locks use GCC atomic builtins 121112 13:00:59 InnoDB: Compressed tables use zlib 1.2.3.4 121112 13:00:59 InnoDB: Initializing buffer pool, size = 128.0M 121112 13:00:59 InnoDB: Completed initialization of buffer pool 121112 13:00:59 InnoDB: highest supported file format is Barracuda. 121112 13:00:59 InnoDB: Waiting for the background threads to start 121112 13:01:00 InnoDB: 1.1.8 started; log sequence number 1595675 121112 13:01:00 [ERROR] Aborting 121112 13:01:00 InnoDB: Starting shutdown... 121112 13:01:00 InnoDB: Shutdown completed; log sequence number 1595675 121112 13:01:00 [Note] 121112 13:01:00 mysqld_safe mysqld from pid file /var/run/mysqld/mysqld.pid ended 121112 13:03:49 mysqld_safe Starting mysqld daemon with databases from /usr/local/mysql/data 121112 13:03:49 [ERROR] Can't find messagefile '/usr/share/errmsg.sys' 121112 13:03:49 InnoDB: The InnoDB memory heap is disabled 121112 13:03:49 InnoDB: Mutexes and rw_locks use GCC atomic builtins 121112 13:03:49 InnoDB: Compressed tables use zlib 1.2.3.4 121112 13:03:49 InnoDB: Initializing buffer pool, size = 128.0M 121112 13:03:49 InnoDB: Completed initialization of buffer pool 121112 13:03:49 InnoDB: highest supported file format is Barracuda. 121112 13:03:49 InnoDB: Waiting for the background threads to start 121112 13:03:50 InnoDB: 1.1.8 started; log sequence number 1595675 121112 13:03:50 [ERROR] Aborting 121112 13:03:50 InnoDB: Starting shutdown... 121112 13:03:50 InnoDB: Shutdown completed; log sequence number 1595675 121112 13:03:50 [Note] 121112 13:03:50 mysqld_safe mysqld from pid file /var/run/mysqld/mysqld.pid ended -- Tianyin XU, http://cseweb.ucsd.edu/~tixu/
