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.

EasyApache 3.28.8 released

Discussion in 'EasyApache' started by cPStacy, Apr 21, 2015.

  1. cPStacy

    cPStacy Technical Writer
    Staff Member

    Joined:
    Jul 23, 2014
    Messages:
    58
    Likes Received:
    4
    Trophy Points:
    8
    cPanel Access Level:
    Root Administrator
    Hello, everyone!

    The EasyApache team has published EasyApache 3.28.8:

    2015-4-21


    EASYAPACHE CHANGE LOG: http://documentation.cpanel.net/display/EA/EasyApache+Change+Log
    EASYAPACHE RELEASE NOTES: http://documentation.cpanel.net/display/EA/EasyApache+3.28+Release+Notes

    NOTE: The documentation may take a few hours to sync up between the documentation servers.
     
  2. sneader

    sneader Well-Known Member

    Joined:
    Aug 21, 2003
    Messages:
    1,126
    Likes Received:
    21
    Trophy Points:
    38
    Location:
    La Crosse, WI
    cPanel Access Level:
    Root Administrator
    As a data point, when running EasyApache, I started seeing piles of "auth failed" messages in maillog, which caused customer IPs to be blocked in CSF due to LFD (login failure detection. Had a rash of customers opening tickets due to not being able to check mail or see their sites (due to IP blocks).

    - Scott
     
  3. cPJacob

    cPJacob cPanel Product Owner
    Staff Member

    Joined:
    May 2, 2014
    Messages:
    509
    Likes Received:
    65
    Trophy Points:
    28
    cPanel Access Level:
    DataCenter Provider
    Twitter:
    Hi,

    I do not think running EasyApache will have any affect on CSF or the firewalls. Did you find any other correlations?
     
  4. mtindor

    mtindor Well-Known Member

    Joined:
    Sep 14, 2004
    Messages:
    1,281
    Likes Received:
    37
    Trophy Points:
    48
    Location:
    inside a catfish
    cPanel Access Level:
    Root Administrator
    Scott and I were doing EA builds on our servers at the same time, well nearly. Right after he did his I did mine. I experienced the same exact thing. We are not hallucinating.

    a. It occurred [for me] on boxes running Dovecot
    b. It did not occur [for me] on the one box I had running Courier

    I don't know if it automatically "fixed" itself after the build was done, because after the builds were done I restarted exim/dovecot on the servers just to be sure it was authenticating.

    BTW -- the only reason CSF is involved in the discussion is because when normally authenticating clients start to fail authentication, our CSF setups start temp-blocking the IPs that are failing auth.

    What is really being reported here is that from start-to-finish of a build, it seems like Dovecot stopped authenticating. I only updated one Courier box, but the Courier box didn't suffer from the same thing.

    Mike
     
  5. sneader

    sneader Well-Known Member

    Joined:
    Aug 21, 2003
    Messages:
    1,126
    Likes Received:
    21
    Trophy Points:
    38
    Location:
    La Crosse, WI
    cPanel Access Level:
    Root Administrator
    I'm using Dovecot here as well. During the build, my log shows non-stop 'auth failed' messages, which started here (there was nothing interesting in the log prior to the start of the failures):

    Apr 21 19:19:57 www14 dovecot: pop3-login: Disconnected (auth failed, 1 attempts in 2 secs): user=<phil+example.com>, method=PLAIN, rip=2.2.2.2, lip=1.1.1.1, TLS, session=<9L1qH0UUVABCbef+>
    Apr 21 19:19:58 www14 dovecot: pop3-login: Disconnected (auth failed, 1 attempts in 2 secs): user=<dennis@redacted.com>, method=PLAIN, rip=3.3.3.3, lip=1.1.1.1, TLS: Disconnected, session=<PSl6H0UUMgBCirTN>
    (these were the first two entries, and happened to be pop3, but there are piles of imap failures also)

    These auth failed messages continue from 19:19:57 until 19:33:33 (yes, almost 15 minutes!)
    Then I saw this:

    Apr 21 19:33:33 www14 dovecot: master: Warning: Killed with signal 15 (by pid=958750 uid=0 code=kill)

    And then:

    Apr 21 19:33:33 www14 dovecot: imap(info@redacted.com): Server shutting down. in=107, out=1249, bytes=107/1249
    Apr 21 19:33:33 www14 dovecot: imap(jim@example.net): Server shutting down. in=449, out=1065, bytes=449/1065
    Apr 21 19:33:33 www14 dovecot: imap(tom@foobar.net): Server shutting down. in=410, out=1010, bytes=410/1010
    (lots and lots of these)

    Then a couple more auth failed messages

    Then:
    Apr 21 19:33:36 www14 dovecot: master: Dovecot v2.2.16 starting up for imap, pop3 (core dumps disabled)

    And THEN we had successful logins (for those customers that weren't already blocked by CSF LFD)

    I hope this helps.

    - Scott
     
  6. cPJacob

    cPJacob cPanel Product Owner
    Staff Member

    Joined:
    May 2, 2014
    Messages:
    509
    Likes Received:
    65
    Trophy Points:
    28
    cPanel Access Level:
    DataCenter Provider
    Twitter:
    Hi,

    What version cPanel are you running? Would you mind putting in a support ticket on this so we can take a look? You can use the links in my signature to put that in.
     
  7. sneader

    sneader Well-Known Member

    Joined:
    Aug 21, 2003
    Messages:
    1,126
    Likes Received:
    21
    Trophy Points:
    38
    Location:
    La Crosse, WI
    cPanel Access Level:
    Root Administrator
    I saw this on at least three servers, all running 11.48.3.0 Release. Sure, I'll pop a ticket in.

    - Scott
     
  8. sneader

    sneader Well-Known Member

    Joined:
    Aug 21, 2003
    Messages:
    1,126
    Likes Received:
    21
    Trophy Points:
    38
    Location:
    La Crosse, WI
    cPanel Access Level:
    Root Administrator
    Ticket #6412667
     
    mtindor likes this.
  9. cPanelPeter

    cPanelPeter Technical Analyst III
    Staff Member

    Joined:
    Sep 23, 2013
    Messages:
    569
    Likes Received:
    15
    Trophy Points:
    18
    cPanel Access Level:
    Root Administrator
    Twitter:
    Hello,

    As an update to this, our support team could not reproduce this. Scott was asked to try running EA again and was also unable to reproduce the issue. If anyone can reproduce this again, please do let us know and please open a ticket using the link in my signature.
     
Loading...

Share This Page