KMC login error

Hello,

I am not able to log in to KMC. This is the output of kaltlog.
Please reply as soon as possible.

2015-10-05 19:11:08 [0.000657] [127.0.0.1] [1805039911] [5] [API] [kCoreException->__construct] ERR: exception ‘kCoreException’ with message ‘INVALID_STR’ in /opt/kaltura/app/alpha/apps/kaltura/lib/kCurrentContext.class.php:209
Stack trace:
#0 /opt/kaltura/app/api_v3/lib/KalturaDispatcher.php(77): kCurrentContext::initKsPartnerUser(‘NGMyNTYzYmIwNjV…’, ‘-1’, ‘’)

==> /opt/kaltura/log/batch/kschedulehelper-0-2015-10-05.err.log <==
PHP Fatal error: Uncaught exception ‘KalturaException’ with message ‘Invalid KS “NGMyNTYzYmIwNjVlNWIwOWQyMjg2NDY2OWY3OGEyNzcwOWJjMWY3ZHwtMTs7MTQ0NjY0NDQ2ODsyOzE0NDQwNTI0NjguMTc4NDtiYXRjaFVzZXI7ZGlzYWJsZWVudGl0bGVtZW50Oy0xOw==”, Error “-1,INVALID_STR”’ in /opt/kaltura/app/batch/client/KalturaClientBase.php:768
Stack trace:
#0 /opt/kaltura/app/batch/client/KalturaClient.php(4558): KalturaClientBase->throwExceptionIfError(Array)

]
2015-10-05 19:11:10 [0.000905] [172.31.29.176] [482153967] [4] [API] [ks->logError] ERR: exception ‘Exception’ with message ‘Hash [c02da56545e282668a17dd26f7527bcef155df9f] doesn’t match the sha1 on the salt on partner [-1].’ in /opt/kaltura/app/infra/log/KalturaLog.php:83
Stack trace:
#0 /opt/kaltura/app/alpha/apps/kaltura/lib/webservices/kSessionUtils.class.php(698): KalturaLog::err(‘Hash [c02da5654…’)

#9 {main}
2015-10-05 19:11:10 [0.000690] [172.31.29.176] [482153967] [5] [API] [kCoreException->__construct] ERR: exception ‘kCoreException’ with message ‘INVALID_STR’ in /opt/kaltura/app/alpha/apps/kaltura/lib/kCurrentContext.class.php:209
Stack trace:
#0 /opt/kaltura/app/api_v3/lib/KalturaDispatcher.php(77): kCurrentContext::initKsPartnerUser(‘YzAyZGE1NjU0NWU…’, ‘-1’, ‘’)

]
2015-10-05 19:11:14 [0.000904] [127.0.0.1] [399131872] [4] [API] [ks->logError] ERR: exception ‘Exception’ with message ‘Hash [18e62be0c1c72b4e086c39888972b3767873f95e] doesn’t match the sha1 on the salt on partner [-1].’ in /opt/kaltura/app/infra/log/KalturaLog.php:83
Stack trace:
#0 /opt/kaltura/app/alpha/apps/kaltura/lib/webservices/kSessionUtils.class.php(698): KalturaLog::err(‘Hash [18e62be0c…’)

]
2015-10-05 19:11:14 [0.000911] [127.0.0.1] [949622053] [4] [API] [ks->logError] ERR: exception ‘Exception’ with message ‘Hash [356c4ee140273dc817c59c90cb52bd1a0edfd09c] doesn’t match the sha1 on the salt on partner [-1].’ in /opt/kaltura/app/infra/log/KalturaLog.php:83
Stack trace:
#0 /opt/kaltura/app/alpha/apps/kaltura/lib/webservices/kSessionUtils.class.php(698): KalturaLog::err(‘Hash [356c4ee14…’)

]
2015-10-05 19:11:14 [0.000819] [127.0.0.1] [248948487] [4] [API] [ks->logError] ERR: exception ‘Exception’ with message ‘Hash [1ecfd06f437a420e5fe79cc94dc6f601fce698a0] doesn’t match the sha1 on the salt on partner [-1].’ in /opt/kaltura/app/infra/log/KalturaLog.php:83
Stack trace:
#0 /opt/kaltura/app/alpha/apps/kaltura/lib/webservices/kSessionUtils.class.php(698): KalturaLog::err(‘Hash [1ecfd06f4…’)

#9 {main}
2015-10-05 19:11:14 [0.010064] [127.0.0.1] [399131872] [5] [API] [kCoreException->__construct] ERR: exception ‘kCoreException’ with message ‘INVALID_STR’ in /opt/kaltura/app/alpha/apps/kaltura/lib/kCurrentContext.class.php:209
Stack trace:
#0 /opt/kaltura/app/api_v3/lib/KalturaDispatcher.php(77): kCurrentContext::initKsPartnerUser(‘MThlNjJiZTBjMWM…’, ‘-1’, ‘’)

2015-10-05 19:11:14 [0.000137] [127.0.0.1] [399131872] [7] [API] [KalturaFrontController->serializeResponse] DEBUG: Serialize took - 0.00013494491577148
2015-10-05 19:11:14 [0.006654] [127.0.0.1] [949622053] [5] [API] [kCoreException->__construct] ERR: exception ‘kCoreException’ with message ‘INVALID_STR’ in /opt/kaltura/app/alpha/apps/kaltura/lib/kCurrentContext.class.php:209
Stack trace:
#0 /opt/kaltura/app/api_v3/lib/KalturaDispatcher.php(77): kCurrentContext::initKsPartnerUser(‘MzU2YzRlZTE0MDI…’, ‘-1’, ‘’)

2015-10-05 19:11:14 [0.000489] [127.0.0.1] [949622053] [6] [API] [KalturaFrontController->serializeResponse] DEBUG: Serialize start
2015-10-05 19:11:14 [0.002996] [127.0.0.1] [248948487] [5] [API] [kCoreException->__construct] ERR: exception ‘kCoreException’ with message ‘INVALID_STR’ in /opt/kaltura/app/alpha/apps/kaltura/lib/kCurrentContext.class.php:209
Stack trace:
#0 /opt/kaltura/app/api_v3/lib/KalturaDispatcher.php(77): kCurrentContext::initKsPartnerUser(‘MWVjZmQwNmY0Mzd…’, ‘-1’, ‘’)

==> /opt/kaltura/log/batch/partnerloadcleanup-0-2015-10-05.err.log <==
PHP Fatal error: Uncaught exception ‘KalturaException’ with message ‘Invalid KS “MzU2YzRlZTE0MDI3M2RjODE3YzU5YzkwY2I1MmJkMWEwZWRmZDA5Y3wtMTs7MTQ0NjY0NDQ3NDsyOzE0NDQwNTI0NzQuMzM1OTtiYXRjaFVzZXI7ZGlzYWJsZWVudGl0bGVtZW50Oy0xOw==”, Error “-1,INVALID_STR”’ in /opt/kaltura/app/batch/client/KalturaClientBase.php:768
Stack trace:
#0 /opt/kaltura/app/batch/client/KalturaClient.php(1128): KalturaClientBase->throwExceptionIfError(Array)

==> /opt/kaltura/log/batch/dbcleanup-0-2015-10-05.err.log <==
PHP Fatal error: Uncaught exception ‘KalturaException’ with message ‘Invalid KS “MThlNjJiZTBjMWM3MmI0ZTA4NmMzOTg4ODk3MmIzNzY3ODczZjk1ZXwtMTs7MTQ0NjY0NDQ3NDsyOzE0NDQwNTI0NzQuMzM0NTtiYXRjaFVzZXI7ZGlzYWJsZWVudGl0bGVtZW50Oy0xOw==”, Error “-1,INVALID_STR”’ in /opt/kaltura/app/batch/client/KalturaClientBase.php:768
Stack trace:
#0 /opt/kaltura/app/batch/client/KalturaClient.php(1310): KalturaClientBase->throwExceptionIfError(Array)

==> /opt/kaltura/log/batch/jobsuspender-0-2015-10-05.err.log <==
PHP Fatal error: Uncaught exception ‘KalturaException’ with message ‘Invalid KS “MWVjZmQwNmY0MzdhNDIwZTVmZTc5Y2M5NGRjNmY2MDFmY2U2OThhMHwtMTs7MTQ0NjY0NDQ3NDsyOzE0NDQwNTI0NzQuMzM4MTtiYXRjaFVzZXI7ZGlzYWJsZWVudGl0bGVtZW50Oy0xOw==”, Error “-1,INVALID_STR”’ in /opt/kaltura/app/batch/client/KalturaClientBase.php:768
Stack trace:
#0 /opt/kaltura/app/batch/client/KalturaClient.php(1145): KalturaClientBase->throwExceptionIfError(A

Hello,

The errors you posted indicate that the batch -1 admin secret defined in /opt/kaltura/app/configurations/batch.ini.
This would happen if you dropped the Kaltura DB and later did not reconfigure the base, front, and batch packages.
If you are running on an RPM based system, you should use:
# kaltura-config-all.sh
or, if you are running a cluster, run these depending on a node’s specific role:
# kaltura-base-config.sh
# kaltura-front-config.sh
# kaltura-batch-config.sh

For deb based systems:
# dpkg-reconfigure kaltura-base
# dpkg-reconfigure kaltura-front
# dpkg-reconfigure kaltura-batch

If after doing that you still have issues, please post the new kaltlog output and I’ll gladly take a look.

1 Like

Hi Jess
I have done a fresh installation of kaltura cluster 10.19 and imported an old database to it.
Now i have run

kaltura-base-config.sh

kaltura-front-config.sh

kaltura-batch-config.sh

on respective nodes.

Below is output after running these commands:---------

2015-10-06 11:16:55 [0.000099] [1292845670] [50] [BATCH] [kFileTransferMgr->fileExists] DEBUG: File does not exist
2015-10-06 11:16:55 [0.001086] [1292845670] [51] [BATCH] [KAsyncDropFolderWatcher->setDropFolderError] ERR: exception ‘Exception’ with message ‘Error with folder id [3] - Drop folder path not valid [/opt/kaltura/web/content/TestDropFolder]’ in /opt/kaltura/app/infra/log/KalturaLog.php:83
Stack trace:
#0 /opt/kaltura/app/plugins/drop_folder/batch/DropFolderWatcher/KAsyncDropFolderWatcher.class.php(117): KalturaLog::err(‘Error with fold…’)

2015-10-06 11:16:55 [0.000081] [1292845670] [65] [BATCH] [kFileTransferMgr->fileExists] DEBUG: File does not exist
2015-10-06 11:16:55 [0.000151] [1292845670] [66] [BATCH] [KAsyncDropFolderWatcher->setDropFolderError] ERR: exception ‘Exception’ with message ‘Error with folder id [6] - Drop folder path not valid [/mys3bucket/TestRM]’ in /opt/kaltura/app/infra/log/KalturaLog.php:83
Stack trace:
#0 /opt/kaltura/app/plugins/drop_folder/batch/DropFolderWatcher/KAsyncDropFolderWatcher.class.php(117): KalturaLog::err(‘Error with fold…’)