Roderick A. Anderson wrote: > System: CentOS 5 with all current updates from the CentOS > {base,update,etc}, dhozac-vserver, and rpmforge repositories. > > I have been noticing the following type of errors in the host log files > coming from several guests. > > May 8 09:01:01 admin kernel: vxW: [�crond�,6875:#1195|1195|1195] > messing with the procfs. Brain-impaction. Solution found. Seems this really was only happening on /some/ guests and is tied to getting ssh access into a guest. I put the sed commands into a script file which, during guest creation process, is copied to the guest, executed, then removed. I have several guests that were created before I discovered this and don't need to be accessed vis ssh so were not fixed. The problem manifests itself in other places but I never never caught it until now. Thanks for reading the posts and please don't throw any rocks or sticks at me. Rod -- > > 1195 is the context for a guest but I see similar messages for other > guests. > > Researching, I see it is happening when crond runs the entires in > /etc/crontab that call run-parts and where the corresponding > cron.{hourly,daily,weekly,monthly} directory has no entries. > > Looking a bit more I see entires in the guest's /var/log/cron file like > this: > > May 8 09:01:01 rptas crond[6874]: Cannot make/remove an entry for the > specified session > May 8 09:01:01 rptas crond[6874]: CRON (root) ERROR: failed to open PAM > security session: Success > May 8 09:01:01 rptas crond[6874]: CRON (root) ERROR: cannot set ecurity > context > > Each of the files in the hosts /etc/pam.d directory have had the > following sed script applied to them. > > sed --in-place -e "s/^session.*required.*pam_loginuid.so/# > session\trequired\tpam_loginuid.so/g" /etc/pam.d/* > > This came from one of the install HOWTOs and as I reflect on it now I > wonder what it really is accomplishing. I know I've had problems with > getting a ssh login to a guest before applying this but do I need to do > it in the guests also? > > Any clues as to why I'm getting the entires? And possibly the fix? > > > Thanks, > Rod