You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@httpd.apache.org by Mike Dewhirst <mi...@dewhirst.com.au> on 2005/08/08 03:23:20 UTC
[users@httpd] Access log stops - might be a mod_python symptom
My Apache2.0.53-5.1 on SuSE 9.1 has stopped logging accesses. Can anyone
help please? (TIA)
Apache is running fine for my Subversion repositories which are also
being accessed by other people.
It happened on 25 July which I think is contemporaneous with my attempts
to include mod_python. Joshua suggested I set the CoreDumpDirectory in
httpd.conf to catch a bug because including mod_python in the list
clobbered Subversion and Apache's children threw tantrums. As it
happened time escaped me; I needed Subversion so I removed mod_python
and put repositories back on-line.
Including CoreDumpDirectory (/var/log/Apache2/ set to wwwrun and www
group and user) didn't collect any info. That directory remains empty to
this day.
Today when I discovered that the access log had stopped (error log is
OK) I removed the CoreDumpDirectory directive and restarted Apache,
access Subversion from a remote machine and checked to find no access
entries.
I stopped Apache, deleted access_log and tried again but it would not
even recreate the access log.
I stopped the machine and restarted with the same results.
Thank you for any help - more detail below.
Mike
Here are my existing (since 24 July) modules ...
# 05410 added dav, dav_svn and authz_svn
# 05724 removed last module in list - php4
# 05724 apppended python - prevented subversion from working
# 05724 removed python - subversion now working
APACHE_MODULES="access actions alias auth auth_dbm autoindex cgi dav
dav_svn authz_svn dir env expires include log_config mime negotiation
setenvif ssl userdir"
Here is the last set of accesses in access_log before it goes silent ...
192.168.0.37 - miked [25/Jul/2005:23:36:36 -0700] "PROPFIND
/repos/xfiles/xwiz/wip95 HTTP/1.1" 207 704 "-" "SVN/1.1.4 (r13838)
neon/0.24.7"
192.168.0.37 - miked [25/Jul/2005:23:36:37 -0700] "PROPFIND
/repos/xfiles/!svn/vcc/default HTTP/1.1" 207 408 "-" "SVN/1.1.4 (r13838)
neon/0.24.7"
192.168.0.37 - miked [25/Jul/2005:23:36:37 -0700] "PROPFIND
/repos/xfiles/!svn/bln/194 HTTP/1.1" 207 463 "-" "SVN/1.1.4 (r13838)
neon/0.24.7"
192.168.0.37 - miked [25/Jul/2005:23:36:38 -0700] "PROPFIND
/repos/xfiles/xwiz/wip95 HTTP/1.1" 207 704 "-" "SVN/1.1.4 (r13838)
neon/0.24.7"
192.168.0.37 - miked [25/Jul/2005:23:36:38 -0700] "REPORT
/repos/xfiles/!svn/vcc/default HTTP/1.1" 200 643 "-" "SVN/1.1.4 (r13838)
neon/0.24.7"
-0700 means my SuSE box had a dud time setting because Melbourne
Australia should be -1000 but hey ... that should made local time around
16:36. It is now fixed and showing the correct time.
Here is the complete error log from a few entries before the above
guessed 16:36 time to the end of the day (sorry for the bandwidth
consumption) ...
[Mon Jul 25 15:16:13 2005] [notice] caught SIGTERM, shutting down
[Mon Jul 25 15:25:48 2005] [warn] Init: Session Cache is not configured
[hint: SSLSessionCache]
[Mon Jul 25 15:25:48 2005] [notice] suEXEC mechanism enabled (wrapper:
/usr/sbin/suexec2)
[Mon Jul 25 15:25:48 2005] [notice] mod_python: Creating 32 session
mutexes based on 150 max processes and 0 max threads.
[Mon Jul 25 15:25:48 2005] [notice] Apache/2.0.53 (Linux/SUSE)
configured -- resuming normal operations
[Mon Jul 25 15:32:19 2005] [notice] child pid 3102 exit signal
Segmentation fault (11)
[Mon Jul 25 15:32:32 2005] [notice] child pid 3103 exit signal
Segmentation fault (11)
[Mon Jul 25 15:42:32 2005] [notice] child pid 3104 exit signal
Segmentation fault (11)
# assuming the access log was working prior to this ... hour or so gap
[Mon Jul 25 17:26:31 2005] [notice] child pid 3105 exit signal
Segmentation fault (11)
[Mon Jul 25 17:54:46 2005] [notice] child pid 3106 exit signal
Segmentation fault (11)
[Mon Jul 25 17:58:53 2005] [warn] child process 3797 still did not exit,
sending a SIGTERM
[Mon Jul 25 17:58:53 2005] [warn] child process 3940 still did not exit,
sending a SIGTERM
[Mon Jul 25 17:58:53 2005] [warn] child process 4120 still did not exit,
sending a SIGTERM
[Mon Jul 25 17:58:53 2005] [warn] child process 4157 still did not exit,
sending a SIGTERM
[Mon Jul 25 17:58:53 2005] [warn] child process 3784 still did not exit,
sending a SIGTERM
[Mon Jul 25 17:58:53 2005] [warn] child process 3797 still did not exit,
sending a SIGTERM
[Mon Jul 25 17:58:53 2005] [warn] child process 3940 still did not exit,
sending a SIGTERM
[Mon Jul 25 17:58:53 2005] [warn] child process 4120 still did not exit,
sending a SIGTERM
[Mon Jul 25 17:58:53 2005] [warn] child process 4157 still did not exit,
sending a SIGTERM
[Mon Jul 25 17:58:53 2005] [warn] child process 3784 still did not exit,
sending a SIGTERM
[Mon Jul 25 17:58:54 2005] [warn] child process 3797 still did not exit,
sending a SIGTERM
[Mon Jul 25 17:58:54 2005] [warn] child process 3940 still did not exit,
sending a SIGTERM
[Mon Jul 25 17:58:54 2005] [warn] child process 4120 still did not exit,
sending a SIGTERM
[Mon Jul 25 17:58:54 2005] [warn] child process 4157 still did not exit,
sending a SIGTERM
[Mon Jul 25 17:58:54 2005] [warn] child process 3784 still did not exit,
sending a SIGTERM
[Mon Jul 25 17:58:59 2005] [notice] caught SIGTERM, shutting down
[Mon Jul 25 18:00:31 2005] [warn] Init: Session Cache is not configured
[hint: SSLSessionCache]
[Mon Jul 25 18:00:32 2005] [notice] Apache/2.0.53 (Linux/SUSE)
configured -- resuming normal operations
[Mon Jul 25 18:42:20 2005] [notice] caught SIGTERM, shutting down
[Mon Jul 25 18:43:46 2005] [warn] Init: Session Cache is not configured
[hint: SSLSessionCache]
[Mon Jul 25 18:43:46 2005] [notice] mod_python: Creating 32 session
mutexes based on 150 max processes and 0 max threads.
[Mon Jul 25 18:43:47 2005] [notice] Apache/2.0.53 (Linux/SUSE)
configured -- resuming normal operations
[Mon Jul 25 18:50:25 2005] [notice] child pid 3099 exit signal
Segmentation fault (11)
[Mon Jul 25 19:00:40 2005] [notice] child pid 3100 exit signal
Segmentation fault (11)
[Mon Jul 25 19:02:22 2005] [warn] child process 3840 still did not exit,
sending a SIGTERM
[Mon Jul 25 19:02:22 2005] [warn] child process 3101 still did not exit,
sending a SIGTERM
[Mon Jul 25 19:02:22 2005] [warn] child process 3102 still did not exit,
sending a SIGTERM
[Mon Jul 25 19:02:22 2005] [warn] child process 3103 still did not exit,
sending a SIGTERM
[Mon Jul 25 19:02:22 2005] [warn] child process 3771 still did not exit,
sending a SIGTERM
[Mon Jul 25 19:02:23 2005] [warn] child process 3840 still did not exit,
sending a SIGTERM
[Mon Jul 25 19:02:23 2005] [warn] child process 3101 still did not exit,
sending a SIGTERM
[Mon Jul 25 19:02:23 2005] [warn] child process 3102 still did not exit,
sending a SIGTERM
[Mon Jul 25 19:02:23 2005] [warn] child process 3103 still did not exit,
sending a SIGTERM
[Mon Jul 25 19:02:23 2005] [warn] child process 3771 still did not exit,
sending a SIGTERM
[Mon Jul 25 19:02:24 2005] [warn] child process 3840 still did not exit,
sending a SIGTERM
[Mon Jul 25 19:02:24 2005] [warn] child process 3101 still did not exit,
sending a SIGTERM
[Mon Jul 25 19:02:24 2005] [warn] child process 3102 still did not exit,
sending a SIGTERM
[Mon Jul 25 19:02:24 2005] [warn] child process 3103 still did not exit,
sending a SIGTERM
[Mon Jul 25 19:02:24 2005] [warn] child process 3771 still did not exit,
sending a SIGTERM
[Mon Jul 25 19:02:28 2005] [notice] caught SIGTERM, shutting down
[Mon Jul 25 19:03:52 2005] [warn] Init: Session Cache is not configured
[hint: SSLSessionCache]
[Mon Jul 25 19:03:53 2005] [notice] Apache/2.0.53 (Linux/SUSE)
configured -- resuming normal operations
[Mon Jul 25 20:08:37 2005] [notice] caught SIGTERM, shutting down
[Mon Jul 25 23:35:54 2005] [notice] Apache/2.0.53 (Linux/SUSE)
configured -- resuming normal operations
[Mon Jul 25 23:40:08 2005] [notice] caught SIGTERM, shutting down
[Mon Jul 25 23:41:36 2005] [notice] Apache/2.0.53 (Linux/SUSE)
configured -- resuming normal operations
Next entry was Tuesday morning after breakfast
---------------------------------------------------------------------
The official User-To-User support forum of the Apache HTTP Server Project.
See <URL:http://httpd.apache.org/userslist.html> for more info.
To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
" from the digest: users-digest-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org
Re: [users@httpd] Access log stops [Thanks]
Posted by Mike Dewhirst <mi...@dewhirst.com.au>.
Joshua Slive wrote:
> On 8/7/05, Mike Dewhirst <mi...@dewhirst.com.au> wrote:
>
>>Including CoreDumpDirectory (/var/log/Apache2/ set to wwwrun and www
>>group and user) didn't collect any info. That directory remains empty to
>>this day.
>
>
> You need to set ulimit and possibly kernel parameters to make sure
> that the user running apache (generally root) can dump core.
>
>
>
>>Here is the last set of accesses in access_log before it goes silent ...
>
>
> I have never heard of any bug in apache that would cause access logs
> not to be written. The most likely cause is a bad configuration.
> Check your CustomLog directives.
Spot on. access_log has restarted.
I (or Kate or Kwrite) had inadvertently inserted a carriage-return in
the conf file at that point. I went through everything and found a few
more word-wrapped lines with hard returns and fixed them.
I'm about to retry mod_python
Thanks heaps
mike
---------------------------------------------------------------------
The official User-To-User support forum of the Apache HTTP Server Project.
See <URL:http://httpd.apache.org/userslist.html> for more info.
To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
" from the digest: users-digest-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org
Re: [users@httpd] Access log stops - might be a mod_python symptom
Posted by Joshua Slive <js...@gmail.com>.
On 8/7/05, Mike Dewhirst <mi...@dewhirst.com.au> wrote:
> Including CoreDumpDirectory (/var/log/Apache2/ set to wwwrun and www
> group and user) didn't collect any info. That directory remains empty to
> this day.
You need to set ulimit and possibly kernel parameters to make sure
that the user running apache (generally root) can dump core.
> Here is the last set of accesses in access_log before it goes silent ...
I have never heard of any bug in apache that would cause access logs
not to be written. The most likely cause is a bad configuration.
Check your CustomLog directives.
Joshua.
---------------------------------------------------------------------
The official User-To-User support forum of the Apache HTTP Server Project.
See <URL:http://httpd.apache.org/userslist.html> for more info.
To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
" from the digest: users-digest-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org