Please whitelist cPanel in your adblocker so that you’re able to see our version release promotions, thanks!

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.

what is (imedated) process?

Discussion in 'General Discussion' started by LAZer, Sep 3, 2017.

  1. LAZer

    LAZer Well-Known Member

    Joined:
    Jan 18, 2010
    Messages:
    76
    Likes Received:
    1
    Trophy Points:
    58
    Location:
    at net :D
    Hi , I have vps for a customer with centos 7.3 under a vmware 6 host ( with hw raid 10 )
    the vps had around 3 month of uptime till last night it hung with multiple email alerts of
    HANG: ⚠: chkservd.
    I rebooted the vm , and saw that it had a fsck error on /dev/sda7 which was /tmp partition.

    at the time of error there is a process named (imedated) using full cpu.

    after the reboot it happened again after some hours when there was no backup process on any high i/o process active . there is no mail in exim queue. and network traffic is normal.
    this time I had a ssh session open and I could see a process (imedated) using cpu and I killed it with sigterm . but after some minutes it returned.
    in /var/log/messages I saw these errors :

    Code:
    PID     Owner     CPU %     Memory %     Command
    29033     root     98.46     0.52     (imedated)
    Code:
    Preview of “cpanel_tailwatchd_log_tail.txt”
    [17346] [2017-09-03 15:57:36] [Cpanel::TailWatch] [INFO] Opened /usr/local/cpanel/logs/tailwatchd_log in append mode
    [8223] [2017-09-03 15:57:35] [Cpanel::TailWatch] tailwatch exiting on SIGTERM
    [8223] [2017-09-03 15:57:35] [Cpanel::TailWatch] [8223] [2017-09-03 15:57:35 +0430] [Cpanel::TailWatch] tailwatch exiting on SIGTERM
    [8223] [2017-09-03 15:56:27] [Cpanel::TailWatch] [INFO] Flushing all readers
    [8223] [2017-09-03 15:56:27] [Cpanel::TailWatch::Eximstats] Loading email sending limits from 1504436400 - 1504440000
    [8223] [2017-09-03 15:56:27] [Cpanel::TailWatch] [INFO] tailwatch saving positions and reloading configuration on SIG
    [8223] [2017-09-03 15:30:00] [Cpanel::TailWatch::Eximstats] Resetting email limits to new starttime of 1504436400
    [8223] [2017-09-03 14:30:00] [Cpanel::TailWatch::Eximstats] Resetting email limits to new starttime of 1504432800
    [8223] [2017-09-03 13:34:42] [Cpanel::TailWatch::ChkServd] [INFO] Opening /var/log/chkservd.log in append mode
    [8223] [2017-09-03 13:34:42] [Cpanel::TailWatch] [INFO] Restored /etc/apache2/logs/modsec_audit.log to position 0
    kernel is :
    uname -r
    3.10.0-514.26.2.el7.x86_64

    CentOS Linux release 7.3.1611 (Core)

    cat /usr/local/cpanel/version
    11.66.0.14

    also the cpanel is on release which is now 66.0.17 on my other servers.
    but when I do /scripts/upcp or via whm . it stays on 66.0.14 !

    Code:
     Detected version '11.66.0.14' from version file.
    [2017-09-03 21:18:56]   Running version '11.66.0.14' of updatenow.
    


    any suggestions?
     
    #1 LAZer, Sep 3, 2017
    Last edited: Sep 3, 2017
  2. cPanelMichael

    cPanelMichael Forums Analyst
    Staff Member

    Joined:
    Apr 11, 2011
    Messages:
    38,165
    Likes Received:
    1,371
    Trophy Points:
    363
    cPanel Access Level:
    Root Administrator
    Hello,

    This looks to relate to your system's Time and Date service:

    timedated

    I recommend reaching out to a system administrator or your hosting provider if this is leading to high CPU usage, especially since this started happening after a file system error.

    You can review the "CPANEL=" entry in the /etc/cpupdate.conf file to see if it's configured to use a specific version of cPanel. You'd set it to "release" if you want to use the "Release" build tier. EX:

    Code:
    # grep CPANEL= /etc/cpupdate.conf
    CPANEL=release
    Thank you.
     
    LAZer likes this.
Loading...

Share This Page