Start another copy of Apache

[jksho1801]

Hi all,

I am presently trying to install 2 copies of the same Apache 2.0 in one solaris box. I have succesfully installed and run the first copy with SSL. When i tried to run the second copy without SSL, in which i have installed in a separate directory and with a different port number, it failed. The error message indicates that it tries to use the first copy 'httpd.conf' to start. Why is this???

Does anyone has encoutered this problem before?
For your information, i have already specified a different directory in './configure --prefix' when running the configure script.

 

[comtec17]

Why would you want 2 copies on the same machine. You can use Virtual Host to do what you are doing.

 

[siberian]

When you compile apache issue the

--prefix=DIRNAMETOAPACHEINSTALL

set this differently for both installations

What is occuring is that your apachectl command is trying to use the base configuration for its start-up. It sounds like you copied your first apache build into the new directory.

Reconfigure/compile with the above command and you should be set.

We do multiple apache instances all the time for developers sandboxes. That way they can bump their own apaches and work on them without disturbing one another.

 

[siberian]

OOps missed your last piece, sorry!

You already used --prefix.

What is in both apachectl scripts? Are they pointed properly? You can hand edit those if needed.

The only time I have ever seen this is when apachectl was not built via configure, sorry

 

[SirCharles]

Make sure your apachectl is pointing to the new location of httpd and/or config file.

 

[jksho1801]

Hi all,

I have checked the apachectl file in the second copy, and it is already pointing to the second copy of Apache.......

rgds

 

[SirCharles]

The path to the new .conf file should be spelled out in the apachectl file. It may be that you are invoking the new .conf file, but have ips/ports messed up. If you have ssl on one site and not ssl on another, you'll probably need more than one ip. Check out docs on ip-based vs name-based vhosts. It indicates that you may only have one ip per ssl site. Now, you may have the non-ssl version of the site listening on port 80 and have it rewrite to port 443. But trying to listen for another 'named' site on port 80 on the same ip will not work.