Image may be NSFW.
Clik here to view.
This is a very old FastCGI issue but I have never found a satisfactory answer.
Searching the phrase “(13) permission denied fastcgi can’t create server” on Google will show that there’s a lot of people experiencing this issue for a long while.
Some people blame it on selinux and suggest turning it off (not acceptable solution).
Other people think that it’s a strange symlink permissions problem and suggest turning the Apache logs directory from symlink to a plain directory. (not acceptable, since it involves moving the logs files) See Installing FastCGI.
Below is the dreaded error as typically logged by Apache.
[Wed Jun 14 22:09:34 2009] [notice] Apache/2.0.40> (Red Hat Linux) configured
-- resuming normal operations
[Wed Jun 14 22:09:35 2009] [crit] (13)Permission
denied: FastCGI: can't create server "/var/rt3/bin/mason_handler.fcgi": bind()
failed [/etc/httpd/logs/fastcgi/70d9a528c5892f2bf0c25e5a334bed81]
Hoping serverfault can finally provide a definitive answer to this perplexing and annoying problem which has plague FastCGI users for years.
I feel uneasy implementing the suggested “cures” when no one really knows the underlying cause of this illness. Hope to get to the bottom of this mystery.
Image may be NSFW.
Clik here to view.
From /usr/lib/errno.h
#define EACCES 13 /* Permission denied */
mod_fcgi communicates with fastCGI children via a named pipe. Apache creates the pipe before spawning the children. I would guess that apache does not have permission to create
/var/rt3/bin/mason_handler.fcgi
To check this try
su - apache "touch /var/rt3/bin/mason_handler.fcgi"
If that failes, adjust the filesystem permissions appropriately to give apache permission to create a file in that directory.
Check more discussion of this question.
