On Wed, Oct 10, 2012 at 6:49 PM, Graham Leggett = <minfrin@sharp.fm> wrote:

On 10 Oct 2012, at 1:55 PM, Jitesh Verma <jitesh.verma@gmail.com> wrote:

We have ported httpd-2.4.2 to a network embedded = box running Linux on Xscale hardware. We have two modules of our own to han= dle XML requests from our Applets. We have added all the 80 odd .so modules= (that get built with default "configure" settings) in httpd.conf= .

Is there a specific problem you're trying to solve by adding all 8= 0 modules to your server? Ideally, you should only load the modules you nee= d, and no more.

<Jitesh> Only the following 8 modules were enough to make my GUI= /Applet work. Remaining modules were added only after "Listen 9000&quo= t; did not work. I was just trying to see if loading all the modules make a= ny difference. But unfortunately, that did not help.
LoadModule authz_core_module modules/mod_authz_core.so
LoadModule authz_= host_module modules/mod_authz_host.so
LoadModule unixd_module modules/mo= d_unixd.so
LoadModule dir_module modules/mod_dir.so
LoadModule cgi_mo= dule modules/mod_cgi.so
LoadModule mime_module modules/mod_mime.so
LoadModule alias_module modul= es/mod_alias.

We are able to access the box's GUI/Applets w= ith "Listen 80" directive in the httpd.conf.
However, when we = add another directive "Listen 9000" to httpd.conf, httpd does not= respond to HTTP request sent to port 80. The following requests from Inter= net Explorer fails to get any response from httpd:
http://192.168.0.1http://192.168.0.1:80
http://192.168.= 0.1:9000
=A0
Wireshark packet trace indicates that the request packet is correctl= y sent to TCP port 80 when request http://192.168.0.1 is sent from browser. However, the outgo= ing packet is missing from the packet trace. It seems httpd did not generat= e any response (not even "File not found" response).

TCP involves the exchange of many packets to establish a connection, a= nd if a connection is not successfully established you cannot expect a high= er level response of any kind. I would first ensure that a TCP connection i= s possible to establish properly before worrying about something running ab= ove it.

<Jitesh> Packet trace shows that TCP session is getting establis= hed successfully. After that, httpd does receive the first HTTP request fro= m browser as is evident from /var/log/access_log. But no HTTP response goes= back to the browser. TCP session remain intact.

"netstat -tnlp" command shows httpd lis= tening on both TCP port 80 and 9000.
/var/log/access_log indicates that = the incoming packet reached httpd.
Gateway/firewall data indicates that = both TCP ports 80 and 9000 are open in both the directions (incoming and ou= tgoing).
The moment additional "Listen 9000" directive is removed from htt= pd.conf, httpd starts working fine (starts serving http://192.168.0.1 request).
We have enabl= ed and configured "debugging" and "loggers" modules. St= ill, /var/log/error_log and /var/log/messages do not show any error or warn= ing.
=A0=A0

We thought adding another "Listen" dire= ctive to httpd.conf is a child's play, but it seems to be a humongous t= ask.

Multiple Listen statements is a standard thing in many installs of the= server, and will be done by definition if a server supports both http and = https. It is definitely not a humungous task.

Are we missing something? Am I doing something wr= ong?? Is it a bug??? Can someone help in this forum? How to debug this issu= e?
=A0
Please find attached httpd.conf and configure wrapper script (= configure.wrapper) used for configuring and building httpd and its componen= ts.

Looking at your configure script that looks very wrong - you've ov= erridden all sorts of low level options without indicating clearly why you&= #39;ve done so. As you're on what seems like custom hardware, I would g= et apr and apr-util built clean and all tests run successfully before even = looking at httpd. Httpd relies heavily on apr and apr-util, and if these un= derlying libraries haven't been installed or configured properly httpd = and any other app that depends on apr/apr-util are certain not to work.

<Jitesh> Low level options were assigned the explicit values for= my platform (Linux/Xscale) because configure script had failed to determin= e these valuses as this is cross-compilation case. Those options are correc= t to the best my knowledge. APR and APR-Util builds cleanly. shared librari= es (.so) of libapr, libapr-util, libpcre and libexpat have been installed p= roperly. These libs get loaded by httpd without any error. I am not using a= ny App other than httpd. My GUI/Applets is up and running with port 80, so = I do not doubt the configuration and compilation of libs. But I may be wron= g.

The whole question is - httpd works fine if there is only "Listen= 80". The moment I add "Listen 9000" (or 9001) to httpd.conf= , httpd stops working even with port 80 (request with port 9000 anyway does= not work). Why should port 9000 affect the fucntionality of port 80?

Regards,

Graham

--