Changing over to apache2

cwwilson721 · 08-08-2006, 10:21 PM

I'm currently running Apache 1.3 on my webservers. I d/l etc. Apache 2.

It does work for my top level domain/website, however, I have a few virtual domains in my old config that don't work. Any ideas on what to do?

Maybe a guide that steps out changing over from 1.3 to 2?

EDIT**** Yes, updated php and mysql also.

ADDITIONAL EDIT ****

It is a fully functioning webserver that can't go offline, so I'm experimenting with a backup server that I don't care what happens. All pages, configs, etc are exact copies from main server.

ryanoa · 08-08-2006, 10:39 PM

What screwed me up when switching over to apache2 was that the config files were no longer in /etc/apache/ but in /etc/apache2/.
I kept editing /etc/apache/httpd.conf over and over again thinking I had made errors in my virtual host sections.

Maybe you already know this and have a different problem, but hopefully it's just as simple as it was for me.

cwwilson721 · 08-08-2006, 10:51 PM

I know that one, thanks.

Some how, they now work...

I have NO clue what I did...

folkenfanel · 08-08-2006, 11:38 PM

Hi

I have been using Apache2 for a while.

At least in the 2.2.x series (don't remember really how it was in 2.0.x), there is a separate /etc/apache/extra dir for all the "miscelaneous" or "extra" configurations, like for example how directories that do not have an index have to be browsed, etc.

You have to activate them from the httpd.conf

Greetings, and may the Source be with you!

cwwilson721 · 08-09-2006, 12:09 AM

Just noticed that the bugger is 2.0.58 Just tried compiling 2.2, and having issues..

Will get back.

cwwilson721 · 08-09-2006, 06:24 PM

OK.

Here's the scoop so far:

Was running 1.3 from Slackware -current, with multiple virtual websites. All working fine, except I could not transfer large files.
Downloaded Apache 2.0 package from Linuxpackages, installed, reconfigured the /etc/apache2/httpd.conf file, is running OK, but no large file support (My bad, thought it was 2.2)
Downloaded source for Apache 2.2, configured (./configure --prefix=/usr), make, checkinstall. Then had a heck of a time finding the httpd.conf file (was in /usr/conf). Never got it running right, was always saying that it was started, but was not.
Uninstalled 2.2, 2.0, 1.3 and reinstalled 1.3, then 2.0 w/php 5. That's what is running now. Still want 2.2 for large file support.

Does anybody know where a running package is of Apache 2.2? The source route is EVENTUALLY usuable, but what a bugger it is.

cwwilson721 · 08-11-2006, 04:53 PM

OK. Redid everything.
/
Instead of

Code:

./configure --prefix=usr

I did

Code:

./configure

That way the thing setsup to the directories in the docs. Then did a 'make', 'checkinstall', then

Code:

rm /usr/sbin/apachectl       ## To remove the old apachectl from 1.3 and 2.0
ln -s /usr/local/apache2/bin/apachectl /usr/sbin/apachectl  ##To make sure that typing 'apachectl' will work

I also removed the old /etc/apache/httpd.conf and /etc/apache2/httpd.conf directories.

Now, for configuring for multiple virtual directories, and directory browsing...

tuxrules · 08-11-2006, 05:10 PM

Quote:

Originally Posted by cwwilson721

Does anybody know where a running package is of Apache 2.2? The source route is EVENTUALLY usuable, but what a bugger it is.

I have compiled 2.2.3 version that I haven't got time to test. I did a rather lengthy configure and actually followed the original slackware layout. I will post the configure options for you later today if you want.

I am still a bit confused (or haven't got a hang) of the new httpd.conf and how everything comes together.

Tux,

cwwilson721 · 08-11-2006, 05:35 PM

I also

Code:

ln -s /usr/local/apache2/conf/httpd.conf /etc/apache2/httpd.conf

just so that part is normal...

tuxrules · 08-11-2006, 11:29 PM

As promised...here's my configure options for apache 2.2.3

Quote:

### apache 2.2.3 config
./configure --prefix=/usr --exec-prefix=/usr --libexecdir=/usr/libexec/apache2 --mandir=/usr/man --sysconfdir=/etc/apache2 --datadir=/var/www --includedir=/usr/include/apache2 --localstatedir=/var --with-apxs --disable-actions --disable-autoindex --disable-cgi --disable-dir --enable-cache --enable-charset-lite --enable-deflate --enable-disk-cache --enable-expires --enable-ext-filter --enable-file-cache --enable-headers --enable-info --enable-logio --enable-mem-cache --enable-mime-magic --enable-rewrite --enable-so --enable-speling --enable-ssl --enable-unique-id --enable-imagemap --enable-log-forensic --enable-version --enable-static-support --enable-usertrack --enable-vhost-alias --enable-auth-dbm --with-mpm=worker --enable-mods-shared='rewrite headers ssl' --enable-shared-support

Hopefully that helps to customize the install.

Tux,

cwwilson721 · 08-11-2006, 11:38 PM

Cool. Too late for me (already configured it...lol)

I'll definately use it next time tho...

folkenfanel · 08-12-2006, 12:36 AM

Why don't you use a SlackBuild? Take the original Slackware SlackBuild for Apache1 as a starting point, then modify it to fit your needs. That's what I did.

It is not only the compile-time options. Take a look inside the SlackBuild. Take a good look. Now build your package the same way Pat would do, but this time this package will be only for you, and you only will be its Master. Isn't it an art?

At the beginning, it gave me lots of problems. But with some time playing with these toys, I can tell I do not regret having upgraded to Apache2. And as it's a package of mine I fitted it to suit my needs like an Armani fit-tailored suit

. That's the good thing about using the Source.

May the Source be with you!

cwwilson721 · 08-12-2006, 12:41 AM

My main constraint was time. Since I ran out, I just did it. When 11 comes out, I'll redo my webserver and backup server, then I'll do Apache 2.2 w/good Slackbuild. I now have the time, and can come up with one, and test it on my backup webserver.

Thanks for all the advice and ways to go.