Bug #41769 | Can't enable external locking in my.cnf | ||
---|---|---|---|
Submitted: | 27 Dec 2008 21:44 | Modified: | 29 Jan 2009 8:24 |
Reporter: | Marc Perkel | Email Updates: | |
Status: | No Feedback | Impact on me: | |
Category: | MySQL Server | Severity: | S3 (Non-critical) |
Version: | 5.0.67 | OS: | Any |
Assigned to: | CPU Architecture: | Any | |
Tags: | external_locking, locking, skip_external_locking |
[27 Dec 2008 21:44]
Marc Perkel
[29 Dec 2008 5:46]
Sveta Smirnova
Thank you for the report. Please indicate accurate version of MySQL and operating system you use.
[29 Dec 2008 5:49]
Marc Perkel
I'm sing Fedora linux 10. MySQL Ver 14.12 Distrib 5.0.67, for redhat-linux-gnu (x86_64) using readline 5.1.
[29 Dec 2008 5:52]
Sveta Smirnova
Thank you for the feedback. I can not repeat described behavior. Please send us output of SHOW VARIABLES LIKE '%locking%'; and your configuration file.
[29 Dec 2008 5:54]
Marc Perkel
-> VARIABLES LIKE '%locking%'; +-----------------------+-------+ | Variable_name | Value | +-----------------------+-------+ | skip_external_locking | ON | +-----------------------+-------+
[29 Dec 2008 6:08]
Sveta Smirnova
Thank you for the feedback. Please send your configuration file.
[29 Dec 2008 6:11]
Marc Perkel
# The MySQL server [mysqld] port = 3306 socket = /mysql/mysql.sock delay_key_write = all key_buffer = 6G max_allowed_packet = 32M table_cache = 4096 tmp_table_size = 64M sort_buffer_size = 8M read_buffer_size = 8M read_rnd_buffer_size = 16M myisam_sort_buffer_size = 256M thread_cache = 512 query_cache_size = 128M # Try number of CPU's*2 for thread_concurrency thread_concurrency = 64 max_connections = 4000 max_connect_errors = 10000 external_locking enable_locking
[29 Dec 2008 8:24]
Sveta Smirnova
Thank you for the feedback. We still can not repeat described behavior. Please send us full error log file(turn it on first, then restart the server)
[30 Jan 2009 0:00]
Bugs System
No feedback was provided for this bug for over a month, so it is being suspended automatically. If you are able to provide the information that was originally requested, please do so and change the status of the bug back to "Open".