[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#326174: marked as done (Heavy harddisc access when i did the following..)

Your message dated Sat, 14 Jul 2007 11:07:20 +0200
with message-id <200707141107.20179.sf@sfritsch.de>
and subject line bug #326174: apache2 going berserk after changing configuration from 1 to 2 listening sockets and back
has caused the attached Bug report 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 I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message --- 
Package: apache2
Version: 2.0.54-4

Application used:
apache2 2.0.54-4 (default installation setting)
mozilla-firefox 1.0.4-2sarge2

Step by step to produce the bug (if it's a bug):
Open Firefox
Go to localhost (display Apache default page)
Go to localhost:443 (connection refused)
Append this line "Listen 443" to "/etc/apache2/ports.conf"
as root, execute /usr/sbin/apache2ctl graceful
Go to url localhost:443 (display Apache default page)
Delete this line "Listen 443" in "/etc/apache2/ports.conf"
as root, execute /usr/sbin/apache2ctl graceful
Go to url localhost:443 (display Apache default page)

Problem:
After doing the above steps, there was a heavy harddisc access, non
stop. I had to hardware shutdown/restart the system. Could produce the
problem twice using the same steps


__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com

--- End Message ---
--- Begin Message --- 
Version: 2.2.4-1

This is likely http://issues.apache.org/bugzilla/show_bug.cgi?id=37680 
and was fixed in 2.2.4. If you encounter this bug again with that 
version, feel free to reopen the bug report.

--- End Message ---
Reply to: