Red Hat Bugzilla – Bug 132437
/etc/cron.daily/makewhatis.cron: numerous lines "zcat: stdout: broken pipe"
Last modified: 2014-01-21 17:49:55 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; de-DE; rv:1.7.2)
Description of problem:
After updating some packages on two systems cron complains about
"zcat: stdout: Broken pipe" and produces mails to root with about 6000
zcat: stdout: Broken pipe
zcat: stdout: Broken pipe
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1.Wait for cron
See bug # 64836
If running makewhatis manually, everythig works as expected.
yes, I have this problem on many WS3 too.
If running makewhatis manually, everythig works as expected, but
cronjob produce errors.
I'm also seeing the problem, on AS3 and AS 2.1.
It started a few weeks ago, at around the same time on both platforms.
can you tell me which two packages? i can't reproduce over here.
for example makewhatis
Issue is seen on system with man-1.5k-10
Created attachment 104266 [details]
List of all rpms on a 2.1 machine experiencing problem
Comment 7: I'm not seeing this on my up2dated AS machine (with
man-1.5k-10). I suspect that a package has been installed that has a
bogus encoding in the man page, or the system is running in a wierd
locale. I'll take a look at the rpm list and see if I can recreate it.
I have man-1.5k-10 on Red Hat Enterprise Linux WS release 3 (Taroon
This is from one of the rebuild projects (centos 3.3) but it's
happening there too and it's from one of the following pkgs
That might help reduce the set to look for a broken man page somewhat.
comment 10: what locale is it running in?
For our System it's LANG=de_DE.UTF-8.
It's LANG=en_US on our RHEL 2.1 systems, and LANG=en_US.UTF-8 for our
RHEL 3.0 systems.
Count me as one that experiences this on hundreds of boxes every week.
Some systems have 3rd-party RPMs, some have not. We use LANG=en_US for
all RHEL3 systems.
Running in en_US.UTF-8
I'm upgrading a system letter by letter:
yum update a\* ; makewhatis -u -w
on a system that's not been updated to u3, yet.
When I find the offending letter I'll let you know
I think you will find that it will always work when makewhatis is run
by hand. If you are willing to test one letter at a time, instead
after you update a letter make sure you run makewhatis out of cron.
I read the /etc/cron.daily script -it's not exactly rocket science.
Why would it fail from cron but not when run from the prompt?
Currently it is not known why it would work from the command line and
not from cron. If you look at what both of the people in Comment 1
and Comment 2 said this is the case and is what we are exploring.
Excuse me, refer to the initial report and Comment 1, not Comment 2.
*** This bug has been marked as a duplicate of 64836 ***
If you dig deep enough in history you'll see that this problem was
observed at least as far back as RH 7.3. Alan Cox surmised that it was
a problem with cron's configuration of signals when running jobs.
Comment #18: because cron has a different environment than you have and is
probably missing something in your PATH.
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.