Jump to content

Recommended Posts

I try to install the Apache 2.4.2 on my Linux.

I have downloaded latest APR, APR-UTIL and extracted them to ./srclib/apr and ./srclib/apr-util. I also extracted the pcre to ./srclib/pcre.

But when I tried to use ./configure --with-included-apr, it sill gave me

 

checking for APR... configure: error: the --with-apr parameter is incorrect. It must specify an install prefix, a build directory, or an apr-config file.

configure failed for srclib/apr-util

 

How to install it correctly? Anything I missed?

Link to comment
https://forums.phpfreaks.com/topic/265116-question-about-installing-apache-242/
Share on other sites

Now, the question above is solved. I installed apr and apr-util, then use --with-apr instead of --with-included-apr

 

I have another question. After I installed, I ./apachect1 start. I can see it when I do ps -eaf | grep httpd. It also shows on netstat -lep --tcp

 

But when I open the link, xxxx:8091 on my browser, the page can not be displayed.

 

I have another apache running on 8090, which works normally.

 

port 8090 apache server is on /home/myname/server1 (installed before, work fine, apache2.22.xx)

port 8091 apache server is on /home/myname/server2 (just installed, apache2.4.2)

 

Could anyone give me a hand? Thank you very much.

It's not localhost. Since I don't have SU right, I only can test remotely.

 

First, I went to 8091, ./apachectl stop the service. Then I went to 8090 to do the same thing, but it says "httpd (no pid file) not running".

 

From ps -eaf, the service(8090) is still running. Even I kill -TERM pid (8090), when I use xxxx:8090 on my browser, the page is still showing no matter how many times I refresh. It seems I couldn't control this Apache server(8090), which I installed before.

 

Like the ps -eaf or netstae -lep --tcp has NO httpd running, but from remotely, http://xxx:8090 is still working.

And now I'm wondering if you have both installations properly separated from each other.

 

First, I went to 8091, ./apachectl stop the service. Then I went to 8090 to do the same thing, but it says "httpd (no pid file) not running".

The one command "./apachectl stop" will only affect one instance. I couldn't tell you which. Running it a second time won't affect the other instance.

 

From ps -eaf, the service(8090) is still running. Even I kill -TERM pid (8090), when I use xxxx:8090 on my browser, the page is still showing no matter how many times I refresh. It seems I couldn't control this Apache server(8090), which I installed before.

You don't mean to say that you ran kill -TERM 8090 right?

 

A simple netstat -lp | egrep '8090|http' should show you something, even if not the full process information (for which you'd need su/sudo).

I used kill -TERM PID (the pid for port 8090) since I couldn't get rid of it before. Since I messed up the vhost conf file, somehow only one instance was ended by ./apachectl stop. Therefore I tried to kill the process to see if it works to stop the server. I am fool. Thanks for your remind. Hahh.

This thread is more than a year old. Please don't revive it unless you have something important to add.

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.