• 04-09-2010, 12:26:26
    #1
    Merhaba,

    sunucum bir kaç site daha ekledikten sonra çok kasmaya başladı, bağlantıları kapatmama rağmen çözemediğim bir problem var

    1-2 saat stabil çalışıyor sonra kiltleniyor


    Sunucu özelliklerim

    Processor NameIntel(R) Atom(TM) CPU 330 @ 1.60GHz Vendor IDGenuineIntel Processor Speed (MHz)1596.078 Processor NameIntel(R) Atom(TM) CPU 330 @ 1.60GHz Vendor IDGenuineIntel Processor Speed (MHz)1596.078 Processor NameIntel(R) Atom(TM) CPU 330 @ 1.60GHz Vendor IDGenuineIntel Processor Speed (MHz)1596.078 Processor NameIntel(R) Atom(TM) CPU 330 @ 1.60GHz Vendor IDGenuineIntel Processor Speed (MHz)1596.078 Total Memory1025184 kB Free Memory597948 kB Total Swap Memory2064376 kB Free Swap Memory2035464 kB System Uptime0 Days, 18 Hours and 40 Minutes Apache 2.2.15Running DirectAdmin 1.36.0 Running Exim 4.67Running MySQL 5.0.91Running Named 9.3.4Running ProFTPd 1.3.3a Running sshd Running dovecot 1.2.12 Running Php 5.2.13

    My.cnf içeriği

    [mysqld]
    query_cache_limit=8M
    query_cache_size=256M
    query_cache_type=1
    max_connections=500
    max_user_connections=150
    interactive_timeout=20
    wait_timeout=20
    connect_timeout=6
    thread_cache_size=128
    key_buffer=16M
    join_buffer=1M
    max_allowed_packet=16M
    table_cache=1024
    record_buffer=1M
    sort_buffer_size=2M
    read_buffer_size=2M
    max_connect_errors=10
    thread_concurrency=4
    myisam_sort_buffer_size=64M
    server-id=1
    open_files_limit=8192


    [mysqldump]
    quick
    max_allowed_packet=16M

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

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

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

    tuning premier kurdum 2 gün bekleyecektim ama nafile tamamen mysqlde kitlendiği için biraz önce resetlemek zorunda kaldım onunda çıktısını aktarıyım

    -- MYSQL PERFORMANCE TUNING PRIMER --
                 - By: Matthew Montgomery -
    
    MySQL Version 5.0.91-community i686
    
    Uptime = 0 days 0 hrs 14 min 34 sec
    Avg. qps = 5
    Total Questions = 5037
    Threads Connected = 1
    
    Warning: Server has not been running for at least 48hrs.
    It may not be safe to use these recommendations
    
    To find out more information on how each of these
    runtime variables effects performance visit:
    http://dev.mysql.com/doc/refman/5.0/en/server-system-variables.html
    Visit http://www.mysql.com/products/enterprise/advisors.html
    for info about MySQL's Enterprise Monitoring and Advisory Service
    
    SLOW QUERIES
    The slow query log is NOT enabled.
    Current long_query_time = 10 sec.
    You have 32 out of 5058 that take longer than 10 sec. to complete
    Your long_query_time seems to be fine
    
    BINARY UPDATE LOG
    The binary update log is NOT enabled.
    You will not be able to do point in time recovery
    See http://dev.mysql.com/doc/refman/5.0/en/point-in-time-recovery.html
    
    WORKER THREADS
    Current thread_cache_size = 128
    Current threads_cached = 17
    Current threads_per_sec = 0
    Historic threads_per_sec = 0
    Your thread_cache_size is fine
    
    MAX CONNECTIONS
    Current max_connections = 500
    Current threads_connected = 2
    Historic max_used_connections = 19
    The number of used connections is 3% of the configured maximum.
    You are using less than 10% of your configured max_connections.
    Lowering max_connections could help to avoid an over-allocation of memory
    See "MEMORY USAGE" section to make sure you are not over-allocating
    
    INNODB STATUS
    Current InnoDB index space = 0 bytes
    Current InnoDB data space = 0 bytes
    Current InnoDB buffer pool free = 96 %
    Current innodb_buffer_pool_size = 8 M
    Depending on how much space your innodb indexes take up it may be safe
    to increase this value to up to 2 / 3 of total system memory
    
    MEMORY USAGE
    Max Memory Ever Allocated : 384 M
    Configured Max Per-thread Buffers : 2.62 G
    Configured Max Global Buffers : 282 M
    Configured Max Memory Limit : 2.89 G
    Physical Memory : 1001 M
    
    nMax memory limit exceeds 90% of physical memory
    
    KEY BUFFER
    Current MyISAM index space = 7 M
    Current key_buffer_size = 16 M
    Key cache miss rate is 1 : 170
    Key buffer free ratio = 57 %
    Your key_buffer_size seems to be fine
    
    QUERY CACHE
    Query cache is enabled
    Current query_cache_size = 256 M
    Current query_cache_used = 4 M
    Current query_cache_limit = 8 M
    Current Query cache Memory fill ratio = 1.66 %
    Current query_cache_min_res_unit = 4 K
    Your query_cache_size seems to be too high.
    Perhaps you can use these resources elsewhere
    MySQL won't cache query results that are larger than query_cache_limit in size
    
    SORT OPERATIONS
    Current sort_buffer_size = 2 M
    Current read_rnd_buffer_size = 256 K
    Sort buffer seems to be fine
    
    JOINS
    Current join_buffer_size = 1.00 M
    You have had 0 queries where a join could not use an index properly
    Your joins seem to be using indexes properly
    
    OPEN FILES LIMIT
    Current open_files_limit = 8192 files
    The open_files_limit should typically be set to at least 2x-3x
    that of table_cache if you have heavy MyISAM usage.
    Your open_files_limit value seems to be fine
    
    TABLE CACHE
    Current table_cache value = 1024 tables
    You have a total of 56 tables
    You have 90 open tables.
    The table_cache value seems to be fine
    
    TEMP TABLES
    Current max_heap_table_size = 16 M
    Current tmp_table_size = 32 M
    Of 484 temp tables, 26% were created on disk
    Effective in-memory tmp_table_size is limited to max_heap_table_size.
    Perhaps you should increase your tmp_table_size and/or max_heap_table_size
    to reduce the number of disk-based temporary tables
    Note! BLOB and TEXT columns are not allow in memory tables.
    If you are using these columns raising these values might not impact your
    ratio of on disk temp tables.
    
    TABLE SCANS
    Current read_buffer_size = 2 M
    Current table scan ratio = 6530 : 1
    You have a high ratio of sequential access requests to SELECTs
    You may benefit from raising read_buffer_size and/or improving your use of indexes.
    
    TABLE LOCKING
    Current Lock Wait ratio = 1 : 76
    You may benefit from selective use of InnoDB.
    If you have long running SELECT's against MyISAM tables and perform
    frequent updates consider setting 'low_priority_updates=1'
    If you have a high concurrency of inserts on Dynamic row-length tables
    consider setting 'concurrent_insert=2'.

    yardım edebilirseniz sevinirim teşekkürler.
  • 04-09-2010, 12:38:17
    #2
    Gösterdiklerinizden pek birşey çıkmıyor. Ancak işlemciniz kötü. Sql saldırı alıyor yada sitenin biri yoğun sorgu yapılıyorsa sql down oluyor olabilir. Sql loglarına bakın orda sorgu yapan cpu'ya yüklenen kayıtları bize gösterin böylece bir sonuç çıkartabiliriz.
  • 04-09-2010, 12:50:33
    #3
    şimdi onu araştırıyorum, ama sanırım log tutmuyor log tutmasını nasıl sağlıyabilirim panelim direct admin apache eror log/access log var ama mysql ile ilgili kayıt yok.