On 09 Mar 2011, at 20:16, Timo Sirainen wrote:
> On 8.3.2011, at 19.42, Thierry de Montaudry wrote:
>
>>> So... if the httpd process is the one consuming all of the CPU, doesn't
>>> it stand to reason that it might be something to do with one of your web
>>> apps, and not dovecot?
>>>
>> But the
On 8.3.2011, at 19.42, Thierry de Montaudry wrote:
>> So... if the httpd process is the one consuming all of the CPU, doesn't
>> it stand to reason that it might be something to do with one of your web
>> apps, and not dovecot?
>>
> But then why was it fine with 1.1.13, which never had once this
On 03/08/2011 10:37 PM, Robert Schetterer wrote:
Am 08.03.2011 21:38, schrieb Attila Nagy:
On 03/08/2011 06:51 PM, Charles Marcus wrote:
On 2011-03-08 12:42 PM, Thierry de Montaudry wrote:
On 08 Mar 2011, at 19:37, Charles Marcus wrote:
So... if the httpd process is the one consuming all o
On 03/08/2011 09:58 PM, Charles Marcus wrote:
I think this is clearly related to Dovecot. It handles load very badly
Whoa, pardner, fyi, there are many, many installations humming along
smoothly.
No offense. It may be more correct to say situations, where the OS can't
deliver prompt resources
Am 08.03.2011 21:38, schrieb Attila Nagy:
> On 03/08/2011 06:51 PM, Charles Marcus wrote:
>> On 2011-03-08 12:42 PM, Thierry de Montaudry wrote:
>>> On 08 Mar 2011, at 19:37, Charles Marcus wrote:
So... if the httpd process is the one consuming all of the CPU, doesn't
it stand to reason
On 2011-03-08 3:38 PM, Attila Nagy wrote:
> On 03/08/2011 06:51 PM, Charles Marcus wrote:
>> You don't see how it might be possible that 2.0.x does something that
>> 1.1.x didn't do that your webmail app might not like, without it being a
>> dovecot bug?
>>
>> I'm not saying it is or it isn't, but
On 03/08/2011 06:51 PM, Charles Marcus wrote:
On 2011-03-08 12:42 PM, Thierry de Montaudry wrote:
On 08 Mar 2011, at 19:37, Charles Marcus wrote:
So... if the httpd process is the one consuming all of the CPU, doesn't
it stand to reason that it might be something to do with one of your web
app
On 2011-03-08 12:42 PM, Thierry de Montaudry wrote:
> On 08 Mar 2011, at 19:37, Charles Marcus wrote:
>> So... if the httpd process is the one consuming all of the CPU, doesn't
>> it stand to reason that it might be something to do with one of your web
>> apps, and not dovecot?
> But then why was
On 2011-03-08 12:30 PM, Thierry de Montaudry wrote:
> On 08 Mar 2011, at 19:11, Charles Marcus wrote:
>> The reason I asked about your webmail server is you had specifically
>> said that it was the httpd process that was consuming all of the CPU...
> Yes, because they were in the top of the top li
On 08 Mar 2011, at 19:37, Charles Marcus wrote:
> On 2011-03-08 12:30 PM, Thierry de Montaudry wrote:
>> On 08 Mar 2011, at 19:11, Charles Marcus wrote:
>>> The reason I asked about your webmail server is you had specifically
>>> said that it was the httpd process that was consuming all of the CP
On 2011-03-08 12:30 PM, Thierry de Montaudry wrote:
> On 08 Mar 2011, at 19:11, Charles Marcus wrote:
>> The reason I asked about your webmail server is you had specifically
>> said that it was the httpd process that was consuming all of the CPU...
> Yes, because they were in the top of the top li
On 08 Mar 2011, at 19:12, Charles Marcus wrote:
> On 2011-03-08 12:00 PM, Thierry de Montaudry wrote:
>> but moving from dovecot 1.10.13 to 2.0.9
>
> First time I thought it was a typo and ignored it...
>
> There has never been a version 1.10.xxx
>
> Maybe you mean 1.0.13?
>
Sorry, my mista
On 08 Mar 2011, at 19:11, Charles Marcus wrote:
> On 2011-03-08 11:49 AM, Thierry de Montaudry wrote:
>> Using HastyMail2-1.0. But the problem only started when we moved to
>> dovecot 2.0.9 (from 1.10.13), without changing anything else on any
>> of our 7 machines, and now it's happening randomly
On 2011-03-08 12:00 PM, Thierry de Montaudry wrote:
> but moving from dovecot 1.10.13 to 2.0.9
First time I thought it was a typo and ignored it...
There has never been a version 1.10.xxx
Maybe you mean 1.0.13?
--
Best regards,
Charles
On 2011-03-08 11:49 AM, Thierry de Montaudry wrote:
> Using HastyMail2-1.0. But the problem only started when we moved to
> dovecot 2.0.9 (from 1.10.13), without changing anything else on any
> of our 7 machines, and now it's happening randomly on any of them. So
> that's why I suspect it has to do
On 08 Mar 2011, at 18:26, Chris Wilson wrote:
> Hi Thierry,
>
> On Tue, 8 Mar 2011, Thierry de Montaudry wrote:
>> On 08 Mar 2011, at 13:24, Chris Wilson wrote:
>>>
top - 11:10:14 up 14 days, 12:04, 2 users, load average: 55.04, 29.13,
14.55
Tasks: 474 total, 60 running, 414
On 08 Mar 2011, at 18:14, Charles Marcus wrote:
> On 2011-03-08 10:40 AM, Thierry de Montaudry wrote:
>> On 08 Mar 2011, at 13:24, Chris Wilson wrote:
>>> There's nothing to debug in dovecot here. Your server is overloaded
>>> by about 55 times. Buy 55 times as many servers or do something
>>> ab
On 03/08/2011 09:26 AM, Chris Wilson wrote:
Hi Thierry,
On Tue, 8 Mar 2011, Thierry de Montaudry wrote:
On 08 Mar 2011, at 13:24, Chris Wilson wrote:
top - 11:10:14 up 14 days, 12:04, 2 users, load average: 55.04, 29.13, 14.55
Tasks: 474 total, 60 running, 414 sleeping, 0 stopped, 0 z
Hi Thierry,
On Tue, 8 Mar 2011, Thierry de Montaudry wrote:
> On 08 Mar 2011, at 13:24, Chris Wilson wrote:
> >
> >> top - 11:10:14 up 14 days, 12:04, 2 users, load average: 55.04, 29.13,
> >> 14.55
> >> Tasks: 474 total, 60 running, 414 sleeping, 0 stopped, 0 zombie
> >> Cpu(s): 99.6%us,
On 2011-03-08 10:40 AM, Thierry de Montaudry wrote:
> On 08 Mar 2011, at 13:24, Chris Wilson wrote:
>> There's nothing to debug in dovecot here. Your server is overloaded
>> by about 55 times. Buy 55 times as many servers or do something
>> about your webmail interface (maybe a separate webmail clu
On 08 Mar 2011, at 13:24, Chris Wilson wrote:
> Hi Thierry,
>
> On Tue, 8 Mar 2011, Thierry de Montaudry wrote:
>> On 07 Mar 2011, at 19:15, Timo Sirainen wrote:
>>> On Mon, 2011-03-07 at 19:03 +0200, Thierry de Montaudry wrote:
> Mar 7 11:19:51 xxx dovecot: pop3-login: Error:
On 07 Mar 2011, at 19:15, Timo Sirainen wrote:
> On Mon, 2011-03-07 at 19:03 +0200, Thierry de Montaudry wrote:
>>> Mar 7 11:19:51 xxx dovecot: pop3-login: Error: net_connect_unix(pop3)
>>> failed: Resource temporarily unavailable
>>> ..
>> As it is happening at least once a day, is ther
On Mon, 2011-03-07 at 19:03 +0200, Thierry de Montaudry wrote:
> > Mar 7 11:19:51 xxx dovecot: pop3-login: Error: net_connect_unix(pop3)
> > failed: Resource temporarily unavailable
> > ..
> As it is happening at least once a day, is there anything I can do to trace
> it? and whatever I'
On 07 Mar 2011, at 17:17, Timo Sirainen wrote:
> On Mon, 2011-03-07 at 13:40 +0200, Thierry de Montaudry wrote:
> Mar 7 11:19:51 xxx dovecot: pop3-login: Error: net_connect_unix(pop3)
> failed: Resource temporarily unavailable
> ..
>>> Do you see any warning messages in logs containing
On Mon, 2011-03-07 at 13:40 +0200, Thierry de Montaudry wrote:
> >>> Mar 7 11:19:51 xxx dovecot: pop3-login: Error: net_connect_unix(pop3)
> >>> failed: Resource temporarily unavailable
..
> > Do you see any warning messages in logs containing "client connections are
> > being dropped"?
> >
> I
On 07 Mar 2011, at 12:01, Timo Sirainen wrote:
> On 7.3.2011, at 11.51, Thierry de Montaudry wrote:
>
>> Since we upgraded to 2.0.9 (from 1.10 stock CentOS release), we are getting
>> some errors with pop3. When the machines get busy, now and then it start
>> with the following:
>>> Mar 7 11:
On 7.3.2011, at 11.51, Thierry de Montaudry wrote:
> Since we upgraded to 2.0.9 (from 1.10 stock CentOS release), we are getting
> some errors with pop3. When the machines get busy, now and then it start with
> the following:
>> Mar 7 11:19:51 xxx dovecot: pop3-login: Error: net_connect_unix(po
On 3/9/2009 8:07 PM, Mark Sapiro wrote:
Jeff Grossman wrote:
I just looked over my logs and noticed the following error:
Mar 9 19:07:34 apple dovecot: Panic: POP3(april): Trying to allocate 0
bytes
Mar 9 19:07:34 apple dovecot: POP3(april): Raw backtrace: pop3
[0x492952] -> pop3 [0x4929
Jeff Grossman wrote:
> I just looked over my logs and noticed the following error:
>
> Mar 9 19:07:34 apple dovecot: Panic: POP3(april): Trying to allocate 0
> bytes
> Mar 9 19:07:34 apple dovecot: POP3(april): Raw backtrace: pop3
> [0x492952] -> pop3 [0x4929d3] -> pop3 [0x4920e6] -> pop3 [0x
29 matches
Mail list logo
