search

beimuaihui / common-schema

Automatically exported from code.google.com/p/common-schema
0 stars 0 forks source link

common_schema 1.2.2 - crashed mysqld on production! #35

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
Which version of common_schema are you using? (specify
revision+distribution)
1.2.2
Which component is failing? (specify the view, function, etc.)
`_expand_statement_variables`
What is the expected output? What do you see instead?
during execution the file- the session disconnected... 
(mysql> \. common_schema-1.2.2.sql;) 
Can you provide with sample data?
please see attached error log
(As of version 1.1), please provide output of
SELECT * FROM common_schema.status
  project_name: common_schema
                            version: 1.2.2
                           revision: 368
                       install_time: 2012-12-03 22:06:02
                    install_success: 0
          base_components_installed: 0
 innodb_plugin_components_installed: 0
percona_server_components_installed: 0
              install_mysql_version: 5.5.13-log
                   install_sql_mode:

Please provide any additional information below.

Original issue reported on code.google.com by kizer.a...@gmail.com on 3 Dec 2012 at 11:15

Attachments:

GoogleCodeExporter commented 9 years ago 
Anything that crashes MySQL on production is a MySQL bug - right?

However I don't understand how you have imported the file; your command:

mysql> \. common_schema-1.2.2.sql;

is NOT a way to import a SQL file but rather inline a shell script. Since this 
does not actually import common_schema, I have nothing to offer you.

Please use:

bash$ mysql < common_schema-1.2.2.sql

or

mysql> SOURCE common_schema-1.2.2.sql

I'll await your comment and then change to WontFix

Original comment by shlomi.n...@gmail.com on 4 Dec 2012 at 7:06

GoogleCodeExporter commented 9 years ago 
Nevertheless I can see your log file does provide information about the error.

Funny enough, this is the third crashing bug of MySQL I find using 
common_schema.
Can you please output the values of:

thread_styck_size
group_concat_max_len
sql_mode

?

Original comment by shlomi.n...@gmail.com on 4 Dec 2012 at 7:10

GoogleCodeExporter commented 9 years ago 
And, apologies, "\." is same as SOURCE; my bad.

Is this Windows or Linux?

Original comment by shlomi.n...@gmail.com on 4 Dec 2012 at 7:25

GoogleCodeExporter commented 9 years ago 
-- Linux - Red Hat 5 Ent. 64-bit.
-- sql_mode=''
-- group_concat_max_len = 1024 
-- thread_styck_size??? do you mean thread_cache_size=100

Original comment by kizer.a...@gmail.com on 4 Dec 2012 at 4:18

GoogleCodeExporter commented 9 years ago 
No, sorry, meant for thread_stack

Original comment by shlomi.n...@gmail.com on 4 Dec 2012 at 9:45

GoogleCodeExporter commented 9 years ago 
thread_stack = 262144

Original comment by kizer.a...@gmail.com on 4 Dec 2012 at 10:54

GoogleCodeExporter commented 9 years ago 
I am able to reproduce this on 5.5.13. However, the problem does not reproduce 
on some earlier/later versions of MySQL. I can assume this is a MySQL bug 
introduced at about 5.5.13 and resolved since.

I encourage you to upgrade your MySQL server.

Original comment by shlomi.n...@gmail.com on 24 Dec 2012 at 6:40