MySQL Bugs: #34375: mysqld adjusts its own default value for thread

Bug #34375	mysqld adjusts its own default value for thread_stack
Submitted:	7 Feb 2008 9:37	Modified:	28 Sep 2010 19:50
Reporter:	Philip Stoev	Email Updates:
Status:	Won't fix	Impact on me:	None
Category:	MySQL Server: Packaging	Severity:	S3 (Non-critical)
Version:	5.0.56	OS:	Linux
Assigned to:	Jonathan Perkin	CPU Architecture:	Any

Description:
When one starts mysqld, the following warnings is printed out:

080207 11:33:39 [Warning] option 'thread_stack': unsigned value 126976 adjusted to 131072

Same warnings pops up on the console when one uses mysql_install_db -- it is not a good idea if one of the first things customers see from mysql is this (non-intuitive) warning.

How to repeat:
$ cd /path/to/mysql-binary-distribution/bin

$ ./mysqld

080207 11:33:39 [Warning] option 'thread_stack': unsigned value 126976 adjusted to 131072
...

Thank you for the report.

Verified as described.

Workaround: Value should be set before running the script

Hello, 

I just upgraded to MySQL 5.1.23 RC on a Windows XP box and receive the same error in the application-log when I start MySQL as a service.

Bernhard

Receiving same message when running mysql_install_db for first time installation using mysql installation procedure as mentioned in online documentation.

output of concern:

[root@webdev mysql]# ./scripts/mysql_install_db --user=mysql
Installing MySQL system tables...
081020 17:02:03 [Warning] option 'thread_stack': unsigned value 126976 adjusted to 131072
OK
Filling help tables...
081020 17:02:03 [Warning] option 'thread_stack': unsigned value 126976 adjusted to 131072
OK
......

[opem prompt, not bash]

so I hit ctrl+C and get...
[1]+  Done                    ./bin/mysqld_safe

then I try to run the server...

When I try to start mysqld, I get the following:

[root@webdev mysql]# cd . ; ./bin/mysqld_safe &
[1] 30404
[root@webdev mysql]# Starting mysqld daemon with databases from /var/lib/mysql
STOPPING server from pid file /var/run/mysqld/mysqld.pid
081020 17:15:27  mysqld ended

I then look at my logs and see the following:

081020 17:15:26  mysqld started
081020 17:15:26 [Warning] option 'thread_stack': unsigned value 126976 adjusted to 131072
InnoDB: Log scan progressed past the checkpoint lsn 0 36808
081020 17:15:26  InnoDB: Database was not shut down normally!
InnoDB: Starting crash recovery.
InnoDB: Reading tablespace information from the .ibd files...
InnoDB: Restoring possible half-written data pages from the doublewrite
InnoDB: buffer...
InnoDB: Doing recovery: scanned up to log sequence number 0 43655
081020 17:15:26  InnoDB: Starting an apply batch of log records to the database...
InnoDB: Progress in percents: 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 
InnoDB: Apply batch completed
081020 17:15:27  InnoDB: Started; log sequence number 0 43655
081020 17:15:27 [ERROR] /usr/local/mysql/bin/mysqld: Can't create/write to file '/var/run/mysqld/mysqld.pid' (Errcode: 2)
081020 17:15:27 [ERROR] Can't start server: can't create PID file: No such file or directory
081020 17:15:27  mysqld ended

I noticed there is a work-around, but exactly HOW does one assign the value before running the script?

load data infile '/sources/networks.txt' into table roaming_suite.NETWORKS fields terminated by ';' (NETWORK_ID, OPERATOR_NAME,

Attachment: networks.txt (text/plain), 27.66 KiB.

This was specific to the fully-static build we produced during the 5.0 series on Linux.

Since 5.1 we no longer build that product, and 5.0 is EOL. Thus WontFix (well, CantFix).