All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
cpanel mysql server crashing issuse
InnoDB issues preventing MySQL from starting:
from /var/lib/mysql/panel.rockbelthost.com.err
150922 11:27:30 InnoDB: Page checksum 2552953640, prior-to-4.0.14-form checksum 736362004
InnoDB: stored checksum 1030413112, prior-to-4.0.14-form stored checksum 736362004
InnoDB: Page lsn 7 3439037475, low 4 bytes of lsn at page end 3439037475
InnoDB: Page number (if stored to page already) 215,
InnoDB: space id (if created with >= MySQL-4.1.1 and stored already) 0
InnoDB: Page may be a system page
InnoDB: Database page corruption on disk or a failed
InnoDB: file read of page 215.
InnoDB: You may have to recover from a backup.
InnoDB: It is also possible that your operating
InnoDB: system has corrupted its own file cache
InnoDB: and rebooting your computer removes the
InnoDB: error.
InnoDB: If the corrupt page is an index page
InnoDB: you can also try to fix the corruption
InnoDB: by dumping, dropping, and reimporting
InnoDB: the corrupt table. You can use CHECK
InnoDB: TABLE to scan your table for corruption.
InnoDB: See also http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
InnoDB: Ending processing because of a corrupt database page.
150922 11:27:30 InnoDB: Assertion failure in thread 140662512957184 in file buf0buf.c line 3620
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
InnoDB: If you get repeated assertion failures or crashes, even
InnoDB: immediately after the mysqld startup, there may be
InnoDB: corruption in the InnoDB tablespace. Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
02:27:30 UTC - mysqld got signal 6 ;
I opened a ticket at cpanel and they provided me link about how to do so.
but I have never done this honestly and don't want to end up f***ing everything up.
So if anyone can help me out here or show how you are doing via
teamviewer that would be nice. I will pay for it ofc.
also this is a live production server 
Comments
Hello, I have sent you a PM.
Mr general fixed it!
thanks
You're welcome!
:-)
innodb_force_recovery = n
n from 1,2,3,4,5,6
just test to start the mysql, then dump the sql.