CentOS - Dec 2007 - [Fwd: dovecot errors after upgrade to 5.1]

Everyone,

Looks like my Centos 5.0 mail server upgraded automatically last night
to 5.1.  It appears to have worked normally until about 16:00 CST when
dovecot began to fail.  I have rebooted the system to be able to use the
5.1 kernel, but dovecot still continues to fail.

Has anyone else made this observation?

My log entries are below

Thanks in advance!!!!

Greg Ennis
----------------------------------------------------------------


Dec  3 19:11:29 Mail dovecot: Dovecot v1.0.rc15 starting up
Dec  3 19:11:30 Mail dovecot: Temporary failure in creating login
processes, slo
wing down for now
Dec  3 19:11:30 Mail dovecot: imap-login: imap-login: error while
loading shared
 libraries: libsepol.so.1: failed to map segment from shared object:
Cannot allo
cate memory
Dec  3 19:11:30 Mail last message repeated 2 times
Dec  3 19:11:30 Mail dovecot: pop3-login: pop3-login: error while
loading shared
 libraries: libsepol.so.1: failed to map segment from shared object:
Cannot allo
cate memory
Dec  3 19:11:30 Mail last message repeated 2 times
Dec  3 19:11:30 Mail dovecot: child 7342 (login) returned error 127
Dec  3 19:11:30 Mail dovecot: child 7343 (login) returned error 127
Dec  3 19:11:30 Mail dovecot: child 7344 (login) returned error 127
Dec  3 19:11:30 Mail dovecot: child 7345 (login) returned error 127
Dec  3 19:11:30 Mail dovecot: child 7346 (login) returned error 127
Dec  3 19:11:30 Mail dovecot: child 7347 (login) returned error 127

---------------------------------------------------------------------
Do you have SELinux turned on?   If so, do things begin working if you 
turn it off?

Best,
-------------------------------------------------------------------

Good suggestion, but I do have it disabled.  I have SeLinux on my wish list to
understand, but for now it is disabled.

Greg

Gregory P. Ennis wrote:
> Everyone,
> 
> Looks like my Centos 5.0 mail server upgraded automatically last night
> to 5.1.  It appears to have worked normally until about 16:00 CST when
> dovecot began to fail.  I have rebooted the system to be able to use the
> 5.1 kernel, but dovecot still continues to fail.
> 
> Has anyone else made this observation?
It is a known problem, please read the release notes. You need to alter 
a parameter in the dovecot config.

//Morten