Very Computer

Symptoms:
 In the configuration with both servers being version 1.3.0,
whether I have the port 8081 server running or not, when I
"apachectl start" the 8080 server, it insists on conecting to
port 8081. All the obvious *.conf file settings are for 8080.
( See *.conf setup info below ).

 The 8081 httpd.pid file is updated, so I can't "apachectl stop"
from the 8080 sbin directory unless I copy the 8081 httpd.pid
file .

 "ps -ef" shows that it is the 8081 httpd that is running.

 Log files in the 8081 server directory tree are updated instead
of the 8080 directory tree. In fact, there are no log files at
all in the 8080 directory tree. If I have the 8081 server running,
the startup for the 8080 server fails because the 8081 port is
unavailable.

Background:
 Port 8080 was being served by the 1.2.6 server. Port 8080 was
how the rest of my co-workers accessed my "released" HTML documents
& cgi scripts.

 This week I successfully setup and ran version 1.3.0 on port 8081,
simultaneously with the version 1.2.6 server. I intend to use port
8081 for development.

 The 1.3.0 tar package was untarred into a directory ~/apache_1.3.0 .
I built the first 1.3.0 server into directory ~/apache ; this is
server set to port 8081.

 The second 1.3.0 server was built into directory ~/apache_pub/ from
directory apache_1.3.0; it is supposed to connect to port 8080.

 The ~/apache_pub/etc/.conf files were copied from ~/apache/etc/*.conf
versions, and then edited to change "/apache/" refs to "/apache_pub/"
and "8081" to "8080". This includes "Port" and "BindAddress"
and "LockFile" and "ScoreBoardFile".  I have triple-plus checked the
values of these directives .

Any help would be greatly appreciated.

Larry Ching

( warning: still learning the Apache http server )

 First, I deleted the scripts and executables from ~/apache_pub/sbin/,
and deleted the *.conf files from ~/apache_pub/etc/. Then I defined
the compiler enviroment variable with "setenv CC gcc", and then re-ran
~/apache_1.3.0/configure :

./configure --verbose --prefix=/home/myusername/apache_pub --with-perl=/usr/local/bin/perl

 This time, I omitted the suexec setup, that I had done previously. I
did keep the ~/apache_pub/sbin/suexec file I had generated previously.

 Did "make" and "make install" with no incident.

 Edited the ~/apache_pub/etc/*.conf files this time, instead of copying
and editing the *.conf files from my other 1.3 server directory
~/apache/etc/ .

 Used ~/apache_pub/sbin/apachectl to start the server, and it started
up just fine, using port 8080. Log files are created and are in the
~/apache_pub/ directory tree instead of the ~/apache/ directory tree.

 Started ~/apache/sbin/httpd , and it's running just fine on port 8081.

 suEXEC is working for both servers.

 Why it works now, I don't know ... I do remember that I did repeat the
configure/make/make install cycle without the suEXEC setup the first time
I tried to get version 1.3.0 running in ~/apache/ .

Larry Ching

( warning: still learning the Apache http server )