Hi, here it is: Normal FastCGI-Application (not using witty):[Fri Mar 13 12:30:48 2009] [warn] FastCGI: (dynamic) server "/srv/www/fcgi-bin/hello.fcg" started (pid 4601) [Fri Mar 13 12:30:48 2009] [error] [client 127.0.0.1] FastCGI: incomplete headers (0 bytes) received from server "/srv/www/fcgi-bin/hello.fcg"
hello.wt-application:[Fri Mar 13 12:31:03 2009] [warn] FastCGI: (dynamic) server "/srv/www/fcgi-bin/hello/hello.wt" started (pid 4603)
stat: No such file or directory
Document root ("") not valid.
[Fri Mar 13 12:31:04 2009] [warn] FastCGI: (dynamic) server
"/srv/www/fcgi-bin/hello/hello.wt" (pid 4603) terminated by calling exit
with status '1'
And for this, I have the question: how to set the document root for fastcgi? Greetings Torsten Am 13.03.2009 08:14, schrieb Koen Deforche:
Hey Torsten, 2009/3/12 Torsten Schulz<[email protected]>:Hi, yes, I'm sorry. Here are the Log, but I don't know why it don't work: [Wed Mar 11 19:51:21 2009] [warn] mod_fcgid: Read data error, fastcgi server has close connection [Wed Mar 11 19:51:21 2009] [error] [client ::1] Premature end of script headers: test.fcg [Wed Mar 11 19:51:27 2009] [notice] mod_fcgid: process /srv/www/htdocs/test.fcg(22869) exit(communication error), get unexpected signal 11This indicates that Wt's FastCGI handler crashed...and [Thu Mar 12 22:00:55 2009] [warn] (104)Connection reset by peer: mod_fcgid: read data from fastcgi server error. [Thu Mar 12 22:00:55 2009] [error] [client 127.0.0.1] Premature end of script headers: hello.wt [Thu Mar 12 22:00:59 2009] [notice] mod_fcgid: process /srv/www/htdocs/hello.wt(4574) exit(communication error), terminated by calling exit(), return code: 1Here, Wt detects a major problem and quits. Can you try the same with FastCGI? We are still missing the output from the Wt processes themselves: by experience we know that FastCGI outputs this also to the Apache error log, while mod_fcgid does not always do that. Some things that could be wrong: - ld-library path problems: perhaps the 'apache' user (the uid which runs the webserver) does not have access to the correct libwt.so and libwthttp.so versions. You could mitigate this also by building static libraries (SHARED_LIBS = OFF) - the apache user may also not have proper write access to the /usr/wt/run directory needed for keeping tracking of sessions Regards, koen ------------------------------------------------------------------------------ Apps built with the Adobe(R) Flex(R) framework and Flex Builder(TM) are powering Web 2.0 with engaging, cross-platform capabilities. Quickly and easily build your RIAs with Flex Builder, the Eclipse(TM)based development software that enables intelligent coding and step-through debugging. Download the free 60 day trial. http://p.sf.net/sfu/www-adobe-com _______________________________________________ witty-interest mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/witty-interest
------------------------------------------------------------------------------ Apps built with the Adobe(R) Flex(R) framework and Flex Builder(TM) are powering Web 2.0 with engaging, cross-platform capabilities. Quickly and easily build your RIAs with Flex Builder, the Eclipse(TM)based development software that enables intelligent coding and step-through debugging. Download the free 60 day trial. http://p.sf.net/sfu/www-adobe-com
_______________________________________________ witty-interest mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/witty-interest
