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.

logwatch not executing anymore

Discussion in 'General Discussion' started by corey_s, Nov 24, 2005.

  1. corey_s

    corey_s Member

    Joined:
    Apr 6, 2005
    Messages:
    21
    Likes Received:
    0
    Trophy Points:
    1
    Hello - for some reason, the daily morning logwatch job doesn't seem to be executing any longer via our whm server.

    Perhaps it's actualy the cron.daily that's not executing - I see the cron.hourly's in the cron log but not cron.daily.

    Where should I look to track down the issue?

    Thanks!
     
  2. chirpy

    chirpy Well-Known Member

    Joined:
    Jun 15, 2002
    Messages:
    13,475
    Likes Received:
    20
    Trophy Points:
    38
    Location:
    Go on, have a guess
    Is cron actually running? Try:

    /etc/init.d/crond restart

    If it was running, try running the logwatch script in /etc/cron.daily/

    Also, if you're not seeing cron.daily in the cron log, which is unusual, make sure that it's not actually still running for some reason by checking the ps axf output.

    Lastly, make sure there's a line to run cron.daily in /etc/crontab.
     
  3. corey_s

    corey_s Member

    Joined:
    Apr 6, 2005
    Messages:
    21
    Likes Received:
    0
    Trophy Points:
    1
    Yep - crond is running.

    I checked ps, and everything looks ok - no hung or zombie'd processes or anything like that.

    /etc/crontab does have an entry for daily.

    Running it by hand, I can see the message go out via exim... but we don't ever recieve it, so that's probably where the actual problem is. I'll have to look more closely at our mail routing. Perhaps, it's been running all along, but we just haven't been getting the mail for whatever reason.... weird though that we don't see the cron.daily in the cron log though.

    Thanks for your assistance!
     
  4. sinfield

    sinfield Member

    Joined:
    Jan 13, 2004
    Messages:
    14
    Likes Received:
    0
    Trophy Points:
    1
    Thanks to some of the URLs in the NAMED log, our logwatch messages are sometimes grabbed by SpamAssassin. Even whitelisting is not always enough. I guess it is high time I do some SpamAssassin configuration. :)
     
  5. corey_s

    corey_s Member

    Joined:
    Apr 6, 2005
    Messages:
    21
    Likes Received:
    0
    Trophy Points:
    1

    Hey - that's interesting, and something which had never occurred to me as a possibility.

    I wouldn't be surprised if that was part of the culprit -- thanks for the tip!
     
  6. sinfield

    sinfield Member

    Joined:
    Jan 13, 2004
    Messages:
    14
    Likes Received:
    0
    Trophy Points:
    1
    Since the NAMED log is usually long and boring I just disabled NAMED in logwatch.conf. :D
     
Loading...

Share This Page