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.

PAM-hulk: error logging into huld: 500 AUTH FAILED

Discussion in 'General Discussion' started by cooty, Nov 14, 2011.

  1. cooty

    cooty Member

    Joined:
    Nov 14, 2011
    Messages:
    10
    Likes Received:
    0
    Trophy Points:
    1
    cPanel Access Level:
    Root Administrator
    Hi
    We've just set-up a new Internet based server and are in the process of locking the server down. We have no active users yet and nobody should be logging into this server at all other than us perhaps once an hour. /var/log/messages is full of the above errors (PAM-hulk: error logging into hulkd: 500 AUTH FAILED) which occur every minute or so. I'm not familiar with hulkd or PAM-hulk, questions:
    Is this evidence of failed login attempts to hulkd or is something else going on here?
    Please advise, thanks.
     
  2. cPanelTristan

    cPanelTristan Quality Assurance Analyst
    Staff Member

    Joined:
    Oct 2, 2010
    Messages:
    7,623
    Likes Received:
    21
    Trophy Points:
    38
    Location:
    somewhere over the rainbow
    cPanel Access Level:
    Root Administrator
    This would be in conjunction with WHM > cPHulk Brute Force Protection being enabled but it is an actual error message with that service functioning.

    Can you check if there are further errors in /usr/local/cpanel/logs/cphulkd_errors.log location and paste those errors?

    Code:
    tail -50 /usr/local/cpanel/logs/cphulkd_errors.log
    Also, could you provide your cPanel version:

    Code:
    cat /usr/local/cpanel/version
     
  3. cooty

    cooty Member

    Joined:
    Nov 14, 2011
    Messages:
    10
    Likes Received:
    0
    Trophy Points:
    1
    cPanel Access Level:
    Root Administrator
    Hi Tristan
    Thanks for your response, there are errors, the last 10:

    Auth failed for service: dovecot at /usr/local/cpanel/Cpanel/Hulkd/Processor.pm line 91.
    Auth failed for service: dovecot at /usr/local/cpanel/Cpanel/Hulkd/Processor.pm line 91.
    Auth failed for service: pam at /usr/local/cpanel/Cpanel/Hulkd/Processor.pm line 91.
    Auth failed for service: pam at /usr/local/cpanel/Cpanel/Hulkd/Processor.pm line 91.
    Auth failed for service: pam at /usr/local/cpanel/Cpanel/Hulkd/Processor.pm line 91.
    Auth failed for service: dovecot at /usr/local/cpanel/Cpanel/Hulkd/Processor.pm line 91.
    Auth failed for service: dovecot at /usr/local/cpanel/Cpanel/Hulkd/Processor.pm line 91.
    Auth failed for service: pam at /usr/local/cpanel/Cpanel/Hulkd/Processor.pm line 91.
    Auth failed for service: pam at /usr/local/cpanel/Cpanel/Hulkd/Processor.pm line 91.
    Auth failed for service: pam at /usr/local/cpanel/Cpanel/Hulkd/Processor.pm line 91.

    cpanel version 11.30.4.6
     
  4. cPanelTristan

    cPanelTristan Quality Assurance Analyst
    Staff Member

    Joined:
    Oct 2, 2010
    Messages:
    7,623
    Likes Received:
    21
    Trophy Points:
    38
    Location:
    somewhere over the rainbow
    cPanel Access Level:
    Root Administrator
    Could you try a forced cPanel update:

    Code:
    /scripts/upcp --force
    If that doesn't work, could you issue the following command:

    Code:
    /scripts/restartsrv_cphulkd
    Then check it is running:

    Code:
    /scripts/restartsrv_cphulkd --status
    While issuing the above, please tail the error log in another window:

    Code:
    tail -f /usr/local/cpanel/logs/cphulkd_errors.log
    We were having a prior issue where this was happening in versions prior to 11.30.1.0 but your cPanel version is higher than that. That prior case was 50877 but it should not be happening on the version you are using for cPanel.
     
  5. cooty

    cooty Member

    Joined:
    Nov 14, 2011
    Messages:
    10
    Likes Received:
    0
    Trophy Points:
    1
    cPanel Access Level:
    Root Administrator
    ...that wasn't a small update!
    The update ran but I can't tell you if was successful or not - there's a large amount of info here. The version is the same before 11.30.4.6. I tried to use the script to restart it but it doesn't exist and since we're only doing a cat of a file I don't believe it'll make a difference to the version number.
    I apologise but I didn't see the last part until I finished the forced update. There's been no errors since though - 25 minutes. I'll check again in the morning.
     
  6. cooty

    cooty Member

    Joined:
    Nov 14, 2011
    Messages:
    10
    Likes Received:
    0
    Trophy Points:
    1
    cPanel Access Level:
    Root Administrator
    Hi Tristan
    I can confirm that I've had no more PAM-hulk messages. Thanks for your help.
     
  7. cPanelTristan

    cPanelTristan Quality Assurance Analyst
    Staff Member

    Joined:
    Oct 2, 2010
    Messages:
    7,623
    Likes Received:
    21
    Trophy Points:
    38
    Location:
    somewhere over the rainbow
    cPanel Access Level:
    Root Administrator
    Certainly, you are very welcome and I'm glad that resolved the issue for you.
     
  8. akazdenko

    akazdenko Registered

    Joined:
    Mar 15, 2012
    Messages:
    1
    Likes Received:
    0
    Trophy Points:
    1
    cPanel Access Level:
    Root Administrator
    Hi to all,

    i'm getting same error as cooty

    Auth failed for service: (cpaneld, whostmgrdat...) /usr/local/cpanel/Cpanel/Hulkd/Processor.pm line 91.

    i'm using WHM 11.30.6 (build 4), CENTOS 6.2 x86_64 standard, clean install

    i don't have /scripts/restartsrv_cphulkd so don't know what to do :)

    thanks in advance,

    z
     
  9. cPanelMichael

    cPanelMichael Forums Analyst
    Staff Member

    Joined:
    Apr 11, 2011
    Messages:
    30,678
    Likes Received:
    653
    Trophy Points:
    113
    cPanel Access Level:
    Root Administrator
    Hello :)

    You could try setting up cPHulk again using the following command:

    Code:
    # /usr/local/cpanel/bin/hulkdsetup
    I have seen cases where this has resolved the issue you are experiencing. Please try this and let us know if you still experience any additional problems.

    Thank you.
     
Loading...

Share This Page