Koozali.org: home of the SME Server
Obsolete Releases => SME Server 7.x => Topic started by: steveo on July 22, 2006, 11:38:27 AM
-
I have ran an upgrade on my sme6 box and the boot sequence fails with:
syntax error on line 111 of /etc/httpd/conf/httpd.conf cannot load /etc/httpd/modules/mod_ssl.so into server /etc/httpd/modules/mod_ssl.so cannot open shared object file: no such file or directory
It would seem that a file is missing or the /etc/httpd/conf/httpd.conf file is wrong.
At the moment the server continues to cycle through this message and will not continue the book sequence.
Have not seen this before in the forums. Any ideas on how this should be fixed?
Cheers,
Steve Curren
-
Ok, renamed the /etc/httpd/conf/httpd.conf to /etc/httpd/conf/httpd.conf.old. The server is at least running, but with no web server (and no access to the server-manager).
It seems as though all SSL type stuff is causing problems.
-
I have expanded the template:
expand-template /etc/httpd/conf/httpd.conf
I restart httpd with
/etc/init.d/httpd restart
and receive this error message:
Starting httpd: Syntax error on line 111 of /etc/httpd/conf/httpd.conf:
Cannot load /etc/httpd/modules/mod_ssl.so into server: /etc/httpd/modules/mod_ssl.so: cannot open shared object file: No such file or directory
ls -l /etc/httpd/modules/mod_ssl.so reveals no such file or directory
Line 111 from /etc/httpd/conf/httpd.conf
LoadModule ssl_module modules/mod_ssl.so
There is no such file as [modules/mod_ssl.so] so either the config file is wrong (and if so where is the reference coming from) or I am missing a file.
The httpd.conf file also contains an entry
SSLEngine off
and SSLEngine on
Which also cause errors - do I have the write stuff in the file for SME7?
-
Which also cause errors - do I have the write stuff in the file for SME7?
The error is most likely caused by a contrib which is not compatible with SME7. Search the wiki and the bug tracker here for the error messages you are seeing and you will probably find the details. Or look at line 111 of your httpd.conf.
Or remove all contribs, and then re-install them one at a time until you find the one which is broken. Report the broken contrib via the bug tracker.
-
I ended up installing a fresh SME7 on a test server and copied the HTTPD.conf template files over to the effected server and expanded the templates. This got the web server running again.
I also needed to install quite a few packages using yum that did not seem to be installed during the upgrade. I've just about got everything fixed.