XF 1.5 Have this error currently blowing up my error logs

[OUTL4W]

Zend_Db_Statement_Mysqli_Exception: Mysqli statement execute error : Incorrect key file for table './fps247_setup/xf_session.MYI'; try to repair it - library/Zend/Db/Statement/Mysqli.php:214
Generated By: Unknown Account, A moment ago

#0 /home/fps247/public_html/library/Zend/Db/Statement.php(297): Zend_Db_Statement_Mysqli->_execute(Array)
#1 /home/fps247/public_html/library/Zend/Db/Adapter/Abstract.php(479): Zend_Db_Statement->execute(Array)
#2 /home/fps247/public_html/library/Zend/Db/Adapter/Abstract.php(574): Zend_Db_Adapter_Abstract->query('INSERT INTO `xf...', Array)
#3 /home/fps247/public_html/library/XenForo/Session.php(855): Zend_Db_Adapter_Abstract->insert('xf_session', Array)
#4 /home/fps247/public_html/library/XenForo/Session.php(573): XenForo_Session->saveSessionToSource('f2ee42308e06d14...', false)
#5 /home/fps247/public_html/library/XenForo/Controller.php(414): XenForo_Session->save()
#6 /home/fps247/public_html/library/XenForo/Controller.php(358): XenForo_Controller->updateSession(Object(XenForo_ControllerResponse_View), 'XenForo_Control...', 'Index')
#7 /home/fps247/public_html/library/XenForo/FrontController.php(358): XenForo_Controller->postDispatch(Object(XenForo_ControllerResponse_View), 'XenForo_Control...', 'Index')
#8 /home/fps247/public_html/library/XenForo/FrontController.php(134): XenForo_FrontController->dispatch(Object(XenForo_RouteMatch))
#9 /home/fps247/public_html/index.php(13): XenForo_FrontController->run()
#10 {main}

Request state:
array(3) {
  ["url"] => string(63) "a different thread for every error"
  ["_GET"] => array(0) {
  }
  ["_POST"] => array(0) {
  }
}

The request state string is displaying a different thread for every single error?....

 

[Paul B]

Have you recently migrated to a new server/host or restored from a backup?

That error is typically due to an incorrect backup/restore.

 

[OUTL4W]

I'm just a super admin not owner...will discuss with the owner. Thanks brogan.

 

[Mike]

Running this MySQL query will hopefully resolve it as well:

REPAIR TABLE xf_session;

 

[OUTL4W]

Running this MySQL query will hopefully resolve it as well:

REPAIR TABLE xf_session;

crisis averted....the errors have finally stopped...thanks guys

 

[TPerry]

Now you need to find out why mysql crashed. Especially if you see this happen again.

 

[OUTL4W]

Now you need to find out why mysql crashed. Especially if you see this happen again.

And it did

Spoiler: MySQL

 

[Paul B]

It could be due to some sort of server instability.

You will need to contact your sysadmin or host and ask them to investigate.

 

[OUTL4W]

Finally figured it's due to when I updated jaxel's streams addon
https://xenforo.com/community/threads/8wayrun-com-xenrio-streams-pro-paid.47788/page-60#post-1109159

 

[Mike]

Tables being corrupted really don't have anything to do with an application running on top of MySQL. It indicates that either MySQL crashing/being stopped unexpectedly, the disk is filling up and writes are failing, or some other system instability. You'll really want to investigate what is happening at a lower level than XF/a web app.

 

[OUTL4W]

Tables being corrupted really don't have anything to do with an application running on top of MySQL. It indicates that either MySQL crashing/being stopped unexpectedly, the disk is filling up and writes are failing, or some other system instability. You'll really want to investigate what is happening at a lower level than XF/a web app.

It could be due to some sort of server instability.

You will need to contact your sysadmin or host and ask them to investigate.

So are you suggesting to open a support ticket with the server host (wiredTree)?

 

[Divvens]

So are you suggesting to open a support ticket with the server host (wiredTree)?

I'm with them too and my server had SQL crash multiple times.

Go to your grove management and check for any out of memory logs. if you are running out of memory sql stops and restarts. we are having issues coz of low memory too. if you find any entries in out of memory log there lies the problem.

 

[Mike]

An out-of-memory process killer that's killing MySQL would absolutely be a cause (and killing MySQL is reasonable in the mind of that script as it tends to hold a lot of memory). That's exactly the sort of thing that would cause data corruption like this. It would indicate tweaks need to be made to the configuration to prevent an OOM situation like that. Your host will likely be able to provide more guidance (assuming it's a managed service).