Not sure how to file this particular issue, as it probably is not very common. Summary: if you see "Unable to change UID to" or "Unable to change GID to" in your syslog, you should go review the file ownership and file name of your cron files. Sep 13 10:25:02 c ypher crond[32723]: pam_keyinit(crond:session): Unable to change GID to 1063 temporarily Sep 13 10:25:02 cypher crond[32723]: pam_keyinit(crond:session): Unable to change UID to 60064 temporarily My specific issue happe ned because a username was changed which had the UID of 600 64. Previously jradtke:x: 60064 :1 063 :J ames Radtke :/home/ jradtke :/bin/bash [jradtke@cyper Kickstart]$ sudo ls -l /var/spool/cron/ | grep jrad -rw-------. 1 jradtke jradtke 25 Sep 13 11:57 jradtke N ow.. my username had been changed to jradtke@c o rp.company.com jradtke@c o rp.company.com :x: 60064 :1 063 :J ames Radtke :/home/ jradtke :/bin/bash To remedy th e issue: mv /var/spool/cron /jradtke /v...
Linux: The whole world made it for you... This blog is a collection of things I come across either at home or at work as a Linux Administrator. I have worked as an Admin working with Solaris, SAN, Backups and Linux at the Enterprise level for over 16 years.