Apache 2.0, PHP 5.0, Perl 5.8, MySQL 4.1

[Petraverse]

Hi,

I need Apache 2.0, PHP 5.0, Perl 5.8 and MySQL 4.1 for a new web site I am putting up. I have a DirectAdmin based VPS but can only get Apache 1.3, PHP 4.3, Perl 5.8 and MySQL 4.0?

How would I go about the upgrade?

Thanks

[jlasman]

DirectAdmin does not support Apache 2.

So you're on your own.

There are a few threads on these forums by people who've attempted it.

I don't recall if any have been successful.

Jeff

[jmstacey]

Php, Perl, and Mysql should be no problem but they will not be installed by default. You shouldn't run into any trouble with them.

As Jeff said though DA doesn't support Apache2 at this time but its possible with some editing and tweaking here and there. Probably the biggest concerns are the layout for the user config files and if Apache2 will continue to read the format DA uses, if not you'll have to write your own httpd.conf template that will work. And if all the modules you need are supported by Apache2

[BigWil]

What would you say the best way is to update MySQL to 4.1x?

BigWil

[jmstacey]

4.1.x is a Gamma release (use for new development) which is specified on the mysql website.

I'm afraid you would run into the same problem people are having with trying to install mysql-max because directadmin does not recoginze that its running and tries to start mysqld. Disabling DA's mysql monitoring will fix that problem but I wouldn't use it on a production server.

[BigWil]

I was hoping you would discourage me.

I am on a Beta team and the developers of a certain software are developing it for use on 4.1.x believe it or not. Can't say what software as I am under an NDA, but I think they might want to rethink things a bit. I tried 4.1.x a LONG time ago and it wasn't very good. Nothing but problems. And since DA isn't going to like it that does it for me.

I will just tell the dev team of this software that we can't run the 4.1.x on production machines because a good source told us it was a bad idea. :-)

Works for me.........

BigWil

[Icheb]

I'm going to do an experiment with a new (hence backup) server, to use PHP 5.0 and MySQL 4.1.x. Last time I tried that MySQLd it worked rather good.

Although their alpha release (that 5.0) seems to be segfaulting a bit much on our intranet test server.

I've had a few people asking for PHP 5.0 with a MySQLd that supports subquery's without using innodb :D

[icreative]

could we upgrade to PHP5 via customapache?
if yes how? :)

appreciate any input :)

[Icheb]

Originally posted by icreative
could we upgrade to PHP5 via customapache?
if yes how? :)

appreciate any input :)
No, not in it's current condition...
I'll try after I have the license stuff sorted out for that server.

I think it's possible, although not entirely in the standard way...

[Icheb]

Originally posted by jmstacey
4.1.x is a Gamma release (use for new development) which is specified on the mysql website.

I'm afraid you would run into the same problem people are having with trying to install mysql-max because directadmin does not recoginze that its running and tries to start mysqld. Disabling DA's mysql monitoring will fix that problem but I wouldn't use it on a production server.

DA recognises it, as it should, as long as you don't use the max version...
The main problem, I think, is PHP 5.
Check out http://www.directadmin.com/forum/showthread.php?s=&postid=32000#post32000 to see what I mean.

[interfasys]

Quick note to let some people know that DA is working on Apache 2.

http://www.directadmin.com/features.php?id=441

[BigWil]

I still need to know how Apache2 was able to run with Frontpage. If there was a patch I need to check it out first because I have other "sandbox" applications that will need to be exempt from Suexec.

Do you see a fp-patch in the distribution you could share?

BigWil

[Icheb]

Originally posted by BigWil
I still need to know how Apache2 was able to run with Frontpage. If there was a patch I need to check it out first because I have other "sandbox" applications that will need to be exempt from Suexec.

Do you see a fp-patch in the distribution you could share?

BigWil
Check the versions todo/release on the da main site. The customapache system is going to be released for Apache 2 soon. So why not just wait until that's available to see if it will work ? :)

[ilan]

Apache 2 support has been released as a beta with Version 1.231

http://www.directadmin.com/features.php?id=441

[Cameron Braid]

I have installed apache2, and it works by default, except I believe that something is incorrect in the /usr/local/directadmin/customapache/configure.apache_2 script

apache 1.3 uses

--enable-module=all
or
--enable-module=most

where as apache 2 uses

--enable-mods-shared=all
or
--enable-mods-shared=most

therefore, when running with the default /usr/local/directadmin/customapache/configure.apache_2 file, the additional shared modules aren't build and installed

i.e. I changed /usr/local/directadmin/customapache/configure.apache_2 to be like :


#!/bin/sh
OPTIM="-DHARD_SERVER_LIMIT=32768 -DFD_SETSIZE=32768 " \
./configure \
--enable-ssl \
--prefix=/etc/httpd \
--exec-prefix=/etc/httpd \
--bindir=/usr/bin \
--sbindir=/usr/sbin \
--sysconfdir=/etc/httpd/conf \
--enable-mods-shared=all \
--enable-rewrite \
--enable-suexec \
--with-suexec-docroot=/ \
--with-suexec-caller=apache \
--with-suexec-userdir=public_html \
--with-suexec-logfile=/var/log/httpd/suexec_log \
--with-suexec-bin=/usr/sbin/suexec \
--includedir=/usr/include/apache \
--libexecdir=/usr/lib/apache \
--datadir=/var/www \
--localstatedir=/var \
--disable-auth-dbm --disable-auth-db


and now I have all shared modules in /usr/lib/httpd

I believe that this may be what you were trying to achieve with the --enable-module=all directive. I am new to httpd2, so I was confused with this directive, since it did nothing.

I suggest it should either be removed, or replaced with the apache2 style version.

DirectAdmin is great, I have found it bettern than ensim and plesk reloaded. I don't mean to criticise DirectAdmin, just help to improve its quality :)

[Cameron Braid]

Well.. it seems like my understanding of apache2 has failed me again :)

When using the above conffigure script, a lot of the modules are not compiled statically, as they were before.

using your config script :


# apachectl -l
core.c
mod_access.c
mod_auth.c
mod_include.c
mod_log_config.c
mod_env.c
mod_setenvif.c
mod_ssl.c
prefork.c
http_core.c
mod_mime.c
mod_status.c
mod_autoindex.c
mod_asis.c
mod_suexec.c
mod_cgi.c
mod_negotiation.c
mod_dir.c
mod_imap.c
mod_actions.c
mod_userdir.c
mod_alias.c
mod_rewrite.c
mod_so.c


using my config script :


# apachectl -l
core.c
prefork.c
http_core.c
mod_so.c


So my question is : Is there any way to get those modules statically compiled, and the rest compiled as shared objects, without having to specify each one with a separate configure parameter ?