Skip to main content

mysql Server Failing to start

Comments

20 comments

  • Patrick Heinz
    Hello, Did you change the MySQL data dir? Check in your /etc/my.cnf if the paths are right.
    0
  • Matthew Ridings
    I've not changed nothing this just randomly happened this is what's in my.cnf
    [mysqld] nnodb_buffer_pool_size=134217728 max_allowed_packet=268435456 open_files_limit=10000 default-storage-engine=MyISAM innodb_file_per_table=1
    0
  • Patrick Heinz
    Hum.. Looks like a default configuration. Try to add to cnf: local-infile=0 EDIT: In your 1st cnf line, the correct parameter is innodb_buffer_pool_size
    0
  • Matthew Ridings
    added and edited still not starting
    0
  • Patrick Heinz
    Googling the first error:
    -03-26 21:37:13 8751 [ERROR] InnoDB: Tried to read 65536 bytes at offset 6836224. Was only able to read 40960.

    , seems like to be a i/o error. But you can try to add the parameter
    innodb_force_recovery =
    from 1 to 6. I really don't have more sql skills, but that can help you: Forcing InnoDB Recovery Good luck!
    0
  • Matthew Ridings
    Thanks for your help I tried this but don't seem to have made any progress with that method still failing to start :(
    0
  • triantech
    Hey Matt, Are you on a VPS or a physical server ? Did you try putting the value innodb_force_recovery as 1 and attempting a restart ? You get the same errors ?
    0
  • Matthew Ridings
    I'm on a physical server and have tried restarting with the innodb_force_recovery and still get the same result.
    0
  • triantech
    Hey, Looks to be a hardware - disk related issue as Patrick suggested. Meanwhile, make sure your /tmp isnt ful ?
    0
  • Matthew Ridings
    tmp isn't full only 4% of it being used just don't understand how its randomly happened because no one has made any edits at all to make it go off the way it has everything else is working on whm fine apart from database server and the parts that need the database :(
    0
  • 24x7ss
    It seems that Innodb of your server gets crashed and you have to go with innodb recovery. First check if Innodb engine is installed or not. You can check it from mysql prompt and fire below command. show engines; If it is showing no in Innodb engine then you have to install Innodb engine again and I hope you are having backup of your databases.
    0
  • Matthew Ridings
    this is what i get when trying to use the mysql prompt
    root@server1 [~]# mysql ERROR 2002 (HY000): Can't connect to local MySQL server through socket '/var/lib/mysql/mysql.sock' (2)
    0
  • 24x7ss
    Error clearly shows that mysql socket file is missing. Try to create symlinked mysql socket file. That file connects to mysql.sock in temp.
    0
  • triantech
    You can check it from mysql prompt and fire below command.

    His MySQL is not starting at the first place.
    0
  • 24x7ss
    ok, do one thing open my.cnf and comment out all innodb entries and insert skip-innodb. This will skip your Innodb and start mysql with other engines.
    0
  • cPanelMichael
    Hello, The following thread is a good place to get started when InnoDB is corrupted: InnoDB Repair Guide Thank you.
    0
  • Matthew Ridings
    I manage to get it all sorted in the end thanks for the help I got it running without innodb then noticed permission errors then some other error afterwards then managed to get innodb started in the end :)
    0
  • cPanelMichael
    I am happy to see you were able to resolve the issue. Thank you for updating us with the outcome.
    0
  • Khaled A.
    Hi, In my case it was "clamavconnector" plugin in WHM panel that brought down my database. I disabled it and now back online.
    0
  • cPanelMichael
    In my case it was "clamavconnector" plugin in WHM panel that brought down my database. I disabled it and now back online.

    ClamAV should not cause MySQL to fail. What error messages were you seeing in your MySQL error log? Thank you.
    0

Please sign in to leave a comment.