Accidentally installed httpd - now webserver down

dperren

Verified User
Joined
Jun 8, 2007
Messages
28
Oh dear. I've just made a massive mistake.

Whilst playing about with yum on my Centos 4.4 server, I accidentlly hit 'y', and managed to install:

Code:
=============================================================================
 Package                 Arch       Version          Repository        Size
=============================================================================
Installing:
 compat-openldap         i386       2.1.30-7.4E      base              221 k
 mod_authz_ldap          i386       0.26-2.1         base               87 k
 openldap-servers        i386       2.2.13-7.4E      base              3.2 M
 openldap-servers-sql    i386       2.2.13-7.4E      base               88 k
 php-ldap                i386       4.3.9-3.22.9     update             35 k
Installing for dependencies:
 apr                     i386       0.9.4-24.5.c4.2  base               88 k
 apr-util                i386       0.9.4-21         base               51 k
 httpd                   i386       2.0.52-32.3.ent.centos4  update            888 k
 httpd-suexec            i386       2.0.52-32.3.ent.centos4  update             29 k
 php                     i386       4.3.9-3.22.9     update            1.3 M
 php-pear                i386       4.3.9-3.22.9     update            268 k
 unixODBC                i386       2.2.11-1.RHEL4.1  base              829 k

Now, apache won't restart:

Code:
Stopping httpd:                                            [  OK  ]
Starting httpd:
 Apache 1.3 configuration directives found
 please read /usr/share/doc/httpd-2.0.52/migration.html
                                                           [FAILED]

Presumably because I've confused directadmin with the new version. How can I revert this, ideally without loosing any mysql, dns, mail, or web data (though I do have backups)?

Thanks: any help would be massively appriciated.
 
Last edited:
Also you might want to see if there is any .rpmsave these may be your old config files.

yum erase package you might have to run custombuild again.
 
Also you might want to see if there is any .rpmsave these may be your old config files.

yum erase package you might have to run custombuild again.

Okay, I've done
Code:
yum erase httpd
, and then
Code:
cd /usr/local/directadmin/customapache
./build clean
./build all

Fingers firmly crossed...
 
This seems to have fixed things, aside from that this now appears when starting httpd:

Code:
[warn] module perl_module is already loaded, skipping

Presumably the command to load the module has been duplicated somewhere - any ideas where?
 
Code:
<IfDefine HAVE_PERL>
LoadModule perl_module        modules/libperl.so
</IfDefine>

Code:
LoadModule perl_module        /usr/lib/apache/libperl.so

I can see those two: which ought I to comment out?

Thanks, and cheers for the help so far!
 
That depends on which one was loaded by RPM and which by customapache.

My guess would be the one in modules is probably the one loaded by RPM.

Personally, I would have removed all the packages installed by YUM and the dependencies it also installed. Then I would have run yum again to install only what I wanted.

Did you check these forums for the exclude line that should be in your yum.conf file?

This should have been installed by DirectAdmin, but it may not have been, because if it was, then httpd should not have been installed by yum.

Jeff
 
That depends on which one was loaded by RPM and which by customapache.

My guess would be the one in modules is probably the one loaded by RPM.

Personally, I would have removed all the packages installed by YUM and the dependencies it also installed. Then I would have run yum again to install only what I wanted.
I commented out the first, and everything seems okay so for.

Did you check these forums for the exclude line that should be in your yum.conf file?

This should have been installed by DirectAdmin, but it may not have been, because if it was, then httpd should not have been installed by yum.

Jeff
Embaressingly, I actually manually removed this. Now I know why it was there!

Everything seems to be back to normal now, thanks for the help everyone :)

Now, fixing the problem that actually caused all this: how can I install and enable the php-ldap module?

Thanks again,
 
If I were asking I'd open up a new thread in the PHP/MySQL subforum, and ask there.

Jeff
 
Back
Top