Topic: updates.log on : var/lib/mysql/

[darmasanthi]

Dear Support,
today i found "updates.log" on var/lib/mysql/ - the size is around 670GB,
its look like become bigger and bigger and taking all of hard drive size

What is make that log increasing every-time?

Here is the "my.cnf: file

[mysqld]
local-infile=0
skip-locking
skip-innodb
query_cache_limit=1M
query_cache_size=128M
query_cache_type=1
max_user_connections=60
max_connections=60
interactive_timeout=100
wait_timeout=28840
connect_timeout=28840
thread_cache_size=128
key_buffer=512M
join_buffer_size=1M
max_allowed_packet=16M
tmp_table_size=8192
table_cache=4096
max_heap_table_size=4096
record_buffer=1M
sort_buffer_size=4M
read_buffer_size=4M
read_rnd_buffer_size=4M
max_connect_errors=30
myisam_sort_buffer_size=64M
old-passwords
# Try number of CPU's*2 for thread_concurrency
thread_concurrency=4
server-id=1


# enable slow query log
#This is a great tool for checking what queries take too long
log-slow-queries=/tmp/slow_queries.log
log-update = /var/lib/mysql/updates.log


[safe_mysqld]
err-log=/var/log/mysqld.log
pid-file=/var/lib/mysql/mysql.pid
open_files_limit=8192

[mysqldump]
quick
max_allowed_packet=16M

[mysql]
no-auto-rehash
#safe-updates

[isamchk]
key_buffer=64M
sort_buffer=64M
read_buffer=16M
write_buffer=16M

[myisamchk]
key_buffer=64M
sort_buffer=64M
read_buffer=16M
write_buffer=16M

[mysqlhotcopy]
interactive-timeout

My server specification is :
- Dual Intel Xeon, with 8GB RAM

regards,
darmasanthi

[cactus]

Dear Support,
today i found "updates.log" on var/lib/mysql/ - the size is around 670GB,
its look like become bigger and bigger and taking all of hard drive size

What is make that log increasing every-time?

Are you sure this is on SME Server 7.x otherwise you posted in the wrong forums. If this is SME Server 7.x it seems  you have a heavily modified my.cnf file which has the slow query log enabled as well as a update.log:

Here is the "my.cnf: file

Code: [Select]

# enable slow query log
#This is a great tool for checking what queries take too long
log-slow-queries=/tmp/slow_queries.log
log-update = /var/lib/mysql/updates.log

The update log is a deprecated log option and should not be used, it has been replaced by the more efficient binary log option (for more information see: http://dev.mysql.com/doc/refman/4.1/en/update-log.html).
The log-update option ensures every update query that is run on your MySQL server is logged in the file, I am unsure why this was enabled at all, but if you do not need it you need to remove this form your configuration file, it most likely is set through a custom-template fragment.

You can read more on the template system in the Developers Guide linked from the wiki.

[darmasanthi]

If you don't mind,
could you please give me the best "my.cnf" configuration

rgds,
gede

[cactus]

If you don't mind,
could you please give me the best "my.cnf" configuration

There is no best setup, it totally depends on situations, used cases, server specs and database use, but you have a lot of additional things configured compared to a stock my.cnf file.

What is the output of the following command:

Code: [Select]

ls -la /etc/e-smith/templates-custom/etc/my.cnf/