Uploads failing. General error: 145 Table './kaltura/scheduler_status' is marked as crashed and should be repaired]'

1 
Stack trace:
#0 /opt/kaltura/app/batch/client/KalturaClient.php(640): KalturaClientBase->throwExceptionIfError(Array)
--
2017-01-23 15:18:32 [0.001952] [10.40.1.80] [1004244351] [22] [API] [KalturaStatement->execute] DEBUG: /* emlnx-media1.emcc.edu[1004244351][propel] */ INSERT INTO scheduler_status (`ID`,`CREATED_AT`,`UPDATED_AT`,`SCHEDULER_ID`,`SCHEDULER_CONFIGURED_ID`,`TYPE`,`VALUE`) VALUES (NULL,'2017-01-23 15:18:32','2017-01-23 15:18:32','13','80445','7','1')
2017-01-23 15:18:32 [0.000459] [10.40.1.80] [1004244351] [23] [API] [BasePeer::doInsert] ERR: exception 'Exception' with message 'SQLSTATE[HY000]: General error: 145 Table './kaltura/scheduler_status' is marked as crashed and should be repaired' in /opt/kaltura/app/infra/log/KalturaLog.php:83
Stack trace:
#0 /opt/kaltura/app/vendor/propel/Propel.php(408): KalturaLog::err('SQLSTATE[HY000]...')
--
2017-01-23 15:18:32 [0.000393] [10.40.1.80] [1004244351] [24] [API] [KalturaFrontController->getExceptionObject] ALERT: exception 'PropelException' with message 'Unable to execute INSERT statement. [wrapped: SQLSTATE[HY000]: General error: 145 Table './kaltura/scheduler_status' is marked as crashed and should be repaired]' in /opt/kaltura/app/vendor/propel/util/BasePeer.php:299
Stack trace:
#0 /opt/kaltura/app/alpha/lib/model/om/BaseSchedulerStatusPeer.php(766): BasePeer::doInsert(Object(Criteria), Object(KalturaPDO))
--
==> /opt/kaltura/log/batch/kschedulehelper-0-2017-01-23.err.log <==
PHP Fatal error:  Uncaught exception 'KalturaException' with message 'Internal database error' in /opt/kaltura/app/batch/client/KalturaClientBase.php:894
Stack trace:
#0 /opt/kaltura/app/batch/client/KalturaClient.php(640): KalturaClientBase->throwExceptionIfError(Array)
--
2017-01-23 15:19:37 [0.001765] [10.40.1.80] [1963159995] [22] [API] [KalturaStatement->execute] DEBUG: /* emlnx-media1.emcc.edu[1963159995][propel] */ INSERT INTO scheduler_status (`ID`,`CREATED_AT`,`UPDATED_AT`,`SCHEDULER_ID`,`SCHEDULER_CONFIGURED_ID`,`TYPE`,`VALUE`) VALUES (NULL,'2017-01-23 15:19:37','2017-01-23 15:19:37','13','80445','7','1')
2017-01-23 15:19:37 [0.000468] [10.40.1.80] [1963159995] [23] [API] [BasePeer::doInsert] ERR: exception 'Exception' with message 'SQLSTATE[HY000]: General error: 145 Table './kaltura/scheduler_status' is marked as crashed and should be repaired' in /opt/kaltura/app/infra/log/KalturaLog.php:83
Stack trace:
#0 /opt/kaltura/app/vendor/propel/Propel.php(408): KalturaLog::err('SQLSTATE[HY000]...')
--
2017-01-23 15:19:37 [0.000406] [10.40.1.80] [1963159995] [24] [API] [KalturaFrontController->getExceptionObject] ALERT: exception 'PropelException' with message 'Unable to execute INSERT statement. [wrapped: SQLSTATE[HY000]: General error: 145 Table './kaltura/scheduler_status' is marked as crashed and should be repaired]' in /opt/kaltura/app/vendor/propel/util/BasePeer.php:299
Stack trace:
#0 /opt/kaltura/app/alpha/lib/model/om/BaseSchedulerStatusPeer.php(766): BasePeer::doInsert(Object(Criteria), Object(KalturaPDO))
--
==> /opt/kaltura/log/batch/kschedulehelper-0-2017-01-23.err.log <==
PHP Fatal error:  Uncaught exception 'KalturaException' with message 'Internal database error' in /opt/kaltura/app/batch/client/KalturaClientBase.php:894
Stack trace:
2

Try:
# mysqlrepair kaltura scheduler_status -r

If the DB suffered a crush, perhaps you should go right ahead and run:
# mysqlrepair kaltura -r
so it goes over all tables in the ‘kaltura’ DB.

3

Do you mean mysqlcheck?

4

mysqlrepair or mysqlcheck, yeah. I think mysqlrepair only exists in Debian/Ubuntu whereas mysqlcheck exists in both, anyhow, they do the same thing.