[BlueOnyx:10425] Syntax error on line 10 of /etc/httpd/conf.d/ssl_perl.conf:

[Dr. Blunt]

Now getting this error which essentially cannot start httpd


[root at s3 /]# service httpd restart
Stopping httpd:                                            [FAILED]
Starting httpd: Syntax error on line 10 of /etc/httpd/conf.d/ssl_perl.conf:
$parms->add_config() has failed: SSLCertificateFile: file 
'/home/.sites/70/site4/certs/certificate' does not exist or is empty at 
/usr/lib/perl5/Apache2/PerlSections.pm line 215.\n
                                                            [FAILED]


At 10:07 AM 5/2/2012, you wrote:
>Hi all,
>
>Updates for BlueOnyx have been released which fix SSL certificate and
>open_basedir issues.
>
>The HTML page of the news is avaialble through this short URL:
>http://tinyurl.com/7fve24t
>
>
>base-apache (5107R + 5108R):
>==========================
>
>This update fixes the problem that could happen if you have multiple sites
>with SSL enabled. In such cases it could happen that one or more sites were
>not comming up via HTTPS and would instead do an endless redirect loop. The
>cause of it (and the fix) are explained in a devel blog entry
>(http://tinyurl.com/88pm5r7) in more detail.
>
>
>base-ssl (5106R, 5107R + 5108R):
>============================
>
>The GUI pages for uploading intermediate SSL certificates (named "Manage
>Certificate Authorities" in the GUI) would refuse to accept uploaded GoDaddy
>intermediate certificates or intermediate certificates from some other
>vendors. This has been fixed, too.
>
>
>base-vsite (5106R, 5107R + 5108R):
>=============================
>
>This update introduces a somewhat improved and smarter management for PHP's
>'open_basedir' directive. The GUI input boxes for 'open_basedir' have been
>turned into textareas. That makes it easier to see what's entered without 
>much
>horizontal scrolling.
>
>Under 'Server Management' / 'Security' / 'PHP' you can - as before - define
>the server wide PHP settings. However: Changing the information here will now
>also force an update of all PHP settings of all Vsites. If you now change the
>'open_basedir' to add something, then it will be automatically added to the
>PHP settings of all Vsites as well. Note: Only changes to "open_basedir" are
>immediately pushed out to all Vsites, but none of the other settings.
>
>When you look at the GUI pages for the PHP settings of a Vsite, then you see
>that there are now two presentations for 'open_basedir':
>
>One read only text area which shows you the server wide 'open_basedir'
>settings as defined under 'Server Management' / 'Security' / 'PHP' for the
>whole box. Another text area below that allows to specify extra 
>'open_basedir'
>paths that aren't already covered by the server wide settings of this
>parameter and which apply only for this Vsite.
>
>Duplicates are removed, so if you enter a path that's already covered by the
>server wide 'open_basedir' settings, then it will be stripped. If you enter
>nonsense that doesn't start or end with a slash it'll be stripped as well. A
>single slash (to allow access to everything) is permitted, but of course not
>recommended. These changes are compatible with existing sites, new sites and
>also apply when sites are imported with CMU.
>
>--
>With best regards
>
>Michael Stauber
>_______________________________________________
>Blueonyx mailing list
>Blueonyx at mail.blueonyx.it
>http://mail.blueonyx.it/mailman/listinfo/blueonyx
>
>
>-----
>No virus found in this message.
>Checked by AVG - www.avg.com
>Version: 2012.0.1913 / Virus Database: 2411/4933 - Release Date: 04/12/12
>Internal Virus Database is out of date.