We identified the problem which is neither a apache bug nor an issue
after the security update. The problem was a misconfigured logrotate
which leads to this behaviour.
** Changed in: apache2 (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of
** Description changed:
Hi there,
currently we are using apache with the mod_proxy_balancer module to lead
HTTP requests to tomcat backend server.
Since a security patch on 10th of March (Ubuntu Security Notice
USN-2523-1), the apache stops working randomly. The error.log shows on
** Description changed:
- Hallo,
+ Hi there,
- wir betreiben den apache mit mod_proxy_balancer und leiten unsere Http-
- Requests an Tomcat Applicationserver weiter. Seit dem Security-Update
- vom 10.03. (Ubuntu Security Notice USN-2523-1) haben wir das Problem,
- dass unser Apache nach einer W
** Summary changed:
- Apache Crash nach Security-Update
+ Apache Crash after Security-Update
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to apache2 in Ubuntu.
https://bugs.launchpad.net/bugs/1432571
Title:
Apache Crash after Securi
** Summary changed:
- random apache crash - configuration failed exiting
+ Apache Crash nach Security-Update
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to apache2 in Ubuntu.
https://bugs.launchpad.net/bugs/1432571
Title:
Apache Cr
Public bug reported:
Hallo,
wir betreiben den apache mit mod_proxy_balancer und leiten unsere Http-
Requests an Tomcat Applicationserver weiter. Seit dem Security-Update
vom 10.03. (Ubuntu Security Notice USN-2523-1) haben wir das Problem,
dass unser Apache nach einer Weile stoppt. Das Error-Log
