How to deal with (104)Connection reset by peer: mod_fcgid...?

Question

PHP

Hello!
During the entire existence of the server, every day I have ~ 30 such errors in the error logs:
[Fri Mar 04 15:52:04 2016] [warn] [client 85.94.17.79] (104)Connection reset by peer: mod_fcgid: error reading data from FastCGI server, referer: site.ru/category/post
[Fri Mar 04 15:52:04 2016] [error] [client 85.94.17.79] Premature end of script headers: kama_postviews.php, referer: site.ru /category/post
They crash on random pages and Premature end of script headers: kama_postviews.php - not always this file, it can be index.php and something else
I reviewed the logs a bunch of times, absolutely everything that is on the server - I can’t identify the reason in any way. The fcgid.conf config changed a thousand times - it does not give any results. Those. this error (displayed as 500 in the browser) is somehow elusive and random, it doesn’t depend on anything at all ... It also appears in a random period of time - i.e. These errors are not only in the morning, afternoon or evening, but are uniform throughout the day. There is also no abnormal load on the server when this error occurs.
If we translate these errors into % relative to the pages viewed - it turns out ~ 0.03% This is not critical and I do not receive any complaints, but the presence of this error in the error logs is very annoying - if not for it, then this log would be empty :(
Also, there are no freezes when an error occurs. Those. I click on a link, then on another and at one moment bam - an error 500 is instantly given, i.e. I don't even wait for the page to be generated. Then I click to refresh the page and everything is fine - the page loads without any brakes.
Question: Do you have any idea what could be causing this and how to deal with it? Or is 0.03% not worth it and you can ignore it?
Additionally:
I once encountered the same error on the 1st site: I wandered around the site and then bam, after clicking on the link, an error 500 came up, but not even a second had passed since the page itself was updated and everything worked fine.
You don’t know what kind of chip it is that the page itself was updated as soon as the 500 error got out?

Answer 1

well, the feature is probably a custom page for 500 errors with a refresh meta tag