Earlier today I did a "sudo gem install fcgi" because I new fcgi ruby gem was supposedly released that fixed some things like a bad memory leak. Upon apache restart, fcgi would not work. This came up with some errors "No definition for fcgi_finish" and many like it, although it reported success.
the log files say:
[Thu Jun 16 14:59:02 2005] [error] [client xx.169.85.248] FastCGI: comm with (dynamic) server "/home/polarity/public/dispatch.fcgi" aborted:
(first read) idle timeout (30 sec)
[Thu Jun 16 14:59:02 2005] [error] [client xx.169.85.248] FastCGI:
incomplete headers (0 bytes) received from server "/home/polarity/public/dispatch.fcgi"
My original FastCGI install steps (done 2 months ago, worked the entire time)
# wget http://www.fastcgi.com/dist/mod_fastcgi-2.4.2.tar.gz
# tar xvzf mod_fastcgi-2.4.2.tar.gz
# cd mod_fastcgi-2.4.2
# /usr/local/apache/bin/apxs -o mod_fastcgi.so -c *.c
# /usr/local/apache/bin/apxs -i -a -n fastcgi mod_fastcgi.so
This should create an entry in httpd.conf that looks like this:
LoadModule fastcgi_module <some_path>/mod_fastcgi.so
Note that if there's a ClearModuleList directive after new entry,
you'll have to either move the LoadModule after the ClearModuleList
or add (have a look at how the other modules are handled):
AddModule mod_fastcgi.c
3. Edit the httpd configuration file(s) to enable your FastCGI
application(s). See docs/mod_fastcgi.html for details.
If you want to wrap the mod_fastcgi directives, use:
<IfModule mod_fastcgi.c>
.
.
</IfModule>
4. Stop and start the server.
# /etc/init.d/httpd stop
# /etc/init.d/httpd startssl
Any help is appreciated!



LinkBack URL
About LinkBacks




