server status not available possible solution

[jptech]

I restarted the server after a few weeks and this is what I find in the logs:

Jun 26 22:48:01 coruscant /usr/sbin/cron[5221]: PAM unable to dlopen(/lib/security/pam_ldap.so)
Jun 26 22:48:01 coruscant /usr/sbin/cron[5221]: PAM [error: /lib/security/pam_ldap.so: cannot open shared object file: No such file or directory]
Jun 26 22:48:01 coruscant /usr/sbin/cron[5221]: PAM adding faulty module: /lib/security/pam_ldap.so
Jun 26 22:48:01 coruscant /usr/sbin/cron[5222]: (zimbra) CMD (/opt/zimbra/libexec/zmstatuslog)
Jun 26 22:48:03 coruscant sudo:   zimbra : TTY=unknown ; PWD=/opt/zimbra ; USER=root ; COMMAND=/opt/zimbra/libexec/zmtomcatmgr status
Jun 26 22:48:03 coruscant sudo: PAM unable to dlopen(/lib/security/pam_ldap.so)
Jun 26 22:48:03 coruscant sudo: PAM [error: /lib/security/pam_ldap.so: cannot open shared object file: No such file or directory]
Jun 26 22:48:03 coruscant sudo: PAM adding faulty module: /lib/security/pam_ldap.so

I checked, and pam_ldap.so wasn't installed. I fired up yast and installed it.
seems to work now.


FALSE ALARM

my logger is dying when the logs rotate.

[jholder]

Yeah, We think we have that fixed.

[jptech]

well then, how do you fix it?

I am still having the problem.

the logger dies after the logs rotate.

[jholder]

It should be included in 4.5.6 when we release it.
We had to alter some connections with the logger
See this bug:
Bug 14945 - logger intermittently stops without warning after pruning