caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: "Anders Thøgersen" <anders@bladre.dk>
To: Christophe TROESTLER <Christophe.Troestler+ocaml@umons.ac.be>
Cc: caml-list@yquem.inria.fr
Subject: Re: [Caml-list] Netcgi_fcgi
Date: Thu, 16 Jul 2009 17:08:54 +0200	[thread overview]
Message-ID: <20090716150854.GA16324@debian> (raw)
In-Reply-To: <20090716.162741.668523372145744396.Christophe.Troestler+ocaml@umons.ac.be>

Hello,

On 16:27 Thu 16 Jul 2009, Christophe TROESTLER wrote:
> On Thu, 16 Jul 2009 13:27:55 +0200, Anders Thøgersen wrote:
> > 
> > Hello,
> > 
> > I am trying to get the fastcgi examples from netcgi2 to work, but am
> > having some problems with this.  I am running with apache2 and
> > mod_fcgid.
> > 
> > I have compiled the counter_fcgi example with ocamlopt and copied the
> > executable to my fcgid directory.
> 
> You should be aware that there are several ways for a web server to
> contact a FCGI script.  According to what you say, you are expecting
> the web server to start (then and contact the script on stdin), in
> which case you have to comment out the "sockaddr" argument (see
> netcgi_fcgi.mli).  The counter_fcgi.ml example, as it prints on

I have also tried this, but to no avail. I still get an internal server
error and a message about a timeout in the logs.

> stdout, expects to be started manually and be contacted by the web
> server on port 1200.  Please see the FCGI doc about how to do that.
> http://www.fastcgi.com/mod_fastcgi/docs/mod_fastcgi.html 

I believe I have done this part correctly, though. Here's a sample
session when starting the program from the commandline as you suggest:

    $ ./counter.fcgi
    ./counter.fcgi (FCGI) listening on port 1200.

And in another shell:

    $ lynx 127.0.0.1:1200

This waits indefinately.  A timeout is also what is reported by
mod_fastcgi.

Maybe I am missing something very obviuos.  Often that is a reason for
obscure problems like this  :-/

> 
> If you believe that the examples should tell more about how FCGI
> connectors work, feel free to write some comment to put at the
> beginning of the files and send it to me.

Yes, I must admint that my knowledge of the FCGI protocol is limited.  I
will gladly do this once I get to the bottom of this problem.

Regards
Anders

> Best,
> C.
> 
> _______________________________________________
> Caml-list mailing list. Subscription management:
> http://yquem.inria.fr/cgi-bin/mailman/listinfo/caml-list
> Archives: http://caml.inria.fr
> Beginner's list: http://groups.yahoo.com/group/ocaml_beginners
> Bug reports: http://caml.inria.fr/bin/caml-bugs
> 
> 


  reply	other threads:[~2009-07-16 15:08 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-16 11:27 Netcgi_fcgi Anders Thøgersen
     [not found] ` <BB046CA812535C45BD0029AA9D04BA7906676353@KL-SRV57.lmsintl.com>
2009-07-16 13:31   ` [Caml-list] Netcgi_fcgi Anders Thøgersen
2009-07-16 14:27 ` Christophe TROESTLER
2009-07-16 15:08   ` Anders Thøgersen [this message]
2009-07-17 13:12     ` Christophe TROESTLER
2009-07-17 14:22       ` Anders Thøgersen
2009-07-17 14:33       ` Christophe TROESTLER
2009-07-22 12:57         ` Anders Thøgersen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20090716150854.GA16324@debian \
    --to=anders@bladre.dk \
    --cc=Christophe.Troestler+ocaml@umons.ac.be \
    --cc=caml-list@yquem.inria.fr \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).