Re: Lots of crond syslog messages...why?

From: Gerry Doris (gdoris_at_rogers.com)
Date: 05/30/05

  • Next message: yufan: "Re: Creating a cluster" 
    Date: Mon, 30 May 2005 11:30:36 -0400 (EDT)
To: "For users of Fedora Core releases" <fedora-list@redhat.com>

    > Am So, den 29.05.2005 schrieb Gerry Doris um 17:48:
    >
    >> I had a nice stable FC2 system that been running for ages. I finally
    >> decided to upgrade yesterday to FC3 and have now managed to get pretty
    >> well
    >> everything working again. However, I do have one problem that I just
    >> can't
    >> find.
    >>
    >> I get the following messages occurring every 5min in my syslog:
    >>
    >> May 29 10:55:01 tiger crond(pam_unix)[5071]: session opened for user
    >> root by
    >> (uid=0)
    >> May 29 10:55:01 tiger crond(pam_unix)[5069]: session opened for user
    >> root by
    >> (uid=0)
    >> May 29 10:55:01 tiger crond(pam_unix)[5070]: session opened for user
    >> root by
    >> (uid=0)
    >> May 29 10:55:01 tiger crond(pam_unix)[5073]: session opened for user
    >> root by
    >> (uid=0)
    >> May 29 10:55:02 tiger crond(pam_unix)[5069]: session closed for user
    >> root
    >> May 29 10:55:04 tiger crond(pam_unix)[5071]: session closed for user
    >> root
    >> May 29 10:55:15 tiger crond(pam_unix)[5070]: session closed for user
    >> root
    >> May 29 10:55:33 tiger crond(pam_unix)[5073]: session closed for user
    >> root
    >>
    >> I've looked at crontab and crond and commented out anything that was
    >> running
    >> at 5min intervals without effect. Is this something that happens on FC3
    >> or
    >> is there something still broken? Any pointers where else to look???
    >
    > A process must be remaining, being called from cron (crontab -l -u root
    > || /etc/cron.d/). "tail -f /var/log/cron" could help you to find out.
    >
    > http://marc.theaimsgroup.com/?l=fedora-list&m=110077335618263&w=2
    >
    > Alexander

    Thanks for your reply. In hind sight I see that the messages weren't
    errors but merely pam notices that root had started a process and then
    that process had ended. As pointed out in the link you provided this is
    new behaviour from the cron package used in FC2.

    I was able to track these processes back to tasks being kicked off every
    5mins in cron. Matthew Miller suggested removing the pam session line for
    cron but that didn't work for me. I ended up removing auth notifications
    in syslog.conf. I'm not really happy with this solution but will use it
    until I can figure out something better. 

    -- 
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: http://www.redhat.com/mailman/listinfo/fedora-list
  • Next message: yufan: "Re: Creating a cluster"

    Relevant Pages

    • [Fwd: OpenBase SQL multiple vulnerabilities Part Deux]
      ... # Writing to roots crontab seems to be fairly prompt at handing out root shells ... This ensures that cron is running when the fake root crontab is created. ... the OpenBase family of products have been enabling some of the most innovative business applications ...
      (Bugtraq)
    • RE: cron.daily stopped working
      ... expiration with command "passwd -f root " and then setup a test root ... cron. ... job in /etc/cron.daily just stopped working. ... unsubscribe mailto:redhat-list-request@redhat.com?subject=unsubscribe ...
      (RedHat)
    • Re: Cron job question
      ... > From: root@somedomain.nl (Cron Daemon) ... You've made the classic mistake of confusing the system crontab ... extra column defining which user ID the command should be run as. ... any new cron jobs for any user (including root) and leave the system ...
      (freebsd-questions)
    • dns and mail question
      ... I have several private networks that I vpn between. ... root run processes that send mail to our admin group, cron, logwatch you ... cron runs a job and generates a mail to root. ...
      (RedHat)
    • Re: Cron as Root and .netrc File
      ... why not user "su - username" in roots crontab? ... I also dont allow users to user cron - only root. ... However if the root cron will not read the .netrc file I ...
      (AIX-L)