The /var/log/secure file is full of the following lines:

Dec 16 06:12:01 dev crond[10012]: pam_loginuid(crond:session): set_loginuid failed opening loginuid
Dec 16 07:00:01 dev crond[10891]: pam_loginuid(crond:session): set_loginuid failed opening loginuid
Dec 16 07:12:01 dev crond[11133]: pam_loginuid(crond:session): set_loginuid failed opening loginuid
Dec 16 08:00:01 dev crond[12014]: pam_loginuid(crond:session): set_loginuid failed opening loginuid
Dec 16 08:12:01 dev crond[12227]: pam_loginuid(crond:session): set_loginuid failed opening loginuid
Dec 16 09:00:01 dev crond[13136]: pam_loginuid(crond:session): set_loginuid failed opening loginuid
Dec 16 09:12:01 dev crond[13349]: pam_loginuid(crond:session): set_loginuid failed opening loginuid
Dec 16 10:00:01 dev crond[14240]: pam_loginuid(crond:session): set_loginuid failed opening loginuid

We can stop this from happening by editing the following file:

# vi /etc/pam.d/crond

And commenting out the following line:

#
# The PAM configuration file for the cron daemon
#
auth       sufficient pam_env.so
auth       required   pam_rootok.so
auth       include    system-auth
account    required   pam_access.so
account    include    system-auth
#session    required   pam_loginuid.so
session    include    system-auth