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.

MySQL process doesnt end, is it normal ??

Discussion in 'Database Discussions' started by absolutenetwork, Jan 29, 2014.

  1. absolutenetwork

    absolutenetwork Active Member

    Joined:
    Dec 12, 2006
    Messages:
    33
    Likes Received:
    0
    Trophy Points:
    6
    Im looking at my Process Manager and shows contantly this proceess:

    /usr/sbin/mysqld --basedir=/usr --datadir=/var/lib/mysql --plugin-dir=/usr/lib64/mysql/plugin --user=mysql --log-error=/var/lib/mysql/server.xxxxx.com.err --open-files-limit=23896 --pid-file=/var/lib/mysql/server.xxxxx.com.pid

    Is this a normal?? my load numbers are all normal... so is not loading the server .. but dont know if it means that something is not working right..

    The error log shows:

    140130 00:56:23 mysqld_safe Number of processes running now: 0
    140130 00:56:23 mysqld_safe mysqld restarted
    140130 0:56:23 [Note] Plugin 'FEDERATED' is disabled.
    140130 0:56:23 InnoDB: The InnoDB memory heap is disabled
    140130 0:56:23 InnoDB: Mutexes and rw_locks use GCC atomic builtins
    140130 0:56:23 InnoDB: Compressed tables use zlib 1.2.3
    140130 0:56:23 InnoDB: Using Linux native AIO
    140130 0:56:23 InnoDB: Initializing buffer pool, size = 128.0M
    140130 0:56:23 InnoDB: Completed initialization of buffer pool
    140130 0:56:23 InnoDB: highest supported file format is Barracuda.
    InnoDB: The log sequence number in ibdata files does not match
    InnoDB: the log sequence number in the ib_logfiles!
    140130 0:56:23 InnoDB: Database was not shut down normally!
    InnoDB: Starting crash recovery.
    InnoDB: Reading tablespace information from the .ibd files...
    InnoDB: Restoring possible half-written data pages from the doublewrite
    InnoDB: buffer...
    140130 0:56:28 InnoDB: Waiting for the background threads to start
    140130 0:56:29 InnoDB: 5.5.34 started; log sequence number 11318076719
    140130 0:56:29 [Note] Server hostname (bind-address): '0.0.0.0'; port: 3306
    140130 0:56:29 [Note] - '0.0.0.0' resolves to '0.0.0.0';
    140130 0:56:29 [Note] Server socket created on IP: '0.0.0.0'.
    140130 0:56:29 [Note] Event Scheduler: Loaded 0 events
    140130 0:56:29 [Note] /usr/sbin/mysqld: ready for connections.
    Version: '5.5.34-cll' socket: '/var/lib/mysql/mysql.sock' port: 3306 MySQL Community Server (GPL)
     
  2. cPanelPeter

    cPanelPeter Technical Analyst III
    Staff Member

    Joined:
    Sep 23, 2013
    Messages:
    569
    Likes Received:
    15
    Trophy Points:
    18
    cPanel Access Level:
    Root Administrator
    Twitter:
    Hello,

    This looks fairly normal. The log file shows that MySQL was not previously shutdown properly, but went into recovery and appears to be recovered fine.

    You said MySQL isn't running, what happens when you try to access MySQL, do you get any errors?
     
  3. cPanelMichael

    cPanelMichael Forums Analyst
    Staff Member

    Joined:
    Apr 11, 2011
    Messages:
    30,854
    Likes Received:
    676
    Trophy Points:
    113
    cPanel Access Level:
    Root Administrator
    Yes, it's normal for the MySQL server to constantly run. Otherwise, your databases would not be accessible.

    Thank you.
     
Loading...

Share This Page