apache problem after update centos

N

Nickvd

New member
Joined
May 26, 2005
Messages
4
Location
The Netherlands
Tonight i updated Centos, a yum update but apache (httpd) won't start... Directadmin gives:

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


Can somebody help me?
 
I had the same problem with Apache getting upgraded through YUM. I found this thread and ran the scripts listed above. After running them, I tried to restart Apache2 and it errored out finding the modules. Turns out it had removed the modules from my server. Not too big a deal, I was able to re-run the Apache2 RPM and it put the modules back. All seems to be good now except when I try to add a new subdomain. When I do that, I get the following error:

Unable to create subdomain



Details


Nothing is listed after the Details. I have tried just adding the line "apache_ver=2.0" in the directadmin.conf file, but it didn't seem to help. I noticed that I had 2 directadmin.conf files, one in the ./conf/ directory and one in the ./data/templates/ directory. I assume I should be changing the one in the ./conf/ directory, but I am pretty new to DirectAdmin.

Does anyone have any idea's on how to get this DirectAdmin newbie backup and working? Like I said, the site is working, but subdomain administration is not.

Thanks!!
 
Okay, one more time...

These are the updates to skip when updating a DirectAdmin server;
be sure to add this line to the bottom of the [main] section of /etc/yum.conf

exclude=httpd* mysql* php* perl* apache* mod_* MySQL* *ftp* exim* sendmail* php* kernel* da_*

Jeff
 
Thanks for the info, I am very new to DirectAdmin and I haven't had much of a chance to look around in the forums yet. I was unaware that we were to exclude packages in the YUM update. I have never used DirectAdmin before and when my host asked if I wanted Plesk or DirectAdmin, I opt'ed to pay more to get DirectAdmin because I hated Plesk so much. Your comments have been noted and this issue will be corrected.

With that said, any ideas on this problem I have?

Thanks!!
 
They actually charged you more for DirectAdmin?

If that weren't sad it would be funny, because Plesk costs so much more than DirectAdmin.

I can't say why you're still having problems because I don't know what you may have broken during your update.

Jeff
 
Yes, we are paying MORE for DirectAdmin, but less than for CPanel.

...and we do like it, we like it better than Plesk, we just need to get past this issue. Because the details of the error say nothing, it makes it hard to find the cause of the problem. Are their any logs that I can check that might give me more info as to what is happening? Like I said, all I did was run the recommended scripts to upgrade from Apache to Apache2. Then I had to re-install the Apache2 RPM package because all my modules were gone. Now I can't manage subdomains.

Any kind of log file with any more info would be great!

Thanks!!
 
Yes, true, but I don't believe it to be an Apache problem (correct me if you think I am wrong). It appears to be a problem with DirectAdmin updating Apache. I think I can manually config Apache with new subdomains, but I can't get DirectAdmin to do it. DirectAdmin seems to be working fine for other tasks, just not Apache. I looked in the DirectAdmin log files from within DirectAdmin, but they don't seem to be logging any problems when I am adding Subdomains.
 
Can anyone give me a quick run down on how DirectAdmin modifies Apache2? I have to get this fixed, but like I said, I am new to DA and I don't really know how it works. I just need to figure out how it modifies the conf files in Apache2 and maybe I can figure out why it isn't working.

Thanks!!!
 
Okay, I got my error fixed when adding subdomains. Somehow the httpd.conf file had the ownership changed on it. I was able to chown it back to the directadmin user and it is now modifying the file during the subdomain change.

The problem I have now, is that it is still changing the <virtual host> httpd.conf file back to Apache 1 version. I have to go in and remove the user and group information from each subdomain to get Apache2 to load again. I added apache_ver=2.0 to the top of the directadmin.conf file, but it doesn't seem to make any difference. Do I need to put it some place else or do I need to change something else to make it work?

Thanks!!
 
You must log in or register to reply here.
Back
Top