On 09.03.09 17:47, Mohit Anchlia wrote:
That's what I thought but it doesn't behave that way. I see that it
still try to take in new sessions and sometimes it just hangs (or
becomes defunct process) even if there are no sessions in progress.
There's bug in apache which appears if more than one
Thanks ..we are indeed listening on 443 also. How do I tell the version apache?
On Tue, Mar 10, 2009 at 4:20 AM, Matus UHLAR - fantomas
uh...@fantomas.sk wrote:
On 09.03.09 17:47, Mohit Anchlia wrote:
That's what I thought but it doesn't behave that way. I see that it
still try to take in new
On Tue, Mar 10, 2009 at 4:20 AM, Matus UHLAR - fantomas
uh...@fantomas.sk wrote:
There's bug in apache which appears if more than one listening socket is
open. It should be fixed in 2.2.12, see bug 42829 at
https://issues.apache.org/bugzilla/show_bug.cgi?id=42829
On 09.03.09 17:47,
Ok ..so that's the reason why I started asking this question that if
it's possible to have apache listen on a socket and then later tell
apache to stop listening only on that port. But I guess that's not
possible.
On Tue, Mar 10, 2009 at 8:59 AM, Matus UHLAR - fantomas
uh...@fantomas.sk wrote:
Apache 2:
Is there a way to tell apache to listen on say port 9000 and then when
apache is up ask apache to stop listening on just port 9000? Which
means it will keep listening on port 80 or 443.
-
The official User-To-User
Mohit,
Short answer: no. You must define the Listen directives then start
apache. If you alter those, apache must be restarted.
Frank
Mohit Anchlia wrote:
Apache 2:
Is there a way to tell apache to listen on say port 9000 and then when
apache is up ask apache to stop listening on just port
Mohit Anchlia wrote:
Apache 2:
Is there a way to tell apache to listen on say port 9000 and then when
apache is up ask apache to stop listening on just port 9000? Which
means it will keep listening on port 80 or 443.
Curiosity : why ?
But can I tell apache to stop listening on only one port? So if apache
is listening on 80, 8080 then ask apache to stop listening on 8080
only.
On Mon, Mar 9, 2009 at 9:05 AM, Frank Gingras
francois.ging...@gmail.com wrote:
Mohit,
Short answer: no. You must define the Listen directives then
-573-1800x27
abia...@formatdynamics.com
http://www.formatdynamics.com
-Original Message-
From: Mohit Anchlia [mailto:mohitanch...@gmail.com]
Sent: Monday, March 09, 2009 11:13 AM
To: users@httpd.apache.org
Subject: Re: [us...@httpd] Ask apache to stop listening on only one socket
On 09.03.09 10:12, Mohit Anchlia wrote:
But can I tell apache to stop listening on only one port? So if apache
is listening on 80, 8080 then ask apache to stop listening on 8080
only.
The most important question you did not answer (or did I miss it?) was:
WHY?
--
Matus UHLAR - fantomas,
Mohit Anchlia wrote:
But can I tell apache to stop listening on only one port? So if apache
is listening on 80, 8080 then ask apache to stop listening on 8080
only.
No, not without restarting Apache.
But if you explained why you want to do that, then maybe we can provide
a better answer than
The problem is that we have F5 before webserver and we want a way to
remove that web server out of service without having to stop apache
and affecting existing connections. So only way is to have apache
listen on socket and F5 do a health check. Other way is using http,
which has more overhead.
On Mon, Mar 9, 2009 at 3:02 PM, Mohit Anchlia mohitanch...@gmail.com wrote:
The problem is that we have F5 before webserver and we want a way to
remove that web server out of service without having to stop apache
and affecting existing connections. So only way is to have apache
listen on
On Mon, Mar 9, 2009 at 3:02 PM, Mohit Anchlia mohitanch...@gmail.com wrote:
The problem is that we have F5 before webserver and we want a way to
remove that web server out of service without having to stop apache
and affecting existing connections. So only way is to have apache
listen on
On Mon, Mar 9, 2009 at 3:05 PM, Eric Covener cove...@gmail.com wrote:
graceful stop?
--
Eric Covener
cove...@gmail.com
Dammit, Eric. You beat me by 1 minute.
=J
-Brian
--
Feel free to contact me using PGP Encryption:
Key Id: 0x3AA70848
Available from: http://pgp.mit.edu/
graceful stop doesn't work ..I've tried multiple times. sometimes it
leaves a defunct process and other times it just hangs even though all
the existing requests have been processed.
On Mon, Mar 9, 2009 at 12:07 PM, Brian Mearns mearn...@gmail.com wrote:
On Mon, Mar 9, 2009 at 3:05 PM, Eric
Mohit,
With a graceful restart, any workers will stay alive until the KeepAlive
timeout is reached, at which point the process will be terminated. If
you want them to die faster, lower the KeepAlive value.
Frank.
Mohit Anchlia wrote:
graceful stop doesn't work ..I've tried multiple times.
apache to stop listening on only one
socket?
Mohit,
With a graceful restart, any workers will stay alive until the KeepAlive
timeout is reached, at which point the process will be terminated. If
you want them to die faster, lower the KeepAlive value.
Frank.
Mohit Anchlia wrote:
graceful stop
That's what I thought but it doesn't behave that way. I see that it
still try to take in new sessions and sometimes it just hangs (or
becomes defunct process) even if there are no sessions in progress.
On Mon, Mar 9, 2009 at 3:22 PM, Frank Gingras
francois.ging...@gmail.com wrote:
Mohit,
With
19 matches
Mail list logo
