When 'make install' is executed it doesn't kill all apache processes.

[GoogleCodeExporter]

What steps will reproduce the problem?
1. sudo make install

What is the expected output? What do you see instead?

I expect apache to be restarted, but I get this output:

 * Restarting web server apache2                                          

 httpd (pid 22361?) not running
(98)Address already in use: make_sock: could not bind to address 0.0.0.0:80
no listening sockets available, shutting down
Unable to open logs

What version of the product are you using? On what operating system?

Updated to revision 914.

Please provide any additional information below.

None

Original issue reported on code.google.com by carl.nob...@gmail.com on 15 May 2008 at 6:42

[GoogleCodeExporter]

The 'make install' target is not meant to restart Apache, it should only 
install the mod_wsgi module. If it 
attempts to on your platform to restart Apache, then you have a non standard 
Apache installation where 
someone has modified the 'apxs' command to do additional things over what it is 
meant to when installing a 
module.

Another possibility is that you didn't mean 'make install' and you meant that 
you ran 'apachectl' to 
stop/restart Apache. If you did this and you use a Linux system where Apache is 
integrated into system init, 
then you perhaps shouldn't be using 'apachectl'. Instead you are meant to use 
'/etc/init.d/httpd' to 
stop/reload Apache. You will need to refer to your system documentation on 
exactly where the script is and 
what options to use.

Finally, are you even using the default system version of Apache or have you 
built your on from src. If the 
latter and you haven't told it to use a different listener socket, you may be 
interfering with an existing Apache 
installation.

Please provide more exact information about the actual commands you are running 
and the exact output. Ie., 
cut and past output from your login shell recording what you did. Also say what 
operating system you are 
using, what Apache and how it is installed.

At the moment I am guessing you are supposed to use '/etc/init.d/httpd' as 
using 'apachectl' direct when that 
is meant to be used does I believe yield those sorts of problems.

BTW, you may need to kill off running httpd process manually now to get things 
back to sane state.

  ps aux | grep httpd

  kill -9 <pids of httpd processes>

Note, processes may actually be called 'apache2', as may init script.

Original comment by Graham.Dumpleton@gmail.com on 15 May 2008 at 9:27

• Added labels: Type-Other
• Removed labels: Type-Defect

[GoogleCodeExporter]

No response and not a problem with mod_wsgi, except maybe to extend that 
documentation may need to be 
clearer about how to restart Apache on Linux boxes. Added notes to README and 
installation on Linux 
documentation.

Original comment by Graham.Dumpleton@gmail.com on 18 May 2008 at 4:59

• Changed state: WontFix