Im reading the Apache error log frequently and im annoyed from two records which they are :

find: `standard output': Broken pipe
find: write error

im just ask if someone can help me in finding what they are as there is no any clarifications in the record to note what is going wrong, and how i can get ride from these two line appearing all the time in my error log

thanks

Somewhere you have a bash/sh shell script running that has a syntax error in piping output from or to the 'find' command. This might occur in a cleanup script (hunts for matching files and deletes them) or it might be part of a website's functionality. If it's happening frequently then that suggests its something coded up for a website - unless you have something in cron that is firing off "frequently".

Without more context it is hard to tell.

If I had to hazard a guess, I'd say that some CGI application is running 'find' in some way that makes it complain. Quite possibly, the complaint is a result of it's runtime environment as a CGI.
If you are the admin, you might find one or more scripts that launch find in the cgi-bin directory of your server.
--- rod.

Dears,
this is my case:

Im Getting this Error in Apache Error log when im using php shellexec function to find some files in linux directory the error is : find: standard output: broken pipe find:write error

here is my php code ; notice : every thing is OK but this error appears in Apache error log as notice im searching in directory to find the specific .xml file depending on the $_POST['keyword']

$arr = array();
$keyWord = trim($_POST['keyword']);
$data = shell_exec('find /var/www/html/Find/XMLDIR/ -name ' .$keyWord.'*.xml | head -n 10');
$data = str_replace('/var/www/html/Find/XMLDIR/','',$data);
$arr = explode(chr(10), $data);
if(isset($arr[count($arr)-1])) unset($arr[count($arr)-1]);

print_r($arr);

Often I find that enclosing strings in quotes (where you have $keyWord) is an essential way to keep 'find' happy. Prevents a string with spaces from being processed as multiple parameters - which seems to be your issue. Can you do [ ..... -name \"'.$keyWord.'\"*.xml.... ] or something like that?

i added 2> /dev/null before the | head what it does is redirects stderr to the null device.... What i did ,trying to do is supress output to stderr.

and it works fine

No errors in httpd/error_log

Isn't that just disguising the actual problem? Making the error messages go away doesn't mean the errors aren't happening. What will you do when some serious error occurs, and the evidence of it is lost in the bit bucket?
--- rod.