Проблемы с Nginx

Exillon
На сайте с 30.01.2008
Offline
94
11228

Добрый день.

Имеется достаточно загруженный мощный файловый сервер. в сутки около 35к пользователей. Плюс файлы грузят на большой скорости например в пики до 135мбит канала жрет, файлы размером от 100мб до 2000мб, большинство более 1гб.

Поэтому недавно после смены сервера на более мощный решил уже поставить на нжиникс. Прикрутил к нему пхп на фастСЖИ. Установил все летает. Но бывает такие моменты когда сайт раз и отрубается не грузит ничего а в еррор-логах пишет это код внизу, длится пару минут, потом нормально начинает работать. Нагрузки на машину нету смотрел все ок. Что бы это могло быть??

[error] 9640#0: *44118 kevent() reported about an closed connection (54: Connection reset by peer) while reading response header from upstream, client: 90.189.86.18, server

[error] 9640#0: *44119 writev() failed (54: Connection reset by peer) while sending request to upstream, client: 90.189.86.18, server: domain.com, request: "GET /img/rand_
[error] 9640#0: *42620 upstream timed out (60: Operation timed out) while reading response header from upstream, client: 89.113.208.163, server: domain.com, request: "GE
[error] 9641#0: *43656 kevent() reported about an closed connection (54: Connection reset by peer) while reading response header from upstream, client: 85.181.133.192, serv
[error] 9641#0: *39914 upstream timed out (60: Operation timed out) while reading response header from upstream, client: 89.232.197.225, server: domain.com, request: "GET
[error] 9641#0: *43655 kevent() reported about an closed connection (54: Connection reset by peer) while reading response header from upstream, client: 85.181.133.192, serv
[error] 9641#0: *43653 kevent() reported about an closed connection (54: Connection reset by peer) while reading response header from upstream, client: 85.181.133.192, serv
[error] 9641#0: *43654 kevent() reported about an closed connection (54: Connection reset by peer) while reading response header from upstream, client: 85.181.133.192, serv
[error] 9638#0: *42624 upstream timed out (60: Operation timed out) while reading response header from upstream, client: 81.1.252.1, server: domain.com, request: "GET /mov
[error] 9641#0: *39914 kevent() reported about an closed connection (54: Connection reset by peer) while reading response header from upstream, client: 89.232.197.225, serv
[error] 9639#0: *42628 upstream timed out (60: Operation timed out) while reading response header from upstream, client: 89.232.197.225, server: domain.com, request: "GET
[error] 9641#0: *39914 writev() failed (32: Broken pipe) while sending request to upstream, client: 89.232.197.225, server: domain.com, request: "GET /img/rand_logo.php?s=
[error] 9638#0: *42636 upstream timed out (60: Operation timed out) while reading response header from upstream, client: 93.100.241.148, server: domain.com, request: "GET /p
[error] 9638#0: *42639 upstream timed out (60: Operation timed out) while reading response header from upstream, client: 80.251.113.10, server: domain.com, request: "GET /
[error] 9638#0: *42640 upstream timed out (60: Operation timed out) while reading response header from upstream, client: 80.251.113.10, server: domain.com, request: "GET /
[error] 9639#0: *43572 kevent() reported about an closed connection (54: Connection reset by peer) while reading response header from upstream, client: 77.52.119.215, serve
[error] 9640#0: *41115 upstream timed out (60: Operation timed out) while reading response header from upstream, client: 93.81.187.189, server: domain.com, request: "GET /
[error] 9641#0: *44148 kevent() reported about an closed connection (54: Connection reset by peer) while reading response header from upstream, client: 83.102.161.100, serv
[error] 9640#0: *44149 kevent() reported about an closed connection (54: Connection reset by peer) while reading response header from upstream, client: 83.102.161.100, serv
[error] 9640#0: *43151 writev() failed (32: Broken pipe) while sending request to upstream, client: 94.51.75.189, server: domain.com, request: "GET /cat/ HTTP/1.1", upstre
[error] 9640#0: *44154 writev() failed (54: Connection reset by peer) while sending request to upstream, client: 92.253.31.61, server: domain.com, request: "GET /port.php?ID
[error] 9641#0: *44156 kevent() reported about an closed connection (54: Connection reset by peer) while reading response header from upstream, client: 84.42.8.173, server:
[error] 9641#0: *44148 writev() failed (54: Connection reset by peer) while sending request to upstream, client: 83.102.161.100, server: domain.com, request: "GET /img/ran
[error] 9640#0: *44149 writev() failed (32: Broken pipe) while sending request to upstream, client: 83.102.161.100, server: domain.com, request: "GET /img/rand_logo.php?s=
[error] 9641#0: *44157 kevent() reported about an closed connection (54: Connection reset by peer) while reading response header from upstream, client: 84.42.8.173, server:
[error] 9639#0: *44163 kevent() reported about an closed connection (54: Connection reset by peer) while reading response header from upstream, client: 62.221.38.93, server
[error] 9641#0: *44148 writev() failed (54: Connection reset by peer) while sending request to upstream, client: 83.102.161.100, server: domain.com, request: "GET /img/ran
[error] 9640#0: *44176 kevent() reported that connect() failed (54: Connection reset by peer) while connecting to upstream, client: 89.218.65.106, server: domain.com, requ
[error] 9640#0: *44177 writev() failed (54: Connection reset by peer) while sending request to upstream, client: 89.218.65.106, server: domain.com, request: "GET /img/rand
[error] 9640#0: *42660 upstream timed out (60: Operation timed out) while reading response header from upstream, client: 195.189.108.66, server: domain.com, request: "GET
[error] 9641#0: *42663 upstream timed out (60: Operation timed out) while reading response header from upstream, client: 195.189.108.66, server: domain.com, request: "GET
[error] 9641#0: *42665 upstream timed out (60: Operation timed out) while reading response header from upstream, client: 195.189.108.66, server: domain.com, request: "GET
[error] 9641#0: *42668 upstream timed out (60: Operation timed out) while reading response header from upstream, client: 195.189.108.66, server: domain.com, request: "GET
[error] 9640#0: *42679 upstream timed out (60: Operation timed out) while reading response header from upstream, client: 79.223.184.254, server: domain.com, request: "GE
[error] 9638#0: *42699 upstream timed out (60: Operation timed out) while reading response header from upstream, client: 90.188.34.97, server: domain.com, request: "GET /l
[error] 9638#0: *42696 upstream timed out (60: Operation timed out) while reading response header from upstream, client: 92.112.231.232, server: domain.com, request: "GET
[error] 9638#0: *42697 upstream timed out (60: Operation timed out) while reading response header from upstream, client: 92.112.231.232, server: domain.com, request: "GET
[error] 9640#0: *42713 upstream timed out (60: Operation timed out) while reading response header from upstream, client: 92.113.138.77, server: domain.com, request: "GET /
[error] 9638#0: *41679 upstream timed out (60: Operation timed out) while reading response header from upstream, client: 92.47.223.164, server: domain.com, request: "POST

И еще помогите пожалуйста оптимально настроить конфиг нжиникса под мои требования, и под нагрузки.

вот то что настроено сейчас:

user nobody nobody;

worker_processes 4;

error_log logs/error.log warn;

pid logs/nginx.pid;

events {
worker_connections 4096;
use kqueue;
}


http {
include mime.types;
default_type application/octet-stream;

log_format main '$remote_addr - $remote_user [$time_local] $request '
'"$status" $body_bytes_sent "$http_referer" ';

access_log logs/access.log main;

sendfile on;
tcp_nopush on;
tcp_nodelay on;

client_header_timeout 3m;
client_body_timeout 3m;
send_timeout 3m;

client_header_buffer_size 1k;
large_client_header_buffers 4 4k;

keepalive_timeout 40;
server_names_hash_max_size 2048;
server_names_hash_bucket_size 128;

Информация о машине

ОС ФриБСД 7

2 квард кора ксеона четырех ядерника 2,5гц

8Гб оперативка

массив жестких 16 дисков по 1тб

Буду очень признателен за любую помощь. Спасибо.

Перехват доменов с ТИЦ и PR, Списки дроп доменов. (https://dropwind.com/exp_domains) Регистрация доменов net-7.66$, com-8.30$, org-5.99. Хостинг от 1.24$. (https://dropwind.com/) wm BL 750+
O
На сайте с 13.08.2008
Offline
26
#1

С хорошей долей вероятности вам не хватает fastcgi-процессов.

Надо параллелиться.

Outsourcenow.ru: оттюним ваш веб-сервер. 100 млн. запросов в сутки - наш размерчик!
RAS
На сайте с 27.11.2005
Offline
126
RAS
#2

Скрипты как быстро выполняются ? И не подвисают ли они ?

Администрируем сервера, впс, вдс. Ускоряем загрузку сайтов - DLE, Word Press, Joomla, Modx... Настраиваем безопасность. Ручная чистка rootkit/malware/вирусов. (/ru/forum/867860) Разработка - shell/bash/sh/python/perl.
Exillon
На сайте с 30.01.2008
Offline
94
#3
RAS:
Скрипты как быстро выполняются ? И не подвисают ли они ?

Да нет при нормальной работе все шустро работает, но бывали моменты когда сервер просто затухал и не отвечал, через пару минут проходило, а в логе те ошибки, которые я описал. Хотя сейчас вот вроде товарищ Outsourcenow посоветовал детей пхп увеличить вроде пока помогло, но все равно как то все не стабильно, вчера ночью например по неизвестным причинам сервер упал, в логах ничего такого подозрительного не нашел.

Exillon добавил 08.10.2008 в 11:49

А вообще старые ошибки пропали, иногда вот только такие проскакивают.

[error] 968#0: accept() failed (53: Software caused connection abort) while accepting new connection on 0.0.0.0:80

[error] 973#0: *375644 upstream timed out (60: Operation timed out) while reading response header from upstream, client: 91.124.242.122, server: domain.com, request: "POST /
N
На сайте с 06.05.2007
Offline
419
#4

Exillon, вы читали их faq ? http://sysoev.ru/nginx/docs/faq.html.

там всего один вопрос и он именно ваш.

это фигня, по сути не ошибка даже.

Кнопка вызова админа ()
Andreyka
На сайте с 19.02.2005
Offline
822
#5

фастцги как апстримы - один упал, так второй ответит

Не стоит плодить сущности без необходимости

Авторизуйтесь или зарегистрируйтесь, чтобы оставить комментарий