Skip to main content

mailman disabled but keep getting "Excessive resource usage: mailman" email

Comments

26 comments

  • cPRex Jurassic Moderator
    Hey there! If you run the following command on your server do you see any mailman processes running? ps aux | grep mailman
    If not, I would check the headers of the message to be sure it is being sent from an active server, or the same server you're expecting. For example, if a server was migrated recently, the hostname could be the same but the message could be sending from a different machine, leading to confusion.
    0
  • Crimpshrine
    Thanks for the quick reply. When I run that code, it says: [root@host03 ~]# ps aux |grep mailman root 107887 0.0 0.0 12148 1108 pts/0 S+ 14:51 0:00 grep --color=auto mailman
    We did migrate the server recently, however, this is definitely coming from the new server. Each server has different host name and I verified it in the email notification that it was in fact coming from the new server. I also requested to destroy the old server about a week ago, and I confirmed that it was no longer accessible.
    0
  • cPRex Jurassic Moderator
    Just to be 100% certain, did you check the IP address from the mail header and not just the hostname? I know it sounds crazy, but it's not really any crazier than getting mailman notifications after you just confirmed there are no processes running with that last command. It's also possible there is *something* attempting to run mailman at that time. Maybe using a tool like sys-snap (
    0
  • Crimpshrine
    I did not check the IP, but it is difinately coming from the new server. Old server was host2.XXXXXXXXXXX.com and the new server is host03.XXXXXXXXXXX.com, and it was coming from root@host03.XXXXXXXXXXX.com. I also never had this issue from the old server (and we never used the mailing list). Every time when I see the email notification it says (each email notification with different date & time and PID): [QUOTE] Time: Mon Jan 30 03:27:09 2023 -0600 Account: mailman Resource: Virtual Memory Size Exceeded: 277 > 256 (MB) Executable: /usr/lib/systemd/systemd Command Line: (sd-pam) PID: 4110292 (Parent PID:4110290) Killed: No
    But the process is never seen if I see Process Manager (maybe it's killed by the time I check it?). I will try to install sys-snap as recommended and see how that goes...
    0
  • cPRex Jurassic Moderator
    It's also worth noting that these notifications come from CSF/LFD, and not cPanel, so maybe there is an issue there.
    0
  • Crimpshrine
    What are the types of possible issues it may have? Are they issues that are unrelated to mailman, but triggering this message? Sorry I'm a beginner...
    0
  • cPRex Jurassic Moderator
    I'm honestly not sure, since we don't create that product on our end. CSF is a separate entity, so if you don't find anything from monitoring the server with sys-snap, it might be worth reaching out to them:
    0
  • Crimpshrine
    Okay, thanks. I will try running sys-snap tonight first and see what the log says overnight.
    0
  • cPRex Jurassic Moderator
    Let us know what you see!
    0
  • Crimpshrine
    So, I run the logging, then I pulled the information around the time I was getting the excessive resource usage email (3:27AM), and this was what I was getting: [QUOTE] [root@host03 /]# /root/sys-snap.pl --print 3:15 3:45 user: root cpu-score: 91.90 memory-score: 369.70 user: mailman cpu-score: 4.00 memory-score: 0.00 user: cpanelsolr cpu-score: 2.70 memory-score: 145.80 user: XXXXXX cpu-score: 2.60 memory-score: 0.00 user: systuser cpu-score: 0.00 memory-score: 5.40 user: dbus cpu-score: 0.00 memory-score: 0.00 user: dovenull cpu-score: 0.00 memory-score: 0.00 user: polkitd cpu-score: 0.00 memory-score: 2.70 user: chrony cpu-score: 0.00 memory-score: 0.00 user: mysql cpu-score: 0.00 memory-score: 16.20 user: named cpu-score: 0.00 memory-score: 32.40 user: cpanelconnecttrack cpu-score: 0.00 memory-score: 0.00 user: memcached cpu-score: 0.00 memory-score: 0.00 user: ossecr cpu-score: 0.00 memory-score: 0.00 user: nscd cpu-score: 0.00 memory-score: 0.00 user: sshd cpu-score: 0.00 memory-score: 0.00 user: telegraf cpu-score: 0.00 memory-score: 16.20 user: _imunify cpu-score: 0.00 memory-score: 0.00 user: dovecot cpu-score: 0.00 memory-score: 0.00 user: ossec cpu-score: 0.00 memory-score: 0.00 user: mailnull cpu-score: 0.00 memory-score: 0.00 user: nobody cpu-score: 0.00 memory-score: 156.60 user: cpanelphpmyadmin cpu-score: 0.00 memory-score: 0.00
    So, apparently, mailman is there although it says the memory score is 0.00...should I just get a support from ConfigServer? Or should I be pulling different kind of information?
    0
  • Crimpshrine
    For some reasons, this is not allowing me to post a reply with the information I obtained...it tells me to try again later there may be some more details in browser console...
    0
  • Crimpshrine
    Okay, so I guess the forum does not like the "passwd" in the texts. After running the command I received below response: [QUOTE] mailman:x:994:991:GNU Mailing List Manager:/usr/local/cpanel/3rdparty/mailman:/usr/local/cpanel/bin/noshell
    0
  • cPRex Jurassic Moderator
    That was just Cloudflare being overprotective. We're fixing that when we do the next Forums update. I think it would be best to create a ticket so we can confirm there are no security issues on the machine.
    0
  • Crimpshrine
    That was just Cloudflare being overprotective. We're fixing that when we do the next Forums update. I think it would be best to create a ticket so we can confirm there are no security issues on the machine.

    Okay, thanks. Will do.
    0
  • cPRex Jurassic Moderator
    Once you do that, please post the ticket number here so I can follow along!
    0
  • Crimpshrine
    Once you do that, please post the ticket number here so I can follow along!

    It seems like cPanel wants me to open support ticket at cPanel license provider first before opening ticket at cPanel support, so I have just opened the ticket with them. I can post the outcome after I get a feedback here though.
    0
  • cPRex Jurassic Moderator
    That sounds good! It's usually best to go with the license provider first, although anyone with root access to their server is welcome to contact us.
    0
  • Crimpshrine
    So, the license provider said: [QUOTE] I took a look and there were still entries in the httpd.conf. I have cleared them, after first verifying that mailman was completely disabled in the service manager. This should completely prevent it from running again.
    I'm thinking this is related to
    0
  • cPRex Jurassic Moderator
    Yes, that issue was solved in version 70. If that didn't happen, it's possible there were other issues that could have been investigated.
    0
  • Crimpshrine
    The support says that there were entries in Apache (/var/cpanel/templates/apache2_4/ea4_main.default) that should have been removed. He was referring to these lines: [QUOTE] [% IF !skipmailman -%] Alias /mailman/archives /usr/local/cpanel/3rdparty/mailman/archives/public/ Alias /pipermail /usr/local/cpanel/3rdparty/mailman/archives/public/ [% END -%]
    [QUOTE] [% IF !skipmailman -%] ScriptAlias /mailman /usr/local/cpanel/3rdparty/mailman/cgi-bin/ [% END -%]
    So regardless of the status in Tweak Settings and Service Manager, did this file need to be edited manually?
    0
  • cPRex Jurassic Moderator
    No, that isn't the proper way to resolve the issue. cPanel will replace the template with as part of the nightly update. It might be time to just make a ticket with us.
    0
  • Crimpshrine
    Okay. I will open a ticket. I will provide the ticket number once submitted. Thank you.
    0
  • Crimpshrine
    Update: cPanel ticket# is 94527290.
    0
  • cPRex Jurassic Moderator
    Thanks for that - I'm following along on my end now.
    0
  • Crimpshrine
    It finally appeared to stop yesterday after I made below changes to ConfigServer (Firewall Configuration): [QUOTE] PT_USERMEM = 1024 (Default 256) PT_USERTIME = 0 (Default 1800)
    Granted, this may happen again, but I did not receive single notification of "Excessive memory usage" notification overnight since yesterday. It was not mailman, but I later found out it was caused by Imunify360. I had tracked down to WebShield in Imunify360 that was causing a lot of memory usage, and actually it was causing hourly notification over the weekend (pointing to /usr/sbin/imunify360-webshield), but once I made above change to ConfigServer, it stopped finally. Thank you for your support.
    0

Please sign in to leave a comment.