SSL/Apache error

[MQ-James]

After server problems I recompiled apache using the build script. I now get an error about unknown command "SSLEngine on" and the only way to fix it is to comment out all the ssl lines but then we do not get any SSL security on httpd. does anyone else get this problem?

[aushost]

Yes I have a similiar problem after an update of DA early today Apache has stopped and the server eventually went down for an hour, had to manually reboot the server to get it back up. Apache is still not working nor can it be activated from the DA admin control panel.

[DirectAdmin Support]

Are you guys restarting apache withservice httpd restart? It's needed so that the -DHAVE_SSL option (among others) is passed.

John

[MQ-James]

Whenever restarting a service I use the service command.

[DirectAdmin Support]

To do a total wipe, run:

rm -f /usr/lib/apache/*
cd /usr/local/directadmin/customapache
rm -f configure.*
rm -f *.gz
./build clean
./build update
./build allJohn

[l0rdphi1]

This is the same problem I have. I emailed you on it yesterday.

And an update on that- it appears I can uncomment all the included httpd.conf's I want and somehow Apache starts by itself (DA, I guess) even though it's impossible to start or restart or reload it manually:[root@server1 customapache]# service httpd restart
Stopping httpd: [ OK ]
/etc/init.d/httpd: line 46: ulimit: open files: cannot modify limit: Invalid argument
/etc/init.d/httpd: line 47: ulimit: open files: cannot modify limit: Invalid argument
/etc/init.d/httpd: line 48: ulimit: open files: cannot modify limit: Invalid argument
/etc/init.d/httpd: line 49: ulimit: open files: cannot modify limit: Invalid argument
Starting httpd: [Wed Feb 11 15:38:52 2004] [warn] module perl_module is already loaded, skipping
[Wed Feb 11 15:38:52 2004] [warn] NameVirtualHost 64.191.24.198:80 has no VirtualHosts
[Wed Feb 11 15:38:52 2004] [warn] NameVirtualHost 64.191.24.198:443 has no VirtualHosts
[FAILED]

And the only way to get the error message is:[root@server1 customapache]# apachectl start
Syntax error on line 15 of /etc/httpd/conf/ips.conf:
Invalid command 'SSLEngine', perhaps mis-spelled or defined by a module not included in the server configuration
/usr/sbin/apachectl start: httpd could not be started



Is it 'service httpd' that is broke?

[host4leicester]

To do a total wipe, run:


code:--------------------------------------------------------------------------------
rm -f /usr/lib/apache/*
cd /usr/local/directadmin/customapache
rm -f configure.*
rm -f *.gz
./build clean
./build update
./build all--------------------------------------------------------------------------------
John

That did not fix it, I invite you to take a look, just PM me....

[l0rdphi1]

Yeah, I meant to meantion that doesn't work.. but I forgot :)

[ProWebUK]

Originally posted by host4leicester
I invite you to take a look, just PM me....

If you want support to take a look at this I advise you to email your server information using: https://www.directadmin.com/clients/safesubmit.php

Chris

[DirectAdmin Support]

Hello,

Just as a followup.. I think the "LoadModule" directive in the main httpd.conf was commented out. Not too sure about that, but I recompiled everyting and uncommented it and it's working now.

John

[DRKT]

Hi!

i have same error:
-----------
[root@one - /usr/local/directadmin/customapache # /sbin/service httpd restart
Stopping httpd: [ OK ]
/etc/init.d/httpd: line 46: ulimit: open files: cannot modify limit: Invalid argument
/etc/init.d/httpd: line 47: ulimit: open files: cannot modify limit: Invalid argument
/etc/init.d/httpd: line 48: ulimit: open files: cannot modify limit: Invalid argument
/etc/init.d/httpd: line 49: ulimit: open files: cannot modify limit: Invalid argument
Starting httpd: [Thu Mar 22 06:04:59 2007] [warn] module perl_module is already loaded, skipping
.....
-----------
why??

[jlasman]

You've posted to an incredibly old post that may not be monitored anymore. Did you check to see if LoadModule was uncommented in your /etc/httpd/conf/httpd.conf file? If that's not resolving the problem, then run customapache to recompile everything, and see if that fixes it. Otherwise, ProWebUK has a good idea; have DA support take a look at your server.

Jeff