I think dreamhost fastcgi is starting up late.
I’ve enabled fastcgi in the panel and DH support has increased the memory allocation (as per DH wiki). I’m testing with the perl and python fastcgi scripts from the DH wiki. The process doesn’t start when I first hit the URIs (returning 500 error) and doesn’t appear in a process listing (ps x). There are a couple of messages in the error log indicating the process hasn’t started:
FastCGI: comm with (dynamic) server “SCRIPT” aborted: …
FastCGI: incomplete headers (0 bytes) received from server “SCRIPT”
After a couple of minutes, the process starts up, appears in the process listing and all seems to be OK when the URI is accessed. I suspect this is done by the DH config monitor or similar, but I expected the process to be started by the apache process manager on first access.
DH support say they can’t help and suggested posting here. sigh
Obviously the workaround is to wait for a couple of minutes for the process to start, but it’s a bit of a pain (and may imply other problems).
Am I missing something?