• There is NO official Otland's Discord server and NO official Otland's server list. The Otland's Staff does not manage any Discord server or server list. Moderators or administrator of any Discord server or server lists have NO connection to the Otland's Staff. Do not get scammed!
  • 2026 staff recruitment is open! Check it out and consider applying!

Ataki na serwer

Dziwna sprawa. Lagi znow sie zaczely pomimo hashlimtia oraz connlimita - zrobil sie save z cleanem i chwilowo wszystko jest ok.
Code: 
14:31 Game map cleaning within 30 seconds, please pick up your items!
14:32 Game saved!
14:32 Game map cleaned, next clean in 30 minutes.
Czy takie lagi sa mozliwe jezeli gracze nawrzucaja duza ilosc itemow na siebie?
 
Ale w tym wypadku wydaje mi sie ze clean pomogl a nie zaszkodzil wiec po co go wylaczac ?
 
Po kolejnych 3 dniach znow pojawily sie te lagi. Load jest niski, ssh nie laguje, www nie laguje, limity na polaczenia i pakiety w iptables sa, ping zablokowany, clean nie pomaga. Pomaga tylko restart serwera. Ktos ma jakies pomysly bo wychodzi na to ze nie jest to ddos?
 
Teraz dochodzi do tego ze odpalam serwer na porcie 7171, 30-40 sek jest ok i wpada lag. Odpalam na 7173 i chodzi normalnie. W iptables mam regulki na limity polaczen i pakietow. Rev 2957 z svna. Koncza mi sie pomysly i chyba po prostu zamkne serwer.
http://wklej.org/id/215397/txt - tak wyglada strace. W ostatnich 10 sek pojawia sie lag.
 
Last edited:
Code: 
[13:31:03.600] handle - OK
[13:31:03.660] request output message - auto = 0
[13:31:03.660] Sending message - SINGLE
[13:31:03.660] Connection::send init
[13:31:03.660] Protocol::onSendMessage
[13:31:03.660] Protocol::onSendMessage - encrypt
[13:31:03.660] Protocol::onSendMessage - crypto header
[13:31:03.660] Connection::send 150
[13:31:03.660] Connection::close
[13:31:03.660] onWrite
[13:31:03.660] Connection::closeSocket
[13:31:03.660] Closing socket
[13:31:03.660] Connection::close
[13:31:03.660] [Error - handleReadError] Reading - detail - Operation canceled (Operation canceled)
[13:31:03.660] Connection::close
[13:31:04.560] Creating new Connection
[13:31:04.560] request output message - auto = 0
[13:31:04.560] Sending message - SINGLE
[13:31:04.560] Connection::send init
[13:31:04.560] Protocol::onSendMessage
[13:31:04.560] Protocol::onSendMessage - crypto header
[13:31:04.560] Connection::send 14
[13:31:04.560] handle - OK
[13:31:04.560] onWrite
[13:31:04.664] request output message - auto = 0
[13:31:04.664] Sending message - SINGLE
[13:31:04.664] Connection::send init
[13:31:04.664] Protocol::onSendMessage
[13:31:04.664] Protocol::onSendMessage - encrypt
[13:31:04.664] Protocol::onSendMessage - crypto header
[13:31:04.664] Connection::send 46
[13:31:04.664] Connection::close
[13:31:04.664] onWrite
[13:31:04.664] Connection::closeSocket
[13:31:04.664] Closing socket
[13:31:04.664] Connection::close
[13:31:04.664] [Error - handleReadError] Reading - detail - Operation canceled (Operation canceled)
[13:31:04.664] Connection::close
[13:31:08.892] Creating new Connection
[13:31:08.892] request output message - auto = 0
[13:31:08.892] Sending message - SINGLE
[13:31:08.892] Connection::send init
[13:31:08.892] Protocol::onSendMessage
[13:31:08.892] Protocol::onSendMessage - crypto header
[13:31:08.892] Connection::send 14
[13:31:08.892] handle - OK
[13:31:08.892] onWrite
[13:31:14.140] Protocol::onRecvMessage
[13:31:14.140] Protocol::onRecvMessage - decrypt
[13:31:14.629] Protocol::onRecvMessage
[13:31:14.630] Protocol::onRecvMessage - decrypt
[13:31:14.686] Protocol::onRecvMessage
[13:31:14.686] Protocol::onRecvMessage - decrypt
[13:31:15.716] Protocol::onRecvMessage
[13:31:15.716] Protocol::onRecvMessage - decrypt
[13:31:16.845] [Error - handleReadError] Reading - detail - End of file (End of file)
[13:31:16.845] Connection::close
[13:31:16.845] Connection::close
[13:31:28.183] Connection::handleReadTimeout
[13:31:28.183] Connection::closeSocket
[13:31:28.183] Closing socket
[13:31:28.183] Connection::close
[13:31:28.183] [Error - handleReadError] Reading - detail - Operation canceled (Operation canceled)
[13:31:28.183] Connection::close
A tak wyglada log z tfsa skompilowanego w trybie debug.

i po chwili pelno
Code: 
[13:32:00.175] Protocol::onRecvMessage
[13:32:00.175] Protocol::onRecvMessage - decrypt
[13:32:00.376] Protocol::onRecvMessage
[13:32:00.376] Protocol::onRecvMessage - decrypt
[13:32:00.846] Protocol::onRecvMessage
[13:32:00.846] Protocol::onRecvMessage - decrypt
[13:32:00.899] Protocol::onRecvMessage
[13:32:00.899] Protocol::onRecvMessage - decrypt
[13:32:00.952] Protocol::onRecvMessage
[13:32:00.952] Protocol::onRecvMessage - decrypt
[13:32:01.006] Protocol::onRecvMessage
[13:32:01.006] Protocol::onRecvMessage - decrypt
[13:32:01.006] Protocol::onRecvMessage
[13:32:01.006] Protocol::onRecvMessage - decrypt
[13:32:01.059] Protocol::onRecvMessage
[13:32:01.059] Protocol::onRecvMessage - decrypt
[13:32:01.060] Protocol::onRecvMessage
[13:32:01.060] Protocol::onRecvMessage - decrypt
[13:32:01.113] Protocol::onRecvMessage
[13:32:01.114] Protocol::onRecvMessage - decrypt
[13:32:01.114] Protocol::onRecvMessage
[13:32:01.114] Protocol::onRecvMessage - decrypt
[13:32:01.166] Protocol::onRecvMessage
[13:32:01.166] Protocol::onRecvMessage - decrypt
[13:32:01.278] Protocol::onRecvMessage
[13:32:01.278] Protocol::onRecvMessage - decrypt
[13:32:01.482] Protocol::onRecvMessage
[13:32:01.482] Protocol::onRecvMessage - decrypt
[13:32:01.677] Protocol::onRecvMessage
[13:32:01.677] Protocol::onRecvMessage - decrypt
[13:32:01.851] Protocol::onRecvMessage
[13:32:01.851] Protocol::onRecvMessage - decrypt
[13:32:02.052] Protocol::onRecvMessage
[13:32:02.052] Protocol::onRecvMessage - decrypt

czasami potrafi tez sie zwiesic kompletnie
np:
[13:36:24.470] Sending message - ALL
[13:36:24.470] Connection::send init
[13:36:24.470] Protocol::onSendMessage
[13:36:24.470] Protocol::onSendMessage - encrypt
[13:36:24.470] Protocol::onSendMessage - crypto header
[13:36:24.470] Connection::send 342
[13:36:24.470] Sending message - ALL
[13:36:24.470] Connection::send init
onWrite
[13:36:24.470] Connection::send init
onWrite
[13:36:24.470] Protocol::onSendMessage
[13:36:24.470] Protocol::onSendMessage - encrypt
[13:36:24.470] Protocol::onSendMessage - crypto header
[13:36:24.470] Connection::send 22
Click to expand...

EDIT:
Zrobilem restart charow i nie zacina. Wracam do starej bazy - zacinka po 10 sek.


Kto pomoze? Jezeli nie za friko to prosze o pm i na pewno sie dogadamy.
 
Last edited:
Odpalam na starej bazie - zacinka po 10-20 sek.
Odpalam na pustej dziala ok.
Odpalam na bazie sprzed miesiaca - zacinka.
Wychodzi na to ze ktos ma bota na autologu i robi 'cos' po zalogowaniu - na psutej bazie sie nie zaloguje bo nie ma konta. Tylko co robi?
 
Back
Top