Permissions Issue Related to Upload After Server Restart

We are currently running Kaltura CE 11.2.0. We have restarted the database of our Kaltura instance and after that we are getting an error uploading video files. The error states “Internal Server Error”. The excpetions are of field missing in different tables. It says permission requires, and SHA1 does not match for kmx user. This error is preventing us from ingesting any content and materially affects our business. Any help is greatly appreciated.

Here are some log entries;

[9/5/16, 6:38:28 PM] Prakhar Budholiya: XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXx
Logs
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
#0 /opt/kaltura/app/alpha/apps/kaltura/lib/KExternalErrors.class.php(128): KalturaLog::err(‘exiting on erro…’)

2016-09-05 19:37:14 [0.001066] [182.73.244.10] [236335513] [39] [API] [KalturaStatement->execute] DEBUG: /* kaltura.babyflix.net[236335513][propel] */ INSERT INTO flavor_asset (ID,INT_ID,PARTNER_ID,TAGS,CREATED_AT,UPDATED_AT,ENTRY_ID,FLAVOR_PARAMS_ID,STATUS,VERSION,WIDTH,HEIGHT,BITRATE,FRAME_RATE,IS_ORIGINAL,CONTAINER_FORMAT,VIDEO_CODEC_ID,TYPE) VALUES (‘0_kyzgvt6c’,NULL,‘101’,‘source’,‘2016-09-05 19:37:14’,‘2016-09-05 19:37:14’,‘0_31zsd38f’,‘0’,‘0’,‘2’,‘0’,‘0’,‘0’,‘0’,‘1’,’’,’’,‘1’)
2016-09-05 19:37:14 [0.000444] [182.73.244.10] [236335513] [40] [API] [BasePeer::doInsert] ERR: exception ‘Exception’ with message ‘SQLSTATE[HY000]: General error: 1364 Field ‘description’ doesn’t have a default value’ in /opt/kaltura/app/infra/log/KalturaLog.php:83
Stack trace:
#0 /opt/kaltura/app/vendor/propel/Propel.php(408): KalturaLog::err(‘SQLSTATE[HY000]…’)

2016-09-05 19:37:14 [0.000262] [182.73.244.10] [236335513] [43] [API] [KalturaFrontController->getExceptionObject] ALERT: exception ‘PropelException’ with message ‘Unable to execute INSERT statement. [wrapped: SQLSTATE[HY000]: General error: 1364 Field ‘description’ doesn’t have a default value]’ in /opt/kaltura/app/vendor/propel/util/BasePeer.php:299
Stack trace:
#0 /opt/kaltura/app/alpha/lib/model/om/BaseassetPeer.php(1501): BasePeer::doInsert(Object(Criteria), Object(KalturaPDO))

2016-09-05 19:37:15 [0.000128] [641706463] [11] [BATCH] [KalturaClientBase->doQueue] INFO: execution time for [https://kaltura.babyflix.net/api_v3/service/dropfolder_dropfolder/action/list]: [0.12383890151978]
2016-09-05 19:37:15 [0.000173] [641706463] [12] [BATCH] [KAsyncDropFolderWatcher->getDropFoldersList] ERR: exception ‘Exception’ with message ‘Cannot get drop folder list - The access to service [dropfolder_dropfolder->list] is forbidden’ in /opt/kaltura/app/infra/log/KalturaLog.php:83
Stack trace:
#0 /opt/kaltura/app/plugins/drop_folder/batch/DropFolderWatcher/KAsyncDropFolderWatcher.class.php(108): KalturaLog::err(‘Cannot get drop…’)
^C
[9/5/16, 6:39:02 PM] Prakhar Budholiya: –
#6 {main}
2016-09-05 19:37:56 [0.000203] [1211794883] [9] [%context%] [InfraBootstrapper->_initNavigation] ERR: exception ‘Exception’ with message 'Class [GenericDistributionProviderConfigureAction] requires permissions [Array
(

]’ in /opt/kaltura/app/infra/log/KalturaLog.php:83
Stack trace:
#0 /opt/kaltura/app/ui_infra/InfraBootstrapper.php(111): KalturaLog::err(‘Class [GenericD…’)

#6 {main}
2016-09-05 19:37:56 [0.000181] [1211794883] [10] [%context%] [InfraBootstrapper->_initNavigation] ERR: exception ‘Exception’ with message 'Class [GenericDistributionProviderDeleteAction] requires permissions [Array
(

Hi @steve_corey,

My guess is that the DB may have been switched over to an earlier snapshot which no longer corresponds to your version’s expected DB schema. Is the DB running on a VM with snapshots? if so, that’s probably the cause.

For example, for the first insert, the flavor_asset description field is defined like so:
| Field | Type | Null | Key | Default
| description | varchar(255) | NO | | NULL |

What does it look like in your current DB?

Note that just changing the default to NULL if it’s not currently the case in your DB is not good enough since I’m sure there will be plenty other mismatches…

I would suggest erecting another machine and restoring the DB from backup on it, then, changing /opt/kaltura/app/configuration/db.ini to point to that newly erected DB and see if that works correctly.

Let me know if you require further assistance,