The Community Forums

Interact with an entire community of cPanel & WHM users!
  1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

cPHulkd internal error

Discussion in 'General Discussion' started by Jason Silver, Apr 1, 2016.

  1. Jason Silver

    Jason Silver Registered

    Apr 1, 2016
    Likes Received:
    Trophy Points:
    Sydenham, Ontario, Canada
    cPanel Access Level:
    Root Administrator
    I am having this same issue - clients cannot check email, and the log says:

    Apr 1 12:47:20 whm dovecot: auth: Error: Cpanel::MailAuth: Brute force checking was skipped because cphulkd failed to process “xxx@xxx.xx” from “IP xxx.xx.xx.xx'” for the “pop3” service.

    I am not able to edit my post for some reason, (spam like?) so trying to post the server details:

    /etc/redhat-release:CentOS release 6.7 (Final)
    Server version: Apache/2.2.29 (Unix)
    Server built:   Feb 12 2015 09:32:28
    Cpanel::Easy::Apache v3.28.3 rev9999
    PHP 5.4.37 (cli) (built: Feb 12 2015 09:41:39) 
    Copyright (c) 1997-2014 The PHP Group
    Zend Engine v2.4.0, Copyright (c) 1998-2014 Zend Technologies
        with the ionCube PHP Loader v4.6.1, Copyright (c) 2002-2014, by ionCube Ltd., and
        with Zend Guard Loader v3.3, Copyright (c) 1998-2013, by Zend Technologies
    mysql  Ver 14.14 Distrib 5.5.48, for Linux (x86_64) using readline 5.1
    #1 Jason Silver, Apr 1, 2016
    Last edited by a moderator: Apr 1, 2016
  2. cPanelMichael

    cPanelMichael Forums Analyst
    Staff Member

    Apr 11, 2011
    Likes Received:
    Trophy Points:
    cPanel Access Level:
    Root Administrator
    Hello :)

    I've moved this post to a new thread because the previous internal case was addressed in cPanel version 54. I've been unable to reproduce the issue. Could you verify the "mysqlcheck cphulkd" command completes successfully and reports no corruption? Can you reproduce the issue after forcing an update of cPanel via "/scripts/upcp --force"? Is this happening for valid email accounts on domain names added to the server, or for email addresses that do not exist on valid domain names?

    Thank you

Share This Page