Skip to main content
cPanel Technical Support has been heavily impacted by hurricane Beryl and our ability to respond to tickets has been hindered as a result. We appreciate your understanding and patience as we address these delays.

systemctl status dovecot.service issue

Comments

7 comments

  • cPanelLauren
    Hi @msullivan Dovecot is responsible for POP and IMAP connections. If you have users connecting to check their mail, the more user's you have the more dovecot related processes you'll see. What I do find odd is that you're seeing output from Apr-Jul when it's Aug. If you restart the service does this behavior continue? /scripts/restartsrv_dovecot --stop /scripts/restartsrv_dovecot --start
    0
  • msullivan
    Hi @msullivan Dovecot is responsible for POP and IMAP connections. If you have users connecting to check their mail, the more user's you have the more dovecot related processes you'll see. What I do find odd is that you're seeing output from Apr-Jul when it's Aug. If you restart the service does this behavior continue? /scripts/restartsrv_dovecot --stop /scripts/restartsrv_dovecot --start

    Thanks for the reply. I get what Dovecot is doing on the server. :) I"ve never seen this behaviour before over the past 9 years of administering several VPS. When I tried to restart Dovecot with the commands you suggested, the service took about a minute and a half to stop, and currently running the "start" script and it"s spewing out the logs from April again, similar to as I noted in my first post. Also just got an email from the system telling me that POP is down. :( Not sure what"s up with the super old logs either. Is there any way to flush them? Thanks, Michael
    0
  • cPanelLauren
    Hi @msullivan I'm not sure either without actually seeing what's going on. Can you please open a ticket using the link in my signature? Once open please reply with the Ticket ID here so that we can update this thread with the resolution once the ticket is resolved. Thanks!
    0
  • msullivan
    Hi @cPanelLauren! I've opened a ticket. Ticket ID is: 10171883 Thanks, Michael
    0
  • cPanelLauren
    Hi @msullivan I just took a look at your ticket and it looks like the analyst believes these older logs are a result of a customization made. You noted you were going to check with your provider, please let us know what becomes of that. Thanks!
    0
  • tui
    Did you resolved your problem? im having exactly the same problem
    0
  • msullivan
    @tui, No direct solution from my provider either. They suggested I use lsof -p to watch the process and see if I could find out what was going on. I also used journalctl --vaccum=500M to reduce the log from gigabytes to 500 megabytes. This reduced the length the process was running, in the end, after having done that I haven't noticed the process running as hard on the system like I was when I asked my initial question. Somewhere along the line (maybe a CentOS update) I've noticed that when I run systemctl status dovecot.service, the output prints nearly immediately instead of running through thousands of lines of log output. Currently running: centos-release-7-5.1804.4.el7.centos.x86_64 & cPanel 74.0.8 Hope this helps in some way! Michael
    0

Please sign in to leave a comment.