> Am 23.07.2017 um 18:02 schrieb Tom Browder :
>
>
> On Sat, Jul 22, 2017 at 07:00 Stefan Eissing
> wrote:
> Hey,
>
> the alpha version for Let's Encrypt (ACME) support for httpd can be found
> here: https://github.com/icing/mod_md
>
> I'd like to get early feedback and stabilize a tad more
Looking for ways to get the server make a graceful restart,
I learned that
a) this requires an OS specific implementation
(some code already there, e.g. Windows service restart)
b) is something that users might want to forbid or
delay to low traffic times/days.
So, while the imple
On 07/19/2017 04:56 AM, Yann Ylavic wrote:
The comment in proxy_fcgi says:
/* This scheme handler does not reuse connections by default, to
* avoid tying up a fastcgi that isn't expecting to work on
* parallel requests. But if the user went out of their way to
* type the
On 2017-07-24 13:29, Jacob Champion wrote:
> I have still not been able to reproduce the "messed up POSTs" that other
> people are reporting with UDS+enablereuse.
In my case it screwed up the POST request by not doing what should have
been done with the request. In the end the request was lost.
(
On 07/24/2017 10:40 AM, Helmut K. C. Tessarek wrote:
In my case it screwed up the POST request by not doing what should have
been done with the request. In the end the request was lost.
(due to timeout, not processing it, or for whatever reason)
Any chance this is because of the hang I mentioned
On 2017-07-24 13:42, Jacob Champion wrote:
> Any chance this is because of the hang I mentioned?
It could be, but this doesn't really change anything.
If the setting enablereuse can change the behaviour of web applications
and introduces hangs and timeouts, it is time to rethink the
implementatio
vOn 07/24/2017 11:34 AM, Helmut K. C. Tessarek wrote:
On 2017-07-24 13:42, Jacob Champion wrote:
Any chance this is because of the hang I mentioned?
It could be, but this doesn't really change anything.
We can't really help debug your problems very well if we can't reproduce
them. Knowing wh
On 2017-07-24 14:38, Jacob Champion wrote:
> We can't really help debug your problems very well if we can't reproduce
> them. Knowing whether this is the root cause or not is important, so we
> can decide what to do next.
Oh, sorry, no I meant the bigger picture, not this specific problem.
I can
On 07/24/2017 11:47 AM, Helmut K. C. Tessarek wrote:
I can try to reproduce it when I have set up a VM to run tests.
Unfortunately I currently do not have the time to do so. Maybe in a
few days.
Thanks! If this is the root cause of lost POSTs, then that'd be a good
reason to implement FCGI_GET
On Mon, Jul 24, 2017 at 7:29 PM, Jacob Champion wrote:
>
> I was able to reproduce a hang with PHP-FPM and enablereuse=on, but I
> don't think it's UDS-specific. (Haven't tried with TCP yet, though.)
>
> If the maximum number of connections opened by httpd to PHP-FPM exceeds
> the maximum number o
On 07/24/2017 12:39 PM, Yann Ylavic wrote:
Hmm, don't we close the backend connection (i.e. conn->close = 1)
whenever an error occurs in the fgci loop? What do you mean by
"queue up for later", by whom? Where do that coonection go on the
httpd side?
I mean that the FCGI application (PHP-FPM) h
On Mon, Jul 24, 2017 at 9:46 PM, Jacob Champion wrote:
> On 07/24/2017 12:39 PM, Yann Ylavic wrote:
>>
>> Hmm, don't we close the backend connection (i.e. conn->close = 1) whenever
>> an error occurs in the fgci loop? What do you mean by
>> "queue up for later", by whom? Where do that coonection g
Hello all,
currently 8 hours of testing without any issues.
@Stefan
i've most probably another issue with http2 where some elements of the
page are sometimes missing and the connection results in
ERR_CONNECTION_CLOSED after 60s. What kind of details do you need?
Greets,
Stefan
Am 22.07.2017 um 1
On 07/24/2017 01:03 PM, Yann Ylavic wrote:
What if the fpm queue in ap_proxy_connect_backend or at POLLOUT time?
If both cases I think the socket is not reused by mod_proxy_fcgi for
the next request, so I don't see how it's a enablereuse issue...
I'm not sure I understand your question, but I t
I have another report of request getting stuck, resulting in the error you
noticed. Will look tomorrow and report back here what I find.
> Am 24.07.2017 um 22:20 schrieb Stefan Priebe - Profihost AG
> :
>
> Hello all,
>
> currently 8 hours of testing without any issues.
>
> @Stefan
> i've mos
On Mon, Jul 24, 2017 at 10:44 PM, Jacob Champion wrote:
> On 07/24/2017 01:03 PM, Yann Ylavic wrote:
>>
>> What if the fpm queue in ap_proxy_connect_backend or at POLLOUT time?
>> If both cases I think the socket is not reused by mod_proxy_fcgi for
>> the next request, so I don't see how it's a en
On Tue, Jul 25, 2017 at 1:19 AM, wrote:
>
> New abort_socket_nonblocking() allows to reset connections when nonblocking is
> required and we can't do much about the connection anymore, nor want the
> system
> to linger on its own after close().
>
[]
>
> +static void abort_socket_nonblocking(apr_
Am 24.07.2017 um 23:06 schrieb Stefan Eissing:
> I have another report of request getting stuck, resulting in the error you
> noticed. Will look tomorrow and report back here what I find.
Thanks, if you need any logs. Pleae ask.
Stefan
>
>> Am 24.07.2017 um 22:20 schrieb Stefan Priebe - Profi
18 matches
Mail list logo
