how frequently does the letter m appear in:
q: pam unable to dlopen(/lib64/security/pam_fprintd.so) causing centos/redhat server to crash centos 6, parallels plesk 10.4, apache
one of my servers went down over the weekend much to my dismay.  on the day and time it occurred, my log errors/messages end with this -
/var/log/secure:
jul 29 03:53:15 u######## su: pam adding faulty module: 
  /lib64/security/pam_fprintd.so
jul 29 03:53:15 u######## su: pam_unix(su-l:session): 
  session opened for user popuser by (uid=0)
jul 29 03:53:16 u######## su: pam_unix(su-l:session): 
  session closed for user popuser
jul 29 03:53:16 u######## su: pam unable to dlopen(/lib64/security/pam_fprintd.so):
 /lib64/security/pam_fprintd.so: cannot open shared object file: no such file or
 directory
jul 29 03:53:16 u######## su: pam adding faulty module: 
 /lib64/security/pam_fprintd.so
jul 29 03:53:16 u######## su: pam_unix(su-l:session):
 session opened for user popuser by (uid=0)
jul 29 03:53:18 u######## su: pam_unix(su-l:session): 
 session closed for user popuser

then immediately afterwards,
/var/log/messages:
jul 29 03:53:21 u######## kernel: imklog 4.6.2, log source = /proc/kmsg started.
jul 29 03:53:21 u######## rsyslogd: [origin software=rsyslogd swversion=4.6.2
 x-pid=1370 x-info=http://www.rsyslog.com] (re)start

/var/log/messages (of that day):
jul 29 03:53:21 u######## rsyslogd: [origin software=rsyslogd swversion=4.6.2
 x-pid=1370 x-info=http://www.rsyslog.com] rsyslogd was huped,type restart.
jul 29 03:53:21 u######## kernel: kernel logging (proc) stopped.

and from /var/log/cron
jul 29 03:53:20 u######## run-parts(/etc/cron.daily)[29257]: starting awstats
jul 29 03:53:20 u######## run-parts(/etc/cron.daily)[32242]: finished awstats
jul 29 03:53:20 u######## run-parts(/etc/cron.daily)[29257]: starting logrotate

thats the last message i get before the server goes down.  everything ive googled leads me to believe that the session opened for user popuser is a fairly common log entry and shouldnt be considered a threat, but for some reason i interpret that as something not so nice.  
others have mentioned that pam adding a faulty module could be a bug?  i dont even know what pam is....
any insight on how to interpret these would be greatly appreciated.  ive checked
/var/log/secure
/var/log/messages
/var/log/cron

are there any other places i could look into to help diagnose this?
many thanks, sf.

a: jul 29 03:53:15 u######## su: pam adding faulty module: 
  /lib64/security/pam_fprintd.so

it looks like a bug: https://bugzilla.redhat.com/show_bug.cgi?id=505266
install authconfig and try this:
authconfig --disablefingerprint --update


user
There are 47 "m"s.
assistant