On 12/12/2022 11:32 am, Jason wrote:
https://serverfault.com/questions/1058677/apache-2-4-37-reload-causes-error-scoreboard-is-full-not-at-maxrequestworkers
and
https://serverfault.com/questions/1084635/apache-mpm-workers-stuck-in-g-gracefully-finishing-growing-scoreboard-is-fu
seems reloadi
https://serverfault.com/questions/1058677/apache-2-4-37-reload-causes-error-scoreboard-is-full-not-at-maxrequestworkers
and
https://serverfault.com/questions/1084635/apache-mpm-workers-stuck-in-g-gracefully-finishing-growing-scoreboard-is-fu
seems reloading is problematic because
>When you g
On 12/12/2022 1:33 am, Jason wrote:
AFAIK, restarting apache process on deployment is standard, is there a
reason you don't want to do that?
With Ubuntu 2020.04 and the version of Apache which came with that,
reload worked fine and I always thought that was the right way to redeploy.
The new
AFAIK, restarting apache process on deployment is standard, is there a
reason you don't want to do that?
Templates are picked up because they're not evaluated and compiled, rather
they're processed dynamically so any changes there do not require a restart.
On Saturday, December 10, 2022 at 9:34
Server Version: Apache/2.4.52 (Ubuntu 2022.04) OpenSSL/3.0.2
mod_wsgi/4.9.0 Python/3.10
Server MPM: event
Server Built: 2022-09-30T04:09:50
Apache *seems* to hang onto something and eventually crashes after I
reload it after deploying a Python file.
That is either scripted (delete site and re
5 matches
Mail list logo
