cajuninho
(usa Outra)
Enviado em 07/07/2015 - 14:13h
zhushazang escreveu:
1GB é bem pouco hein.
Mas veja, como você sabe que é ataque. Mostre os logs que você conseguiu.
Se realmente for ataque, você precisa entrar em contato com o responsável pelo DC de hospedagem e solicitar proteção. É muito provável que te cobrem (e caro) por isso.
Ademais, o que você pode fazer, é garantir utilizando iptables que portas desnecessárias aos usuários externos estejam fechadas. Se bem que pelo tipo de comportamento, eles simplesmente miram na porta do serviço válido e te derrubam por DoS ou DDoS. Saída? Não há. A não ser a proteção a frente de seu servidor.
Sinceramente, você está no mato sem cachorro.
Atenciosamente
---
Hail Hydra!
Obrigado pela atenção.
Será que o log do mysql pode dizer algo também?
0 queries inside InnoDB, 0 queries in queue
1 read views open inside InnoDB
Main thread process no. 9078, id 139794093909760, state: waiting for server activity
Number of rows inserted 0, updated 0, deleted 0, read 16
0.00 inserts/s, 0.00 updates/s, 0.00 deletes/s, 0.34 reads/s
----------------------------
END OF INNODB MONITOR OUTPUT
============================
150707 9:08:44 [ERROR] /usr/sbin/mysqld: Incorrect key file for table './almanaque/wp_options.MYI'; try to repair it
150707 9:08:49 [ERROR] Got an error from thread_id=32, /build/buildd/mysql-5.5-5.5.38/storage/myisam/mi_write.c:226
150707 9:08:52 [ERROR] MySQL thread id 32, OS thread handle 0x7f2458bcb700, query id 171 localhost root update
INSERT INTO `wp_options` (`option_name`, `option_value`, `autoload`) VALUES ('_transient_doing_cron', '1436270725.0389060974121093750000', 'yes') ON DUPLICATE KEY UPDATE `option_name` = VALUES(`option_name`), `option_value` = VALUES(`option_value`), `autoload` = VALUES(`autoload`)
150707 10:03:46 [Warning] Using unique option prefix myisam-recover instead of myisam-recover-options is deprecated and will be removed in a future release. Please use the full name instead.
150707 10:03:46 [Note] Plugin 'FEDERATED' is disabled.
150707 10:03:46 InnoDB: The InnoDB memory heap is disabled
150707 10:03:46 InnoDB: Mutexes and rw_locks use GCC atomic builtins
150707 10:03:46 InnoDB: Compressed tables use zlib 1.2.3.4
150707 10:03:46 InnoDB: Initializing buffer pool, size = 128.0M
150707 10:03:46 InnoDB: Completed initialization of buffer pool
150707 10:03:46 InnoDB: highest supported file format is Barracuda.
InnoDB: The log sequence number in ibdata files does not match
InnoDB: the log sequence number in the ib_logfiles!
150707 10:03:46 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...
150707 10:03:47 InnoDB: Waiting for the background threads to start
150707 10:03:48 InnoDB: 5.5.38 started; log sequence number 33633950753
150707 10:03:48 [Note] Server hostname (bind-address): '127.0.0.1'; port: 3306
150707 10:03:48 [Note] - '127.0.0.1' resolves to '127.0.0.1';
150707 10:03:48 [Note] Server socket created on IP: '127.0.0.1'.
150707 10:03:48 [Note] Event Scheduler: Loaded 0 events
150707 10:03:48 [Note] /usr/sbin/mysqld: ready for connections.
Version: '5.5.38-0ubuntu0.12.04.1' socket: '/var/run/mysqld/mysqld.sock' port: 3306 (Ubuntu)
150707 10:03:51 [ERROR] /usr/sbin/mysqld: Table './almanaque/wp_commentmeta' is marked as crashed and should be repaired
150707 10:03:51 [Warning] Checking table: './almanaque/wp_commentmeta'
150707 10:03:51 [ERROR] /usr/sbin/mysqld: Table './almanaque/wp_comments' is marked as crashed and should be repaired
150707 10:03:51 [Warning] Checking table: './almanaque/wp_comments'
150707 10:03:51 [ERROR] /usr/sbin/mysqld: Table './almanaque/wp_options' is marked as crashed and should be repaired
150707 10:03:51 [Warning] Checking table: './almanaque/wp_options'
150707 10:03:51 [Warning] Recovering table: './almanaque/wp_options'
150707 10:03:51 [Note] Found 644 of 642 rows when repairing './almanaque/wp_options'