Your message dated Sat, 28 May 2016 15:26:34 +0200 (CEST)
with message-id <alpine.deb.2.11.1605281526100.9...@eru.sfritsch.de>
and subject line Re: Bug#573996: Lost recent reports in /var/log/apache2/ when
restarting with /etc/init.d/apache2 restart.
has caused the Debian Bug report #573996,
regarding Lost recent reports in /var/log/apache2/ when restarting with
/etc/init.d/apache2 restart.
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
573996: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=573996
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: apache2.2-common
Version: 2.2.9-10+lenny6
Severity: normal
0.) The server did not resposne http://... requests.
1.) ps showed 110 sleeping apache2 instances, no other anormalities (dmesg,
free, du etc.)
2.) I did a normal restart via /etc/init.d/apache2 restart.
3.) Everything is running ok now.
4.) I tryed to find out what happend, but the report files in
/var/log/apache2 were newly created after restart and not appended.
5.) Older files there (created by logrotate) still exists.
6.) I have no info about the state or content of these logfiles before restart.
7.) I didn't try something like sync before restarting apache2.
TIA!
Bernhard
-- Package-specific info:
List of /etc/apache2/mods-enabled/*.load:
actions alias auth_basic authn_alias authn_default authn_file
authnz_ldap authz_default authz_groupfile authz_host authz_user
autoindex cgi dav dav_fs dav_svn dir* env fcgid fwweb ldap mime
negotiation php5 proxy proxy_http python setenvif ssl status
userdir wsgi
(A * means that the .conf file for that module is not enabled in
/etc/apache2/mods-enabled/)
-- System Information:
Debian Release: 5.0.4
APT prefers proposed-updates
APT policy: (500, 'proposed-updates'), (500, 'stable')
Architecture: i386 (i686)
Kernel: Linux 2.6.25-2-686-bigmem (SMP w/8 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) (ignored: LC_ALL
set to de_DE.UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages apache2 depends on:
ii apache2-mpm-prefork 2.2.9-10+lenny6 Apache HTTP Server - traditional n
apache2 recommends no packages.
apache2 suggests no packages.
Versions of packages apache2.2-common depends on:
ii apache2-utils 2.2.9-10+lenny6 utility programs for webservers
ii libapr1 1.2.12-5+lenny1 The Apache Portable Runtime Librar
ii libaprutil1 1.2.12+dfsg-8+lenny4 The Apache Portable Runtime Utilit
ii libc6 2.7-18lenny2 GNU C Library: Shared libraries
ii libmagic1 4.26-1 File type determination library us
ii libssl0.9.8 0.9.8g-15+lenny6 SSL shared libraries
ii lsb-base 3.2-20 Linux Standard Base 3.2 init scrip
ii mime-support 3.44-1 MIME files 'mime.types' & 'mailcap
ii net-tools 1.60-22 The NET-3 networking toolkit
ii perl 5.10.0-19lenny2 Larry Wall's Practical Extraction
ii procps 1:3.2.7-11 /proc file system utilities
ii zlib1g 1:1.2.3.3.dfsg-12 compression library - runtime
-- no debconf information
--- End Message ---
--- Begin Message ---
No response in 6 years. Closing.
On Sat, 3 Apr 2010, Stefan Fritsch wrote:
> On Monday 15 March 2010, Bernhard Schiffner wrote:
> > Package: apache2.2-common
> > Version: 2.2.9-10+lenny6
> > Severity: normal
> >
> >
> > 0.) The server did not resposne http://... requests.
> > 1.) ps showed 110 sleeping apache2 instances, no other anormalities
> > (dmesg, free, du etc.)
> > 2.) I did a normal restart via /etc/init.d/apache2 restart.
> > 3.) Everything is running ok now.
> > 4.) I tryed to find out what happend, but the report files in
> > /var/log/apache2 were newly created after restart and not appended.
> > 5.) Older files there (created by logrotate) still exists.
> > 6.) I have no info about the state or content of these logfiles
> > before restart.
> > 7.) I didn't try something like sync before restarting apache2.
>
> Are you sure that the log files were still there before the restart?
> It seems more likely to me that logrotate rotated the logs away, but
> the graceful reload did not work because apache2 hung. Therefore new
> log files were not created.
>
> Of course there is still the question why apache2 hung in the first
> place. Has the problem occured again? Can you reproduce it? It would
> be nice to have a gdb backtrace of a hanging process. May the server-
> status page would also give some insight on which script caused the
> problem.
--- End Message ---
