fpCGI failure

[Tyler]

On Thu, Mar 13, 2008 at 10:47 AM, Nancy Palmquist <nlp at vss3.com> wrote:

> Tyler wrote:
> > fpCGI, both v1 and 2, bombs out on our Apache2 web server running
> > fp5.0.14 on SCO OS 6.  It simply stops outputting HTML files for any
> > rreports run.  It requires rebooting the entire machine to get it going
> > again.  Running the commands thru fpcgi that it was stalling on works
> > perfectly fine after the reboot.
> >
> > Via our resller via Ray at fptech, Ron at fptech says that it looks like
> > an application error, and that we should just set Field_nohtmlfound to
> > some other page.  This is obviously unsatisfactory.
> >
> > Can anyone shed any light on this, or how to avoid it?
> >
> > Tyler
> >
> >
> > ------------------------------------------------------------------------
> >
> > _______________________________________________
> > Filepro-list mailing list
> > Filepro-list at lists.celestial.com
> > http://mailman.celestial.com/mailman/listinfo/filepro-list
>
> I use fpCGI 2.0 extensively, and I am not sure you might not be
> experiencing a
> timing issue.
>
> End the filepro command line with something like this:
>
> 1>/tmp/report1 2>/tmp/report2
>
> I use this for troubleshooting and just change the "report" part to
> indicate
> which process is running so I can tell them apart.
>
> Run your app and then look to see if /tmp/report2 has anything (errors go
> here)
>
> Maybe you are getting an error that is displaying in /tmp/report1.
>
> You might find a Deleted Key error (the kind I seem to get in this type of
> hang).
>
> Also maybe something is not waiting long enough.  Make sure you do not
> have
> fpCGI only waiting 20 sec, but your report takes 30 sec to run.
>
> I think it is possible to set Apache2 to timeout also.  Review this
> settings.
>
> Hope that helps.  Mine has worked so long without issue, I hardly look at
> stuff
> anymore.
>
> Nancy
>

Thanks for the advice Nancy!

We already tried the output redirect, with no error output. :(

We suppress deleted key errors via an environment variable :(

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.

Our apache2 timeout is 60sec, I believe.

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.

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.

Tyler
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.celestial.com/pipermail/filepro-list/attachments/20080313/8260b4a0/attachment.html