Skip to main content

Cron Errors

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...)

  
Labels:

Comments

Post a Comment

Popular posts from this blog

Sun USS 7100 foo

TIP: put ALL of your LUNs into a designated TARGET and INITIATOR group when you create them.  If you leave them in the "default" group, then everything that does an discovery against the array will find them :-( I'm struggling to recognize a reason that a default should even be present on the array. Also - who, exactly, is Sun trying to kid.  The USS is simply a box.. running Solaris .. with IPMP and ZFS.  Great.  If you have ever attempted to "break-in" or "p0wn" your IBM HMC, you know that there are people out there that can harden a box - then.. there's Sun.  After a recent meltdown at the office I had to get quite intimate with my USS 7110 and learned quite a bit.  Namely: there's a shell ;-) My current irritation is how they attempt to "warn you" away from using the shell (my coverage expired a long time ago to worry about that) and then how they try to hide things, poorly. I was curious as to what version of SunOS it ...
1 comment
Read more

PXE boot a LiveCD image

Summary: I have wanted to build a kickstart environment which hosted a "rescue CD" or LiveCD to allow you to boot over the network after you blew your stuff up and needed to repair a few things.  Today I have worked through a method of doing so, with the help of the people who published a succinct script with the Red Hat Enterprise Virtualization Hypervisor.  (the script will be at the bottom of this post - if I have somehow not followed the GPL, please let me know and I will correct whatever is necessary) NOTE/Warning: The boot will fail due the initrd being too large (645mb).  I'm not sure how to proceed.  This procedure worked for RHEVh, because it is quite a bit smaller.  Hopefully I can report back with progress on this? :-$ Procedure: download your LiveCD image to /export/isos/RESCUE/Fedora-16-i686-Live-Desktop.iso # cd /var/tmp # vi livecd-iso-to-pxeboot (populate the file with the script shown below) # chmod 754 ./livecd-iso-to-pxeb...
2 comments
Read more

"Error getting authority: Error initializing authority: Could not connect: No such file or directory (g-io-error-quark, 1)"

"Error getting authority: Error initializing authority: Could not connect: No such file or directory (g-io-error-quark, 1)" One issue that may cause this to arise is if you managed to break your /etc/fstab We had an engineer add a line with the intended options of "nfsvers=3" but instead added "-onfsvers=3" and it broke the system fairly catastrophically.
Post a Comment
Read more