Mysql.sock accidental delete!!!

Discussion in 'Server Operation' started by nackgr, Jun 9, 2013.

  1. nackgr

    nackgr New Member


    i accidental delete from /var/lib/mysql the mysql.sock file ! and now can start mysql

    I use centos ! what should i do !!!!!!!!
  2. TiTex

    TiTex New Member

    what error do you get ?
  3. nackgr

    nackgr New Member

    [root@host tmp]# /etc/init.d/mysqld restart
    Stopping mysqld: [ OK ]
    MySQL Daemon failed to start.
    Starting mysqld: [FAILED]
  4. TiTex

    TiTex New Member

    have you google it ? :)
    what linux distribution are you using ?
    also mysql.sock should be recreated when mysql server starts ...

    do you have a line in you my.cnf with bin-logging (log-bin=mysql-bin) ? ... comment it out and try again
  5. nackgr

    nackgr New Member

    i am googling 2 hours now !!

    Centos and mysql 5.5

    i add that to my.cfn


    130609 21:05:52 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
    130609 21:05:53 [Note] Plugin 'FEDERATED' is disabled.
    /usr/libexec/mysqld: Can't find file: './mysql/plugin.frm' (errno: 13)
    130609 21:05:53 [ERROR] Can't open the mysql.plugin table. Please run mysql_upgrade to create it.
    130609 21:05:53 InnoDB: The InnoDB memory heap is disabled
    130609 21:05:53 InnoDB: Mutexes and rw_locks use GCC atomic builtins
    130609 21:05:53 InnoDB: Compressed tables use zlib 1.2.3
    130609 21:05:53 InnoDB: Using Linux native AIO
    130609 21:05:53 InnoDB: Initializing buffer pool, size = 128.0M
    130609 21:05:53 InnoDB: Completed initialization of buffer pool
    130609 21:05:53 InnoDB: Operating system error number 13 in a file operation.
    InnoDB: The error means mysqld does not have the access rights to
    InnoDB: the directory.
    InnoDB: File name ./ibdata1
    InnoDB: File operation call: 'open'.
    InnoDB: Cannot continue operation.
    130609 21:05:53 mysqld_safe mysqld from pid file /var/run/mysqld/ ended
    Last edited: Jun 9, 2013

Share This Page