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.

IMPORTANT: Do not ignore this email. HELP !

Discussion in 'E-mail Discussions' started by oyuncu2, Nov 3, 2004.

  1. oyuncu2

    oyuncu2 Member

    Joined:
    Apr 10, 2004
    Messages:
    9
    Likes Received:
    0
    Trophy Points:
    1
    from root@venus.myserver.com to me

    IMPORTANT: Do not ignore this email.
    This is cPanel stats runner on venus.myserver*****.com!
    While processing the log files for user myuser***, the cpu has been
    maxed out for more then a 6 hour period. The current load/uptime line on the server at the time of
    this email is
    16:17:58 up 5 days, 20:13, 0 users, load average: 2.14, 1.67, 1.26
    You should check the server to see why the load is so high and take
    steps to lower the load. If you want stats to continue to run even with a high load; Edit
    /var/cpanel/cpanel.config and change extracpus to a number larger then 0 (run
    /usr/local/cpanel/startup afterwards to pickup the changes).
    --- end mail ---------
    /var/cpanel/cpanel.config i edit this extracpus number 1
    /usr/local/cpanel/startup and then start this

    i get this email 4-5 all email user changes all story is same
    any body have an idea what must i do ?
     
  2. brown

    brown Member

    Joined:
    Apr 21, 2002
    Messages:
    9
    Likes Received:
    0
    Trophy Points:
    1
    Here's the fix for that annoying email notification problem:

    Here's the fix for that annoying email notification problem:

    Step 1: backup the web pages, email, database(s), and any cron jobs for myuser*** account.

    Step 2: Login to your web host manager and terminate myuser*** hosting account.

    Step 3: Now re-create myuser*** hosting account and re-upload only the webpages, images and database(s) if any. Do not use the cpanel account restore feature to do this.

    Now, the problem is solved. You'll never receive that annoying email again.
     
  3. casey

    casey Well-Known Member

    Joined:
    Jan 17, 2003
    Messages:
    2,303
    Likes Received:
    0
    Trophy Points:
    36
    Location:
    If there is trouble, it will find me
    What about the client's e-mail addresses? Do you make the client re-create their e-mail accounts so that you'll stop getting that message?
     
  4. brown

    brown Member

    Joined:
    Apr 21, 2002
    Messages:
    9
    Likes Received:
    0
    Trophy Points:
    1
    Tell the client to use outlook to download all their emails. And recreate their email accounts after restoring their hosting account.

    Is better to have your client do that than watch your server spent most of its resources processing that user's log files or probably shut down one day.
     
  5. oyuncu2

    oyuncu2 Member

    Joined:
    Apr 10, 2004
    Messages:
    9
    Likes Received:
    0
    Trophy Points:
    1
    way is not imposible

    because i get this error twice a day an other my client .
    i can make it for all my client there must be an other way
     
  6. casey

    casey Well-Known Member

    Joined:
    Jan 17, 2003
    Messages:
    2,303
    Likes Received:
    0
    Trophy Points:
    36
    Location:
    If there is trouble, it will find me
    I suggest putting in a support ticket with cpanel. I'm sure they have an idea of why the message is sent and what is causing it.
     
  7. dgbaker

    dgbaker Well-Known Member
    PartnerNOC

    Joined:
    Sep 20, 2002
    Messages:
    2,578
    Likes Received:
    3
    Trophy Points:
    38
    Location:
    Toronto, Ontario Canada
    cPanel Access Level:
    DataCenter Provider

    Glad I was never one of your clients.
     
  8. bluesaga

    bluesaga Member

    Joined:
    Sep 5, 2004
    Messages:
    6
    Likes Received:
    0
    Trophy Points:
    1
    i used to get this message a lot, try stop parsing system log files (Awstats or webalizer or something)

    Urchin was a main cause for me
     
  9. GufyMike

    GufyMike Member

    Joined:
    Feb 9, 2004
    Messages:
    14
    Likes Received:
    0
    Trophy Points:
    1
    Had this problem recently, awstats and webalizer where trying to parse 1.1GB of domlogs. 913MB in on file. The solution I found was to use logrotate.

    Search for awstats logrotate on google for some hints and "man logrotate" (without the quotes) to get specifics.
     
Loading...

Share This Page