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.

Where are crontab errors logged?

Discussion in 'General Discussion' started by czerdrill, Apr 24, 2012.

  1. czerdrill

    czerdrill Well-Known Member

    Joined:
    Feb 18, 2011
    Messages:
    70
    Likes Received:
    0
    Trophy Points:
    6
    I have a cronjob set up but it failed to run recently. It worked fine before. It's the cPanel backup script thats readily available on the internet. Only change I made to the server was changing the ssh port from the default 22. Is there somewhere I can view what errors were thrown when a cronjob failed to run?
     
  2. czerdrill

    czerdrill Well-Known Member

    Joined:
    Feb 18, 2011
    Messages:
    70
    Likes Received:
    0
    Trophy Points:
    6
    I was able to run it from shell with no issue, and the command I had in crontab worked until today. Any ideas?
     
  3. NetMantis

    NetMantis BANNED

    Joined:
    Apr 22, 2012
    Messages:
    117
    Likes Received:
    0
    Trophy Points:
    0
    Location:
    Utah
    cPanel Access Level:
    DataCenter Provider
    Do you have "shell fork bomb protection" enabled on your server?

    If so, disable it and see if your script runs

    You can also take a look at /var/log/messages and watch the email account listed
    in /root/.forward as that is where cron error reports would usually show up.
     
  4. cPanelJared

    cPanelJared Technical Analyst
    Staff Member

    Joined:
    Feb 25, 2010
    Messages:
    1,842
    Likes Received:
    18
    Trophy Points:
    38
    Location:
    Houston, TX
    cPanel Access Level:
    Root Administrator
    Cron-related messages, including success and failure, are logged to /var/log/cron .
     
  5. czerdrill

    czerdrill Well-Known Member

    Joined:
    Feb 18, 2011
    Messages:
    70
    Likes Received:
    0
    Trophy Points:
    6
    Thanks guys, disabling shell fork bomb protection did the trick!
     
Loading...

Share This Page