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

P2V using dd for KVM-QEMU guest

Preface: I have certainly not exhaustively tested this process.  I had a specific need and found a specific solution that worked. Situation:  I was issued a shiny new laptop running Red Hat Enterprise Linux 7 (with Corp VPN, certs, Authentication configuration, etc...)  The image was great, but I needed more flexibility on my bare metal.  So, my goal was to P2V the corporate image so I could just run it as a VM. * Remove corporate drive and install new SSD * install corp drive in external USB-3 case * Install RHEL 7 on new SSD * dd old drive to a disk-image file in a temp location which will be an image which is the same size as your actual drive (unless you have enough space in your destination to contain a temp and converted image) * convert the raw disk-image to a qcow file while pushing it to the final location - this step should reduce the disk size - however, I believe it will only reduce/collapse zero-byte blocks (not just free space - i.e. if you de...
1 comment
Read more

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

"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