Xampp startup Notices and warnings in lampp error log

[bigpcman]

I have noticed that xampp 1.7.1 startup is now generating the following notices and warning messages in the lampp/logs/error_log that were not present in 1.6.8a:

Code: Select all

[Mon Apr 27 18:34:40 2009] [notice] suEXEC mechanism enabled (wrapper: /opt/lampp/bin/suexec)
[Mon Apr 27 18:34:41 2009] [warn] RSA server certificate is a CA certificate (BasicConstraints: CA == TRUE !?)
[Mon Apr 27 18:34:41 2009] [warn] RSA server certificate CommonName (CN) `localhost' does NOT match server name!?
[Mon Apr 27 18:34:41 2009] [notice] Digest: generating secret for digest authentication ...
[Mon Apr 27 18:34:41 2009] [notice] Digest: done
[Mon Apr 27 18:34:42 2009] [warn] RSA server certificate is a CA certificate (BasicConstraints: CA == TRUE !?)
[Mon Apr 27 18:34:42 2009] [warn] RSA server certificate CommonName (CN) `localhost' does NOT match server name!?
[Mon Apr 27 18:34:42 2009] [notice] Apache/2.2.11 (Unix) DAV/2 mod_ssl/2.2.11 OpenSSL/0.9.8k PHP/5.2.9 mod_apreq2-20051231/2.6.0 mod_perl/2.0.4 Perl/v5.10.0 configured -- resuming normal operations
[Mon Apr 27 18:42:12 2009] [notice] caught SIGTERM, shutting down
[Mon Apr 27 18:42:44 2009] [notice] suEXEC mechanism enabled (wrapper: /opt/lampp/bin/suexec)
[Mon Apr 27 18:42:45 2009] [warn] RSA server certificate is a CA certificate (BasicConstraints: CA == TRUE !?)
[Mon Apr 27 18:42:45 2009] [warn] RSA server certificate CommonName (CN) `localhost' does NOT match server name!?
[Mon Apr 27 18:42:46 2009] [notice] Digest: generating secret for digest authentication ...
[Mon Apr 27 18:42:46 2009] [notice] Digest: done
[Mon Apr 27 18:42:47 2009] [warn] RSA server certificate is a CA certificate (BasicConstraints: CA == TRUE !?)
[Mon Apr 27 18:42:47 2009] [warn] RSA server certificate CommonName (CN) `localhost' does NOT match server name!?
[Mon Apr 27 18:42:47 2009] [notice] Apache/2.2.11 (Unix) DAV/2 mod_ssl/2.2.11 OpenSSL/0.9.8k PHP/5.2.9 mod_apreq2-20051231/2.6.0 mod_perl/2.0.4 Perl/v5.10.0 configured -- resuming normal operations


Does anyone know how to fix the warnings? And what is the "suEXEC mechanism enabled"?

[Wiedmann]

Code: Select all

[Mon Apr 27 18:34:41 2009] [warn] RSA server certificate CommonName (CN) `localhost' does NOT match server name!?

Does anyone know how to fix the warnings?

- Use a correct certificate for your ServerName
- or change your ServerName to match the certificate

And what is the "suEXEC mechanism enabled"?

http://httpd.apache.org/docs/2.2/suexec.html

[bigpcman]

Code: Select all

[Mon Apr 27 18:34:41 2009] [warn] RSA server certificate CommonName (CN) `localhost' does NOT match server name!?

Does anyone know how to fix the warnings?

- Use a correct certificate for your ServerName
- or change your ServerName to match the certificate

Thanks for the response. This is more complicated than it seems. I'm using redirection services to map several urls to my ip address. So for example the following solution often recommended doesn't work for me:

Code: Select all

Replacing the following line in httpd.conf
<VirtualHost *:443>
with
<VirtualHost mysite.com:443>

So that after the change the corresponding piece of Apache (2.2, btw) conf looked like this:

<VirtualHost mysite.com:443>
DocumentRoot /home/bla/bla
ServerName mysite.com
ErrorLog /home/bla/error.log
CustomLog /home/bla/access.log combined
SSLEngine on

SSLCertificateFile /home/bla/ssl/server.crt
SSLCertificateKeyFile /home/bla/ssl/private.key

<Directory /home/bla/bla*>
</Directory>
</VirtualHost>

I have lived with the warnings up to now but they are aggravating. I suppose I need to create separate VirtualHost entries one for each url and each one having unique keys.

I suppose I should take this subject over to the apache forum.

[Wiedmann]

I'm using redirection services to map several urls to my ip address.

http://httpd.apache.org/docs/2.2/ssl/ss ... tml#vhosts

[bigpcman]

I'm using redirection services to map several urls to my ip address.

http://httpd.apache.org/docs/2.2/ssl/ss ... tml#vhosts

Thanks, that's a good reference. looks like I need a separate vHost entry for each url and each one must use a unique port number and unique keys. Then the redirection entries would have to be modified such that https would point to the appropriate port number. Quite a bit more complicated than I thought.