You are viewing an historical archive of past issues. Please report new issues to the appropriate project issue tracker on GitHub.

Bug #1486: Duplicate LogWatch reports from zenyatta.unixhosts.net

Kind bug
Product wincent.dev
When Created , updated
Status closed
Reporter Greg Hurrell
Tags no tags

Description

Seem to be getting two identical reports each day, one at about 12:09 and another at about 15:20.

Compare that with the mondatta.unixhosts.net report, which I receive once only at about 10:05.

Comments

  1. Greg Hurrell

    Seeing entries like this in /var/log/cron:

    Feb 24 06:01:01 domU-12-31-39-00-E9-02 CROND[22907]: (root) CMD (run-parts /etc/cron.hourly)
Feb 24 06:08:39 domU-12-31-39-00-E9-02 anacron[22974]: Anacron 2.3 started on 2010-02-24
Feb 24 06:08:39 domU-12-31-39-00-E9-02 anacron[22974]: Will run job `cron.daily' in 65 min.
Feb 24 06:08:39 domU-12-31-39-00-E9-02 anacron[22974]: Jobs will be executed sequentially

    And a bit later:

    Feb 24 07:13:39 domU-12-31-39-00-E9-02 anacron[22974]: Job `cron.daily' started

    And then later still:

    Feb 24 09:20:22 domU-12-31-39-00-E9-02 anacron[26016]: Anacron 2.3 started on 2010-02-24
Feb 24 09:20:22 domU-12-31-39-00-E9-02 anacron[26016]: Job `cron.daily' locked by another anacron - skipping
Feb 24 09:20:22 domU-12-31-39-00-E9-02 anacron[26016]: Normal exit (0 jobs run)
Feb 24 09:20:45 domU-12-31-39-00-E9-02 anacron[22974]: Job `cron.daily' terminated
Feb 24 09:20:45 domU-12-31-39-00-E9-02 anacron[22974]: Normal exit (1 job run)

    I didn't even know that anacron was installed on these instances, but the process listing shows that both crond and anacron are running on the instance which is seeing the duplicate reports.

    Working instance:

    root       941  0.0  0.0   3072  1120 ?        Ss   Feb17   0:00 cron</pre>

    Broken instance:

    root       941  0.0  0.0   3072  1120 ?        Ss   Feb16   0:00 crond
root      8324  0.0  0.0   2588  1088 ?        Ss   04:02   0:00 /bin/bash /usr/bin/run-parts /etc/cron.daily
root      9127  0.0  0.0   2588  1080 ?        S    05:05   0:00 /bin/bash /etc/cron.daily/0anacron
root      9132  0.0  0.0   2256   628 ?        S    05:05   0:00 awk -v progname=/etc/cron.daily/0anacron progname {?????   print progname ":\n"?????   progname="";????       }????       { print; }

    Output of chkconfig --list anacron on both instances: 

    anacron        	0:off	1:off	2:on	3:on	4:on	5:on	6:off

    /etc/anacrontab is identical on both instances.

    /etc/cron.daily/0anacron is likewise identical on both instances.

    My normal troubleshooting technique here would be to restart the funky service (service anacron restart) but seeing as there isn't actually any need for anacron on these instances (as they will be running 24 hours per day) I'm just going to disable it: 

    # chkconfig anacron off
# service anacron stop
  2. Greg Hurrell

    For some reason service anacron stop doesn't work (even on the good instance); reports "FAILED" and the 0anacron file continues to exist at /etc/cron.daily/ anyway.

    So, got rid of that file (stuck it in /etc/cron.daily.disabled/) on both machines and killed the lingering 0anacron and awk processes (the latter from run-parts).

  3. Greg Hurrell

    Status changed:

    • From: new
    • To: closed
Add a comment

Comments are now closed for this issue.

Menu