The Community Forums

Interact with an entire community of cPanel & WHM users!
  1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

Cron issue

Discussion in 'General Discussion' started by efeito, Sep 14, 2003.

  1. efeito

    efeito Well-Known Member
    PartnerNOC

    Joined:
    Jul 24, 2003
    Messages:
    141
    Likes Received:
    0
    Trophy Points:
    16
    Location:
    .pt
    Hi there,

    today i received an email from cron (as usual) but the subject was "run-parts /etc/cron.weekly" and on the body of the email i get more than 10 lines with this "zcat: stdout: Broken pipe"


    What can be this??

    cPanel.net Support Ticket Number:
     
  2. efeito

    efeito Well-Known Member
    PartnerNOC

    Joined:
    Jul 24, 2003
    Messages:
    141
    Likes Received:
    0
    Trophy Points:
    16
    Location:
    .pt
    Today i receive another email with the subject "Cron <root@servername> run-parts /etc/cron.daily"

    With this in body:

    /etc/cron.daily/makewhatis.cron:


    zcat: stdout: Broken pipe

    zcat: stdout: Broken pipe

    zcat: stdout: Broken pipe

    zcat: stdout: Broken pipe

    zcat: stdout: Broken pipe

    zcat: stdout: Broken pipe

    zcat: stdout: Broken pipe

    zcat: stdout: Broken pipe

    zcat: stdout: Broken pipe



    Anyone can help me???

    cPanel.net Support Ticket Number:
     
  3. Host4u2

    Host4u2 Well-Known Member

    Joined:
    Mar 24, 2002
    Messages:
    248
    Likes Received:
    0
    Trophy Points:
    16
    Ditto! Any feedback on this?
     
  4. scapeweb

    scapeweb Well-Known Member

    Joined:
    Aug 16, 2003
    Messages:
    45
    Likes Received:
    0
    Trophy Points:
    6
    I got the same e-mail from my server, --- I am wondering what that means

    I read this somewhere

    find /usr/share/man -type d | xargs symlinks

    post output.

    because the program into which zcat is attempting to pipe its output is
    not functioning as a program. i.e. it is aborting on the data it's
    receiving (man makewhatis for gory details) you get this error.

    can be attributable to many things. Typically insufficiant resourses or bad links.

    makewhatis is run as a cron job to update the database used by the locate command. So when you type

    locate foo

    the DB will have the path & spit back
    /usr/bin/foo


    ---

    Tony
    Sun Microsystems
     
  5. spiff06

    spiff06 Well-Known Member

    Joined:
    Jan 17, 2004
    Messages:
    87
    Likes Received:
    0
    Trophy Points:
    6
    I got it too, for the first time, this morning.
    Something's awry. What gives?

    Eric
     
  6. spiff06

    spiff06 Well-Known Member

    Joined:
    Jan 17, 2004
    Messages:
    87
    Likes Received:
    0
    Trophy Points:
    6
    Mmh, it appears this is a recurring problem with makewhatis.

    Apparently, the first thing to look at is whether an RPM was installed with a symlink for manpage (see here). Since it seems to be a fresh problem on cPanel, it could be that the automatic system update installed an RPM with a symlink as man page.

    Running find /usr/share/man -type d | xargs symlinks, I get:

    Code:
    absolute: /usr/share/man/man1/jar.1.gz -> /etc/alternatives/jar.1.gz
    absolute: /usr/share/man/man1/rmiregistry.1.gz -> /etc/alternatives/rmiregistry.1.gz
    absolute: /usr/share/man/man1/rmic.1.gz -> /etc/alternatives/rmic.1.gz
    absolute: /usr/share/man/man1/cancel.1.gz -> /etc/alternatives/print-cancelman
    absolute: /usr/share/man/man1/lp.1.gz -> /etc/alternatives/print-lpman
    absolute: /usr/share/man/man1/lpq.1.gz -> /etc/alternatives/print-lpqman
    absolute: /usr/share/man/man1/lpr.1.gz -> /etc/alternatives/print-lprman
    absolute: /usr/share/man/man1/lprm.1.gz -> /etc/alternatives/print-lprmman
    absolute: /usr/share/man/man1/lpstat.1.gz -> /etc/alternatives/print-lpstatman
    absolute: /usr/share/man/man1/java.1.gz -> /etc/alternatives/java.1.gz
    absolute: /usr/share/man/man1/javaws.1.gz -> /etc/alternatives/javaws.1.gz
    absolute: /usr/share/man/man1/keytool.1.gz -> /etc/alternatives/keytool.1.gz
    absolute: /usr/share/man/man1/kinit.1.gz -> /etc/alternatives/kinit.1.gz
    absolute: /usr/share/man/man1/klist.1.gz -> /etc/alternatives/klist.1.gz
    absolute: /usr/share/man/man1/ktab.1.gz -> /etc/alternatives/ktab.1.gz
    absolute: /usr/share/man/man1/orbd.1.gz -> /etc/alternatives/orbd.1.gz
    absolute: /usr/share/man/man1/policytool.1.gz -> /etc/alternatives/policytool.1.gz
    absolute: /usr/share/man/man1/rmid.1.gz -> /etc/alternatives/rmid.1.gz
    absolute: /usr/share/man/man1/servertool.1.gz -> /etc/alternatives/servertool.1.gz
    absolute: /usr/share/man/man1/tnameserv.1.gz -> /etc/alternatives/tnameserv.1.gz
    absolute: /usr/share/man/man8/lpc.8.gz -> /etc/alternatives/print-lpcman
    absolute: /usr/share/man/man8/up2date-nox.8.gz -> /usr/share/man/man8/up2date.8.gz
    absolute: /usr/share/man/ja/man1/java.1.gz -> /etc/alternatives/java-ja.1.gz
    absolute: /usr/share/man/ja/man1/javaws.1.gz -> /etc/alternatives/javaws-ja.1.gz
    absolute: /usr/share/man/ja/man1/keytool.1.gz -> /etc/alternatives/keytool-ja.1.gz
    absolute: /usr/share/man/ja/man1/kinit.1.gz -> /etc/alternatives/kinit-ja.1.gz
    absolute: /usr/share/man/ja/man1/klist.1.gz -> /etc/alternatives/klist-ja.1.gz
    absolute: /usr/share/man/ja/man1/ktab.1.gz -> /etc/alternatives/ktab-ja.1.gz
    absolute: /usr/share/man/ja/man1/orbd.1.gz -> /etc/alternatives/orbd-ja.1.gz
    absolute: /usr/share/man/ja/man1/policytool.1.gz -> /etc/alternatives/policytool-ja.1.gz
    absolute: /usr/share/man/ja/man1/rmid.1.gz -> /etc/alternatives/rmid-ja.1.gz
    absolute: /usr/share/man/ja/man1/rmiregistry.1.gz -> /etc/alternatives/rmiregistry-ja.1.gz
    absolute: /usr/share/man/ja/man1/servertool.1.gz -> /etc/alternatives/servertool-ja.1.gz
    absolute: /usr/share/man/ja/man1/tnameserv.1.gz -> /etc/alternatives/tnameserv-ja.1.gz
    Anything looking suspicious in there?

    Other seemingly relevant entries:
    https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=60282
    Someone got so annoyed with it that he suggests modifying the cron job to add a -u parameter to make makewhatis fail silently.
    Others suggest uninstalling man entirely...

    Eric
     
  7. Angel78

    Angel78 Well-Known Member

    Joined:
    May 9, 2002
    Messages:
    413
    Likes Received:
    1
    Trophy Points:
    16
    any solution for this (without deinstalling man)?
     
  8. rpmws

    rpmws Well-Known Member

    Joined:
    Aug 14, 2001
    Messages:
    1,824
    Likes Received:
    5
    Trophy Points:
    38
    Location:
    back woods of NC, USA
    I just got this in my nightly server emails as well. All my RHE3 boxes but none of my 7.3 and 9 boxes have this problem.
     
  9. Host4u2

    Host4u2 Well-Known Member

    Joined:
    Mar 24, 2002
    Messages:
    248
    Likes Received:
    0
    Trophy Points:
    16
    Actually the makewhatis script runs an update to the whatis db so you can type:

    wmmont@cpdemo [~]# whatis top
    top (1) - display top CPU processes

    Jan 5, 1991 whatis(1)
    whatis(1) whatis(1)

    NAME
    whatis - search the whatis database for complete words.

    SYNOPSIS
    whatis keyword ...

    DESCRIPTION
    whatis searches a set of database files containing short descriptions
    of system commands for keywords and displays the result on the standard
    output. Only complete word matches are displayed.

    The whatis database is created using the command /usr/sbin/makewhatis.

    ************************

    The locate database is updated here:

    mmont@cpdemo [/etc]# cat /etc/cron.daily/slocate.cron
    #!/bin/sh
    renice +19 -p $$ &gt;/dev/null 2&gt;&1
    /usr/bin/updatedb -f "nfs,smbfs,ncpfs,proc,devpts" -e "/tmp,/var/tmp,/usr/tmp,/afs,/net"
    mmont@cpdemo [/etc]#

    This whatis database isn't very useful, so the quickest solution would be to disable the cronjob.
     
  10. rs-freddo

    rs-freddo Well-Known Member

    Joined:
    May 13, 2003
    Messages:
    832
    Likes Received:
    1
    Trophy Points:
    18
    Location:
    Australia
    cPanel Access Level:
    Root Administrator
    Just got this error this morning. The reason I (and you all) have the error is because of the RH3 RPM updates which just recently came out. Something in the updates mucked something up.

    I know what caused it but don't know how to fix it.
     
  11. laura

    laura Active Member

    Joined:
    Sep 12, 2003
    Messages:
    35
    Likes Received:
    0
    Trophy Points:
    6
    Location:
    indonesia
    Me too ! I just got this in my RHE3 boxes but none of my BSD and 9 boxes have this problem.
     
  12. ehsanix

    ehsanix Member

    Joined:
    Mar 3, 2004
    Messages:
    13
    Likes Received:
    0
    Trophy Points:
    1
    I've got this email tooo !
     
  13. CoolMike

    CoolMike Well-Known Member

    Joined:
    Sep 6, 2001
    Messages:
    307
    Likes Received:
    0
    Trophy Points:
    16
    Yes, I have it also on all RHE servers...
     
  14. rpmws

    rpmws Well-Known Member

    Joined:
    Aug 14, 2001
    Messages:
    1,824
    Likes Received:
    5
    Trophy Points:
    38
    Location:
    back woods of NC, USA
    anybody find a simple fix for this yet?
     
  15. FourMat

    FourMat Active Member

    Joined:
    Jun 10, 2004
    Messages:
    34
    Likes Received:
    0
    Trophy Points:
    6
    I'm having this problem also. Anyone have a fix for it yet? Thanks.
     
  16. ParagonHost

    ParagonHost Registered

    Joined:
    Mar 10, 2004
    Messages:
    3
    Likes Received:
    0
    Trophy Points:
    1
    zcat: stdout: Broken pipe after recent upgrade

    After upgrading to the released loads of WHM / cPanel I am now getting the following error as noted in this thread:

    zcat: stdout: Broken pipe

    *** This error is repeated many times reported by way of email with a subject of the following:

    Cron <root@host301> run-parts /etc/cron.daily

    It also appears many others are having this trouble.

    Please post your solution when you get one,

    Thanks all!

    Dave Safley
    ParagonHost.com
     
  17. FourMat

    FourMat Active Member

    Joined:
    Jun 10, 2004
    Messages:
    34
    Likes Received:
    0
    Trophy Points:
    6
    I am continueing to have this problem, now week 2, with the email subject:

    run-parts /etc/cron.weekly

    The body contains this, and nothing else:

    zcat: stdout: Broken pipe

    Any help would be appreciated. Thanks.
     
  18. osogge

    osogge Registered

    Joined:
    Jul 7, 2004
    Messages:
    2
    Likes Received:
    0
    Trophy Points:
    1
    Anyone got a solution on this?

    My server stops responding everynight. Doesn't accept http, ftp, ssh etc.
    Think it's related to this thread. I've tried to remove slocate.cron and makewhatis.cron from /etc/cron.daily/ but this didn't work.
     
  19. FourMat

    FourMat Active Member

    Joined:
    Jun 10, 2004
    Messages:
    34
    Likes Received:
    0
    Trophy Points:
    6
    I haven't had an issue with the server being shut down with this error, just the failure to report.
     
  20. Roberto

    Roberto Active Member

    Joined:
    Jul 9, 2003
    Messages:
    36
    Likes Received:
    0
    Trophy Points:
    6
    I would try updating to the latest stable build of cPanel.
     
Loading...

Share This Page