Question

Starting MySQL database server mysqld [fail]

Posted August 13, 2015 9.1k views
Ubuntu MySQL WordPress

Since yesterday evening my sql server stopped working. I’ve noticed this when my website showed this great message “Error establishing a database connection”. So I’ve tried to restart mysql service. Unfortunately nothing works. I was looking for solutions “with” google but no luck. I even tried to restore my droplet to previous one. But this one doesn’t work either. I don’t know what should I do. I’ll be grateful for any help

Add a comment
Tichor
By:
Tichor
Add a comment
1 comment
  • arsalananwar October 16, 2015
    Reply Report

    We are facing the same issues at our end. When this issue previously happened we found that mysql has stopped. Didn’t get the any reason why it has stopped. We start it again from console using sudo /etc/init.d/mysql start

    This has happened today again and on starting mysql we are getting fail message.

These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.

2 answers
JustSomeTech August 14, 2015

When you would like to fix something that is not working, you should start with reading the logs your software gives ; its all free there on your server ;)
What does your mysql log say?

Reply Report
  • Tichor August 14, 2015

    Hello,

    I got something like that. Found in /var/log/mysql error.log

    <^>150814 14:37:36 [Note] Plugin ‘FEDERATED’ is disabled.
    150814 14:37:36 InnoDB: The InnoDB memory heap is disabled
    150814 14:37:36 InnoDB: Mutexes and rwlocks use GCC atomic builtins
    150814 14:37:36 InnoDB: Compressed tables use zlib 1.2.8
    150814 14:37:36 InnoDB: Using Linux native AIO
    150814 14:37:36 InnoDB: Initializing buffer pool, size = 128.0M
    150814 14:37:37 InnoDB: Completed initialization of buffer pool
    150814 14:37:37 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 iblogfiles!
    150814 14:37:37 InnoDB: Database was not shut down normally!
    InnoDB: Starting crash recovery.
    InnoDB: Reading tablespace information from the .ibd files…
    InnoDB: Error: trying to add tablespace 135 of name ’./adminnewone/wptermrelationships.ibd’
    InnoDB: to the tablespace memory cache, but tablespace
    InnoDB: 135 of name ’./adminmoja/wp_comments.ibd’ already exists in the tablespace
    InnoDB: memory cache!<^>

    Thanks in advance
    Wojtek

    Reply Report
Tichor August 14, 2015
[deleted]
Reply Report
Submit an Answer

Related

Looking for something else?

Ask a new question Search for more help