I have the same problem. The system is up to date and I do not have any
wireless connection.
--
I cannot connect to any server. Conection hangs up at "channel 0: open confirm
rwindow 0 rmax 32768"
https://bugs.launchpad.net/bugs/237894
You received this bug notification because you are a member
This behavior is because in 2.0, proxy.load and proxy.conf contained the
"LoadModule disk_cache_module" and the mod_disk_cache config. Not
enabling mod_disk_cache on upgrades would break caching for proxies
(debian bug 407171).
Maybe enabling mod_disk_cache on upgrades only if something like
egre
fixed in 2.2.9, which has been uploaded to Debian
--
CVE-2008-2364 Apache2 mod_proxy_http.c DOS
https://bugs.launchpad.net/bugs/239894
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to apache2 in ubuntu.
--
Ubuntu-server-bugs mailing list
It is normal behavior that the apache processes stay around until they
have finished processing the currently active requests (since we are
using graceful-stop). Normally you should just be able to start apache
again even before all processes are dead. Is this not the case for you?
What error messa
It would also be interesting to know what apache modules you have
enabled and how the output of top looks just before the OOM situation
(i.e. are there many large apache2 processes or only a few very large
ones?).
You could also try tweaking "memory_limit" in your php.ini.
--
Apache 2 produces a
2.2.8-4 with the patch has just been uploaded to Debian
--
[SRU] memory leaks in apache2 when running mod_ssl
https://bugs.launchpad.net/bugs/224945
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to apache2 in ubuntu.
--
Ubuntu-server-bugs
This happens when the old apache is restarted when libaprutil1 has
already been upgraded. It is fixed as soon as apache is upgraded, too.
Probably the new libaprutil1 should conflict with the old
apache2.2-common.
--
apache2 crashed with SIGSEGV
https://bugs.launchpad.net/bugs/221457
You received
This is a bug in apache2.2-common's postinst (doesn't check for dangling
symlinks). The fix will be in 2.2.8-4:
http://svn.debian.org/wsvn/pkg-
apache/trunk/apache2/apache2.2-common.postinst?op=diff&rev=658&sc=1
--
package apache2.2-common 2.2.8-1 failed to install/upgrade:
https://bugs.launchp
