HOW TO : Upgrade Apache 1.x or 2.x to 2.0.58

Brad · May 23, 2006

Hi
Sorry for first post being a question

Followed instructions in this thread up to...

Code:

cd /usr/local/directadmin/customapache
rm -fr build
wget [url]http://files.directadmin.com/services/customapache/build[/url]
chmod 755 build
./build update
./build update_data_ap2
./build convert
./build clean
./build php_ap2 y

Runs OK up until that same error....

Configuring SAPI modules
checking for AOLserver support... no
checking for Apache 1.x module support via DSO through APXS... no
checking for Apache 1.x module support... no
checking for mod_charset compatibility option... no
checking for Apache 2.0 filter-module support via DSO through APXS... no
checking for Apache 2.0 handler-module support via DSO through APXS... apxs:Error: Invalid query string `BINDIR'
apxs:Error: Invalid query string `MPM_NAME'
apxs:Error: Invalid query string `APU_BINDIR'
apxs:Error: Invalid query string `APR_BINDIR'
./configure: line 5674: /apr-config: No such file or directory
./configure: line 5675: /apu-config: No such file or directory
configure: error: You have enabled Apache 2 support while your server is Apache 1.3. Please use the appropiate switch --with-apxs (without the 2)

*** There was an error while trying to configure php. Check the configure.php file

Apache runs OK as 1.3.36 (I'm on Fedora Core 4, dunno if that makes a difference?). Same thing happened first time I tried and then I successfully went back to 1.3.36.
Tried again this time removing old php folder as suggested, same result.

Brad · May 23, 2006

./build apache_2

Now everything goes OK. (should that step be included in the 1.3.x -2.x procedure, or am I just being a bit dense? If so, at what stage?)

Except I seem to have lost my DA/domains setup??
In addition, now I can't restart Apache

Code:

SSLCertificateFile: file '/etc/httpd/conf/ssl.crt/server.crt' does not exist or is empty

So I'm going to try again and just remove '--enable-ssl \' from configure.apache_2, unless there's specificallya reason I shouldn't?

eddof13 · May 23, 2006

@how@ said:
eddof13 & explodehost.com you need to build with y
remove old php folder in
cd /usr/local/directadmin/customapache
then start build with y
./build php_ap2 y

Wael

Hi I did this, and ssh crashed while outputting:

Code:

Making mhash-0.9.1...
Trying to make mHash...
make  all-recursive
make[1]: Entering directory `/usr/local/directadmin/customapache/mhash-0.9.1'
Making all in lib
make[2]: Entering directory `/usr/local/directadmin/customapache/mhash-0.9.1/lib'
if /bin/sh ../libtool --silent --mode=compile gcc -DHAVE_CONFIG_H -I. -I. -I..     -g -O2 -MT mhash.lo -MD -MP -MF ".deps/mhash.Tpo" \
  -c -o mhash.lo `test -f 'mhash.c' || echo './'`mhash.c; \
then mv -f ".deps/mhash.Tpo" ".deps/mhash.Plo"; \
else rm -f ".deps/mhash.Tpo"; exit 1; \
fi
mhash.c:105: warning: initialization from incompatible pointer type
mhash.c:105: warning: initialization from incompatible pointer type
mhash.c:105: warning: initialization from incompatible pointer type
mhash.c:107: warning: initialization from incompatible pointer type
mhash.c:107: warning: initialization from incompatible pointer type
mhash.c:107: warning: initialization from incompatible pointer type
mhash.c:112: warning: initialization from incompatible pointer type
mhash.c:112: warning: initialization from incompatible pointer type
mhash.c:112: warning: initialization from incompatible pointer type
mhash.c:117: warning: initialization from incompatible pointer type
mhash.c:117: warning: initialization from incompatible pointer type
mhash.c:117: warning: initialization from incompatible pointer type
mhash.c:122: warning: initialization from incompatible pointer type
mhash.c:122: warning: initialization from incompatible pointer type
mhash.c:122: warning: initialization from incompatible pointer type
mhash.c:127: warning: initialization from incompatible pointer type
mhash.c:127: warning: initialization from incompatible pointer type
mhash.c:127: warning: initialization from incompatible pointer type
mhash.c:127: warning: initialization from incompatible pointer type
mhash.c:132: warning: initialization from incompatible pointer type
mhash.c:132: warning: initialization from incompatible pointer type
mhash.c:132: warning: initialization from incompatible pointer type
mhash.c:132: warning: initialization from incompatible pointer type
mhash.c:134: warning: initialization from incompatible pointer type
mhash.c:134: warning: initialization from incompatible pointer type
mhash.c:134: warning: initialization from incompatible pointer type
mhash.c:134: warning: initialization from incompatible pointer type
mhash.c:139: warning: initialization from incompatible pointer type
mhash.c:139: warning: initialization from incompatible pointer type
mhash.c:139: warning: initialization from incompatible pointer type
mhash.c:139: warning: initialization from incompatible pointer type
mhash.c:141: warning: initialization from incompatible pointer type
mhash.c:141: warning: initialization from incompatible pointer type
mhash.c:141: warning: initialization from incompatible pointer type
mhash.c:141: warning: initialization from incompatible pointer type
mhash.c:146: warning: initialization from incompatible pointer type
mhash.c:146: warning: initialization from incompatible pointer type
mhash.c:146: warning: initialization from incompatible pointer type
mhash.c:148: warning: initialization from incompatible pointer type
mhash.c:148: warning: initialization from incompatible pointer type
mhash.c:148: warning: initialization from incompatible pointer type

However if I use ./build php_ap2 n I get the same error as explodehost and brad.

In case it isn't clear, I currently have 1.3 installed and I am trying to upgrade to 2.

koh · May 25, 2006

@how@ said:

Hello,
Changes with Apache 2.0.58
http://www.devlib.org/apache/httpd/CHANGES_2.0

from 2.x to 2.0.58

Code:

cd /usr/local/directadmin/customapache rm -fr build wget [url]http://files.directadmin.com/services/customapache/build[/url] chmod 755 build ./build update ./build update_data_ap2 ./build clean ./build php_ap2 y ./build mod_frontpage_ap2 ./build mod_perl_ap2 ./build zend /sbin/service httpd restart

from 1.3.x to 2.0.58

Code:

cd /usr/local/directadmin/customapache rm -fr build wget [url]http://files.directadmin.com/services/customapache/build[/url] chmod 755 build ./build update ./build update_data_ap2 ./build convert ./build clean ./build php_ap2 y ./build mod_frontpage_ap2 ./build mod_perl_ap2 ./build zend /sbin/service httpd restart

Have a nice day

Wael

I just realise for upgrade from 1.3.x to 2.0.x , isnt it:
./build update_data_ap2
./build convert
./build apache_2
./build php_ap2
./build mod_frontpage_ap2
./build mod_perl_ap2
then
service httpd restart ?

@how@ · May 25, 2006

Re: Re: HOW TO : Upgrade Apache 1.x or 2.x to 2.0.58

koh said:
I just realise for upgrade from 1.3.x to 2.0.x , isnt it:
./build update_data_ap2
./build convert
./build apache_2
./build php_ap2
./build mod_frontpage_ap2
./build mod_perl_ap2
then
service httpd restart ?

Yes

./build apache_2

linuxnewbie · May 28, 2006

Hi,

I followed your instruction and it went through everything, httpd restarted but now ssh service is closed. How can i get connected again back, i just can't do anything now. Also i seem to have lost directadmin setup as well, it doesn't run.

I appreciate any help.

Thanks.

@how@ · May 30, 2006

linuxnewbie said:
Hi,

I followed your instruction and it went through everything, httpd restarted but now ssh service is closed. How can i get connected again back, i just can't do anything now. Also i seem to have lost directadmin setup as well, it doesn't run.

I appreciate any help.

Thanks.

you need to reboot your server

Brad · May 30, 2006

Good new, running Apache 2.0.58 happily

Bad news, DirectAdmin setup still seems to be missing

When I go to the domains previously set up while running 1.3.36 (and successfully tested) I just get the Apache test page, not the Direct Admin holding page.

However, going to http://IP Address/~user/ I get the DA holding page.

Going to http://IP Address:2222 just returns a blank page.

In addition I had a simple index.php setup in a subdirectory under that (just phpinfo()), which doesn't route automatically, but putting in the full path dumps the plain text to the browser window. So it looks like PHP isn't working correctly either.

@how@ · May 30, 2006

Brad said:
Good new, running Apache 2.0.58 happily

Bad news, DirectAdmin setup still seems to be missing

When I go to the domains previously set up while running 1.3.36 (and successfully tested) I just get the Apache test page, not the Direct Admin holding page.

However, going to http://IP Address/~user/ I get the DA holding page.

Going to http://IP Address:2222 just returns a blank page.

In addition I had a simple index.php setup in a subdirectory under that (just phpinfo()), which doesn't route automatically, but putting in the full path dumps the plain text to the browser window. So it looks like PHP isn't working correctly either.

Build again

Code:

 ./build apache_2
./build php_ap2 y
./build mod_frontpage_ap2
./build mod_perl_ap2
./build zend

Brad · Jun 1, 2006

just ran ./build zend

Direct admin working again, seems to have retained it's settings.

However individual domains are still not resolving as they should, just going to the Apache test page.

Having a quick look in httpd.conf there are no VirtualHosts set up, so obviously the DoucmentRoot is just /var/www/. Is this correct? Does DA somehow use it's own .conf files?

Thought I'd try ./build clean then the procedure you suggested from scratch again.

SSH bombed out during running ./build php_ap2 (has done in the past as well, but not everytime), 'connection closed by remote host'. Trying to reconect gives 'ssh_exchange_identification: Connection closed by remote host'.

Was also using 'screen' the other day and when it bombed out that time I lost the connection, as opposed to just dropping out to an SSH shell.

Can't restart SSH myself as DA appears to have stopped working.

Also, index.php (just contains phpinfo()) still just dumps the raw text to the browser.

*** Server restarted, DA/SSH working again.

sullise · Jun 1, 2006

Why bother upgrading from 1.3 - 2.0?

@how@ · Jun 1, 2006

sullise said:
Why bother upgrading from 1.3 - 2.0?

look like

Brad · Jun 2, 2006

I'm running subversion and trac (or at least, I'm trying to).

Roy · Jun 3, 2006

Hello Martink,

I have stumbled upon this problem also when upgrading to apache2 etc. on debian. Now i have found the following solution. You have to apt-get libperl5.8 and apt-get libperl-dev.

After that recompile mod_perl et voila! it workd

Sorrryyy wrong thread :s is not nice when having multiple sessions open

@how@ · Jun 4, 2006

sullise said:
Why bother upgrading from 1.3 - 2.0?

Code:

./build convert

Brad · Jun 4, 2006

OK, 'solved' the problem of the DA setup 'disappearing' (and yes, I'm aware this is a schoolboy error, no need to point it out

)

Picked up a hint from another thread suggesting I remove the /etc/httpd/ directory before trying a rebuild. Of course, in my aplomb to get moving with Apache 2 I omitted to backup the httpd.conf file. So when Apache recreated it from scratch there were no includes to link to the .conf files in the DA user directory structure.

Recreated from scratch, now we're cooking on gas.

EXCEPT

Third build procedure from scratch, no apparent errors, PHP & Zend happily report as to being installed successfully, but PHP files are failing to intepret correctly
ie still dumping raw text to the browser.

koh · Jun 4, 2006

did you do the php for ap2 part? If yes, try recompiling them again

Brad · Jun 4, 2006

Yes

Code:

./build php_ap2 y

@how@ · Jun 4, 2006

koh

Code:

cat /etc/redhat-release

if you want know OS

Brad · Jun 4, 2006

Fedora Core release 4 (Stentz)

HOW TO : Upgrade Apache 1.x or 2.x to 2.0.58

Verified User

Verified User

New member

Verified User

Verified User

Verified User

Verified User

Verified User

Verified User

Verified User

Verified User

Verified User

Verified User

New member

Verified User

Verified User

Verified User

Verified User

Verified User

Verified User