Hi @gregware,
‘Kaltura_Client_Exception’ with message ‘Invalid KS
can be explained away by browser caching. This can happen if you redeployed the DB [which would regenerate all partner secrets] and didn’t clear your browser’s cache.
In regards to the batch daemon, it has a dedicated partner [ID -1] which is used for generating a KS [Kaltura Session]. That’s required since all the server components [and also the web admin interfaces - Admin Console and KMC] make API requests to achieve their various goals. If you’re having problems with the kaltura-batch service, check /opt/kaltura/app/configurations/batch/batch.ini and make sure the string the secret directive is set to corresponds with:
mysql> select admin_secret from batch where id=-1;