Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!


High CPU Load
New on LowEndTalk? Please Register and read our Community Rules.

All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.

High CPU Load

peachstolipeachstoli Member
edited June 2013 in Help

Following Process shows high cpu usage.

28020 (Trace) (Kill) root 0 126 0.0 /bin/ps -ewwo pid,uid,user,nice,pmem,pcpu,command

How to get rid of it ?.

Comments

  • Push the "kill" button to kill it.

  • blackblack Member

    kill -9 28020

  • An error occurred processing your request:
    kill 28603: No such process

  • blackblack Member

    Huh...?

  • SpeedBusSpeedBus Member, Host Rep
    edited June 2013

    if you know the process name, which should be easy to find from htop or top as you said it's consuming a fair bit of CPU, then use killall,

    eg,
    killall process_name_here

  • I can't kill the process its showing up at every 12.00 AM for about 40 to 50 mts.

  • blackblack Member

    Chances are, it's cron job. Look in your crontab.

  • Anyone know what process is it ?.

  • SpeedBusSpeedBus Member, Host Rep
    edited June 2013

    Checkout your crontab like @black said, might just find something there

  • I checked but i can't find anything unusual.

  • `-bash: kill: (28020) - No such process
    root@cloud [~]# for user in $(cut -f1 -d: /etc/passwd); do crontab -u $user -l; done
    0 6 * * * /usr/local/cpanel/scripts/exim_tidydb > /dev/null 2>&1
    30 5 * * * /usr/local/cpanel/scripts/optimize_eximstats > /dev/null 2>&1
    47 3 * * * /usr/local/cpanel/scripts/upcp --cron
    0 1 * * * /usr/local/cpanel/scripts/cpbackup
    35 * * * * /usr/bin/test -x /usr/local/cpanel/bin/tail-check && /usr/local/cpane l/bin/tail-check
    45 */4 * * * /usr/bin/test -x /usr/local/cpanel/scripts/update_mailman_cache && /usr/local/cpanel/scripts/update_mailman_cache
    30 */4 * * * /usr/bin/test -x /usr/local/cpanel/scripts/update_db_cache && /usr/ local/cpanel/scripts/update_db_cache
    45 */8 * * * /usr/bin/test -x /usr/local/cpanel/bin/optimizefs && /usr/local/cpa nel/bin/optimizefs
    30 */2 * * * /usr/local/cpanel/bin/mysqluserstore >/dev/null 2>&1
    15 */2 * * * /usr/local/cpanel/bin/dbindex >/dev/null 2>&1
    15 */6 * * * /usr/local/cpanel/scripts/autorepair recoverymgmt >/dev/null 2>&1
    */5 * * * * /usr/local/cpanel/bin/dcpumon >/dev/null 2>&1
    5 0 * * * /usr/local/cpanel/whostmgr/docroot/cgi/cpaddons_report.pl --notify
    10,25,40,55 * * * * /usr/local/cpanel/whostmgr/bin/dnsqueue > /dev/null 2>&1
    12 2 * * 0 /usr/local/cpanel/bin/cloudflare_update.sh >/dev/null 2>&1
    2,58 * * * * /usr/local/bandmin/bandmin
    0 0 * * * /usr/local/bandmin/ipaddrmap
    0 2 * * * /usr/local/cpanel/bin/backup
    20 0 * * * /usr/bin/freshclam --quiet --no-warnings
    20 * * * * /usr/local/cpanel/3rdparty/attracta/scripts/get_jobs.pl > /dev/null 2 >&1

            • /usr/local/cpanel/3rdparty/attracta/scripts/daily_jobs.pl > /dev/null 2>&1
              42 15 * * * /usr/local/cpanel/3rdparty/attracta/scripts/update-attracta --from-c ron > /dev/null 2>&1
              `
  • blackblack Member
    edited June 2013

    If it shows up once everyday at 12:00AM, the only cronjob that matches your criteria is

    0 0 * * * /usr/local/bandmin/ipaddrmap

    I'd recommend you figure out what that does before you remove it though.

  • peachstolipeachstoli Member
    edited June 2013

    @black said:
    If it shows up once everyday at 12:00AM, the only cronjob that matches your criteria is

    0 0 * * * /usr/local/bandmin/ipaddrmap

    I'd recommend you figure out what that does before you remove it though.

    mai

    Its a normal cpanel process. I hadn't met any problem with that.

  • AdducAdduc Member

    Check the cron stuff in /etc/. If it's happening at 12:00am daily, see if it's from anything in /etc/cron.daily/

  • hcreedhcreed Member

    The process you have given just lists the processes running in the server. It can be a cron as mentioned earlier just taking some stats.
    However, its also possible, that when you are clicking the "Process Manager" it itself executes that command to list the current running processes in the server. If there are a really a lot of processes running in the server, then it can take some CPU but it won't be very high.

Sign In or Register to comment.