List Info

Thread: RE: CPU LOAD




RE: CPU LOAD
country flaguser name
Portugal
2007-10-05 16:55:26
Ok,
Did what you sugested, so i just deleted ALL messages in
postfix queue:
"postsuper -d ALL"

Have a lmtpd process with 100% cpu usage, and it still with
the same usage,
going to restart dbmail and tomorrow morning I'll see if
there's any
diference.



-----Original Message-----
From: dbmail-bouncesdbmail.org [mailto:dbmail-bouncesdbmail.org] On Behalf
Of Paul J Stevens
Sent: sexta-feira, 5 de Outubro de 2007 21:22
To: DBMail mailinglist
Subject: Re: [Dbmail] CPU LOAD

Jorge Bastos wrote:
> Paul,
> With the last svn today, this is still hapenning.
> And using strace to see that are the processes doing,
doesn't show me
> nothing.

And I'm not a psychic. Like Marc said: check your postfix
queue. There
should also be postfix errors in your syslog. Then, on your
postfix
server run 'mailq' and see if there are certain messages
that have been
hanging around in the queue for too long with errors coming
back from
your own lmtp server. Then, once you establish a postfix
queue-ID,
retrieve such a message from the queue using 'postcat -q
queue-ID'.

make any sense?

-- 
 
____________________________________________________________
____
  Paul Stevens                                      paul at
nfg.nl
  NET FACILITIES GROUP                     GPG/PGP:
1024D/11F8CD31
  The Netherlands________________________________http://www.nfg.nl
_______________________________________________
DBmail mailing list
DBmaildbmail.org
htt
ps://mailman.fastxs.nl/mailman/listinfo/dbmail

_______________________________________________
DBmail mailing list
DBmaildbmail.org
htt
ps://mailman.fastxs.nl/mailman/listinfo/dbmail

Re: CPU LOAD
country flaguser name
Netherlands
2007-10-05 18:45:14
>
> Have a lmtpd process with 100% cpu usage, and it still
with the  
> same usage,
> going to restart dbmail and tomorrow morning I'll see
if there's any
> diference.
>

Empty the queue?? No angry customers?

As soon as a message messes a lmtp daemon up (although
dbmail should  
work around this) it keeps on using 100% cpu.
Just try killing the daemon which is eating cpu, and see if
the  
problem returns.

Marc
_______________________________________________
DBmail mailing list
DBmaildbmail.org
htt
ps://mailman.fastxs.nl/mailman/listinfo/dbmail

RE: CPU LOAD
country flaguser name
Portugal
2007-10-06 04:48:30
Marc, i already emptyed the queue :P
No problem, they were spam messages in fact, there were
about 80 messages
there.

Aaron, now everything is working OK after emptyed the
postfix queue, let
past a few days to see if this returns and I'll contact the
list again for
you guys catch this problem.
Even this been spam messages shouldn't happen as you know.



-----Original Message-----
From: dbmail-bouncesdbmail.org [mailto:dbmail-bouncesdbmail.org] On Behalf
Of Aaron Stone
Sent: sábado, 6 de Outubro de 2007 1:12
To: DBMail mailinglist
Subject: Re: [Dbmail] CPU LOAD

On Fri, Oct 5, 2007, Marc Dirix <marcelectronics-design.nl> said:

>>
>> Have a lmtpd process with 100% cpu usage, and it
still with the  
>> same usage,
>> going to restart dbmail and tomorrow morning I'll
see if there's any
>> diference.
>>
> 
> Empty the queue?? No angry customers?
> 
> As soon as a message messes a lmtp daemon up (although
dbmail should  
> work around this) it keeps on using 100% cpu.
> Just try killing the daemon which is eating cpu, and
see if the  
> problem returns.

If strace shows nothing, it likely means we're in a loop
without any
syscalls. If you can pinpoint a message that causes lmtpd to
explode,
that'd be awesome, we can run under gdb and see where the
problem could be
caught.

Aaron
_______________________________________________
DBmail mailing list
DBmaildbmail.org
htt
ps://mailman.fastxs.nl/mailman/listinfo/dbmail

_______________________________________________
DBmail mailing list
DBmaildbmail.org
htt
ps://mailman.fastxs.nl/mailman/listinfo/dbmail

Re: CPU LOAD
country flaguser name
Netherlands
2007-10-06 04:44:53
>>
> If strace shows nothing, it likely means we're in a
loop without any
> syscalls. If you can pinpoint a message that causes
lmtpd to explode,
> that'd be awesome, we can run under gdb and see where
the problem  
> could be
> caught.
>

It is indeed a very tight loop, without any syscalls. We
currently  
have no message saved which triggers this
problem.
_______________________________________________
DBmail mailing list
DBmaildbmail.org
htt
ps://mailman.fastxs.nl/mailman/listinfo/dbmail

RE: CPU LOAD
country flaguser name
Finland
2007-10-06 16:17:39
damn nerds...
 

> -----Original Message-----
> From: dbmail-bouncesdbmail.org 
> [mailto:dbmail-bouncesdbmail.org] On Behalf Of
Jorge Bastos
> Sent: Saturday, October 06, 2007 4:08 PM
> To: 'DBMail mailinglist'
> Subject: RE: [Dbmail] CPU LOAD
> 
> Kiss=kill
> 
> lol
> 
> -----Original Message-----
> From: dbmail-bouncesdbmail.org 
> [mailto:dbmail-bouncesdbmail.org] On Behalf Of
Jorge Bastos
> Sent: sábado, 6 de Outubro de 2007 13:35
> To: 'DBMail mailinglist'
> Subject: RE: [Dbmail] CPU LOAD
> 
> Yap, i've remembered that after reading these last
emails... 
> now caputz.
> If this happens again, and I hope so to kiss this bug,
I'll do it.
> 
> 
> 
> 
> -----Original Message-----
> From: dbmail-bouncesdbmail.org 
> [mailto:dbmail-bouncesdbmail.org] On Behalf Of
Aleksander Kamenik
> Sent: sábado, 6 de Outubro de 2007 13:17
> To: DBMail mailinglist
> Subject: Re: [Dbmail] CPU LOAD
> 
> Jorge Bastos wrote:
> > Marc, i already emptyed the queue :P
> > No problem, they were spam messages in fact, there
were about 80 
> > messages there.
> 
> You should have saved all the messages from the queue
and 
> then for example by deleting them one by one and
restaring 
> dbmail-lmtpd between each delete determine which
message was 
> the problematic one that caused the problem.
> 
> Try this or something similar next time this problem
occurs.
> 
> --
> Aleksander Kamenik
> system administrator
> +372 6659 649
> aleksanderkrediidiinfo.ee
> 
> Krediidiinfo AS
> http://www.krediidiinfo.e
e/
> _______________________________________________
> DBmail mailing list
> DBmaildbmail.org
> htt
ps://mailman.fastxs.nl/mailman/listinfo/dbmail
> 
> _______________________________________________
> DBmail mailing list
> DBmaildbmail.org
> htt
ps://mailman.fastxs.nl/mailman/listinfo/dbmail
> 
> _______________________________________________
> DBmail mailing list
> DBmaildbmail.org
> htt
ps://mailman.fastxs.nl/mailman/listinfo/dbmail
> 
> 

_______________________________________________
DBmail mailing list
DBmaildbmail.org
htt
ps://mailman.fastxs.nl/mailman/listinfo/dbmail

Re: CPU LOAD
country flaguser name
Portugal
2007-10-09 15:47:50
Paul/Aaron,
I have an possible idea on what was causing this high load
on lmtpd.
I've noticed some messages that were beeing sent to a user
who has the 
mailbox full.
It's just a remote idea for now, i'll tell you more when i
have something 
more consistent.

I say this because now i had clamd using the cpu too, and i
went to see the 
postfix queue, and most of the emails are some of those,
with the mailbox 
status full


----- Original Message ----- 
From: "Jorge Bastos" <mysql.jorgedecimal.pt>
To: "'DBMail mailinglist'" <dbmaildbmail.org>
Sent: Saturday, October 06, 2007 2:08 PM
Subject: RE: [Dbmail] CPU LOAD


Kiss=kill

lol

-----Original Message-----
From: dbmail-bouncesdbmail.org [mailto:dbmail-bouncesdbmail.org] On Behalf
Of Jorge Bastos
Sent: sábado, 6 de Outubro de 2007 13:35
To: 'DBMail mailinglist'
Subject: RE: [Dbmail] CPU LOAD

Yap, i've remembered that after reading these last emails...
now caputz.
If this happens again, and I hope so to kiss this bug, I'll
do it.




-----Original Message-----
From: dbmail-bouncesdbmail.org [mailto:dbmail-bouncesdbmail.org] On Behalf
Of Aleksander Kamenik
Sent: sábado, 6 de Outubro de 2007 13:17
To: DBMail mailinglist
Subject: Re: [Dbmail] CPU LOAD

Jorge Bastos wrote:
> Marc, i already emptyed the queue :P
> No problem, they were spam messages in fact, there were
about 80 messages
> there.

You should have saved all the messages from the queue and
then for
example by deleting them one by one and restaring
dbmail-lmtpd between
each delete determine which message was the problematic one
that caused
the problem.

Try this or something similar next time this problem
occurs.

-- 
Aleksander Kamenik
system administrator
+372 6659 649
aleksanderkrediidiinfo.ee

Krediidiinfo AS
http://www.krediidiinfo.e
e/
_______________________________________________
DBmail mailing list
DBmaildbmail.org
htt
ps://mailman.fastxs.nl/mailman/listinfo/dbmail

_______________________________________________
DBmail mailing list
DBmaildbmail.org
htt
ps://mailman.fastxs.nl/mailman/listinfo/dbmail

_______________________________________________
DBmail mailing list
DBmaildbmail.org
htt
ps://mailman.fastxs.nl/mailman/listinfo/dbmail

_______________________________________________
DBmail mailing list
DBmaildbmail.org
htt
ps://mailman.fastxs.nl/mailman/listinfo/dbmail

[1-6]

about | contact  Other archives ( Real Estate discussion Medical topics )