2024-03-21 13:12 skrev Yaroslav Halchenko:
FWIW here is a dirty workaround script I just crafted with chatgpt to
monitor/restart apache2 as soon as it starts happening
My workaround is simpler, I have this line in root's crontab:
5 * * * * curl --silent --max-time 5 --output /dev/null
"All ingenious is simple" -- thanks for sharing. I might redo following
your example but to check more frequently.
On Thu, 21 Mar 2024, Peter Krefting wrote:
> My workaround is simpler, I have this line in root's crontab:
> 5 * * * * curl --silent --max-time 5 --output /dev/null
>
I think "my" https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067104
is a duplicate of this one. I blame mod_wsgi since this I believe
started to happen after I started to use it.
FWIW here is a dirty workaround script I just crafted with chatgpt to
monitor/restart apache2 as soon as it starts
Am 18.03.24 um 13:59 schrieb Yaroslav Halchenko:
Package: apache2
Version: 2.4.57-2
Severity: important
Server was working just fine for years and recently started to stall
completely after 3-7 days of functioning normally. error logs get filled up
first with AH03490 and then eventually with
Processing commands for cont...@bugs.debian.org:
> tags 1032628 + pending
Bug #1032628 [libapache2-mod-proxy-uwsgi] please drop transitional package
libapache2-mod-proxy-uwsgi from src:apache2
Added tag(s) pending.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
5 matches
Mail list logo
