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!

MySQL Error in WHM Service Status Daily Process Log

Discussion in 'Database Discussion' started by Sunlander, Jun 28, 2018.

  1. Sunlander

    Sunlander Well-Known Member

    May 7, 2018
    Likes Received:
    Trophy Points:
    cPanel Access Level:
    Root Administrator

    firstly, I hope I am posting this in the correct location.

    I am trying to troubleshoot why my site is very slow and hangs and I read somewhere on cpanel forums (one of many things I am trying) to see what the error logs say. One thread I am following now is this one:

    Is this an error logging for mysql?

    As when I checked the processes in WHM I sawl the following message:

    /usr/sbin/mysqld --basedir/usr --datadir/var/lib/mysql --plugin-dir/usr/lib64/mysql/plugin --usermysql --open-files-limit50000 --pid-file/var/lib/mysql/

    I have just ran the following as per the above mentioned post:


    And this is what it returned:

    2017-02-26 19:46:56 8248 [Note] Plugin 'FEDERATED' is disabled.
    2017-02-26 19:46:56 8248 [Note] InnoDB: Using atomics to ref count buffer pool $
    2017-02-26 19:46:56 8248 [Note] InnoDB: The InnoDB memory heap is disabled
    2017-02-26 19:46:56 8248 [Note] InnoDB: Mutexes and rw_locks use GCC atomic bui$
    2017-02-26 19:46:56 8248 [Note] InnoDB: Memory barrier is not used
    2017-02-26 19:46:56 8248 [Note] InnoDB: Compressed tables use zlib 1.2.3
    2017-02-26 19:46:56 8248 [Note] InnoDB: Using Linux native AIO
    2017-02-26 19:46:56 8248 [Note] InnoDB: Not using CPU crc32 instructions
    2017-02-26 19:46:56 8248 [Note] InnoDB: Initializing buffer pool, size = 128.0M
    2017-02-26 19:46:56 8248 [Note] InnoDB: Completed initialization of buffer pool
    2017-02-26 19:46:58 8248 [Note] InnoDB: Highest supported file format is Barrac$
    2017-02-26 19:46:58 8248 [Note] InnoDB: 128 rollback segment(s) are active.
    2017-02-26 19:46:58 8248 [Note] InnoDB: Waiting for purge to start
    2017-02-26 19:46:58 8248 [Note] InnoDB: 5.6.35 started; log sequence number 162$
    2017-02-26 19:46:58 8248 [Warning] No existing UUID has been found, so we assum$
    2017-02-26 19:46:58 8248 [Note] Server hostname (bind-address): '*'; port: 3306
    2017-02-26 19:46:58 8248 [Note] IPv6 is available.
    2017-02-26 19:46:58 8248 [Note] - '::' resolves to '::';
    2017-02-26 19:46:58 8248 [Note] Server socket created on IP: '::'.

    My question is, are any of the above cause for concern? If yes, can anyone give me any tips on how to fix them?

    Kind regards
  2. vacancy

    vacancy Well-Known Member

    Sep 20, 2012
    Likes Received:
    Trophy Points:
    cPanel Access Level:
    Root Administrator
    There are no errors.

    /usr/sbin/mysqld --basedir/usr --datadir/var/lib/mysql --plugin-dir/usr/lib64/mysql/plugin --usermysql --open-files-limit50000 --pid-file/var/lib/mysql/
    This mysql transaction represents the pid and the command line.

    There is also no problem with your mysql logs.

    In whm, follow the prompts in the queries "show mysql process"
    cPanelMichael likes this.
  3. cPanelMichael

    cPanelMichael Technical Support Community Manager Staff Member

    Apr 11, 2011
    Likes Received:
    Trophy Points:
    cPanel Access Level:
    Root Administrator

    The previous post is correct. The output you provided is normal and does not suggest there are any errors with MySQL. As far as performance, the following resource is a good place to start (even if the loads are not high):

    Tutorial - Troubleshooting high server loads on Linux servers

    Thank you.
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...

Share This Page

  1. This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.
    Dismiss Notice