Skip to main content

Help! Exim and IMAP going down constantly

Comments

12 comments

  • cPRex Jurassic Moderator
    Hey there! Intermittent issues are always the worst to troubleshoot. Since you mentioned you have a large number of users, does this seem to happen more during certain times of day? If so, it could be hitting authentication limits on the mailserver. I'd recommend checking the /var/log/maillog file on the system as that would show users authenticating to the mailserver, and could provide clues as to what the issue may be.
    0
  • Lksrainmaker
    Thanks for your reply, Well, we have something around 100 users perhaps less, and I mean, we had a year working without problems. I'll get a tail of the log to show: Sep 2 13:46:00 vps-281291 dovecot: imap-login: Login: user=, method=PLAIN, rip=xxx.xxx.xxx.xxx, lip=xxx.xxx.xxx.xxx, mpid=15035, TLS, session=<4AQvwQbLFeqkTYHb> Sep 2 13:46:01 vps-281291 dovecot: auth: Error: policy(mail@mail.cl,xxx.xxx.xxx.xxx,): Policy server HTTP error: Absolute request timeout expired (Request queued 3.000 secs ago, not yet sent, 0.000 in other ioloops) Sep 2 13:46:01 vps-281291 dovecot: pop3-login: Login: user=, method=PLAIN, rip=xxx.xxx.xxx.xxx, lip=xxx.xxx.xxx.xxx, mpid=15036, session= Sep 2 13:46:02 vps-281291 dovecot: pop3(svallejos@wabo.cl)<15036>: Disconnected: Logged out top=0/0, retr=0/0, del=0/61, size=49831208, bytes=24/2098 Sep 2 13:46:02 vps-281291 dovecot: auth: Error: policymail@mail.cll,xxx.xxx.xxx.xxx,): Policy server HTTP error: Absolute request timeout expired (Request queued3.001 secs ago, not yet sent, 0.000 in other ioloops) Sep 2 13:46:03 vps-281291 dovecot: auth: Error: policy(mail@mail.cl,xxx.xxx.xxx.xxx,<4AQvwQbLFeqkTYHb>): Policy server HTTP error: Absolute request timeout expired (Request queued 3.000 secs ago, not yet sent, 0.000 in other ioloops) Sep 2 13:46:04 vps-281291 dovecot: auth: Error: policy(mail@mail.cl,xxx.xxx.xxx.xxx,): Policy server HTTP error: Absolute request timeout expired (Request queued 3.000 secs ago, not yet sent, 0.000 in other ioloops) Sep 2 13:46:05 vps-281291 dovecot: auth: Error: policy(mail@mail.cl,xxx.xxx.xxx.xxx,): Policy server HTTP error: Absolute request timeout expired (Request queued3.001 secs ago, not yet sent, 0.000 in other ioloops) Sep 2 13:46:05 vps-281291 dovecot: imap-login: Login: user=, method=PLAIN, rip=xxx.xxx.xxx.xxx, lip=xxx.xxx.xxx.xxx, mpid=15038, TLS, session= Sep 2 13:46:08 vps-281291 dovecot: auth: Error: policy(mail@mail.cl,xxx.xxx.xxx.xxx,): Policy server HTTP error: Absolute request timeout expired (Request queued3.002 secs ago, not yet sent, 0.000 in other ioloops) at least now I know what to search on google! Any insight on this?
    0
  • cPRex Jurassic Moderator
    I'm glad that log was helpful, and that's exactly what I needed to see. While it doesn't lead us to the exact issue, it's a major clue. Out of curiosity, what do you see in WHM >> cPHulk Brute Force Protection by going to the "History Reports" tab? Are there a lot of IP addresses being blocked in a relatively short timeframe? Could you also try running this command and let me know the number it provides? ps aux | grep -i [c]phulk | grep -v tail | wc -l
    0
  • Lksrainmaker
    Thanks! cPHulk actually sometimes is shown as down in service status, regarding your question it is shown as active in the cPHulk menu and the History Reports are blank, except for one IP in the one day blocked. En the code result is: 2
    0
  • cPRex Jurassic Moderator
    So what I'm wondering is if some other service not related to email is causing issues with cPHulk and that's causing other problems. Did you get a chance to get the locked history list to see if there is a large amount of IPs there?
    0
  • Lksrainmaker
    Thanks for your reply, well, I'm attaching images about that. but as mentioned earlier, there was only one blocked IP in the GUI log, I've been looking for a command in the web to see another blocked IP log without success.
    0
  • cPRex Jurassic Moderator
    Interesting...it might be best to open a ticket to have us take a look directly as it seems there is something else going on with the machine. If you do open a ticket, please post the number here so I can follow along and make sure this thread gets updated.
    0
  • Lksrainmaker
    Thanks for your help! I did raise a ticket, here is the ID Support ID 94359454. I Will let you know when the problem gets solved.
    0
  • cPRex Jurassic Moderator
    Thanks for that - I'm following along with that on my end now.
    0
  • cPRex Jurassic Moderator
    Well it looks like we were on the right track! After some troubleshooting it was found that ClamD wasn't working properly due to some issues with the machine's firewall not allowing connections on port 579.
    0
  • Lksrainmaker
    Yes, it seems so far that was the problem... I've been monitoring for about an hour without problems, will wait a couple of days to see if the problem is totally solved. Thanks a lot cPRex
    0
  • cPRex Jurassic Moderator
    Glad to hear it's working well now!
    0

Please sign in to leave a comment.