Fixing Kaltura CE5

Kaltura CE is a great product in a lousy suite, it offers some of the most advanced and high end features for a video platform, it’s free and open sourced.

Back to our subject, the problem is with the suite, things like the installation script and installation process, the VMWare package and other small pieces that destroy the entire puzzle for the entire community.

Luckily, I have been installing quite a few of those and this post will show how to fix some very common errors and hopefully get you closer to your Kaltura CE working perfectly.

Installing Kaltura CE

  1. Download the svn package and use it rather then the VMware image, the latest might have other less common errors.
  2. Try to install: using the installation manual. Use “sudo” or root user to bypass some known issues.
  3. Take a close look of what’s written on the screen, the installation script does some preliminary checks for Kaltura prerequisites.
  4. Some of the most common missing prerequisites are:
    • Several modules in apache mostly the mod_cache_file, module rewrite and Memchached.
    • Pentaho or ETL packages.

    * You can see the prerequisites here.

  5. Check the installation log for errors. located on /kalturaCE_v5.0.0/ open the log file something like: install_log_12.06.2012_21.14.44, check to see if any errors occurred.
  6. If you see any errors, try to fix them and reinstall until the log is clean and you see installation success.

Making it work

Now after we know the installation is done for sure there are some common issues that usually arise.
One is where no analytics are present on the KMC, I’ve already written about it in this post.
Now we can check Kaltura log for fatal errors and common notices.

Checking the log

Kaltura API log is the main log we’re interested in. it’s located at /opt/kaltura/log/kaltura_api_v3.log, open it and examine it. use “shift + g” on less to go to bottom.

If you don’t see anything then you are okay, search the log file for “fatal” or “err” strings to see if there are any.

Now let’s take a closer look on the log.
Use “less /opt/kaltura/log/kaltura_api_v3.log”
Now take a look, you should see the occasional permission issue on permission id’s 571, 633 and 17.

Some thing like:
[kPermissionManager::addPartnerGroupAction] NOTICE: Permission item id [571] is not of type PermissionItemType::API_ACTION_ITEM but still defined in partner group permission id [117]

[kPermissionManager::addPartnerGroupAction] NOTICE: Permission item id [633] is not of type PermissionItemType::API_ACTION_ITEM but still defined in partner group permission id [117]

Those issues can be resolved and keep your log nice and clean by deleting two lines from the DB using the next steps:

  1. Log in to mysql console and use ‘kaltura’ DB:
    mysql -u root -p
    use kaltura; 
  2. delete the two buggy rows from the DB.
    delete from permission_to_permission_item  where permission_id = 117 and (permission_item_id = 633 or permission_item_id= 571);
    * You can select the rows before using:  select * from permission_to_permission_item  where permission_id = 117 and (permission_item_id = 633 or permission_item_id= 571);

I haven’t experienced any issues after this changed and it shouldn’t effect your system.

memcached module error

You might find other issues on you log like the memcached module. which is cache for PHP and apache, those aren’t critical errors but you want your cache to work.

If you see these error lines on kaltura_api_v3.log:
NOTICE: /opt/kaltura/app/infra/general/myCache.class.php line 39 – Memcache::connect(): Server Your.Server (tcp 11211) failed with: Connection refused (111)

WARN: /opt/kaltura/app/infra/general/myCache.class.php line 39 – Memcache::connect(): Can’t connect to Your.Server:11211, Connection refused (111)

To fix this just check closely that you have memcached module installed and loaded on your apache, you can see the memcached configurations on: /opt/kaltura/app/alpha/config/kConfLocal.php

If you still suffer issues check that your firewall is open for such connections, although it shouldn’t matter if you’re working on localhost.
Some helpful threads on memcached are:

I think that three errors on a single post are more then most can handle so I’ll stop here.

If you encounter any other issue or error, feel free to leave a comment below.

Leave a Reply

Your email address will not be published. Required fields are marked *