You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@httpd.apache.org by Jitesh Verma <ji...@gmail.com> on 2012/10/10 13:55:48 UTC
Help reqd. for httpd-2.4.2
Hi List,
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 handle XML requests from
our Applets. We have added all the 80 odd .so modules (that get built with
default "configure" settings) in httpd.conf.
We are able to access the box's GUI/Applets with "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 Internet Explorer fails to get any response from httpd:
http://192.168.0.1
http://192.168.0.1:80 <http://192.168.0.1/>
http://192.168.0.1:9000
Wireshark packet trace indicates that the request packet is correctly sent
to TCP port 80 when request http://192.168.0.1 is sent from browser.
However, the outgoing packet is missing from the packet trace. It seems
httpd did not generate any response (not even "File not found" response).
"netstat -tnlp" command shows httpd listening 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 outgoing).
The moment additional "Listen 9000" directive is removed from httpd.conf,
httpd starts working fine (starts serving http://192.168.0.1 request).
We have enabled and configured "debugging" and "loggers" modules. Still,
/var/log/error_log and /var/log/messages do not show any error or warning.
We thought adding another "Listen" directive to httpd.conf is a child's
play, but it seems to be a humongous task.
Are we missing something? Am I doing something wrong?? Is it a bug??? Can
someone help in this forum? How to debug this issue?
Please find attached httpd.conf and configure wrapper script
(configure.wrapper) used for configuring and building httpd and its
components.
Thanks,
Jitesh
Re: Help reqd. for httpd-2.4.2
Posted by Jitesh Verma <ji...@gmail.com>.
Althouh I see "Response sent with status 200, headers ......." in
error_log, I do not see matching write()/send() system call in strace
output. However, I do see "Request received from client: GET / HTTP/1.1
......." for incoming HTTP packet in both error_log and strace output.
Thanks,
Jitesh
On Thu, Oct 11, 2012 at 5:52 PM, Jitesh Verma <ji...@gmail.com>wrote:
> Jeff,
> Are you aware of any "Listen" related configure setting?
> Which files and functions handle socket bind() and socket write()/send()?
>
> Thanks,
> Jitesh
>
> On Thu, Oct 11, 2012 at 4:25 PM, Jeff Trawick <tr...@gmail.com> wrote:
>
>> On Thu, Oct 11, 2012 at 3:09 AM, Jitesh Verma <ji...@gmail.com>
>> wrote:
>> > Jeff,
>> > We tried LogLevel trace8. It indicates "Response was sent with status
>> 200".
>> > But we are not sure whether the response packet was handed over to
>> TCP/IP
>> > statck properly. We are puzzled. We need to double check if something is
>> > wrong with the network settings of our box itself.
>>
>> Maybe some APR settings are wrong due to the cross-compile??? The
>> strace might show something interesting, either because of something
>> that is present or something that is absent.
>>
>>
>> >
>> > Thanks,
>> > Jitesh
>> >
>> > On Wed, Oct 10, 2012 at 7:54 PM, Jitesh Verma <ji...@gmail.com>
>> > wrote:
>> >>
>> >> Hi Jeff,
>> >> Thanks for your reply.
>> >> I had added only the first 8 modules in httpd.conf. Remaining modules
>> were
>> >> added later only when I started facing this problem. Reducing the
>> number of
>> >> modules back to 8 does not make any difference with respect to this
>> issue.
>> >> With these 8 modules httpd worked fine with port 80. The problem
>> started
>> >> when I tried adding additional ports. Adding more ports is need of the
>> hour.
>> >> I can not escape it. I have run strace with "follow the fork" option
>> (rather
>> >> than single process). There are only 4 processess to follow. strace
>> output
>> >> did not help. It does not indicate any error condition as such. I can
>> make
>> >> it run as a single process by running httpd with -X option in
>> foreground.
>> >> But I am not sure whether that is going to help. Anyway, I will try
>> that.
>> >>
>> >> Thanks,
>> >> Jitesh
>> >>
>> >> On Wed, Oct 10, 2012 at 6:47 PM, Jeff Trawick <tr...@gmail.com>
>> wrote:
>> >>>
>> >>> On Wed, Oct 10, 2012 at 7:55 AM, Jitesh Verma <jitesh.verma@gmail.com
>> >
>> >>> wrote:
>> >>> > Hi List,
>> >>> > 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 handle XML requests from
>> >>> > our
>> >>> > Applets. We have added all the 80 odd .so modules (that get built
>> with
>> >>> > default "configure" settings) in httpd.conf.
>> >>> > We are able to access the box's GUI/Applets with "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 Internet Explorer fails to get any response from httpd:
>> >>> > http://192.168.0.1
>> >>> > http://192.168.0.1:80 <http://192.168.0.1/>
>> >>> > http://192.168.0.1:9000
>> >>> >
>> >>> > Wireshark packet trace indicates that the request packet is
>> correctly
>> >>> > sent
>> >>> > to TCP port 80 when request http://192.168.0.1 is sent from
>> browser.
>> >>> > However, the outgoing packet is missing from the packet trace. It
>> seems
>> >>> > httpd did not generate any response (not even "File not found"
>> >>> > response).
>> >>> > "netstat -tnlp" command shows httpd listening 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 outgoing).
>> >>> > The moment additional "Listen 9000" directive is removed from
>> >>> > httpd.conf,
>> >>> > httpd starts working fine (starts serving http://192.168.0.1request).
>> >>> > We have enabled and configured "debugging" and "loggers" modules.
>> >>> > Still,
>> >>> > /var/log/error_log and /var/log/messages do not show any error or
>> >>> > warning.
>> >>> >
>> >>> > We thought adding another "Listen" directive to httpd.conf is a
>> child's
>> >>> > play, but it seems to be a humongous task.
>> >>> > Are we missing something? Am I doing something wrong?? Is it a
>> bug???
>> >>> > Can
>> >>> > someone help in this forum? How to debug this issue?
>> >>> >
>> >>> > Please find attached httpd.conf and configure wrapper script
>> >>> > (configure.wrapper) used for configuring and building httpd and its
>> >>> > components.
>> >>> >
>> >>> > Thanks,
>> >>> > Jitesh
>> >>>
>> >>> users@httpd.apache.org is a better mailing list for this.
>> >>>
>> >>> A few things to start with...
>> >>>
>> >>> Get unnecessary modules out of the configuration to simplify
>> >>> logging/potential problems.
>> >>> See what is logged with LogLevel trace8.
>> >>> Configure the MPM to use a single child process to handle requests,
>> >>> and run strace against that.
>> >>>
>> >>> --
>> >>> Born in Roswell... married an alien...
>> >>> http://emptyhammock.com/
>> >>
>> >>
>> >
>>
>>
>>
>> --
>> Born in Roswell... married an alien...
>> http://emptyhammock.com/
>>
>
>
Re: Help reqd. for httpd-2.4.2
Posted by Jitesh Verma <ji...@gmail.com>.
Jeff,
Are you aware of any "Listen" related configure setting?
Which files and functions handle socket bind() and socket write()/send()?
Thanks,
Jitesh
On Thu, Oct 11, 2012 at 4:25 PM, Jeff Trawick <tr...@gmail.com> wrote:
> On Thu, Oct 11, 2012 at 3:09 AM, Jitesh Verma <ji...@gmail.com>
> wrote:
> > Jeff,
> > We tried LogLevel trace8. It indicates "Response was sent with status
> 200".
> > But we are not sure whether the response packet was handed over to TCP/IP
> > statck properly. We are puzzled. We need to double check if something is
> > wrong with the network settings of our box itself.
>
> Maybe some APR settings are wrong due to the cross-compile??? The
> strace might show something interesting, either because of something
> that is present or something that is absent.
>
>
> >
> > Thanks,
> > Jitesh
> >
> > On Wed, Oct 10, 2012 at 7:54 PM, Jitesh Verma <ji...@gmail.com>
> > wrote:
> >>
> >> Hi Jeff,
> >> Thanks for your reply.
> >> I had added only the first 8 modules in httpd.conf. Remaining modules
> were
> >> added later only when I started facing this problem. Reducing the
> number of
> >> modules back to 8 does not make any difference with respect to this
> issue.
> >> With these 8 modules httpd worked fine with port 80. The problem started
> >> when I tried adding additional ports. Adding more ports is need of the
> hour.
> >> I can not escape it. I have run strace with "follow the fork" option
> (rather
> >> than single process). There are only 4 processess to follow. strace
> output
> >> did not help. It does not indicate any error condition as such. I can
> make
> >> it run as a single process by running httpd with -X option in
> foreground.
> >> But I am not sure whether that is going to help. Anyway, I will try
> that.
> >>
> >> Thanks,
> >> Jitesh
> >>
> >> On Wed, Oct 10, 2012 at 6:47 PM, Jeff Trawick <tr...@gmail.com>
> wrote:
> >>>
> >>> On Wed, Oct 10, 2012 at 7:55 AM, Jitesh Verma <ji...@gmail.com>
> >>> wrote:
> >>> > Hi List,
> >>> > 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 handle XML requests from
> >>> > our
> >>> > Applets. We have added all the 80 odd .so modules (that get built
> with
> >>> > default "configure" settings) in httpd.conf.
> >>> > We are able to access the box's GUI/Applets with "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 Internet Explorer fails to get any response from httpd:
> >>> > http://192.168.0.1
> >>> > http://192.168.0.1:80 <http://192.168.0.1/>
> >>> > http://192.168.0.1:9000
> >>> >
> >>> > Wireshark packet trace indicates that the request packet is correctly
> >>> > sent
> >>> > to TCP port 80 when request http://192.168.0.1 is sent from browser.
> >>> > However, the outgoing packet is missing from the packet trace. It
> seems
> >>> > httpd did not generate any response (not even "File not found"
> >>> > response).
> >>> > "netstat -tnlp" command shows httpd listening 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 outgoing).
> >>> > The moment additional "Listen 9000" directive is removed from
> >>> > httpd.conf,
> >>> > httpd starts working fine (starts serving http://192.168.0.1request).
> >>> > We have enabled and configured "debugging" and "loggers" modules.
> >>> > Still,
> >>> > /var/log/error_log and /var/log/messages do not show any error or
> >>> > warning.
> >>> >
> >>> > We thought adding another "Listen" directive to httpd.conf is a
> child's
> >>> > play, but it seems to be a humongous task.
> >>> > Are we missing something? Am I doing something wrong?? Is it a bug???
> >>> > Can
> >>> > someone help in this forum? How to debug this issue?
> >>> >
> >>> > Please find attached httpd.conf and configure wrapper script
> >>> > (configure.wrapper) used for configuring and building httpd and its
> >>> > components.
> >>> >
> >>> > Thanks,
> >>> > Jitesh
> >>>
> >>> users@httpd.apache.org is a better mailing list for this.
> >>>
> >>> A few things to start with...
> >>>
> >>> Get unnecessary modules out of the configuration to simplify
> >>> logging/potential problems.
> >>> See what is logged with LogLevel trace8.
> >>> Configure the MPM to use a single child process to handle requests,
> >>> and run strace against that.
> >>>
> >>> --
> >>> Born in Roswell... married an alien...
> >>> http://emptyhammock.com/
> >>
> >>
> >
>
>
>
> --
> Born in Roswell... married an alien...
> http://emptyhammock.com/
>
Re: Help reqd. for httpd-2.4.2
Posted by Jeff Trawick <tr...@gmail.com>.
On Thu, Oct 11, 2012 at 3:09 AM, Jitesh Verma <ji...@gmail.com> wrote:
> Jeff,
> We tried LogLevel trace8. It indicates "Response was sent with status 200".
> But we are not sure whether the response packet was handed over to TCP/IP
> statck properly. We are puzzled. We need to double check if something is
> wrong with the network settings of our box itself.
Maybe some APR settings are wrong due to the cross-compile??? The
strace might show something interesting, either because of something
that is present or something that is absent.
>
> Thanks,
> Jitesh
>
> On Wed, Oct 10, 2012 at 7:54 PM, Jitesh Verma <ji...@gmail.com>
> wrote:
>>
>> Hi Jeff,
>> Thanks for your reply.
>> I had added only the first 8 modules in httpd.conf. Remaining modules were
>> added later only when I started facing this problem. Reducing the number of
>> modules back to 8 does not make any difference with respect to this issue.
>> With these 8 modules httpd worked fine with port 80. The problem started
>> when I tried adding additional ports. Adding more ports is need of the hour.
>> I can not escape it. I have run strace with "follow the fork" option (rather
>> than single process). There are only 4 processess to follow. strace output
>> did not help. It does not indicate any error condition as such. I can make
>> it run as a single process by running httpd with -X option in foreground.
>> But I am not sure whether that is going to help. Anyway, I will try that.
>>
>> Thanks,
>> Jitesh
>>
>> On Wed, Oct 10, 2012 at 6:47 PM, Jeff Trawick <tr...@gmail.com> wrote:
>>>
>>> On Wed, Oct 10, 2012 at 7:55 AM, Jitesh Verma <ji...@gmail.com>
>>> wrote:
>>> > Hi List,
>>> > 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 handle XML requests from
>>> > our
>>> > Applets. We have added all the 80 odd .so modules (that get built with
>>> > default "configure" settings) in httpd.conf.
>>> > We are able to access the box's GUI/Applets with "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 Internet Explorer fails to get any response from httpd:
>>> > http://192.168.0.1
>>> > http://192.168.0.1:80
>>> > http://192.168.0.1:9000
>>> >
>>> > Wireshark packet trace indicates that the request packet is correctly
>>> > sent
>>> > to TCP port 80 when request http://192.168.0.1 is sent from browser.
>>> > However, the outgoing packet is missing from the packet trace. It seems
>>> > httpd did not generate any response (not even "File not found"
>>> > response).
>>> > "netstat -tnlp" command shows httpd listening 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 outgoing).
>>> > The moment additional "Listen 9000" directive is removed from
>>> > httpd.conf,
>>> > httpd starts working fine (starts serving http://192.168.0.1 request).
>>> > We have enabled and configured "debugging" and "loggers" modules.
>>> > Still,
>>> > /var/log/error_log and /var/log/messages do not show any error or
>>> > warning.
>>> >
>>> > We thought adding another "Listen" directive to httpd.conf is a child's
>>> > play, but it seems to be a humongous task.
>>> > Are we missing something? Am I doing something wrong?? Is it a bug???
>>> > Can
>>> > someone help in this forum? How to debug this issue?
>>> >
>>> > Please find attached httpd.conf and configure wrapper script
>>> > (configure.wrapper) used for configuring and building httpd and its
>>> > components.
>>> >
>>> > Thanks,
>>> > Jitesh
>>>
>>> users@httpd.apache.org is a better mailing list for this.
>>>
>>> A few things to start with...
>>>
>>> Get unnecessary modules out of the configuration to simplify
>>> logging/potential problems.
>>> See what is logged with LogLevel trace8.
>>> Configure the MPM to use a single child process to handle requests,
>>> and run strace against that.
>>>
>>> --
>>> Born in Roswell... married an alien...
>>> http://emptyhammock.com/
>>
>>
>
--
Born in Roswell... married an alien...
http://emptyhammock.com/
Re: Help reqd. for httpd-2.4.2
Posted by Jitesh Verma <ji...@gmail.com>.
Firewall is disabled. So, if packet is handed over to TCP/IP statck, it
won't get dropped.
On Thu, Oct 11, 2012 at 12:39 PM, Jitesh Verma <ji...@gmail.com>wrote:
> Jeff,
> We tried LogLevel trace8. It indicates "Response was sent with status
> 200". But we are not sure whether the response packet was handed over to
> TCP/IP statck properly. We are puzzled. We need to double check
> if something is wrong with the network settings of our box itself.
>
> Thanks,
> Jitesh
>
> On Wed, Oct 10, 2012 at 7:54 PM, Jitesh Verma <ji...@gmail.com>wrote:
>
>> Hi Jeff,
>> Thanks for your reply.
>> I had added only the first 8 modules in httpd.conf. Remaining modules
>> were added later only when I started facing this problem. Reducing the
>> number of modules back to 8 does not make any difference with respect to
>> this issue. With these 8 modules httpd worked fine with port 80. The
>> problem started when I tried adding additional ports. Adding more ports is
>> need of the hour. I can not escape it. I have run strace with "follow the
>> fork" option (rather than single process). There are only 4 processess to
>> follow. strace output did not help. It does not indicate any error
>> condition as such. I can make it run as a single process by running httpd
>> with -X option in foreground. But I am not sure whether that is going to
>> help. Anyway, I will try that.
>>
>> Thanks,
>> Jitesh
>>
>> On Wed, Oct 10, 2012 at 6:47 PM, Jeff Trawick <tr...@gmail.com> wrote:
>>
>>> On Wed, Oct 10, 2012 at 7:55 AM, Jitesh Verma <ji...@gmail.com>
>>> wrote:
>>> > Hi List,
>>> > 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 handle XML requests from
>>> our
>>> > Applets. We have added all the 80 odd .so modules (that get built with
>>> > default "configure" settings) in httpd.conf.
>>> > We are able to access the box's GUI/Applets with "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 Internet Explorer fails to get any response from httpd:
>>> > http://192.168.0.1
>>> > http://192.168.0.1:80 <http://192.168.0.1/>
>>> > http://192.168.0.1:9000
>>> >
>>> > Wireshark packet trace indicates that the request packet is correctly
>>> sent
>>> > to TCP port 80 when request http://192.168.0.1 is sent from browser.
>>> > However, the outgoing packet is missing from the packet trace. It seems
>>> > httpd did not generate any response (not even "File not found"
>>> response).
>>> > "netstat -tnlp" command shows httpd listening 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 outgoing).
>>> > The moment additional "Listen 9000" directive is removed from
>>> httpd.conf,
>>> > httpd starts working fine (starts serving http://192.168.0.1 request).
>>> > We have enabled and configured "debugging" and "loggers" modules.
>>> Still,
>>> > /var/log/error_log and /var/log/messages do not show any error or
>>> warning.
>>> >
>>> > We thought adding another "Listen" directive to httpd.conf is a child's
>>> > play, but it seems to be a humongous task.
>>> > Are we missing something? Am I doing something wrong?? Is it a bug???
>>> Can
>>> > someone help in this forum? How to debug this issue?
>>> >
>>> > Please find attached httpd.conf and configure wrapper script
>>> > (configure.wrapper) used for configuring and building httpd and its
>>> > components.
>>> >
>>> > Thanks,
>>> > Jitesh
>>>
>>> users@httpd.apache.org is a better mailing list for this.
>>>
>>> A few things to start with...
>>>
>>> Get unnecessary modules out of the configuration to simplify
>>> logging/potential problems.
>>> See what is logged with LogLevel trace8.
>>> Configure the MPM to use a single child process to handle requests,
>>> and run strace against that.
>>>
>>> --
>>> Born in Roswell... married an alien...
>>> http://emptyhammock.com/
>>>
>>
>>
>
Re: Help reqd. for httpd-2.4.2
Posted by Jitesh Verma <ji...@gmail.com>.
Jeff,
We tried LogLevel trace8. It indicates "Response was sent with status 200".
But we are not sure whether the response packet was handed over to TCP/IP
statck properly. We are puzzled. We need to double check if something is
wrong with the network settings of our box itself.
Thanks,
Jitesh
On Wed, Oct 10, 2012 at 7:54 PM, Jitesh Verma <ji...@gmail.com>wrote:
> Hi Jeff,
> Thanks for your reply.
> I had added only the first 8 modules in httpd.conf. Remaining modules were
> added later only when I started facing this problem. Reducing the number of
> modules back to 8 does not make any difference with respect to this issue.
> With these 8 modules httpd worked fine with port 80. The problem started
> when I tried adding additional ports. Adding more ports is need of the
> hour. I can not escape it. I have run strace with "follow the fork" option
> (rather than single process). There are only 4 processess to follow. strace
> output did not help. It does not indicate any error condition as such. I
> can make it run as a single process by running httpd with -X option in
> foreground. But I am not sure whether that is going to help. Anyway, I will
> try that.
>
> Thanks,
> Jitesh
>
> On Wed, Oct 10, 2012 at 6:47 PM, Jeff Trawick <tr...@gmail.com> wrote:
>
>> On Wed, Oct 10, 2012 at 7:55 AM, Jitesh Verma <ji...@gmail.com>
>> wrote:
>> > Hi List,
>> > 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 handle XML requests from our
>> > Applets. We have added all the 80 odd .so modules (that get built with
>> > default "configure" settings) in httpd.conf.
>> > We are able to access the box's GUI/Applets with "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 Internet Explorer fails to get any response from httpd:
>> > http://192.168.0.1
>> > http://192.168.0.1:80 <http://192.168.0.1/>
>> > http://192.168.0.1:9000
>> >
>> > Wireshark packet trace indicates that the request packet is correctly
>> sent
>> > to TCP port 80 when request http://192.168.0.1 is sent from browser.
>> > However, the outgoing packet is missing from the packet trace. It seems
>> > httpd did not generate any response (not even "File not found"
>> response).
>> > "netstat -tnlp" command shows httpd listening 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 outgoing).
>> > The moment additional "Listen 9000" directive is removed from
>> httpd.conf,
>> > httpd starts working fine (starts serving http://192.168.0.1 request).
>> > We have enabled and configured "debugging" and "loggers" modules. Still,
>> > /var/log/error_log and /var/log/messages do not show any error or
>> warning.
>> >
>> > We thought adding another "Listen" directive to httpd.conf is a child's
>> > play, but it seems to be a humongous task.
>> > Are we missing something? Am I doing something wrong?? Is it a bug???
>> Can
>> > someone help in this forum? How to debug this issue?
>> >
>> > Please find attached httpd.conf and configure wrapper script
>> > (configure.wrapper) used for configuring and building httpd and its
>> > components.
>> >
>> > Thanks,
>> > Jitesh
>>
>> users@httpd.apache.org is a better mailing list for this.
>>
>> A few things to start with...
>>
>> Get unnecessary modules out of the configuration to simplify
>> logging/potential problems.
>> See what is logged with LogLevel trace8.
>> Configure the MPM to use a single child process to handle requests,
>> and run strace against that.
>>
>> --
>> Born in Roswell... married an alien...
>> http://emptyhammock.com/
>>
>
>
Re: Help reqd. for httpd-2.4.2
Posted by Guenter Knauf <fu...@apache.org>.
Hi Jitesh,
Am 10.10.2012 16:24, schrieb Jitesh Verma:
> > We are able to access the box's GUI/Applets with "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.
I just did a quick test with httpd-2.4.3 on Windows and NetWare, and
both work fine with your configuration:
Listen 80
Listen 9000
httpd serves both ports as it should.
One thing I found though: before I did look into the manual I did just
wrongly configure:
Listen 80 9000
this leaded to multiple crashes (on Windows) where nothing was logged to
the error log; but eventlog entries:
Fehlgeschlagene Anwendung httpd.exe, Version 2.4.3.0, fehlgeschlagenes
Modul libhttpd.dll, Version 2.4.3.0, Fehleradresse 0x00028628.
so seems we could here do a better check for the 2nd parameter ...
Gün.
Re: Help reqd. for httpd-2.4.2
Posted by Jitesh Verma <ji...@gmail.com>.
Hi Jeff,
Thanks for your reply.
I had added only the first 8 modules in httpd.conf. Remaining modules were
added later only when I started facing this problem. Reducing the number of
modules back to 8 does not make any difference with respect to this issue.
With these 8 modules httpd worked fine with port 80. The problem started
when I tried adding additional ports. Adding more ports is need of the
hour. I can not escape it. I have run strace with "follow the fork" option
(rather than single process). There are only 4 processess to follow. strace
output did not help. It does not indicate any error condition as such. I
can make it run as a single process by running httpd with -X option in
foreground. But I am not sure whether that is going to help. Anyway, I will
try that.
Thanks,
Jitesh
On Wed, Oct 10, 2012 at 6:47 PM, Jeff Trawick <tr...@gmail.com> wrote:
> On Wed, Oct 10, 2012 at 7:55 AM, Jitesh Verma <ji...@gmail.com>
> wrote:
> > Hi List,
> > 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 handle XML requests from our
> > Applets. We have added all the 80 odd .so modules (that get built with
> > default "configure" settings) in httpd.conf.
> > We are able to access the box's GUI/Applets with "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 Internet Explorer fails to get any response from httpd:
> > http://192.168.0.1
> > http://192.168.0.1:80 <http://192.168.0.1/>
> > http://192.168.0.1:9000
> >
> > Wireshark packet trace indicates that the request packet is correctly
> sent
> > to TCP port 80 when request http://192.168.0.1 is sent from browser.
> > However, the outgoing packet is missing from the packet trace. It seems
> > httpd did not generate any response (not even "File not found" response).
> > "netstat -tnlp" command shows httpd listening 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 outgoing).
> > The moment additional "Listen 9000" directive is removed from httpd.conf,
> > httpd starts working fine (starts serving http://192.168.0.1 request).
> > We have enabled and configured "debugging" and "loggers" modules. Still,
> > /var/log/error_log and /var/log/messages do not show any error or
> warning.
> >
> > We thought adding another "Listen" directive to httpd.conf is a child's
> > play, but it seems to be a humongous task.
> > Are we missing something? Am I doing something wrong?? Is it a bug??? Can
> > someone help in this forum? How to debug this issue?
> >
> > Please find attached httpd.conf and configure wrapper script
> > (configure.wrapper) used for configuring and building httpd and its
> > components.
> >
> > Thanks,
> > Jitesh
>
> users@httpd.apache.org is a better mailing list for this.
>
> A few things to start with...
>
> Get unnecessary modules out of the configuration to simplify
> logging/potential problems.
> See what is logged with LogLevel trace8.
> Configure the MPM to use a single child process to handle requests,
> and run strace against that.
>
> --
> Born in Roswell... married an alien...
> http://emptyhammock.com/
>
Re: Help reqd. for httpd-2.4.2
Posted by Jeff Trawick <tr...@gmail.com>.
On Wed, Oct 10, 2012 at 7:55 AM, Jitesh Verma <ji...@gmail.com> wrote:
> Hi List,
> 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 handle XML requests from our
> Applets. We have added all the 80 odd .so modules (that get built with
> default "configure" settings) in httpd.conf.
> We are able to access the box's GUI/Applets with "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 Internet Explorer fails to get any response from httpd:
> http://192.168.0.1
> http://192.168.0.1:80
> http://192.168.0.1:9000
>
> Wireshark packet trace indicates that the request packet is correctly sent
> to TCP port 80 when request http://192.168.0.1 is sent from browser.
> However, the outgoing packet is missing from the packet trace. It seems
> httpd did not generate any response (not even "File not found" response).
> "netstat -tnlp" command shows httpd listening 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 outgoing).
> The moment additional "Listen 9000" directive is removed from httpd.conf,
> httpd starts working fine (starts serving http://192.168.0.1 request).
> We have enabled and configured "debugging" and "loggers" modules. Still,
> /var/log/error_log and /var/log/messages do not show any error or warning.
>
> We thought adding another "Listen" directive to httpd.conf is a child's
> play, but it seems to be a humongous task.
> Are we missing something? Am I doing something wrong?? Is it a bug??? Can
> someone help in this forum? How to debug this issue?
>
> Please find attached httpd.conf and configure wrapper script
> (configure.wrapper) used for configuring and building httpd and its
> components.
>
> Thanks,
> Jitesh
users@httpd.apache.org is a better mailing list for this.
A few things to start with...
Get unnecessary modules out of the configuration to simplify
logging/potential problems.
See what is logged with LogLevel trace8.
Configure the MPM to use a single child process to handle requests,
and run strace against that.
--
Born in Roswell... married an alien...
http://emptyhammock.com/
Re: Help reqd. for httpd-2.4.2
Posted by Jitesh Verma <ji...@gmail.com>.
Hi Graham,
Thanks for your reply.
Please see my reply in-line.
On Wed, Oct 10, 2012 at 6:49 PM, Graham Leggett <mi...@sharp.fm> wrote:
> On 10 Oct 2012, at 1:55 PM, Jitesh Verma <ji...@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 handle 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 80
> modules to your server? Ideally, you should only load the modules you need,
> 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" did not work. I
was just trying to see if loading all the modules make any 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/mod_unixd.so
LoadModule dir_module modules/mod_dir.so
LoadModule cgi_module modules/mod_cgi.so
LoadModule mime_module modules/mod_mime.so
LoadModule alias_module modules/mod_alias.
>
> We are able to access the box's GUI/Applets with "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 Internet Explorer fails to get any response from httpd:
> http://192.168.0.1
> http://192.168.0.1:80 <http://192.168.0.1/>
> http://192.168.0.1:9000
>
> Wireshark packet trace indicates that the request packet is correctly sent
> to TCP port 80 when request http://192.168.0.1 is sent from browser.
> However, the outgoing packet is missing from the packet trace. It seems
> httpd did not generate any response (not even "File not found" response).
>
>
> TCP involves the exchange of many packets to establish a connection, and
> if a connection is not successfully established you cannot expect a higher
> level response of any kind. I would first ensure that a TCP connection is
> possible to establish properly before worrying about something running
> above it.
>
<Jitesh> Packet trace shows that TCP session is getting established
successfully. After that, httpd does receive the first HTTP request from
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 listening 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 outgoing).
> The moment additional "Listen 9000" directive is removed from httpd.conf,
> httpd starts working fine (starts serving http://192.168.0.1 request).
> We have enabled and configured "debugging" and "loggers" modules. Still,
> /var/log/error_log and /var/log/messages do not show any error or warning.
>
>
> We thought adding another "Listen" directive to httpd.conf is a child's
> play, but it seems to be a humongous task.
>
>
> 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 wrong?? Is it a bug??? Can
> someone help in this forum? How to debug this issue?
>
> Please find attached httpd.conf and configure wrapper script
> (configure.wrapper) used for configuring and building httpd and its
> components.
>
>
> Looking at your configure script that looks very wrong - you've overridden
> all sorts of low level options without indicating clearly why you've done
> so. As you're on what seems like custom hardware, I would get 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 underlying
> 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 determine
these valuses as this is cross-compilation case. Those options are correct
to the best my knowledge. APR and APR-Util builds cleanly. shared libraries
(.so) of libapr, libapr-util, libpcre and libexpat have been installed
properly. These libs get loaded by httpd without any error. I am not using
any 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
wrong.
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
> --
>
>
Re: Help reqd. for httpd-2.4.2
Posted by Graham Leggett <mi...@sharp.fm>.
On 10 Oct 2012, at 1:55 PM, Jitesh Verma <ji...@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 handle 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 80 modules to your server? Ideally, you should only load the modules you need, and no more.
> We are able to access the box's GUI/Applets with "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 Internet Explorer fails to get any response from httpd:
> http://192.168.0.1
> http://192.168.0.1:80
> http://192.168.0.1:9000
>
> Wireshark packet trace indicates that the request packet is correctly sent to TCP port 80 when request http://192.168.0.1 is sent from browser. However, the outgoing packet is missing from the packet trace. It seems httpd did not generate any response (not even "File not found" response).
TCP involves the exchange of many packets to establish a connection, and if a connection is not successfully established you cannot expect a higher level response of any kind. I would first ensure that a TCP connection is possible to establish properly before worrying about something running above it.
> "netstat -tnlp" command shows httpd listening 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 outgoing).
> The moment additional "Listen 9000" directive is removed from httpd.conf, httpd starts working fine (starts serving http://192.168.0.1 request).
> We have enabled and configured "debugging" and "loggers" modules. Still, /var/log/error_log and /var/log/messages do not show any error or warning.
>
> We thought adding another "Listen" directive to httpd.conf is a child's play, but it seems to be a humongous task.
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 wrong?? Is it a bug??? Can someone help in this forum? How to debug this issue?
>
> Please find attached httpd.conf and configure wrapper script (configure.wrapper) used for configuring and building httpd and its components.
Looking at your configure script that looks very wrong - you've overridden all sorts of low level options without indicating clearly why you've done so. As you're on what seems like custom hardware, I would get 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 underlying libraries haven't been installed or configured properly httpd and any other app that depends on apr/apr-util are certain not to work.
Regards,
Graham
--