Results 1 to 9 of 9
  1. #1
    Join Date
    Jul 2007
    Location
    Porto, Portugal
    Posts
    18

    How to: crontab 4755 cPanel error fix

    A common error that cPanel show after a fresh install is the:
    /usr/bin/crontab permissions are wrong. Please set to 4755
    An easy fix is the using the following commands.
    Make sure you're using root.
    chmod 4755 /usr/bin/crontab
    ps -aux |grep cron
    /scripts/restartsrv_crond
    /etc/init.d/crond restart
    ps -aux |grep cron
    ls -l /usr/bin/crontab

  2. #2
    Join Date
    Dec 2002
    Location
    chica go go
    Posts
    11,858
    Since when is it known as the "4755 cpanel error"? Wouldn't anyone searching for it know the solution already?

  3. #3
    Join Date
    Jul 2007
    Location
    Porto, Portugal
    Posts
    18
    And...?

    If you search for it you'll see someone asking and some other user giving the solution. Why not giving the solution at the first post for anyone searching in the forum? This way maybe there will be less posts asking.

    If you have any better suggestion for this topic name, then just suggest it, flaming isn't productive at all.

    Edit:
    And what used in the title are just a few tags, as you can see: crontab, 4755, cPanel, Error and Fix
    In my opinion helps in future searchs.
    Last edited by DStuart; 05-28-2008 at 03:15 PM.

  4. #4
    Join Date
    Jan 2006
    Location
    Athens, Greece
    Posts
    1,479
    Which OS installs this binary without the setuid bit set?

  5. #5
    Join Date
    Jun 2006
    Location
    APE: 6202A
    Posts
    1,273
    I can remember that I encount this isuue with centos 5.x but can't remember how did I fix it...

  6. #6
    Join Date
    Jul 2007
    Location
    Porto, Portugal
    Posts
    18
    I also experienced it on centos 5.x and this was how I fixed it.

  7. #7
    Join Date
    Sep 2002
    Location
    Top Secret
    Posts
    11,687
    ps -aux |grep cron
    /scripts/restartsrv_crond
    /etc/init.d/crond restart
    ps -aux |grep cron
    ls -l /usr/bin/crontab
    ALL unnecessary

    To fix this, all you need to do is simply
    Code:
        chmod 4775 /usr/bin/crontab
    You don't need to grep for the cron process, restart the cron process, list the binary, or tell the server to go fsck itself

    This problem has been known for at least 6 months now, probably longer. I say at least 6 months, because I've had it noted for that long, and had the solution public that long ago.

    Which OS installs this binary without the setuid bit set?
    At the very minimum, CentOS 5 does. I don't know of any others right offhand, though I'm sure if it's in Cent, it's in the whole family (redhat).

    The above fsck comment is NOT an attempt at getting around the 'rules', if you don't know what it means, then pass the report on to someone that does, they'll laugh.
    Last edited by whmcsguru; 05-28-2008 at 11:52 PM.
    WHMCS Guru - WHMCS addons, management, support and more.
    WHMCS Notifications Extended - Add slack, hipchat, SMS, pushover to WHMCS !!
    Always looking for Linux, WHMCS, Support Desk work. PM for details

  8. #8
    Join Date
    Dec 2002
    Location
    chica go go
    Posts
    11,858
    Quote Originally Posted by DStuart View Post
    And...?

    If you search for it you'll see someone asking and some other user giving the solution. Why not giving the solution at the first post for anyone searching in the forum? This way maybe there will be less posts asking.

    If you have any better suggestion for this topic name, then just suggest it, flaming isn't productive at all.

    Edit:
    And what used in the title are just a few tags, as you can see: crontab, 4755, cPanel, Error and Fix
    In my opinion helps in future searchs.
    because when someone else on a forum makes a post, your post goes further down the list.

    I recommend you look for threads where people ask questions, and provide answers in them.

  9. #9
    Join Date
    May 2008
    Posts
    44
    chmod 4775 /usr/bin/crontab

    After run those command, check permission of /var/spool/cron and user owner permission files too.

    They should be:

    root 04:00:15 AM /var/spool/cron 900 # ls -al
    total 24
    drwxr-xr-x 2 root root 4096 Jun 5 03:41 ./
    drwxr-xr-x 12 root root 4096 May 23 22:53 ../
    -rw------- 1 root root 1394 Jun 4 12:04 mailman
    -rw------- 1 root root 385 Jun 5 00:47 root
    -rw------- 1 taoto taoto 154 Jun 5 03:38 taoto
    -rw------- 1 thumb thumb 51 Jun 5 03:41 thumb

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •