We rebooted an RHEL 5.3 system after installing the 5.2->5.3 upgrade via
yum. At start time, dovecot failed to start with the above message.
I googled this and found a couple of similar reports (nothing in the
RedHat KB, but a couple of bug reports in bugzilla--see
https://bugzilla.redhat.com/show_bug.cgi?id=103401 which is still open).
It seems the portmapper (starting up prior to dovecot) handed out port
995 to rpc.statd (lsof and rpcinfo confirmed this). Subsequent attempts
to start dovecot resulted in the same message.
As a quick fixed, I killed rpc.statd, started dovecot, and re-started
rpc.statd, which got assigned a different port.
As a longer-range fix, I re-named /etc/rc3.d/S64dovecot to
/etc/rc3.d/S13dovecot, so it would start prior to the portmapper. Have
not rebooted since, however, to test this.
Is this a valid approach, or is there some other workaround? Read the
above bug report suggests it should be ok, since it starts dovecot prior
to portmapper and all its sub-stuff like NIS.
--
Tim Evans, TKEvans.com, Inc. | 5 Chestnut Court
UNIX System Admin Consulting | Owings Mills, MD 21117
http://www.tkevans.com/ | 443-394-3864
http://www.come-here.com/News/ | [email protected]
_______________________________________________
rhelv5-list mailing list
[email protected]
https://www.redhat.com/mailman/listinfo/rhelv5-list
