MySQL had stopped working

[hchouhan]

Hello,

After few hours of using a new VPS with easy engine, I noticed the website showed the database error page. When I did ee system status, it showed mySQL had stopped working. I waited for few minutes and then used ee system restart to get MySQL working again.

My question is, is there any way to track and restart these core processes if they accidently stop? If not built into EE, then can you refer any links to tools that can be used for this?

Thanks.

[hchouhan]

In error logs I found this

140514 17:15:50 [Note]   - '127.0.0.1' resolves to '127.0.0.1';
140514 17:15:50 [Note] Server socket created on IP: '127.0.0.1'.
140514 17:15:50 [Note] Event Scheduler: Loaded 0 events
140514 17:15:50 [Note] /usr/sbin/mysqld: ready for connections.
Version: '5.5.37-0ubuntu0.13.10.1'  socket: '/var/run/mysqld/mysqld.sock'  port: 3306  (Ubuntu)
140514 17:15:51 [ERROR] /usr/sbin/mysqld: Table './flatzcom_flattrendz/flattrendz_options' is marked as crashed and should be repaired
140514 17:15:51 [Warning] Checking table:   './flatzcom_flattrendz/flattrendz_options'
140514 17:15:51 [ERROR] /usr/sbin/mysqld: Table './flatzcom_flattrendz/flattrendz_rg_form_view' is marked as crashed and should be repaired
140514 17:15:51 [Warning] Checking table:   './flatzcom_flattrendz/flattrendz_rg_form_view'
(END)

I have optimized my tables after the first crash but I only came to know about the crash when a user told me the site is down. This has happened twice in last 8 hours.

[MiteshShah]

@hchouhan Its seems like mysql tables is corrupted
You need to repair mysql tables

 mysqlcheck --repair --all-databases

Ref: http://dev.mysql.com/doc/refman/5.0/en/rebuilding-tables.html

As of now easyengine don't monitor process and restart the services but we have a plan to include this in our Monitor release - https://github.com/rtCamp/easyengine/issues?milestone=7&state=open

[hchouhan]

Hello @MiteshShah,

Thanks for that. After I ran the command, I got below output.

dev_flattrendz_com.flattrendz_commentmeta          OK
dev_flattrendz_com.flattrendz_comments             OK
dev_flattrendz_com.flattrendz_cst_new_files        OK
dev_flattrendz_com.flattrendz_irecommendthis_votes OK
dev_flattrendz_com.flattrendz_iwp_backup_status
note     : The storage engine for the table doesn't support repair
dev_flattrendz_com.flattrendz_links                OK
dev_flattrendz_com.flattrendz_mc4wp_log            OK
dev_flattrendz_com.flattrendz_options              OK
dev_flattrendz_com.flattrendz_postmeta             OK
dev_flattrendz_com.flattrendz_posts                OK
dev_flattrendz_com.flattrendz_rg_form              OK
dev_flattrendz_com.flattrendz_rg_form_meta         OK
dev_flattrendz_com.flattrendz_rg_form_view         OK
dev_flattrendz_com.flattrendz_rg_lead              OK
dev_flattrendz_com.flattrendz_rg_lead_detail       OK
dev_flattrendz_com.flattrendz_rg_lead_detail_long  OK
dev_flattrendz_com.flattrendz_rg_lead_meta         OK
dev_flattrendz_com.flattrendz_rg_lead_notes        OK
dev_flattrendz_com.flattrendz_rg_zapier            OK
dev_flattrendz_com.flattrendz_seorankreporter      OK
dev_flattrendz_com.flattrendz_term_relationships   OK
dev_flattrendz_com.flattrendz_term_taxonomy        OK
dev_flattrendz_com.flattrendz_terms                OK
dev_flattrendz_com.flattrendz_usermeta             OK
dev_flattrendz_com.flattrendz_users                OK
dev_flattrendz_com.flattrendz_w3tc_cdn_queue       OK
flatzcom_flattrendz.flattrendz_commentmeta         OK
flatzcom_flattrendz.flattrendz_comments            OK
flatzcom_flattrendz.flattrendz_cst_new_files       OK
flatzcom_flattrendz.flattrendz_irecommendthis_votes OK
flatzcom_flattrendz.flattrendz_iwp_backup_status
note     : The storage engine for the table doesn't support repair
flatzcom_flattrendz.flattrendz_links               OK
flatzcom_flattrendz.flattrendz_mc4wp_log           OK
flatzcom_flattrendz.flattrendz_options             OK
flatzcom_flattrendz.flattrendz_postmeta            OK
flatzcom_flattrendz.flattrendz_posts               OK
flatzcom_flattrendz.flattrendz_rg_form             OK
flatzcom_flattrendz.flattrendz_rg_form_meta        OK
flatzcom_flattrendz.flattrendz_rg_form_view        OK
flatzcom_flattrendz.flattrendz_rg_lead             OK
flatzcom_flattrendz.flattrendz_rg_lead_detail      OK
flatzcom_flattrendz.flattrendz_rg_lead_detail_long OK
flatzcom_flattrendz.flattrendz_rg_lead_meta        OK
flatzcom_flattrendz.flattrendz_rg_lead_notes       OK
flatzcom_flattrendz.flattrendz_rg_zapier           OK
flatzcom_flattrendz.flattrendz_seorankreporter     OK
flatzcom_flattrendz.flattrendz_term_relationships  OK
flatzcom_flattrendz.flattrendz_term_taxonomy       OK
flatzcom_flattrendz.flattrendz_terms               OK
flatzcom_flattrendz.flattrendz_usermeta            OK
flatzcom_flattrendz.flattrendz_users               OK
flatzcom_flattrendz.flattrendz_w3tc_cdn_queue      OK
flatzcom_flattrendz.wp_commentmeta
note     : The storage engine for the table doesn't support repair
flatzcom_flattrendz.wp_comments
note     : The storage engine for the table doesn't support repair
flatzcom_flattrendz.wp_links
note     : The storage engine for the table doesn't support repair
flatzcom_flattrendz.wp_options
note     : The storage engine for the table doesn't support repair
flatzcom_flattrendz.wp_postmeta
note     : The storage engine for the table doesn't support repair
flatzcom_flattrendz.wp_posts
note     : The storage engine for the table doesn't support repair
flatzcom_flattrendz.wp_term_relationships
note     : The storage engine for the table doesn't support repair
flatzcom_flattrendz.wp_term_taxonomy
note     : The storage engine for the table doesn't support repair
flatzcom_flattrendz.wp_terms
note     : The storage engine for the table doesn't support repair
flatzcom_flattrendz.wp_usermeta
note     : The storage engine for the table doesn't support repair
flatzcom_flattrendz.wp_users
note     : The storage engine for the table doesn't support repair
mysql.columns_priv                                 OK
mysql.db                                           OK
mysql.event                                        OK
mysql.func                                         OK
mysql.general_log                                  OK
mysql.help_category                                OK
mysql.help_keyword                                 OK
mysql.help_relation                                OK
mysql.help_topic                                   OK
mysql.host                                         OK
mysql.ndb_binlog_index                             OK
mysql.plugin                                       OK
mysql.proc                                         OK
mysql.procs_priv                                   OK
mysql.proxies_priv                                 OK
mysql.servers                                      OK
mysql.slow_log                                     OK
mysql.tables_priv                                  OK
mysql.time_zone                                    OK
mysql.time_zone_leap_second                        OK
mysql.time_zone_name                               OK
mysql.time_zone_transition                         OK
mysql.time_zone_transition_type                    OK
mysql.user                                         OK
slow_query_log.global_query_review
note     : The storage engine for the table doesn't support repair
slow_query_log.global_query_review_history
note     : The storage engine for the table doesn't support repair

Something seriously wrong with my DB? Any wild guesses on how to fix this?

[MiteshShah]

@hchouhan
As per error log two tables marked as crash

140514 17:15:51 [ERROR] /usr/sbin/mysqld: Table './flatzcom_flattrendz/flattrendz_options' is marked as crashed and should be repaired
140514 17:15:51 [ERROR] /usr/sbin/mysqld: Table './flatzcom_flattrendz/flattrendz_rg_form_view' is marked as crashed and should be repaired

In mysql repair says those two tables are ok so nothing to worry

flatzcom_flattrendz.flattrendz_options             OK
flatzcom_flattrendz.flattrendz_rg_form_view        OK

[hchouhan]

Thanks @MiteshShah.

Also can you let me know if when database is created, does EE set the DB engine to InnoDB by default?

[MiteshShah]

@hchouhan
EasyEngine change the following things when installing MySQL

wait_timeout 
interactive_timeout

[MiteshShah]

@hchouhan
I'm closing this issue as your table is repaired