These instructions are applicable for Kaltura CE version 5.0.x.
The following prerequisites are required for installing and for running the Kaltura CE V5.0 on a Linux server.
Hardware resources should be set according to expected usage estimations.
- 1GB RAM
- 2 CPUs
- Storage – according to storage needs according to expected usage estimations
It is recommended to install Kaltura CE on CentOS 6.2 Linux installation. You may install Kaltura CE5.0 on other Linux distributions, however, these installations are currently not supported by Kaltura.
Apache 2.2 or higher with following modules enabled:
rewrite, headers, expires, filter, deflate, file_cache, env, proxy.
- PHP 5.2.x/PHP 5.3.x are supported.
- Both php and php-cli must be present.
- The following php extensions should be included and enabled:
fileinfo, bc, calander, date, filter, zlib, hash, mbstring, openssl, pcre, Gd, Curl, Memcache, Mysql, Mysqli, Exif, ftp, iconv, json, Session, apc (recommended), spl, DOM, SimpleXML, xml, xsl, ctype, ssh2 (optional, required for enabling the remote storage functionality)
- Verify that the following settings within the php.ini file are set on each server (for both php and php-cli):
- For PHP 5.3: Verify that request_order parameter includes C, G and P (recommended: "CGP")
- For PHP 5.2: Verify that variables_order parameter in php.ini includes C, G and P.
- Please verify that date.timezone parameter is set to the right timezone.
Please refer to a specific way for handling this prerequisite as reported in our CE forum
- MySQL 5.1.37 or higher
- Please verify that mysql server character set is UTF8.
- The following settings should be added to the my.cnf file
lower_case_table_names = 1
thread_stack = 262144
open_files_limit = 20000
MySQL should be restarted after this adjustment is made.
Package should be installed
Package should be installed
Package should be installed.
32-bit packages required on 64-bit servers
Some of the binaries that are in use by the Kaltura Platform are available in a 32-bit compiled version only. To enable these binaries,
the following packages (or equivalents per Linus Distribution) may be required on a 64-bit server:
- Ubuntu 64-bit: ia32-libs, lib32asound2, lib32gcc1, lib32ncurses5, lib32stdc++6, lib32z1, libc6-i386
- CentOS: glibc.i686 , ncurses-libs, zlib-1.2.x , freetype , bzip2-libs
Required for the video analytics module
Pentaho data integration package
The pentaho data integration package (version 3.2) is required for the analytics module. It should be downloaded and extracted to the
- Create the /usr/local/pentaho/ directory.
- Change to the
- Download the pentaho data-integration package.
- Extract the pentaho data-integration package.
tar xvfz pdi-ce-3.2.0-stable.tar.gz -C /usr/local/pentaho
- Rename the data-integration root directory into pdi.
mv data-integration pdi
Required for managing outgoing emails as part of the Kaltura platform workflow. Suggested packages: Sendmail, postfix
Required during installation
Xymon 4.3.7 (optional)
This is an open source system monitoring package required for the Kaltura Admin Console's out-of-the-box monitoring dashboard and alert system.
- For installing xymon on CentOS 6.2 or RHEL 6, please refer to the installation instructions at http://www.kaltura.org/kaltura-ce-v50-installing-xymon-monitoring-package-centos-62rhel-6.
For further information go to http://www.xymon.com
Kaltura CE cannot run when the Security-Enhanced Linux (SELinux) feature is deployed and enabled. If the SELinux feature is deployed on your server, you must disable it to use Kaltura CE.
Within the /etc/sysconfig/selinux file (if exists on your server) set:
Your server should be restarted after this adjustment is made.
Domain name/virtual host name set within
HOSTS file. (Can be done before/after installation)
The domain name (or virtual hostname) you use for the Kaltura CE installation should be set within the
/etc/hosts file as follows:
You are directed to make this change at the end of the installation script.
This entry is required so that Kaltura internal API client applications (For example, the Admin Console application and the Kaltura Batch Application) can be directed to the relevant Kaltura web services according to their internal 'server url' configuration.