Nie jesteś zalogowany.
Jeśli nie posiadasz konta, zarejestruj je już teraz! Pozwoli Ci ono w pełni korzystać z naszego serwisu. Spamerom dziękujemy!
Prosimy o pomoc dla małej Julki — przekaż 1% podatku na Fundacji Dzieciom zdazyć z Pomocą.
Więcej informacji na dug.net.pl/pomagamy/.
Witam,
Mam taki problem, testuję wydajność apache2 bo koledze wolno strona się ładuje. Znalazłem takie polecenie do testów
siege -b -c 100 -r 10 http://212.87.XX.XX/
Jeśli test puszczę raz wszystko jest super wydajność w 100% jeśli go puszczę kilka razy to wydajność mi spada do 60% i na ekranie pojawiają mi się takie błędy
[error] socket: unable to connect sock.c:222: No route to host [error] socket: unable to connect sock.c:222: No route to host HTTP/1.1 404 0.01 secs: 234 bytes ==> / [error] socket: unable to connect sock.c:222: No route to host [error] socket: unable to connect sock.c:222: No route to host [error] socket: unable to connect sock.c:222: No route to host [error] socket: unable to connect sock.c:222: No route to host [error] socket: unable to connect sock.c:222: No route to host [error] socket: unable to connect sock.c:222: No route to host [error] socket: unable to connect sock.c:222: No route to host HTTP/1.1 404 0.02 secs: 234 bytes ==> / HTTP/1.1 404 0.01 secs: 234 bytes ==> / [error] socket: unable to connect sock.c:222: No route to host [error] socket: unable to connect sock.c:222: No route to host [error] socket: unable to connect sock.c:222: No route to host [error] socket: unable to connect sock.c:222: No route to host [error] socket: unable to connect sock.c:222: No route to host HTTP/1.1 404 0.01 secs: 234 bytes ==> / [error] socket: unable to connect sock.c:222: No route to host HTTP/1.1 404 0.01 secs: 234 bytes ==> / [error] socket: unable to connect sock.c:222: No route to host HTTP/1.1 404 0.10 secs: 234 bytes ==> / [error] socket: unable to connect sock.c:222: No route to host [error] socket: unable to connect sock.c:222: No route to host [error] socket: unable to connect sock.c:222: No route to host HTTP/1.1 404 0.01 secs: 234 bytes ==> / [error] socket: unable to connect sock.c:222: No route to host [error] socket: unable to connect sock.c:222: No route to host [error] socket: unable to connect sock.c:222: No route to host [error] socket: unable to connect sock.c:222: No route to host [error] socket: unable to connect sock.c:222: No route to host HTTP/1.1 404 0.02 secs: 234 bytes ==> / [error] socket: unable to connect sock.c:222: No route to host [error] socket: unable to connect sock.c:222: No route to host HTTP/1.1 404 0.00 secs: 234 bytes ==> / [error] socket: unable to connect sock.c:222: No route to host [error] socket: unable to connect sock.c:222: No route to host HTTP/1.1 404 0.02 secs: 234 bytes ==> / [error] socket: unable to connect sock.c:222: No route to host HTTP/1.1 404 0.01 secs: 234 bytes ==> / [error] socket: unable to connect sock.c:222: No route to host [error] socket: unable to connect sock.c:222: No route to host [error] socket: unable to connect sock.c:222: No route to host [error] socket: unable to connect sock.c:222: No route to host HTTP/1.1 404 0.01 secs: 234 bytes ==> /
Wyłączyłem firewall bo myślałem , że to jego wina ale nadal to samo. Serwer to VPS w ovh, oni twierdzą, że to wina systemu. W logach nie mam żadnych błędów z tym związanych. I już nie wiem czy to ta aplikacja czy to naprawdę system.
Dzięki za pomoc i wskazówki
Offline