Bug 159647

Please supply some further information:
1. Do you have SELinux disabled / enabled / enforcing / permissive ?
2. Has SELinux ever been enabled on the machine ?
3. Have you modified the cron initscript to run cron in a chroot
   or as a non-root user ?
4. What cron job runs every half hour - is it run for a NIS / LDAP
   or normal user ?
5. Have you modified the default /etc/pam.d/crond file ? If so ,
   please append it to this bug report.
Thank you!

1.) It is is presently disabled.
2.) Unknown. On some of our boxes it was disabled at the outset, in
some of them I had to remember to disable it after the fact.
3.) No. I haven't modified the cron initscript at all.
4.) Has to be a normal user. We have no NIS/LDAP users.
5.) No. It is the stock /etc/pam.d/crond as supplied by
vixie-cron-4.1-33_FC3.

I am not able to reproduce this problem.

Please answer the following questions:
1. What version of PAM are you running (rpm -q pam) ?
2. What version of SELinux are you running (rpm -q libselinux) ?
3. What is the cron job command that causes these messages ?
   There is no cron job that runs every half hour installed by 
   default.
   If you don't know which job it is, please gather the data:
   # tar -cpf - /var/spool/cron /var/log/cron /etc/cron.d /etc/crontab   | gzip
> /tmp/cron.tar.gz
   and attach the /tmp/cron.tar.gz file to this bug. 
4. Can you reproduce the problem with a cron job run every minute
   by the root user ? Eg, as root:
   # echo '* * * * * /bin/date>/tmp/cron.root.test' \   
     >/var/spool/cron/root
   Then do the messages appear in the log every minute?

   If so, then please gather strace information :
   # strace -tvfp `pidof crond` > /tmp/crond.strace.log 2>&1 &
   and wait for one of the messages to be emitted to /var/log/cron; 
   then:
   # pkill strace; gzip /tmp/crond.strace.log
   and append the /tmp/crond.strace.log.gz file to this bug report.

   If it is not reproducible with a command run every minute as 
   root, please try to reproduce with a command run every minute as
   non-root user, gathering the strace log as above.

Thank you!

I have verified that this problem is not reproducible with the 
default PAM and CRON configuration shipped. 
It is possible that PAM may be misconfigured in some way as to
cause this problem, but without the further information requested,
I am unable to determine what this might be.
Hence, this bug is being closed.
If it is still a problem for you, please reopen and supply the 
further information requested in previous comment - thanks.