<br><br><div class="gmail_quote">On Thu, Mar 13, 2008 at 10:47 AM, Nancy Palmquist <<a href="mailto:nlp@vss3.com">nlp@vss3.com</a>> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div><div></div><div class="Wj3C7c">Tyler wrote:<br>
> fpCGI, both v1 and 2, bombs out on our Apache2 web server running<br>
> fp5.0.14 on SCO OS 6. It simply stops outputting HTML files for any<br>
> rreports run. It requires rebooting the entire machine to get it going<br>
> again. Running the commands thru fpcgi that it was stalling on works<br>
> perfectly fine after the reboot.<br>
><br>
> Via our resller via Ray at fptech, Ron at fptech says that it looks like<br>
> an application error, and that we should just set Field_nohtmlfound to<br>
> some other page. This is obviously unsatisfactory.<br>
><br>
> Can anyone shed any light on this, or how to avoid it?<br>
><br>
> Tyler<br>
><br>
><br>
</div></div><div class="Ih2E3d">> ------------------------------------------------------------------------<br>
><br>
> _______________________________________________<br>
> Filepro-list mailing list<br>
> <a href="mailto:Filepro-list@lists.celestial.com">Filepro-list@lists.celestial.com</a><br>
> <a href="http://mailman.celestial.com/mailman/listinfo/filepro-list" target="_blank">http://mailman.celestial.com/mailman/listinfo/filepro-list</a><br>
<br>
</div>I use fpCGI 2.0 extensively, and I am not sure you might not be experiencing a<br>
timing issue.<br>
<br>
End the filepro command line with something like this:<br>
<br>
1>/tmp/report1 2>/tmp/report2<br>
<br>
I use this for troubleshooting and just change the "report" part to indicate<br>
which process is running so I can tell them apart.<br>
<br>
Run your app and then look to see if /tmp/report2 has anything (errors go here)<br>
<br>
Maybe you are getting an error that is displaying in /tmp/report1.<br>
<br>
You might find a Deleted Key error (the kind I seem to get in this type of hang).<br>
<br>
Also maybe something is not waiting long enough. Make sure you do not have<br>
fpCGI only waiting 20 sec, but your report takes 30 sec to run.<br>
<br>
I think it is possible to set Apache2 to timeout also. Review this settings.<br>
<br>
Hope that helps. Mine has worked so long without issue, I hardly look at stuff<br>
anymore.<br>
<br>
Nancy<br>
</blockquote></div><br>Thanks for the advice Nancy! <br><br>We already tried the output redirect, with no error output. :(<br><br>We suppress deleted key errors via an environment variable :(<br><br>The wait time is a possibility, but I don't think it would prevent every subsequent report on any table being run by fpcgi - it would just keep that one report from outputting. Besides, these are very simple reports, and when run manually usually take milliseconds.<br>
<br>Our apache2 timeout is 60sec, I believe.<br><br>I'm glad your setup works well. Ours never has, and neither has filepro. My particular favourite is when filepro spontaneously gives syntax errors on import or export commands when you try to save a processing table. If you then save without a syntax check, go back in, and save again the second time with a syntax check, it won't complain. It will do this even if you don't edit the processing table, just look at it and then save it.<br>
<br>While others on this list go on about fp's reliability and stability, I have never found our setup to behave so. If someone could resolve these issues for us and is here in Phoenix, we would certainly consider contracting them for our sysadmin issues and maintenance, as our current contractor hasn't been able to solve these and other issues for the two years I've been here.<br>
<br>Tyler<br>