Error after upgrading to newer Apache

[bruceeaston]

One of our clients on fpCGI is now getting the white screen error "Please try again later. System Busy.  Could not gain access to the counter file."   This just began after moving his application to a newer Red Hat box with latest Linux and Apache.  He is on filepro 2.0.  We have scoured the box in terms of permissions, and have tried changing the counter file, moving it out of the way and making a new one, etc.  Apache seems to be runnning OK, fpcgi seems to start OK - but I notice even will three active debug lines on in the log config file, set to write log files to /tmp, there are no logging files being written.  Any ideas? 

Also, we modified the new Apache config file following the pattern of an older Red Hat config file that we could reference, since the config instructions for Linux fpCGI are messed up with stuff about Windows. 

Bruce

Bruce Easton
STN, Inc.

[ernieb]

Apache 2.0 (or so)
My uid.conf has:

User filepro
Group www

 And in my default-server.conf:
    SetEnv PFDATA
    SetEnv PFDIR /var/aamgweb/appl
    SetEnv PFPROG /appl
    SetEnv PFSERVROOT /srv/www/htdocs/
    SetEnv PFGLOB /appl/fp/lib/edits
    SetEnv PFSERVER 10.25.33.140
    SetEnv PFCOUNTERMAX 100
    SetEnv FPCGILOG /tmp/fpcgi.log
    SetEnv PFADDWP OFF
    SetEnv PFUFLAG ON
    SetEnv PFMBTO 1
    SetEnv PFBIXERRORS OFF
    PassEnv PATH HOME COLUMNS LINES TERM

[bruceeaston]

Apache 2.0 (or so)
My uid.conf has:

[..]

Thanks, Ernie - turns out our config was OK, but that SELinux was active and
getting in the way of fpCGI accessing the counter file.  For this client, we
did not need SELinux to run anyway, so by completely deactivating it, the
problem disappeared.

Bruce