I can't say that I've run into something like that before. Maybe some of the
other folks that have been running BQ longer than I have would be able to
shed some light on the subject.
As for the updates. Comment-out the lines inside this file or just move the
BlueQuartz-Base.repo to a temporary location and then run yum update.
Or. Just update Dovecot it's self.
I don't believe that the newer dovecot is what has been causing all the
recent issues, but then again, there are others on this list that know the
history of BQ/Linux much better than I.
Doug
-----Original Message-----
From: Xin CHEN [mailto:xchen (at mark) housleyconsulting.com.au]
Sent: Sunday, March 15, 2009 4:13 PM
To: coba-e (at mark) bluequartz.org
Subject: [coba-e:15318] Re: Dovecot Auth I/O Leak Error
Hi Jimmy,
Thanks for the comments. We have other Servers running just fine
without update as well. The reason I am afraid of updating system is
that I saw a lot of emails that says "after updating, we have problems
with ..... " These are all production Servers. So I don't want to
update unless have to. Has anyone had this kind of error messages
before?
Thanks,
tim
On 15/03/2009, at 1:03 PM, Jimmy Gross wrote:
> You need to run yum update so your servers are updated with the newest
> version on Dovecot.
>
> jimmy
>
> -----Original Message-----
> From: Xin CHEN [mailto:xchen (at mark) housleyconsulting.com.au]
> Sent: Saturday, March 14, 2009 7:50 PM
> To: coba-e (at mark) bluequartz.org
> Subject: [coba-e:15314] Dovecot Auth I/O Leak Error
>
>
> Hi All,
>
> We have couple of BQ Servers running (Centos 4.5). We didn't do yum
> update to any of the Server yet.
>
> One of our Server has some problems with Dovecot these days.
>
> In the maillog file, there are a lot of messages:
> Mar 15 11:01:09 s8 dovecot: auth(default): I/O leak: 0x805e160 (928)
> Mar 15 11:01:09 s8 dovecot: auth(default): I/O leak: 0x805e160 (919)
> Mar 15 11:01:09 s8 dovecot: auth(default): I/O leak: 0x805e160 (569)
> Mar 15 11:01:09 s8 dovecot: auth(default): I/O leak: 0x805e160 (153)
> Mar 15 11:01:09 s8 dovecot: auth(default): I/O leak: 0x805e160 (533)
> Mar 15 11:01:09 s8 dovecot: auth(default): I/O leak: 0x805e160 (361)
> Mar 15 11:01:09 s8 dovecot: auth(default): I/O leak: 0x805e160 (271)
> Mar 15 11:01:09 s8 dovecot: auth(default): I/O leak: 0x805e160 (219)
> Mar 15 11:01:09 s8 dovecot: auth(default): I/O leak: 0x805e160 (424)
> Mar 15 11:01:09 s8 dovecot: auth(default): I/O leak: 0x805e160 (413)
> Mar 15 11:01:09 s8 dovecot: auth(default): I/O leak: 0x805e160 (374)
> Mar 15 11:01:09 s8 dovecot: auth(default): I/O leak: 0x805e160 (947)
> Mar 15 11:01:09 s8 dovecot: auth(default): I/O leak: 0x805e160 (930)
> Mar 15 11:01:09 s8 dovecot: auth(default): I/O leak: 0x805e160 (923)
> Mar 15 11:01:09 s8 dovecot: auth(default): I/O leak: 0x805e160 (249)
>
> We can get more than 1000 process running when checking process: ps -
> ef |grep dovecot-auth
> root 26456 1 0 Mar08 ? 00:00:00 dovecot-auth
> root 26457 1 0 Mar08 ? 00:00:00 dovecot-auth
> root 26458 1 0 Mar08 ? 00:00:00 dovecot-auth
> root 26459 1 0 Mar08 ? 00:00:00 dovecot-auth
> root 26460 1 0 Mar08 ? 00:00:00 dovecot-auth
> root 26461 1 0 Mar08 ? 00:00:00 dovecot-auth
> root 26462 1 0 Mar08 ? 00:00:00 dovecot-auth
> root 26463 1 0 Mar08 ? 00:00:00 dovecot-auth
> root 26464 1 0 Mar08 ? 00:00:00 dovecot-auth
> root 26711 1 0 Mar08 ? 00:00:00 dovecot-auth
> root 26712 1 0 Mar08 ? 00:00:00 dovecot-auth
> root 26713 1 0 Mar08 ? 00:00:00 dovecot-auth
> root 26720 1 0 Mar08 ? 00:00:00 dovecot-auth
> root 26721 1 0 Mar08 ? 00:00:00 dovecot-auth
> root 26722 1 0 Mar08 ? 00:00:00 dovecot-auth
> root 26831 1 0 Mar08 ? 00:00:00 dovecot-auth
> root 26833 1 0 Mar08 ? 00:00:00 dovecot-auth
>
> Is this a bug in dovecot ?
>
> I will try to kill them all and restart dovecot for now. Any
> suggestions are appreciated!
>
> -tim
>
>
>