Analyzing and Troubleshooting FastCGI Errors
This section discusses gathering information for diagnosis, from the FastCGI application. The following topic provides this information:
This section also describes how to troubleshoot errors received when using FastCGI processes. The following topics describe common errors:
Getting More Information
Fastcgistub is a process manager that manages the life cycle of the FastCGI application processes. Fastcgistub logs its messages into Fastcgistub.log file under the Web Server's temporary directory. In case of any error, analyzing this file can help in debugging the problem.
FastCGI Requests Are Not Getting Served
FastCGI request not getting served is one of the common problems.
1. While starting the Web Server, did you see the following message?
FCGI1000: Sun Java System Web Server 7.0 FastCGI NSAPI Plugin <build-information>
Yes — FastCGI Plug-in has been loaded successfully.
No — Check the path to the plug-in library within the magnus.conf file.
2. Check if the request mapping is correctly specified within obj.conf file. For more information, see Sun Java System Web Server 7.0 Administrator's Configuration File Reference Guide.
3. Check the Server Log for any error message.
4. Check the permissions for the stub binary and FastCGI applications. Without sufficient permissions, the plug-in will fail to start the stub/application.
5. Check the Fastcgistub.log file for any possible error on the stub side.
6. Try executing the FastCGI application in a standalone mode and check if the application runs normally.
Dependency Issues
If library dependency errors are thrown, then whichever path is required to be added to LD_LIBRARY_PATH for resolving the library dependency errors in the standalone mode, the same library path should be specified within obj.conf file as app-env parameter with LD_LIBRARY_PATH value.
Sign up or Log in to add a comment or watch this page.