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 always gets lock and stops ruuning

Discussion in 'Database Discussions' started by mojamoi, Jan 31, 2014.

  1. mojamoi

    mojamoi Well-Known Member

    Joined:
    Jul 23, 2007
    Messages:
    186
    Likes Received:
    0
    Trophy Points:
    16
    Hi,

    Here are log files


    I always have to delete the lock and restart mysql

    and create mysql.sock


    /var/liv/mysql/host.err

    131106 12:32:24 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
    131106 12:32:24 [Note] Plugin 'FEDERATED' is disabled.
    131106 12:32:24 InnoDB: The InnoDB memory heap is disabled
    131106 12:32:24 InnoDB: Mutexes and rw_locks use GCC atomic builtins
    131106 12:32:24 InnoDB: Compressed tables use zlib 1.2.3
    131106 12:32:24 InnoDB: Using Linux native AIO
    131106 12:32:24 InnoDB: Initializing buffer pool, size = 128.0M
    131106 12:32:24 InnoDB: Completed initialization of buffer pool
    InnoDB: The first specified data file ./ibdata1 did not exist:
    InnoDB: a new database to be created!
    131106 12:32:24 InnoDB: Setting file ./ibdata1 size to 10 MB
    InnoDB: Database physically writes the file full: wait...
    131106 12:32:24 InnoDB: Log file ./ib_logfile0 did not exist: new to be created
    InnoDB: Setting log file ./ib_logfile0 size to 5 MB
    InnoDB: Database physically writes the file full: wait...
    131106 12:32:24 InnoDB: Log file ./ib_logfile1 did not exist: new to be created
    InnoDB: Setting log file ./ib_logfile1 size to 5 MB
    InnoDB: Database physically writes the file full: wait...
    InnoDB: Doublewrite buffer not found: creating new
    InnoDB: Doublewrite buffer created
    InnoDB: 127 rollback segment(s) active.
    InnoDB: Creating foreign key constraint system tables
    InnoDB: Foreign key constraint system tables created
    131106 12:32:25 InnoDB: Waiting for the background threads to start
    131106 12:32:26 InnoDB: 5.5.32 started; log sequence number 0
    131106 12:32:26 [Note] Server hostname (bind-address): '0.0.0.0'; port: 3306
    131106 12:32:26 [Note] - '0.0.0.0' resolves to '0.0.0.0';
    131106 12:32:26 [Note] Server socket created on IP: '0.0.0.0'.
    131106 12:32:26 [Note] Event Scheduler: Loaded 0 events
    131106 12:32:26 [Note] /usr/sbin/mysqld: ready for connections.
    Version: '5.5.32-cll' socket: '/var/lib/mysql/mysql.sock' port: 3306 MySQL Community Server (GPL)
    131106 12:32:39 mysqld_safe A mysqld process already exists
    131107 4:27:48 [Warning] IP address '57.221.45.166' could not be resolved: Name or service not known
     
  2. Sreejit

    Sreejit Member

    Joined:
    Apr 11, 2011
    Messages:
    20
    Likes Received:
    0
    Trophy Points:
    1
    cPanel Access Level:
    Root Administrator
    Is there an innodb issue with your database? Are you deleting the innodb files and then restarting mysql? You can take a look at below url's for recovering data.

    MySQL :: MySQL 5.0 Reference Manual :: 14.2.5.2 Forcing InnoDB Recovery
    https://dev.mysql.com/doc/refman/5.5/en/innodb-recovery.html


     
  3. cPanelMichael

    cPanelMichael Forums Analyst
    Staff Member

    Joined:
    Apr 11, 2011
    Messages:
    30,854
    Likes Received:
    675
    Trophy Points:
    113
    cPanel Access Level:
    Root Administrator
    Hello :)

    Could you elaborate on what behavior you notice when MySQL stops responding? Also, which specific files are you deleting? Note that you should not manually delete the "ib_logfile1" file.

    Thank you.
     
Loading...

Share This Page