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 cypher 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 happened because a username was changed which had the UID of 60064.
Previously
jradtke:x:60064:1063:James 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
Now.. my username had been changed to
jradtke@corp.company.com
jradtke@corp.company.com:x:60064:1063:James Radtke:/home/jradtke:/bin/bash
To remedy the issue:
mv /var/spool/cron/jradtke /var/spool/cron/jradtke@corp.company.com
chown `getent passwd jradtke@corp.company.com | awk -F\: '{ print $3":"$4 }'` /var/spool/cron/jradtke@corp.company.com
I decided to document this as I was unable to find any useful information that dealt with my particular situation. (all the other examples with that error mentioned updating pam, etc...)
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 cypher 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 happened because a username was changed which had the UID of 60064.
Previously
jradtke:x:60064:1063:James 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
Now.. my username had been changed to
jradtke@corp.company.com
jradtke@corp.company.com:x:60064:1063:James Radtke:/home/jradtke:/bin/bash
To remedy the issue:
mv /var/spool/cron/jradtke /var/spool/cron/jradtke@corp.company.com
chown `getent passwd jradtke@corp.company.com | awk -F\: '{ print $3":"$4 }'` /var/spool/cron/jradtke@corp.company.com
I decided to document this as I was unable to find any useful information that dealt with my particular situation. (all the other examples with that error mentioned updating pam, etc...)
Comments
Post a Comment