root@net [/etc]# tail -200 ../var/lib/mysql/net.networkdawn.com.err
InnoDB: for how to resolve the issue.
141125 18:50:22  InnoDB: Operating system error number 2 in a file operation.
InnoDB: The error means the system cannot find the path specified.
InnoDB: If you are installing InnoDB, remember that you must create
InnoDB: directories yourself, InnoDB does not create them.
141125 18:50:22  InnoDB: Error: trying to open a table, but could not
InnoDB: open the tablespace file './frenchex_wrdp1/wp_wfNet404s.ibd'!
InnoDB: Have you moved InnoDB .ibd files around without using the
InnoDB: commands DISCARD TABLESPACE and IMPORT TABLESPACE?
InnoDB: It is also possible that this is a temporary table #sql...,
InnoDB: and MySQL removed the .ibd file for this.
InnoDB: Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting-datadict.html
InnoDB: for how to resolve the issue.
141125 18:50:22  InnoDB: Operating system error number 2 in a file operation.
InnoDB: The error means the system cannot find the path specified.
InnoDB: If you are installing InnoDB, remember that you must create
InnoDB: directories yourself, InnoDB does not create them.
141125 18:50:22  InnoDB: Error: trying to open a table, but could not
InnoDB: open the tablespace file './frenchex_wrdp1/wp_wfVulnScanners.ibd'!
InnoDB: Have you moved InnoDB .ibd files around without using the
InnoDB: commands DISCARD TABLESPACE and IMPORT TABLESPACE?
InnoDB: It is also possible that this is a temporary table #sql...,
InnoDB: and MySQL removed the .ibd file for this.
InnoDB: Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting-datadict.html
InnoDB: for how to resolve the issue.
141125 18:50:22  InnoDB: Operating system error number 2 in a file operation.
InnoDB: The error means the system cannot find the path specified.
InnoDB: If you are installing InnoDB, remember that you must create
InnoDB: directories yourself, InnoDB does not create them.
141125 18:50:22  InnoDB: Error: trying to open a table, but could not
InnoDB: open the tablespace file './southaus_wrdp1/wp_wfHoover.ibd'!
InnoDB: Have you moved InnoDB .ibd files around without using the
InnoDB: commands DISCARD TABLESPACE and IMPORT TABLESPACE?
InnoDB: It is also possible that this is a temporary table #sql...,
InnoDB: and MySQL removed the .ibd file for this.
InnoDB: Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting-datadict.html
InnoDB: for how to resolve the issue.
141125 18:50:22  InnoDB: Operating system error number 2 in a file operation.
InnoDB: The error means the system cannot find the path specified.
InnoDB: If you are installing InnoDB, remember that you must create
InnoDB: directories yourself, InnoDB does not create them.
141125 18:50:22  InnoDB: Error: trying to open a table, but could not
InnoDB: open the tablespace file './southaus_wrdp1/wp_wfNet404s.ibd'!
InnoDB: Have you moved InnoDB .ibd files around without using the
InnoDB: commands DISCARD TABLESPACE and IMPORT TABLESPACE?
InnoDB: It is also possible that this is a temporary table #sql...,
InnoDB: and MySQL removed the .ibd file for this.
InnoDB: Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting-datadict.html
InnoDB: for how to resolve the issue.
141125 18:50:22  InnoDB: Operating system error number 2 in a file operation.
InnoDB: The error means the system cannot find the path specified.
InnoDB: If you are installing InnoDB, remember that you must create
InnoDB: directories yourself, InnoDB does not create them.
141125 18:50:22  InnoDB: Error: trying to open a table, but could not
InnoDB: open the tablespace file './southaus_wrdp1/wp_wfVulnScanners.ibd'!
InnoDB: Have you moved InnoDB .ibd files around without using the
InnoDB: commands DISCARD TABLESPACE and IMPORT TABLESPACE?
InnoDB: It is also possible that this is a temporary table #sql...,
InnoDB: and MySQL removed the .ibd file for this.
InnoDB: Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting-datadict.html
InnoDB: for how to resolve the issue.
141125 18:50:22  InnoDB: Waiting for the background threads to start
141125 18:50:23  InnoDB: Error: page 3 log sequence number 7290022815
InnoDB: is in the future! Current system log sequence number 7279413947.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
141125 18:50:23  InnoDB: Error: page 4 log sequence number 7280198310
InnoDB: is in the future! Current system log sequence number 7279413947.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
141125 18:50:23  InnoDB: Error: page 3 log sequence number 7288832258
InnoDB: is in the future! Current system log sequence number 7279413947.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
141125 18:50:23  InnoDB: Error: page 145 log sequence number 7288832124
InnoDB: is in the future! Current system log sequence number 7279413947.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
141125 18:50:23  InnoDB: Error: page 3 log sequence number 7290533344
InnoDB: is in the future! Current system log sequence number 7279413947.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
141125 18:50:23  InnoDB: Error: page 1 log sequence number 7290523101
InnoDB: is in the future! Current system log sequence number 7279413947.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
141125 18:50:23  InnoDB: Error: page 4 log sequence number 7290131613
InnoDB: is in the future! Current system log sequence number 7279413947.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
141125 18:50:23  InnoDB: Error: page 123 log sequence number 7290583195
InnoDB: is in the future! Current system log sequence number 7279413947.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
141125 18:50:23  InnoDB: Error: page 11 log sequence number 7290608421
InnoDB: is in the future! Current system log sequence number 7279413947.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
141125 18:50:23  InnoDB: Error: page 10 log sequence number 7290583510
InnoDB: is in the future! Current system log sequence number 7279413947.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
141125 18:50:23  InnoDB: Error: page 4 log sequence number 7288877658
InnoDB: is in the future! Current system log sequence number 7279413947.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
141125 18:50:23  InnoDB: Error: page 3 log sequence number 7288877625
InnoDB: is in the future! Current system log sequence number 7279413947.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
141125 18:50:23 InnoDB: 5.5.40 started; log sequence number 7279413947
141125 18:50:23 [Note] Server hostname (bind-address): '0.0.0.0'; port: 3306
InnoDB: Dump of the tablespace extent descriptor:  len 40; hex 0000141125 18:50:23 [Note]   - '0.0.0.0' resolves to '0.0.0.0';
0000000000020000000000eeffffffff000000000004ffbfaaaaaaaabaaafabffeffeafafbff; asc                                         ;
InnoDB: Serious error! InnoDB is trying to free page 98
InnoDB: though it is already marked as free in the tablespace!
InnoDB: The tablespace free space info is corrupt.
InnoDB: You may need to dump your InnoDB tables and recreate the whole
InnoDB: database!
InnoDB: Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
141125 18:50:23  InnoDB: Assertion failure in thread 140383190222592 in file fsp0fsp.c line 3309
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.
00:50:23 UTC - mysqld got signal 6 ;
This could be because you hit a bug. It is also possible that this binary
or one of the libraries it was linked against is corrupt, improperly built,
or misconfigured. This error can also be caused by malfunctioning hardware.
We will try our best to scrape up some info that will hopefully help
diagnose the problem, but since we have already crashed,
something is definitely wrong and this may fail.

key_buffer_size=8388608
read_buffer_size=131072
max_used_connections=0
max_threads=300
thread_count=0
connection_count=0
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 664533 K  bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x0
Attempting backtrace. You can use the following information to find out
where mysqld died. If you see no messages after this, something went
terribly wrong...
stack_bottom = 0 thread_stack 0x40000
/usr/sbin/mysqld(my_print_stacktrace+0x35)[0x7aa745]
/usr/sbin/mysqld(handle_fatal_signal+0x4a4)[0x685e74]
/lib64/libpthread.so.0(+0xf710)[0x7fad92913710]
/lib64/libc.so.6(gsignal+0x35)[0x7fad91ada625]
/lib64/libc.so.6(abort+0x175)[0x7fad91adbe05]
/usr/sbin/mysqld[0x8cf55a]
/usr/sbin/mysqld[0x8cfa0b]
/usr/sbin/mysqld[0x882d68]
/usr/sbin/mysqld[0x92609f]
/usr/sbin/mysqld[0x9265a8]
/usr/sbin/mysqld[0x91ad32]
/usr/sbin/mysqld[0x85765a]
/usr/sbin/mysqld[0x84c5a2]
/lib64/libpthread.so.0(+0x79d1)[0x7fad9290b9d1]
/lib64/libc.so.6(clone+0x6d)[0x7fad91b909dd]
The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
information that should help you find out what is causing the crash.
141125 18:50:23 mysqld_safe mysqld from pid file /var/run/mysqld/mysqld.pid ended