The latest version is now available.
Or, if running a cluster:
I have just upgraded my dev server and I`m getting a server error when accessing the content tab under KMC. The entries list shows nothing.
This is the output from kaltlog:
2017-05-11 08:45:12 [0.000337] [22.214.171.124]   [API] [KalturaFrontController->getExceptionObject] CRIT: exception 'Exception' with message 'Cannot find  in config' in /opt/kaltura/app/alpha/config/kConf.php:227Stack trace:
I already cleaned the /opt/kaltura/app/cache and ran the sphinx_reindex script.
Should I report as a bug ? This is a clean setup that I use to test the new versions so it seems to be a real issue.
I need a bit more info in order to effectively troubleshoot it.Can you please open /opt/kaltura/log/kaltura_api_v3.log and attach the lines leading to the final exception?In addition, please open your browser's dev tools and, under the "Network" tab, locate the failing request[s] and paste them here? I imagine HTTP 500 will be the RC for these but anything that does not return with 200, 301 or 302 is worth looking into.
I forgot to copy the following line:
I just get the Internal Server error pop-up but I don't get a 500 or any errors on my browser debugger.
This is the complete kaltlog error message:
2017-05-11 14:14:53 [0.000189] [126.96.36.199]   [API] [KalturaStatement->execute] DEBUG: Sql took - 0.00010514259338379 seconds2017-05-11 14:14:53 [0.000338] [188.8.131.52]   [API] [KalturaFrontController->getExceptionObject] CRIT: exception 'Exception' with message 'Cannot find  in config' in /opt/kaltura/app/alpha/config/kConf.php:227Stack trace:
I have checked against different partners and different browsers, just to make sure. I also ran the config-setup script twice.
I hope it will help,
Is the kaltura-sphinx daemon running? If this is a cluster, check all Sphinx nodes, of course.
Yes it is.
I restarted the process, just in case, and same results.
Does anybody else get the same problem ? If not, I'l check my config again but I believe it's a very clean setup that I only use for testing the new versions.
I have just checked and one of my test partners works. I had it blocked before the upgrade and after unblocking him, everything works. I'm figuring out the difference between him and my other accounts and I let you know.
Just to remind everybody. If you are using live streaming don't forget to set your broadcast.ini again after an upgrade... I finally found the error.
This topic was automatically closed after 8 days. New replies are no longer allowed.