httpd-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gagan Puri" <gaganp...@infosys.com>
Subject IBM Http Server 2.0.42.2 web server on Linux mysteriously spawning mulitple childs
Date Thu, 28 Aug 2003 11:33:36 GMT
Hi

We are facing a problem with IBM Http Server 2.0.42.2 web server on Linux 7.3 & Adanced
Server 2.1 m/c.  Afterconfiguring the webserver to accept html page requests, on accessing
there html resource, error page comes instead of the page being displayed. This is happening
when we configure our application webagent with the webserver. However the same application
web server is working correctly when configured with apache 2.0.46(IBM IHs 2.0.42.2 is based
on apache 2.0.46). The resource is shown properly by webserver as per required. Also the same
IBM Http Server 2.0.42.2 is working fine on Solaris with our application.  

On exporing the web server behaviour, we found that in case of IBM Http Server 2.0.42.2 web
server on Linux lots of child processes are getting spawned on starting the webserver which
is not the case with normal apacahe 2.0.46 & IBM IHS 2.0.42.2 on Solaris. 

In normal apache 2,0.46, the child processes are spawned upto one level . Output of ps -ef
commad just after starting the webserver is as below:

agent6   14119     1  0 12:05 ?        00:00:00 /home/agent6/Apache2046/bin/http
agent6   14120 14119  0 12:05 ?        00:00:00 /home/agent6/Apache2046/bin/http
agent6   14122 14120  0 12:05 ?        00:00:00 /home/agent6/Apache2046/bin/http
agent6   14123 14119  0 12:05 ?        00:00:00 /home/agent6/Apache2046/bin/http
agent6   14124 14119  0 12:05 ?        00:00:00 /home/agent6/Apache2046/bin/http
agent6   14125 14119  0 12:05 ?        00:00:00 /home/agent6/Apache2046/bin/http

In & IBM IHS 2.0.42.2 on solaris, the child processes are spawned upto one level . Output
of ps -ef commad just after starting the webserver is as below:

nobody 7872 	7871 	0 18:23:31 ? 0:00 /opt/IBMIHS20422/bin/httpd -d /opt/IBMIHS20422 -k start
nobody 7873 	7871 	0 18:23:31 ? 0:00 /opt/IBMIHS20422/bin/httpd -d /opt/IBMIHS20422 -k start
root 	7871 	1 	0 18:23:30 ? 0:00 /opt/IBMIHS20422/bin/httpd -d /opt/IBMIHS20422 -k start
nobody 7874 	7871 	0 18:23:31 ? 0:00 /opt/IBMIHS20422/bin/httpd -d /opt/IBMIHS20422 -k start


In case of IBM Http Server 2.0.42.2 web server on Linux, the child processes span to multiple
levels. Output of ps -ef commad just after starting the webserver is as below
root     32082     1  0 13:02 ?        00:00:00 /opt/IHS20422/bin/httpd -d /opt/
root     32083 32082  0 13:02 ?        00:00:00 /opt/IHS20422/bin/httpd -d /opt/
root     32085 32083  0 13:02 ?        00:00:00 /opt/IHS20422/bin/httpd -d /opt/
nobody   32086 32082  0 13:02 ?        00:00:00 /opt/IHS20422/bin/httpd -d /opt/
nobody   32087 32082  0 13:02 ?        00:00:00 /opt/IHS20422/bin/httpd -d /opt/
nobody   32088 32082  0 13:02 ?        00:00:00 /opt/IHS20422/bin/httpd -d /opt/
nobody   32089 32087  0 13:02 ?        00:00:00 /opt/IHS20422/bin/httpd -d /opt/
nobody   32090 32088  0 13:02 ?        00:00:00 /opt/IHS20422/bin/httpd -d /opt/
nobody   32093 32089  0 13:02 ?        00:00:00 /opt/IHS20422/bin/httpd -d /opt/
nobody   32094 32090  0 13:02 ?        00:00:00 /opt/IHS20422/bin/httpd -d /opt/
nobody   32095 32089  0 13:02 ?        00:00:00 /opt/IHS20422/bin/httpd -d /opt/
nobody   32096 32089  0 13:02 ?        00:00:00 /opt/IHS20422/bin/httpd -d /opt/
nobody   32097 32089  0 13:02 ?        00:00:00 /opt/IHS20422/bin/httpd -d /opt/
nobody   32098 32089  0 13:02 ?        00:00:00 /opt/IHS20422/bin/httpd -d /opt/
nobody   32099 32089  0 13:02 ?        00:00:00 /opt/IHS20422/bin/httpd -d /opt/
nobody   32100 32089  0 13:02 ?        00:00:00 /opt/IHS20422/bin/httpd -d /opt/
nobody   32101 32089  0 13:02 ?        00:00:00 /opt/IHS20422/bin/httpd -d /opt/
nobody   32102 32089  0 13:02 ?        00:00:00 /opt/IHS20422/bin/httpd -d /opt/
nobody   32103 32089  0 13:02 ?        00:00:00 /opt/IHS20422/bin/httpd -d /opt/
nobody   32104 32089  0 13:02 ?        00:00:00 /opt/IHS20422/bin/httpd -d /opt/
nobody   32105 32089  0 13:02 ?        00:00:00 /opt/IHS20422/bin/httpd -d /opt/
nobody   32106 32089  0 13:02 ?        00:00:00 /opt/IHS20422/bin/httpd -d /opt/
nobody   32107 32089  0 13:02 ?        00:00:00 /opt/IHS20422/bin/httpd -d /opt/
nobody   32108 32089  0 13:02 ?        00:00:00 /opt/IHS20422/bin/httpd -d /opt/
nobody   32109 32089  0 13:02 ?        00:00:00 /opt/IHS20422/bin/httpd -d /opt/
nobody   32110 32089  0 13:02 ?        00:00:00 /opt/IHS20422/bin/httpd -d /opt/
nobody   32111 32089  0 13:02 ?        00:00:00 /opt/IHS20422/bin/httpd -d /opt/
nobody   32112 32089  0 13:02 ?        00:00:00 /opt/IHS20422/bin/httpd -d /opt/
nobody   32113 32089  0 13:02 ?        00:00:00 /opt/IHS20422/bin/httpd -d /opt/
nobody   32114 32089  0 13:02 ?        00:00:00 /opt/IHS20422/bin/httpd -d /opt/
nobody   32115 32089  0 13:02 ?        00:00:00 /opt/IHS20422/bin/httpd -d /opt/
nobody   32116 32089  0 13:02 ?        00:00:00 /opt/IHS20422/bin/httpd -d /opt/
nobody   32117 32089  0 13:02 ?        00:00:00 /opt/IHS20422/bin/httpd -d /opt/
nobody   32118 32089  0 13:02 ?        00:00:00 /opt/IHS20422/bin/httpd -d /opt/
nobody   32119 32089  0 13:02 ?        00:00:00 /opt/IHS20422/bin/httpd -d /opt/
nobody   32120 32090  0 13:02 ?        00:00:00 /opt/IHS20422/bin/httpd -d /opt/
nobody   32121 32090  0 13:02 ?        00:00:00 /opt/IHS20422/bin/httpd -d /opt/
nobody   32122 32090  0 13:02 ?        00:00:00 /opt/IHS20422/bin/httpd -d /opt/
nobody   32123 32090  0 13:02 ?        00:00:00 /opt/IHS20422/bin/httpd -d /opt/
nobody   32124 32090  0 13:02 ?        00:00:00 /opt/IHS20422/bin/httpd -d /opt/
nobody   32125 32090  0 13:02 ?        00:00:00 /opt/IHS20422/bin/httpd -d /opt/
nobody   32126 32090  0 13:02 ?        00:00:00 /opt/IHS20422/bin/httpd -d /opt/
nobody   32127 32090  0 13:02 ?        00:00:00 /opt/IHS20422/bin/httpd -d /opt/
nobody   32128 32090  0 13:02 ?        00:00:00 /opt/IHS20422/bin/httpd -d /opt/
nobody   32129 32090  0 13:02 ?        00:00:00 /opt/IHS20422/bin/httpd -d /opt/
nobody   32130 32090  0 13:02 ?        00:00:00 /opt/IHS20422/bin/httpd -d /opt/
nobody   32131 32090  0 13:02 ?        00:00:00 /opt/IHS20422/bin/httpd -d /opt/
nobody   32132 32090  0 13:02 ?        00:00:00 /opt/IHS20422/bin/httpd -d /opt/
nobody   32133 32090  0 13:02 ?        00:00:00 /opt/IHS20422/bin/httpd -d /opt/
nobody   32134 32090  0 13:02 ?        00:00:00 /opt/IHS20422/bin/httpd -d /opt/
nobody   32135 32090  0 13:02 ?        00:00:00 /opt/IHS20422/bin/httpd -d /opt/
nobody   32136 32090  0 13:02 ?        00:00:00 /opt/IHS20422/bin/httpd -d /opt/
nobody   32137 32090  0 13:02 ?        00:00:00 /opt/IHS20422/bin/httpd -d /opt/
nobody   32138 32090  0 13:02 ?        00:00:00 /opt/IHS20422/bin/httpd -d /opt/
nobody   32139 32090  0 13:02 ?        00:00:00 /opt/IHS20422/bin/httpd -d /opt/
nobody   32140 32090  0 13:02 ?        00:00:00 /opt/IHS20422/bin/httpd -d /opt/
nobody   32141 32090  0 13:02 ?        00:00:00 /opt/IHS20422/bin/httpd -d /opt/
nobody   32142 32090  0 13:02 ?        00:00:00 /opt/IHS20422/bin/httpd -d /opt/
nobody   32143 32090  0 13:02 ?        00:00:00 /opt/IHS20422/bin/httpd -d /opt/
nobody   32144 32090  0 13:02 ?        00:00:00 /opt/IHS20422/bin/httpd -d /opt/


NOTES: above output of ps --ef are onplain web server starup withour our application configured.

Apache is mysteriously spawn a child of a child process to handle a request. This is creating
uncertain behaviour in our application. 
Is the behaviour IBM IHS 2,0,42,2 correct on Linux ?? If not how to get rid of this behaviour??

Is this a known issue on linux???

Regards,
Gagan


Mime
View raw message