Skip to main content

Dovecot killed alltime

Comments

5 comments

  • User Avatar
    adamzolo
    the problem was noticed for 1 account. he has large volumes of mail
    0
  • User Avatar
    cPRex Jurassic Moderator
    Hey there! It's hard to recommend much for this situation without some additional details. Do you see that chkservd was killing this process? This would show up in /var/log/chkservd.log on the system. After restarting dovecot you can use a tool like "top" to see the amount of resources it is using.
    0
  • User Avatar
    adamzolo
    Hey there! It's hard to recommend much for this situation without some additional details. Do you see that chkservd was killing this process? This would show up in /var/log/chkservd.log on the system. After restarting dovecot you can use a tool like "top" to see the amount of resources it is using.

    Hello. Thank you for reply. Yes, dovecot had 451 error after proccess qouta-status which usage 100% cpu. I see this problem for 1 account. Account has a large emails folders, ~50GB
    0
  • User Avatar
    cPRex Jurassic Moderator
    Thanks for the details. The size of that account is going to be challenging for dovecot to read properly, as other users have experienced similar issues:
    0
  • User Avatar
    adamzolo
    O
    Thanks for the details. The size of that account is going to be challenging for dovecot to read properly, as other users have experienced similar issues:
    0

Please sign in to leave a comment.