I think the directives are similar for event and worker and any config changes
would not be too bad, but the worker documentation would give better info. To
switch I think you would load the worker module instead of event or recompile
with worker depending on how you are doing it.
Date: Tue, 2
I read that as well but the following statement he made did not make me feel
like it totally resolved the issue.
"However, what I did notice is that the same server periodically had all of its
workers taken up with requests, so that may be relevant to the problem as well."
If I did switch to "Wor
I don't know much on this, but for the bug link you included, one comment
mentioned it being a problem with event mpm, that went away when using worker
mpm. Is it possible to try the worker mpm?
Date: Mon, 1 Jun 2015 23:58:13 +
From: mark_jacq...@yahoo.com.INVALID
To: users@httpd.apache.org
Sorry for the bandwidth, this is a repeat send from January.We STILL have this
issue.
Perhaps a new look might jolt your memory and help me resolve this issue!!!
Problem: Apache server will stay up for random amount of time, usually days,
but eventually enters a hung state. When hung the CPU lo
Hi Kurtis,
It is a possibility I guess, but my timezone is EST.
Thanks,
Emir
On Mon, Jun 1, 2015 at 3:14 PM, Kurtis Rader wrote:
> On Mon, Jun 1, 2015 at 11:18 AM, Emir Ibrahimbegovic <
> emir.ibrahimbego...@gmail.com> wrote:
>>
>> You might also look for the string 786297600 somewhere in conf
On Mon, Jun 1, 2015 at 11:18 AM, Emir Ibrahimbegovic <
emir.ibrahimbego...@gmail.com> wrote:
>
> You might also look for the string 786297600 somewhere in configurations
> or your webapp, because that is the seconds since the epoch that would
> result in December 1st, 1994, 16:00 GMT. Is it always
One more thing,
You might also look for the string 786297600 somewhere in configurations or
your webapp, because that is the seconds since the epoch that would result
in December 1st, 1994, 16:00 GMT. Is it always exactly the same value? - Yes
it's always the same value
On Mon, Jun 1, 2015 at 2:0
Thanks Rainer for the tips. Here is the follow up.
1. Added ""%{Expires}o"" to logging valve pattern in the
server.xml, sets the correct headers expires on the webserver side, doesn't
set the 1994 year one. But still when I look at the browser, the double
header appear the one from 1994 and the o
On Mon, Jun 1, 2015 at 10:22 AM, Tom Browder wrote:
> Okay, here's what I had to do to my Linux Deb 7, 64-bit system:
...
> 2. Source packages used (in order of installation):
...
> pcre2-10.00.tar.bz2
Oops, my error: I had to use pcre-8.36 (httpd cannot yet use pcre2).
Best,
-Tom
-
On Wed, May 27, 2015 at 11:33 AM, Mario Brandt wrote:
> Hi Tom,
>
> I tried on Debian 7 and 8 both x64
>
> To see your configure options would help a lot.
Okay, here's what I had to do to my Linux Deb 7, 64-bit system:
1. Remove any deb packages of httpd, apr, apr-util, openssl.
2. Source pac
10 matches
Mail list logo
