Linux Centos and fpCGI

[John Sica]

Not sure if this is going to help, but there are logs in the cgi-bin 
directory that might help. (using Filepro 5.6 and fpcgi 2.0 with Apache 
2.  The OS is Openserver OSR6.

If your not getting logs like these, then you might not have the right 
permissions on the cgi-bin directory. We had to make them 777 to get it 
to work.  AND when it wasn't set properly, the error output was 
concatenated to the key file.  The .err files are text files, but the 
.out are not.  However, when there were no errors, fpcgi would work 
properly.  I just thought knowing these files were there might help.

-rw-r--r--    1 filepro  group       1317 Feb  7 06:00 fpcgi29890.out
-rw-r--r--    1 filepro  group          0 Feb  7 06:00 fpcgi29890.err
-rw-r--r--    1 filepro  group        201 Feb  4 18:34 fpcgi6504.err
-rw-r--r--    1 filepro  group        201 Feb  4 18:34 fpcgi6500.err
-rw-r--r--    1 filepro  group        253 Feb  4 06:47 fpcgi29846.err
-rw-r--r--    1 filepro  group        253 Feb  4 06:47 fpcgi29813.err
-rw-r--r--    1 filepro  group        204 Feb  3 15:18 fpcgi28896.err
-rw-r--r--    1 filepro  group        198 Feb  3 15:17 fpcgi28840.err


John


On 2/7/2011 9:08 AM, Nancy Palmquist wrote:
> My Esteemed Collegues,
>
> We are changing a server that was running SuSE Linux to Centos and are
> having difficulty getting fpCGI to work correctly.  FilePro version is
> 5.0 - it has run flawlessly with these processes for years.
>
> General functioning of fpCGI is as follows:
>
> 1)Capture form data,
> 2)write the data to a CSV file
> 3)Launch filepro
> 4)    filepro reads the csv file, processes the data, writes an HTML
> file and exits
> 5) fpCGI then picks up the HTML file created and feeds it back to the user.
>
> Now 1, 2, 3, and 5 are running.  I can see the dclerk process running in
> step 4 in the process table, but I do not get any output at all.  I have
> LOGTEXT commands and HTML commands in the table and I do not get
> anything from them.  fpCGI does not allow standard output to be captured
> so we can not do that.
>
> If I run the dclerk process in a test mode without fpCGI, it runs and
> does everything it is supposed to do.  In the fpCGI debug log, dclerk
> exits without error.  But it is really timing out and fpCGI is closing
> the process.
>
> Anyone got a clue where to try to troubleshoot this issue?
>
> BTW - I have ONEGATE also acting as a CGI for some newer processes.  It
> works without issue on this new Linux.  If I can not solve this, my path
> is to rewrite the stuff that uses fpCGI to ONEGATE.  I hate to re-write
> when the stuff was working just fine.  It was written before Onegate
> came out and we did not think a rewrite was cost-effective.  Without a
> resolution, we will have no choice.
>
> Nancy
>