Меню
Что нового?

Apache Segmentation Fault

Drakon

Drakon

Новичок
Периодически в логах апача отслеживаю сообщения типа:
Код: 
[Wed Feb 08 08:30:01 2012] [notice] caught SIGTERM, shutting down
[Wed Feb 08 08:30:04 2012] [notice] Apache/2.2.21 (Unix) Phusion_Passenger/3.0.2 configured -- resuming normal operations
[Wed Feb 08 08:33:11 2012] [error] [client 127.0.0.1] request failed: error reading the headers
[Wed Feb 08 08:33:55 2012] [error] [client 127.0.0.1] request failed: error reading the headers
[Wed Feb 08 08:35:46 2012] [error] [client 127.0.0.1] request failed: error reading the headers
[Wed Feb 08 08:36:26 2012] [error] [client 127.0.0.1] request failed: error reading the headers
[Wed Feb 08 08:36:27 2012] [error] [client 127.0.0.1] request failed: error reading the headers
[Wed Feb 08 08:37:54 2012] [error] [client 127.0.0.1] request failed: error reading the headers
[Wed Feb 08 08:37:55 2012] [error] [client 127.0.0.1] request failed: error reading the headers
[Wed Feb 08 08:37:58 2012] [error] [client 127.0.0.1] request failed: error reading the headers
[Wed Feb 08 08:41:25 2012] [error] [client 127.0.0.1] request failed: error reading the headers
[Wed Feb 08 08:41:31 2012] [error] [client 127.0.0.1] request failed: error reading the headers
[Wed Feb 08 08:41:58 2012] [error] [client 127.0.0.1] request failed: error reading the headers
[Wed Feb 08 08:42:23 2012] [error] [client 127.0.0.1] request failed: error reading the headers
[Wed Feb 08 08:42:23 2012] [error] [client 127.0.0.1] request failed: error reading the headers
[Wed Feb 08 08:42:49 2012] [error] [client 127.0.0.1] request failed: error reading the headers
[Wed Feb 08 08:42:59 2012] [error] [client 127.0.0.1] request failed: error reading the headers
[Wed Feb 08 08:44:03 2012] [error] [client 127.0.0.1] request failed: error reading the headers
[Wed Feb 08 08:44:48 2012] [error] [client 127.0.0.1] request failed: error reading the headers
[Wed Feb 08 08:44:50 2012] [error] [client 127.0.0.1] request failed: error reading the headers
[Wed Feb 08 08:45:25 2012] [error] [client 127.0.0.1] request failed: error reading the headers
[Wed Feb 08 08:45:28 2012] [error] [client 127.0.0.1] request failed: error reading the headers
[Wed Feb 08 08:45:37 2012] [error] [client 127.0.0.1] request failed: error reading the headers
[Wed Feb 08 08:46:11 2012] [error] [client 127.0.0.1] request failed: error reading the headers
[Wed Feb 08 08:46:52 2012] [error] [client 127.0.0.1] request failed: error reading the headers
[Wed Feb 08 08:47:40 2012] [error] [client 127.0.0.1] request failed: error reading the headers
[Wed Feb 08 08:47:40 2012] [error] [client 127.0.0.1] request failed: error reading the headers
[Wed Feb 08 08:48:41 2012] [error] [client 127.0.0.1] request failed: error reading the headers
[Wed Feb 08 08:49:16 2012] [error] [client 127.0.0.1] request failed: error reading the headers
[Wed Feb 08 08:49:22 2012] [error] [client 127.0.0.1] request failed: error reading the headers
[Wed Feb 08 08:50:04 2012] [error] [client 127.0.0.1] request failed: error reading the headers
[Wed Feb 08 08:50:11 2012] [error] [client 127.0.0.1] request failed: error reading the headers
[Wed Feb 08 08:50:41 2012] [error] [client 127.0.0.1] request failed: error reading the headers
[Wed Feb 08 08:50:53 2012] [error] [client 127.0.0.1] request failed: error reading the headers
[Wed Feb 08 08:51:19 2012] [error] [client 127.0.0.1] request failed: error reading the headers
[Wed Feb 08 08:51:19 2012] [error] [client 127.0.0.1] request failed: error reading the headers
[Wed Feb 08 08:51:19 2012] [error] [client 127.0.0.1] request failed: error reading the headers
[Wed Feb 08 08:51:39 2012] [error] [client 127.0.0.1] request failed: error reading the headers
[Wed Feb 08 08:52:02 2012] [error] [client 127.0.0.1] request failed: error reading the headers
[Wed Feb 08 08:52:11 2012] [error] [client 127.0.0.1] request failed: error reading the headers
[Wed Feb 08 08:52:50 2012] [error] [client 127.0.0.1] request failed: error reading the headers
[Wed Feb 08 08:53:22 2012] [error] [client 127.0.0.1] request failed: error reading the headers
[Wed Feb 08 08:53:46 2012] [error] [client 127.0.0.1] request failed: error reading the headers
[Wed Feb 08 08:54:18 2012] [error] [client 127.0.0.1] request failed: error reading the headers
[Wed Feb 08 08:54:19 2012] [error] [client 127.0.0.1] request failed: error reading the headers
[Wed Feb 08 08:54:31 2012] [error] [client 127.0.0.1] request failed: error reading the headers
[Wed Feb 08 08:54:37 2012] [error] [client 127.0.0.1] request failed: error reading the headers
[Wed Feb 08 08:54:55 2012] [error] [client 127.0.0.1] request failed: error reading the headers
[Wed Feb 08 08:56:16 2012] [error] [client 127.0.0.1] request failed: error reading the headers
[Wed Feb 08 08:56:40 2012] [error] [client 127.0.0.1] request failed: error reading the headers
[Wed Feb 08 08:57:27 2012] [error] [client 127.0.0.1] request failed: error reading the headers
[Wed Feb 08 08:57:33 2012] [error] [client 127.0.0.1] request failed: error reading the headers
[Wed Feb 08 08:57:45 2012] [error] [client 127.0.0.1] request failed: error reading the headers
[Wed Feb 08 08:57:46 2012] [error] [client 127.0.0.1] request failed: error reading the headers
[Wed Feb 08 08:57:51 2012] [error] [client 127.0.0.1] request failed: error reading the headers
[Wed Feb 08 08:57:53 2012] [error] [client 127.0.0.1] request failed: error reading the headers
[Wed Feb 08 08:58:06 2012] [error] [client 127.0.0.1] request failed: error reading the headers
[Wed Feb 08 08:58:32 2012] [error] [client 127.0.0.1] request failed: error reading the headers
[Wed Feb 08 08:58:57 2012] [error] [client 127.0.0.1] request failed: error reading the headers
[Wed Feb 08 08:59:45 2012] [error] [client 127.0.0.1] request failed: error reading the headers
[Wed Feb 08 08:59:59 2012] [error] [client 127.0.0.1] request failed: error reading the headers
[Wed Feb 08 09:00:06 2012] [error] [client 127.0.0.1] request failed: error reading the headers
[Wed Feb 08 09:00:28 2012] [error] [client 127.0.0.1] request failed: error reading the headers
[Wed Feb 08 09:00:28 2012] [error] [client 127.0.0.1] request failed: error reading the headers
[Wed Feb 08 09:00:44 2012] [error] [client 127.0.0.1] request failed: error reading the headers
[Wed Feb 08 09:00:56 2012] [error] [client 127.0.0.1] request failed: error reading the headers
[Wed Feb 08 09:01:10 2012] [error] [client 127.0.0.1] request failed: error reading the headers
[Wed Feb 08 09:01:43 2012] [error] [client 127.0.0.1] request failed: error reading the headers
[Wed Feb 08 09:04:27 2012] [error] [client 127.0.0.1] request failed: error reading the headers
[Wed Feb 08 09:04:36 2012] [error] [client 127.0.0.1] request failed: error reading the headers
[Wed Feb 08 09:05:01 2012] [error] [client 127.0.0.1] request failed: error reading the headers
[Wed Feb 08 09:06:15 2012] [error] [client 127.0.0.1] request failed: error reading the headers
[Wed Feb 08 09:07:01 2012] [error] [client 127.0.0.1] request failed: error reading the headers
[Wed Feb 08 09:07:45 2012] [error] [client 127.0.0.1] request failed: error reading the headers
[Wed Feb 08 09:17:15 2012] [error] [client 127.0.0.1] request failed: error reading the headers
Storing outgoing emails configuration in config/email.yml is deprecated. You should now store it in config/configuration.yml using the email_delivery setting.
[Wed Feb 08 09:33:10 2012] [error] [client 127.0.0.1] request failed: error reading the headers
[Wed Feb 08 12:41:39 2012] [error] [client 127.0.0.1] request failed: error reading the headers
[Wed Feb 08 13:48:02 2012] [notice] child pid 8034 exit signal Segmentation fault (11)
[Wed Feb 08 21:52:19 2012] [error] server reached MaxClients setting, consider raising the MaxClients setting
В 8:30 стоит утренняя перезагрузка, т. к. апач падает.
В 13:48 в данном случае произошёл segfault (но всего лишь на одном из процессов). В 21:52 упал сайт (т. е. nginx который проксирует ему запросы пишет всё время gateway timeout).
Т. е. судя по всему процессы зависают постепенно, при этом перестают обрабатывать запросы и остаются висеть.
Настройки (используется prefork MPM):
Код: 
StartServers 12
MinSpareServers 12
MaxSpareServers 48
MaxClients 48
Видимо когда число зависших процессов достигает 48, обработка запросов останавливается.

В это же время проскакивала ошибка PHP (но всего одна):
Код: 
MESSAGE: require_once() [function.require-once]: GC cache entry '/var/www/site/www/models/main.php' (dev=64769 ino=802012) was on gc-list for 3643 seconds
Как определить причину? Есть подозрение на APC, отключу пока его.
 
fixxxer

fixxxer

К.О.
Партнер клуба
версии то какие?

zend.enable_gc = off попробуй, если помогает и php не последний обновляйся, там фиксили
 
Drakon

Drakon

Новичок
apache 2.2.21-r1
php 5.3.9
apc 3.1.7 (был, пока не удалил вчера)

Сейчас попробую обновить PHP до версии 5.3.10 и вернуть APC.
 
fixxxer

fixxxer

К.О.
Партнер клуба
в 5.3.9 дырка, точнее ДЫРЕНЬ (вплоть до ремотного выполнения произвольного кода). обновляться надо в любом случае
 

Sad Spirit

мизантроп (Старожил PHPClub)
Команда форума
У меня тут Апач, оснащённый PHP с APC, начал с завидной регулярностью в кору падать. Оказалось, один одарённый боец выложил туда файлы похапэ с синтаксическими ошибками. После исправления ошибок падения закончились.
 
fixxxer

fixxxer

К.О.
Партнер клуба
Похапе с синтакс-еррорами на продакшене - это сильно! :)))
 
Drakon

Drakon

Новичок
Чего-та всё равно падает с APC... Без APC пока работает, подожду ещё несколько дней сколько протянет.
 
confguru

confguru

ExAdmin
Команда форума
У тебя nignx перед ним стоит? Если да то похоже что буферов для headers не хватает. Хотя там вроде другая ошибка
 
Drakon

Drakon

Новичок
Кстати вспомнил... Я же настройки nginx недавно крутил... Примерно после этого начало падать. Сейчас такие:
Код: 
output_buffers 1 64k;
postpone_output 1460;
client_header_buffer_size 64k;
large_client_header_buffers 4 32k;
Подожду пока. Если не будет падать, значит APC тупит.
 
Drakon

Drakon

Новичок
Без APC перестал падать, уже 4-ые сутки работает. Кто-нить знает что делать?

И ещё вопрос возник - заметил в логах такое:
Код: 
[Wed Feb 15 01:59:33 2012] [error] [client 79.174.68.42] client denied by server configuration: /usr/htdocs
[Wed Feb 15 04:52:01 2012] [error] [client 79.174.68.42] client denied by server configuration: /usr/htdocs
Как такое возможно, если запросы к апачу приходят только от nginx (все остальные ошибки в логах про IP 127.0.0.1)?
 
Войдите или зарегистрируйтесь для ответа.
Сверху