Всем привет!
Столкнулся с проблемой спам/флуд/DoS атаки приводящей к отказу сервера без автоматической возможности восстановления его работы (ручной килл процесса и ручной запуск).
Лог спам/флуд/DoS вследствии которого он зависает:
IP rate limiting client 193.122.227.214:8801 at 301 hits (59 buckets, 344 global count).
IP rate limiting client 193.122.227.214:8801 sustained 3060 hits at 102.0 pps (57 buckets, 31 global count).
IP rate limiting client 193.122.227.214:8801 at 420 hits (57 buckets, 337 global count).
IP rate limiting client 193.122.227.214:8801 at 523 hits (62 buckets, 351 global count).
IP rate limiting client 176.148.39.23:80 at 301 hits (62 buckets, 352 global count).
IP rate limiting client 91.169.207.152:80 at 301 hits (51 buckets, 351 global count).
IP rate limiting client 91.169.207.152:80 at 337 hits (60 buckets, 360 global count).
IP rate limiting client 45.88.109.71:27015 at 301 hits (62 buckets, 333 global count).
IP rate limiting client 45.88.109.71:27015 at 420 hits (60 buckets, 404 global count).
IP rate limiting client 45.88.109.71:27015 at 479 hits (68 buckets, 423 global count).
IP rate limiting client 45.88.109.71:27015 at 537 hits (63 buckets, 429 global count).
IP rate limiting client 45.88.109.71:27015 at 578 hits (51 buckets, 446 global count).
IP rate limiting client 45.88.109.71:27015 at 614 hits (63 buckets, 437 global count).
IP rate limiting client 45.88.109.71:27015 at 655 hits (50 buckets, 393 global count).
IP rate limiting client 45.88.109.71:27015 at 693 hits (58 buckets, 374 global count).
IP rate limiting client 45.88.109.71:27015 at 736 hits (64 buckets, 343 global count).
IP rate limiting client 45.88.109.71:27015 at 778 hits (53 buckets, 310 global count).
IP rate limiting client 135.125.52.230:30533 at 301 hits (56 buckets, 270 global count).
IP rate limiting client 135.125.52.230:30533 at 306 hits (65 buckets, 267 global count).
IP rate limiting client 135.125.52.230:30533 at 317 hits (68 buckets, 264 global count).
IP rate limiting client 135.125.52.230:30533 at 343 hits (67 buckets, 236 global count).
IP rate limiting client 135.125.52.230:30533 at 358 hits (59 buckets, 217 global count).
IP rate limiting client 135.125.52.230:30533 at 378 hits (60 buckets, 194 global count).
IP rate limiting client 135.125.52.230:30533 at 395 hits (52 buckets, 175 global count).
IP rate limiting client 135.125.52.230:30533 at 409 hits (67 buckets, 176 global count).
IP rate limiting client 135.125.52.230:30533 at 411 hits (62 buckets, 169 global count).
IP rate limiting client 135.125.52.230:30533 at 301 hits (53 buckets, 342 global count).
IP rate limiting client 135.125.52.230:30533 at 433 hits (59 buckets, 342 global count).
IP rate limiting client 135.125.52.230:30533 at 493 hits (58 buckets, 343 global count).
IP rate limiting client 135.125.52.230:30533 at 550 hits (59 buckets, 342 global count).
IP rate limiting client 135.125.52.230:30533 sustained 1736 hits at 57.9 pps (62 buckets, 27 global count).
IP rate limiting client 135.125.52.230:30533 at 568 hits (58 buckets, 343 global count).
IP rate limiting client 135.125.52.230:30533 at 611 hits (62 buckets, 349 global count).
IP rate limiting client 135.125.52.230:30533 sustained 1740 hits at 58.0 pps (61 buckets, 12 global count).
IP rate limiting client 135.125.52.230:30533 at 622 hits (45 buckets, 332 global count).
IP rate limiting client 135.125.52.230:30533 at 625 hits (56 buckets, 343 global count).
IP rate limiting client 135.125.52.230:30533 at 701 hits (61 buckets, 341 global count).
IP rate limiting client 135.125.52.230:30533 at 771 hits (64 buckets, 348 global count).
IP rate limiting client 135.125.52.230:30533 at 301 hits (57 buckets, 34 global count).
IP rate limiting client 135.125.52.230:30533 at 428 hits (61 buckets, 397 global count).
IP rate limiting client 135.125.52.230:30533 at 490 hits (46 buckets, 346 global count).
IP rate limiting client 135.125.52.230:30533 at 514 hits (59 buckets, 362 global count).
IP rate limiting client 135.125.52.230:30533 at 608 hits (64 buckets, 365 global count).
IP rate limiting client 135.125.52.230:30533 at 660 hits (68 buckets, 369 global count).
IP rate limiting client 135.125.52.230:30533 at 673 hits (55 buckets, 359 global count).
IP rate limiting client 135.125.52.230:30533 at 753 hits (70 buckets, 371 global count).
IP rate limiting client 135.125.52.230:30533 sustained 1684 hits at 56.1 pps (62 buckets, 36 global count).
IP rate limiting client 135.125.52.230:30533 at 759 hits (64 buckets, 368 global count).
IP rate limiting client 135.125.52.230:30533 at 799 hits (52 buckets, 353 global count).
IP rate limiting client 188.208.32.82:80 at 301 hits (55 buckets, 163 global count).
IP rate limiting client 45.88.109.71:27015 at 301 hits (64 buckets, 278 global count).
IP rate limiting client 45.88.109.71:27015 at 313 hits (58 buckets, 255 global count).
IP rate limiting client 45.88.109.71:27015 at 328 hits (54 buckets, 232 global count).
IP rate limiting client 45.88.109.71:27015 at 347 hits (40 buckets, 204 global count).
IP rate limiting client 45.88.109.71:27015 at 348 hits (44 buckets, 207 global count).
IP rate limiting client 45.88.109.71:27015 at 372 hits (47 buckets, 184 global count).
IP rate limiting client 45.88.109.71:27015 sustained 443 hits at 14.8 pps (49 buckets, 194 global count).
IP rate limiting client 45.88.109.71:27015 at 371 hits (47 buckets, 184 global count).
IP rate limiting client 45.88.109.71:27015 at 380 hits (53 buckets, 189 global count).
IP rate limiting client 45.88.109.71:27015 at 394 hits (61 buckets, 183 global count).
IP rate limiting client 45.88.109.71:27015 at 411 hits (57 buckets, 155 global count).
IP rate limiting client 45.88.109.71:27015 at 301 hits (60 buckets, 329 global count).
IP rate limiting client 45.88.109.71:27015 at 406 hits (53 buckets, 330 global count).
IP rate limiting client 45.88.109.71:27015 at 448 hits (50 buckets, 330 global count).
IP rate limiting client 45.88.109.71:27015 at 468 hits (56 buckets, 330 global count).
IP rate limiting client 45.88.109.71:27015 at 497 hits (50 buckets, 330 global count).
IP rate limiting client 188.208.32.82:80 at 301 hits (53 buckets, 264 global count).
IP rate limiting client 188.208.32.82:80 at 468 hits (54 buckets, 116 global count).
IP rate limiting client 188.208.32.82:80 at 509 hits (52 buckets, 75 global count).
IP rate limiting client 188.208.32.82:80 sustained 1658 hits at 55.3 pps (37 buckets, 99 global count).
IP rate limiting client 188.208.32.82:80 at 551 hits (42 buckets, 37 global count).
IP rate limiting client 188.208.32.82:80 at 575 hits (60 buckets, 12 global count).
IP rate limiting client 188.208.32.82:80 sustained 1673 hits at 55.8 pps (50 buckets, 43 global count).
IP rate limiting client 188.208.32.82:80 at 600 hits (55 buckets, 10 global count).
IP rate limiting client 188.208.32.82:80 sustained 1686 hits at 56.2 pps (46 buckets, 37 global count).
IP rate limiting client 188.208.32.82:80 at 605 hits (40 buckets, 10 global count).
IP rate limiting client 188.208.32.82:30120 at 638 hits (61 buckets, 13 global count).
IP rate limiting client 188.208.32.82:80 at 662 hits (59 buckets, 10 global count).
IP rate limiting client 188.208.32.82:80 at 914 hits (64 buckets, 9 global count).
IP rate limiting client 51.195.62.56:30120 at 301 hits (56 buckets, 335 global count).
IP rate limiting client 51.195.62.56:30120 at 442 hits (41 buckets, 323 global count).
IP rate limiting client 51.195.62.56:30120 sustained 3391 hits at 113.0 pps (50 buckets, 21 global count).
IP rate limiting client 51.195.62.56:30120 at 422 hits (47 buckets, 327 global count).
IP rate limiting client 51.195.62.56:30120 at 495 hits (46 buckets, 326 global count).
IP rate limiting client 51.195.62.56:30120 at 640 hits (42 buckets, 328 global count).
IP rate limiting client 51.195.62.56:30120 at 698 hits (39 buckets, 319 global count).
IP rate limiting client 51.195.62.56:30120 at 788 hits (49 buckets, 324 global count).
IP rate limiting client 51.195.62.56:30120 at 902 hits (56 buckets, 324 global count).
IP rate limiting client 51.195.62.56:30120 at 868 hits (47 buckets, 321 global count).
Но как только я отключаю RevEmu, то проблема сразу исчезает. Это не пустые слова. Я столкнулся с данной проблемой более полугода назад - выключил RevEmu проблема не возникала полгода, а вчера включил снова и сервер снова уводят в отказ без авто-рестарта. То есть когда он ложится, то последнее что есть в логе сервера это спам-флуд выше.
8 августа 2021 17:28
