Re: [users@httpd] Mystifying start failure

2022-05-30 Thread Frank Gingras
Glad you figured it out, TLS errors can be cryptic to debug. On Mon, 30 May 2022 at 13:14, jnil...@jala.com wrote: > That solved it! Apache has successfully started. > Thanks Yehuda and Frank! > > On 30 May 2022, at 8:51, Yehuda Katz wrote: > > Then something is probably wrong with the contents

Re: [users@httpd] Mystifying start failure

2022-05-30 Thread jnil...@jala.com
That solved it! Apache has successfully started. Thanks Yehuda and Frank! > On 30 May 2022, at 8:51, Yehuda Katz wrote: > > Then something is probably wrong with the contents of one of your SSL > certificates. Make sure they are formatted correctly. > Check if any virtualhost has a separate er

Re: [users@httpd] Mystifying start failure

2022-05-30 Thread jnil...@jala.com
Yep! One of the virtual hosts has a private key/certificate mismatch. I'll try shutting it down temporarily to see if that fixes the apache2 start problem. > On 30 May 2022, at 8:51, Yehuda Katz wrote: > > Then something is probably wrong with the contents of one of your SSL > certificates. Ma

Re: [users@httpd] Mystifying start failure

2022-05-30 Thread Frank Gingras
Errors with certificates will often cause silent failures. Running apachectl -S and making sure that all TLS vhosts have a valid certificate and key is usually the fastest approach here. On Mon, 30 May 2022 at 11:51, Yehuda Katz wrote: > Then something is probably wrong with the contents of one

Re: [users@httpd] Mystifying start failure

2022-05-30 Thread Yehuda Katz
Then something is probably wrong with the contents of one of your SSL certificates. Make sure they are formatted correctly. Check if any virtualhost has a separate error log. - Y On Mon, May 30, 2022 at 11:03 AM jnil...@jala.com wrote: > The tail end of /var/log/apache2/error_log gives: > > [Fr

Re: [users@httpd] Mystifying start failure

2022-05-30 Thread jnil...@jala.com
The tail end of /var/log/apache2/error_log gives: [Fri May 27 00:02:10.914649 2022] [ssl:warn] [pid 1562] AH01873: Init: Session Cache is not configured [hint: SSLSessionCache] [Fri May 27 00:02:10.939405 2022] [:emerg] [pid 1562] AH00020: Configuration Failed, exiting AH00016: Configuration Fai

Re: [users@httpd] PCRE support for Apache Httpd 2.4.53

2022-05-30 Thread Herbert J. Skuhra
On Mon, May 30, 2022 at 05:27:10PM +0530, Shylaja P wrote: > Hi, > We used Apache* httpd-2.4.52* *with PCRE-8.44* in our project, Now I'm > trying to upgrade my project with Apache* httpd-2.4.53*, but It is failing > with pcre-config not found. > >- *Is it mandatory to use PCRE2 to upgrade to

Re: [users@httpd] Mystifying start failure

2022-05-30 Thread Yehuda Katz
systemd doesn't know to look in the HTTPD log file. What does that log say? Likely located in /var/log/apache2/ - Y On Mon, May 30, 2022 at 9:58 AM jnil...@jala.com wrote: > I recently rebooted the server and started apache only to get a failure. > Here's the diagnosis; I'm not sure what to mak

[users@httpd] Mystifying start failure

2022-05-30 Thread jnil...@jala.com
I recently rebooted the server and started apache only to get a failure. Here's the diagnosis; I'm not sure what to make of it. systemctl status apache2.service ● apache2.service - The Apache Webserver Loaded: loaded (/usr/lib/systemd/system/apache2.service; enabled; vendor preset: disable

[users@httpd] PCRE support for Apache Httpd 2.4.53

2022-05-30 Thread Shylaja P
Hi, We used Apache* httpd-2.4.52* *with PCRE-8.44* in our project, Now I'm trying to upgrade my project with Apache* httpd-2.4.53*, but It is failing with pcre-config not found. - *Is it mandatory to use PCRE2 to upgrade to Apache httpd-2.4.53?* - *Is there any way to use PCRE-8.44 and upgra

[users@httpd] PCRE support for Apache Httpd 2.4.53.

2022-05-30 Thread Shylaja P
Hi, We used Apache httpd-2.4.53 with PCRE-8.44 in our project, Now I'm trying to upgrade my project with Apache httpd-2.4.53, but It is failing with pcre-config not found. - *Is it mandatory to use PCRE2 to upgrade to Apache httpd-2.4.53?* - *Is there any way to use PCRE-8.44 and upgrade to