Як я можу їх виправити? Це Centos 6.7, і я використовую вершину та htop, але коли я використовую ці інструменти, сервер прекрасно.
І сервер починає божевільний і споживає багато оперативної пам'яті, дивіться це:
Ви можете мені допомогти, хлопці? хтось має таку ж проблему чи щось таке? наперед дякую.
Вихід з mysqltuner його:
-------- Performance Metrics -----------------------------------------------------------------------
[--] Up for: 3m 43s (11K q [52.305 qps], 107 conn, TX: 35M, RX: 1M)
[--] Reads / Writes: 98% / 2%
[--] Binary logging is disabled
[--] Physical Memory : 2.0G
[--] Max MySQL memory : 583.2M
[--] Other process memory: 1.4G
[--] Total buffers: 168.0M global + 2.8M per thread (151 max threads)
[--] P_S Max memory usage: 0B
[--] Galera GCache Max memory usage: 0B
[OK] Maximum reached memory usage: 181.8M (9.10% of installed RAM)
[OK] Maximum possible memory usage: 583.2M (29.20% of installed RAM)
[!!] Overall possible memory usage with other process exceeded memory
[OK] Slow queries: 0% (0/11K)
[OK] Highest usage of available connections: 3% (5/151)
[OK] Aborted connections: 1.87% (2/107)
[!!] name resolution is active : a reverse name resolution is made for each new connection and can reduce performance
[!!] Query cache may be disabled by default due to mutex contention.
[OK] Sorts requiring temporary tables: 0% (0 temp sorts / 1K sorts)
[OK] No joins without indexes
[!!] Temporary tables created on disk: 63% (841 on disk / 1K total)
[!!] Thread cache is disabled
[OK] Table cache hit rate: 81% (31 open / 38 opened)
[OK] Open file limit used: 1% (20/1K)
[OK] Table locks acquired immediately: 100% (12K immediate / 12K locks)
І mysqld.log:
161010 18:03:39 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
161010 18:03:39 [Note] /usr/libexec/mysqld (mysqld 5.5.50) starting as process 8737 ...
161010 18:03:39 [Note] Plugin 'FEDERATED' is disabled.
161010 18:03:39 InnoDB: The InnoDB memory heap is disabled
161010 18:03:39 InnoDB: Mutexes and rw_locks use GCC atomic builtins
161010 18:03:39 InnoDB: Compressed tables use zlib 1.2.3
161010 18:03:39 InnoDB: Using Linux native AIO
161010 18:03:39 InnoDB: Initializing buffer pool, size = 128.0M
161010 18:03:39 InnoDB: Completed initialization of buffer pool
161010 18:03:39 InnoDB: highest supported file format is Barracuda.
161010 18:03:39 InnoDB: Waiting for the background threads to start
161010 18:03:40 InnoDB: 5.5.50 started; log sequence number 32512613973
161010 18:03:40 [Note] Server hostname (bind-address): '0.0.0.0'; port: 3306
161010 18:03:40 [Note] - '0.0.0.0' resolves to '0.0.0.0';
161010 18:03:40 [Note] Server socket created on IP: '0.0.0.0'.
161010 18:03:40 [ERROR] Missing system table mysql.proxies_priv; please run mysql_upgrade to create it
161010 18:03:40 [ERROR] Native table 'performance_schema'.'events_waits_current' has the wrong structure
161010 18:03:40 [ERROR] Native table 'performance_schema'.'events_waits_history' has the wrong structure
161010 18:03:40 [ERROR] Native table 'performance_schema'.'events_waits_history_long' has the wrong structure
161010 18:03:40 [ERROR] Native table 'performance_schema'.'setup_consumers' has the wrong structure
161010 18:03:40 [ERROR] Native table 'performance_schema'.'setup_instruments' has the wrong structure
161010 18:03:40 [ERROR] Native table 'performance_schema'.'setup_timers' has the wrong structure
161010 18:03:40 [ERROR] Native table 'performance_schema'.'performance_timers' has the wrong structure
161010 18:03:40 [ERROR] Native table 'performance_schema'.'threads' has the wrong structure
161010 18:03:40 [ERROR] Native table 'performance_schema'.'events_waits_summary_by_thread_by_event_name' has the wrong structure
161010 18:03:40 [ERROR] Native table 'performance_schema'.'events_waits_summary_by_instance' has the wrong structure
161010 18:03:40 [ERROR] Native table 'performance_schema'.'events_waits_summary_global_by_event_name' has the wrong structure
161010 18:03:40 [ERROR] Native table 'performance_schema'.'file_summary_by_event_name' has the wrong structure
161010 18:03:40 [ERROR] Native table 'performance_schema'.'file_summary_by_instance' has the wrong structure
161010 18:03:40 [ERROR] Native table 'performance_schema'.'mutex_instances' has the wrong structure
161010 18:03:40 [ERROR] Native table 'performance_schema'.'rwlock_instances' has the wrong structure
161010 18:03:40 [ERROR] Native table 'performance_schema'.'cond_instances' has the wrong structure
161010 18:03:40 [ERROR] Native table 'performance_schema'.'file_instances' has the wrong structure
161010 18:03:40 [Note] Event Scheduler: Loaded 0 events
161010 18:03:40 [Note] /usr/libexec/mysqld: ready for connections.
Version: '5.5.50' socket: '/var/lib/mysql/mysql.sock' port: 3306 MySQL Community Server (GPL) by Remi
Я отримую це сповіщення від linode і сервера повільно. З'єднання Mysql теж падає; а споживання оперативної пам’яті та процесора на кілька моментів занадто велике
—
Гермес C.
Хоча це не дуже. Мій (виділений) сервер використовує 5 Гб пам'яті (+27 гігабайтів кеша / буферів). У вас також призначений лише один процесор. Це насправді не так вже й багато. // Якщо ви вважаєте, що ваш VPS піддається атаці, вам слід вивчити файли журналів усіх загальнодоступних служб.
—
Даніель Б
htop
щоб зробити висновок менш заплутаним.