On 2006-08-07 11:19:04 -0600, Jack L <[EMAIL PROTECTED]> said:
Hello,
This is my first posting to the list - I just started
playing with Cherokee from yesterday :)
I'm trying to use PHP with FastCGI on Windows.
Here's the fcgi part of my conf:
Extension php {
Handler fcgi {
Server localhost:8002 {
Env PHP_FCGI_MAX_REQUESTS "-1"
Env PHP_FCGI_CHILDREN "5"
Interpreter "c:\Internet\Cherokee\php.exe -b 8002"
}
}
}
I first tried the PHP Windows binaries but both php.exe
and php-cgi.exe didn't work. I didn't expect php.exe to
work because I think it's the CLI version. I made sure
php-cgi.exe supports fastcgi by checking "php-cgi -v" and
it shows "cgi-fcgi". However, Cherokee can not start it
and "php-cgi -h" does not show an option of specifying a
port for it to bind to. I have experience setting php-cgi.exe
up with Abyss Web Server. In that test, I had to use pipe.
Socket did not work. So my conclusion is that php-cgi only
supports PIPE connection between web server and itself, but
not sockets. This ends my test with the PHP windows binaries.
I then tried the PHP I built from source with cygwin. I have
the fastcgi support built into it and it also replies "cgi-fcgi"
in "php.exe -v" test. However, it did not work either. Cherokee
does not start a PHP instance even though I have the "Interpreter"
line in the conf file. So I manually started a php fastcgi server
with "php.exe -b 8002" and PHP works with FastCGI.
So the question is, why doesn't Cherokee start a PHP process?
Also, when I ApacheBench-ed it, Cherokee dies (stops responding
although port is still open) after getting a few hundred requests
with 10 concurrent connections. Sometimes php.exe exits. I can not
explain if it's a problem in php.exe or not but the same php.exe
works very reliably with another web server in fastcgi set up so
I suspect the issue is on the Cherokee side.
Another question. I always get this on Cherokee start up:
IMPORTANT: This "fastcgi" module is NOT ready to be used. Please
modify your configuration in order to use the "fastcgi" module
instead.
I get this even when I manually start a PHP instance before I
start Cherokee. I'm using the Windows installer.
I came this same problem and discovered that IPv6 needs to be disabled. I
am on OS X so I was just able to re-compile Cherokee and it solved the
problem. As for the Windows binary of Cherokee, I am not too sure how that
will work. I would call it a bug in Cherokee period which would need to get
resolved.
_______________________________________________
Cherokee mailing list
[email protected]
http://www.0x50.org/cgi-bin/mailman/listinfo/cherokee
