[Solved] enhance fcgi - now causing error500

3 posts / 0 new
Last post
#1 Fri, 07/19/2013 - 13:54
remibruggeman

[Solved] enhance fcgi - now causing error500

Hello,

for one of my servers I am facing a problem. It runs a site which runs on drupal + civicrm. In the civicrm part I regularly (every 10 or so clicks) get an error 500. Looking at the logs, I see this:

[Fri Jul 19 20:42:56 2013] [warn] [client xxx.xxx.xxx.xxx] (104)Connection reset by peer: mod_fcgid: error reading data from FastCGI server, referer: http://domain.be/civicrm?reset=1
[Fri Jul 19 20:42:56 2013] [error] [client xxx.xxx.xxx.xxx] Premature end of script headers: index.php, referer: http://domain.be/civicrm?reset=1

I read some information already. They include several possible issues: - fcgi issue - mysql issue - script issue

If it would be the script though, every page would show error 500. The mysql configuration has been revised and is now working perfectly. The only possible thing left is the fcgi.

I read some remarks on the net saying to configure the php5.fcgi which is in the fcgi bin with 4 children. I made the change (create a new file, because for some obscure reason root cannot edit that file) to 8 children. This however does not solve any problems.

is there anybody who can help me configuring fcgi or help me solve the problem with the error 500's?

Thanks!

Fri, 07/19/2013 - 13:58
remibruggeman

by the way. I tried this also, but sadly this did not work for my issue. http://www.virtualmin.com/node/25539

Fri, 07/19/2013 - 18:20
remibruggeman

okay, I've been through hundreds of sites, configuring and finetuning the server. (I can really recommend http://shiftlock.wordpress.com/2013/06/29/troubleshooting-error-reading-... ) but in the end ... embarrassingly enough it was a script error. A "Developer" published an untested script which caused an error in the fcgi server. once that error was produced, half of the site produced the same error. It seemed that his script just kind of crashed the fcgi deamon.

Well, problem solved.

Moral of the story: dev's will blame server config, sysadmins will blame the devs. The only thing to do is to make sure you check what is happening on the server (and who published what code).

Topic locked