[Sun Oct 29 04:03:14 2006] [notice] suEXEC mechanism enabled (wrapper: /usr/sbin/suexec)
[Sun Oct 29 04:03:14 2006] [notice] Accept mutex: sysvsem (Default: sysvsem)
что это???
| Версия для печати темы
Нажмите сюда для просмотра этой темы в оригинальном формате |
| Форум программистов > Администрирование Web серверов и Web служб > Специалисты по логам Apache, помогите |
| Автор: Vaulter 31.10.2006, 22:43 |
| [Sun Oct 29 04:03:14 2006] [notice] Apache configured -- resuming normal operations [Sun Oct 29 04:03:14 2006] [notice] suEXEC mechanism enabled (wrapper: /usr/sbin/suexec) [Sun Oct 29 04:03:14 2006] [notice] Accept mutex: sysvsem (Default: sysvsem) что это??? |
| Автор: Vaulter 31.10.2006, 23:10 |
| [Mon Oct 30 00:10:12 2006] [warn] child process 31611 did not exit, sending another SIGHUP [Mon Oct 30 00:10:12 2006] [warn] child process 31612 did not exit, sending another SIGHUP [Mon Oct 30 00:10:12 2006] [warn] child process 31615 did not exit, sending another SIGHUP [Mon Oct 30 00:10:12 2006] [warn] child process 31616 did not exit, sending another SIGHUP [Mon Oct 30 00:10:12 2006] [warn] child process 31617 did not exit, sending another SIGHUP [Mon Oct 30 00:10:12 2006] [warn] child process 31618 did not exit, sending another SIGHUP [Mon Oct 30 00:10:12 2006] [warn] child process 31621 did not exit, sending another SIGHUP [Mon Oct 30 00:10:12 2006] [warn] child process 31622 did not exit, sending another SIGHUP [Mon Oct 30 00:10:12 2006] [warn] child process 31623 did not exit, sending another SIGHUP [Mon Oct 30 00:10:12 2006] [warn] child process 31624 did not exit, sending another SIGHUP [Mon Oct 30 00:10:12 2006] [warn] child process 31625 did not exit, sending another SIGHUP [Mon Oct 30 00:10:12 2006] [warn] child process 31626 did not exit, sending another SIGHUP [Mon Oct 30 00:10:12 2006] [warn] child process 31627 did not exit, sending another SIGHUP [Mon Oct 30 00:10:12 2006] [warn] child process 31630 did not exit, sending another SIGHUP [Mon Oct 30 00:10:14 2006] [warn] child process 31133 still did not exit, sending a SIGTERM [Mon Oct 30 00:10:14 2006] [warn] child process 24965 still did not exit, sending a SIGTERM [Mon Oct 30 00:10:14 2006] [warn] child process 25266 still did not exit, sending a SIGTERM [Mon Oct 30 00:10:14 2006] [warn] child process 24640 still did not exit, sending a SIGTERM [Mon Oct 30 00:10:14 2006] [warn] child process 31328 still did not exit, sending a SIGTERM [Mon Oct 30 00:10:14 2006] [warn] child process 23803 still did not exit, sending a SIGTERM [Mon Oct 30 00:10:14 2006] [warn] child process 25499 still did not exit, sending a SIGTERM [Mon Oct 30 00:10:14 2006] [warn] child process 25249 still did not exit, sending a SIGTERM [Mon Oct 30 00:10:14 2006] [warn] child process 24873 still did not exit, sending a SIGTERM [Mon Oct 30 00:10:14 2006] [warn] child process 24941 still did not exit, sending a SIGTERM [Mon Oct 30 00:10:14 2006] [warn] child process 24754 still did not exit, sending a SIGTERM [Mon Oct 30 00:10:14 2006] [warn] child process 25011 still did not exit, sending a SIGTERM [Mon Oct 30 00:10:14 2006] [warn] child process 24966 still did not exit, sending a SIGTERM [Mon Oct 30 00:10:14 2006] [warn] child process 26406 still did not exit, sending a SIGTERM [Mon Oct 30 00:10:14 2006] [warn] child process 25508 still did not exit, sending a SIGTERM [Mon Oct 30 00:10:14 2006] [warn] child process 26895 still did not exit, sending a SIGTERM [Mon Oct 30 00:10:14 2006] [warn] child process 26364 still did not exit, sending a SIGTERM [Mon Oct 30 00:10:14 2006] [warn] child process 28043 still did not exit, sending a SIGTERM [Mon Oct 30 00:10:14 2006] [warn] child process 27315 still did not exit, sending a SIGTERM [Mon Oct 30 00:10:14 2006] [warn] child process 31329 still did not exit, sending a SIGTERM [Mon Oct 30 00:10:14 2006] [warn] child process 30659 still did not exit, sending a SIGTERM [Mon Oct 30 00:10:14 2006] [warn] child process 31572 still did not exit, sending a SIGTERM [Mon Oct 30 00:10:14 2006] [warn] child process 31601 still did not exit, sending a SIGTERM [Mon Oct 30 00:10:14 2006] [warn] child process 31602 still did not exit, sending a SIGTERM [Mon Oct 30 00:10:14 2006] [warn] child process 31603 still did not exit, sending a SIGTERM [Mon Oct 30 00:10:14 2006] [warn] child process 31605 still did not exit, sending a SIGTERM [Mon Oct 30 00:10:14 2006] [warn] child process 31610 still did not exit, sending a SIGTERM [Mon Oct 30 00:10:14 2006] [warn] child process 31611 still did not exit, sending a SIGTERM [Mon Oct 30 00:10:14 2006] [warn] child process 31612 still did not exit, sending a SIGTERM [Mon Oct 30 00:10:14 2006] [warn] child process 31615 still did not exit, sending a SIGTERM [Mon Oct 30 00:10:14 2006] [warn] child process 31616 still did not exit, sending a SIGTERM [Mon Oct 30 00:10:14 2006] [warn] child process 31617 still did not exit, sending a SIGTERM [Mon Oct 30 00:10:14 2006] [warn] child process 31618 still did not exit, sending a SIGTERM [Mon Oct 30 00:10:14 2006] [warn] child process 31621 still did not exit, sending a SIGTERM |
| Автор: JUmPER 1.11.2006, 10:44 |
| Vaulter 1) всё ок, нормально стартанул: сделал chuser через su, создал мьютекс 2) дочерний процесс уже отработал и "умер" до того, как ему был послан сигнал завершиться (судя по количеству это был остановлен сильно юзаемый сервер?) PS: можешь LogLevel поменять, чтоб всякий хлам в логи не сыпался |
| Автор: Vaulter 1.11.2006, 13:40 |
JUmPER, сервер сильно юзабельный и сдается мне, взломанный по самые нехочушки  вопрос вот такой еще (извиняюсь что в этой же теме) сейчас ситуация такова что логи ведутся для каждого вирт.хоста свои. и один access_log вечно почти пустой. вопрос: можно ли сделать "двойное" логирование: и целесообразно ли это? и вообще где толковая статья по настройке и обработке логов |
| Автор: JUmPER 2.11.2006, 09:11 |
| тут: http://httpd.apache.org/docs/1.3/mod/mod_log_config.html#customlog даже пример есть а по поводу целесообразности: это полезно при расследовании взломов скрипткиддсов (потому что умные почистят оба (3,4...) лога) |