Re: [users@httpd] Re: Cron job for Apache managed Letsencrypt TLS certs

2023-03-24 Thread Sean Conner
It was thus said that the Great Ruben Safir once stated: > On 3/24/23 20:53, Sean Conner wrote: > > /usr/local/apache2/bin/apachectl graceful > > that might not work if systemd is superving systemd is not supervising on my server, which is why I'm using apachectl. -spc

Re: [users@httpd] Re: Cron job for Apache managed Letsencrypt TLS certs

2023-03-24 Thread Tom Browder
On Fri, Mar 24, 2023 at 20:26 Ruben Safir wrote: > On 3/24/23 20:53, Sean Conner wrote: > > /usr/local/apache2/bin/apachectl graceful > > that might not work if systemd is superving What would you recommend? -Tom

Re: [users@httpd] Re: Cron job for Apache managed Letsencrypt TLS certs

2023-03-24 Thread Ruben Safir
On 3/24/23 20:53, Sean Conner wrote: > /usr/local/apache2/bin/apachectl graceful that might not work if systemd is superving -- So many immigrant groups have swept through our town that Brooklyn, like Atlantis, reaches mythological proportions in the mind of the world - RI Safir 1998 http://ww

Re: [users@httpd] Re: Cron job for Apache managed Letsencrypt TLS certs

2023-03-24 Thread Sean Conner
It was thus said that the Great Tom Browder once stated: > On Fri, Mar 24, 2023 at 12:23 Tom Browder wrote: > > > I have all my websites using Apache's managed certs. Up to now I have been > > restarting them periodically manually as root executing "apachectl > > graceful" and then checking to se

[users@httpd] Re: Cron job for Apache managed Letsencrypt TLS certs

2023-03-24 Thread Tom Browder
On Fri, Mar 24, 2023 at 12:23 Tom Browder wrote: > I have all my websites using Apache's managed certs. Up to now I have been > restarting them periodically manually as root executing "apachectl > graceful" and then checking to see if the update happened. I have for a > long time been meaning to

Re: [users@httpd] old gen workers sticking around post 2.4.49

2023-03-24 Thread metaed
I wrote: > I'll try to reproduce the problem without mod_php. Using "dehydrated -c -x" to drive my testing, I've hit the 7-day rate limit at Let's Encrypt, so I'll have to come back to this. - To unsubscribe, e-mail: users-unsubs

Re: [users@httpd] Cron job for Apache managed Letsencrypt TLS certs

2023-03-24 Thread metaed
Tom Browder wrote: > Anyone have a suggestion for a good restart frequency for managed certs? > Also, should the cron job use "apachectl" or a systemd command? My Slackware-64 15.0 system checks certs daily using the supplied "dehydrated" Let's Encrypt client. It renew a cert when the system date

[users@httpd] Cron job for Apache managed Letsencrypt TLS certs

2023-03-24 Thread Tom Browder
I have all my websites using Apache's managed certs. Up to now I have been restarting them periodically manually as root executing "apachectl graceful" and then checking to see if the update happened. I have for a long time been meaning to do that as a cron job, but haven't set one up in a great wh

Re: [users@httpd] old gen workers sticking around post 2.4.49

2023-03-24 Thread metaed
Eric Covener wrote: > - the old gen should not be able to accept new connections > - generally if it's left running, I would want to look at what > threads were left running (pstack or often better the few gdb commands > here: https://httpd.apache.org/dev/debugging.html#backtrace Here is the gd