This guide describes RPM installation of an all-in-one Kaltura server and applies to all major RH based Linux distros including Fedora Core, RHEL, CentOS, etc. (Note the supported distros and versions).
Kaltura CE was just ported to CentOS/RHEL 8. Please note that this is a beta version and one must exercise judgement before deploying it to Prod ENVs.
Kaltura Inc. also provides commercial solutions and services including pro-active platform monitoring, applications, SLA, 24/7 support and professional services. If you're looking for a commercially supported video platform with integrations to commercial encoders, streaming servers, eCDN, DRM and more - Start a Free Trial of the Kaltura.com Hosted Platform or learn more about Kaltura' Commercial OnPrem Edition™. For existing RPM based users, Kaltura offers commercial upgrade options.
Non-SSL Step-by-step Installation
Apache SSL Step-by-step Installation
Live Streaming with Nginx and the RTMP module
- This guide assumes that you have a clean, basic install of one of the RHEL based OS's in 64bit architecture.
- During the installation process, you will be prompted about several hostnames. Note that it is crucial that all host names will be resolvable by other members of the cluster (and outside the cluster in the case of API/front machines). Before installing, verify that your DNS contains records for all the hostnames you intend to use or that the /etc/hosts file on all machines is properly configured to include them.
- Before you begin, make sure you're logged in as the system root. Root access is required to install Kaltura, and you should execute
sudo -iorsu -to make sure that you are indeed root.
Kaltura requires certain ports to be open for proper operation. See the list of required open ports. If you're just testing locally and don't mind an open system, you can use the below to disable iptables altogether:
# iptables -F
# service iptables stop
# chkconfig iptables offCurrently Kaltura doesn't properly support running with SELinux in enforcing mode, things will break if you don't set it to permissive.
# setenforce permissiveTo verify SELinux will not revert to enabled next restart:
- Edit the file
/etc/selinux/config - Verify or change the value of SELINUX to permissive:
SELINUX=permissive - Save the file
/etc/selinux/config
# rpm -ihv http://installrepo.kaltura.org/releases/kaltura-release.noarch.rpmBefore proceeding with the deployment process, please ensure that the EPEL repos are enabled.
Depending on your setup, you may need to enable two additional repos: rhui-REGION-rhel-server-extras and rhui-REGION-rhel-server-optional. This can be done by editing /etc/yum.repos.d/redhat-rhui.repo and changing:
enabled=0
to:
enabled=1
under the following sections:
rhui-REGION-rhel-server-optional
rhui-REGION-rhel-server-extras
Or by running the following commands:
# yum -y install yum-utils
# yum-config-manager --enable rhui-REGION-rhel-server-extras rhui-REGION-rhel-server-optional
See https://fedoraproject.org/wiki/EPEL#Quickstart
Please see: https://blog.remirepo.net/post/2017/12/04/Install-PHP-7.2-on-CentOS-RHEL-or-Fedora Then, run:
# dnf module reset php
# dnf module install php:remi-7.2
The kaltura-nginx package depends on certain packages from the main Remi repo.
In addition, while Kaltura CE can work with PHP 5.5 and above, we highly recommend that you pre-install the PHP 7.2 packages from the Remi repos. For instructions, please see remi-php72 repository activation in the document referenced above.
NOTE: Kaltura CE was ported to PHP 7.4 recently but it is not as well tested. You may elect to use that version instead, in which case, invoke:
# dnf module install php:remi-7.4
Please test on a non-production instance first. We're happy to receive bug reports should you encounter issues.
For CentOS/RHEL 8, it is also necessary to enable the PowerTools repos:
# dnf config-manager --set-enabled PowerTools
For CentOS/RHEL 8, it is also necessary to enable the Fusion repos:
# rpm -ihv https://download1.rpmfusion.org/free/el/rpmfusion-free-release-8.noarch.rpm
Kaltura CE does not currently support MySQL 5.6 and above. Please be sure to deploy MySQL 5.5. If your distro's repos do not provide a suitable version (the CentOS/RHEL 8 repos have a higher version), we recommend the Percona project. See: https://github.com/percona/percona-server/tree/5.5 And, in particular: https://github.com/percona/percona-server/blob/5.5/build-ps/build-rpm.sh
RHEL/CentOS 6 setup:
# yum install mysql-server
# service mysqld start
# mysql_secure_installation
# chkconfig mysqld onRHEL/CentOS 7 setup:
# yum install mariadb-server
# service mariadb start
# mysql_secure_installation
# chkconfig mariadb on**Make sure to answer YES for all steps in the mysql_secure_install install, and follow through all the mysql install questions before continuing further.
Failing to properly run mysql_secure_install will cause the kaltura mysql user to run without proper permissions to access your mysql DB, and require you to start over again.
If your machine doesn't have postfix email configured before the Kaltura install, you will not receive emails from the install system nor publisher account activation mails. If postfix runs without further configuration starting it is sufficient to make Kaltura work.
# service postfix restartIf you are using Amazon Web Services (AWS) please note that by default EC2 machines are blocked from sending email via port 25. For more information see this thread on AWS forums.
When installing on a "desktop" environment there may be package conflicts with media encoding/decoding plugins.
In Redhat 6.5 you should run the following to remove the conflicting packages:
# rpm -e gstreamer-plugins-bad-free totem totem-nautilus
Before you can deploy your Kaltura CE Server, you need to perform some preliminary actions such as adding the Kaltura RPM repos, setting SELinux to persmissive mode and deploying MySQL. Please see pre-install steps.
Install the basic Kaltura Packages:
# yum clean all
# yum install kaltura-serverConfigure MySQL with the required Kaltura Settings
# /opt/kaltura/bin/kaltura-mysql-settings.shStart required service and configure them to run at boot:
# service memcached restart
# service ntpd restart
# chkconfig memcached on
# chkconfig ntpd on# /opt/kaltura/bin/kaltura-config-all.shThe below is a sample question answer format, replace the input marked by <> with your own details:
[Email\NO]: "<your email address>"
CDN hostname [kalrpm.lcl]: "<your hostname>"
Apache virtual hostname [kalrpm.lcl]: "<your hostname>"
Which port will this Vhost listen on [80]?:
DB hostname [127.0.0.1]: "<127.0.0.1>"
DB port [3306]: "<3306>"
MySQL super user [this is only for setting the kaltura user passwd and WILL NOT be used with the application]: "<root>"
MySQL super user passwd [this is only for setting the kaltura user passwd and WILL NOT be used with the application]: "<your root password>"
Analytics DB hostname [127.0.0.1]: "<127.0.0.1>"
Analytics DB port [3306]: "<3306>"
Sphinx hostname [127.0.0.1]: "<127.0.0.1>"
Secondary Sphinx hostname: [leave empty if none] "<empty>"
VOD packager hostname [kalrpm.lcl]: "<kaltura-nginx-hostname>"
VOD packager port to listen on [88]:
Service URL [http://kalrpm.lcl:80]: "<http://apache-hostname:80>"
Kaltura Admin user (email address): "<your email address>"
Admin user login password (must be minimum 8 chars and include at least one of each: upper-case, lower-case, number and a special character): "<your kaltura admin password>"
Confirm passwd: "<your kaltura admin password>"
Your time zone [see http://php.net/date.timezone], or press enter for [Europe/Amsterdam]: "<your timezone>"
How would you like to name your system (this name will show as the From field in emails sent by the system) [Kaltura Video Platform]? "<your preferred system name>"
Your website Contact Us URL [http://corp.kaltura.com/company/contact-us]: "<your contact URL>"
'Contact us' phone number [+1 800 871 5224]? "<your phone number>"
Is your Apache working with SSL?[Y/n] "<n>"
It is recommended that you do work using HTTPs. Would you like to continue anyway?[N/y] "<y>"
Which port will this Vhost listen on? [80] "<80>"
Please select one of the following options [0]: "<0>"
Your install will now automatically perform all install tasks.
Your Kaltura installation is now complete.
Before you can deploy your Kaltura CE Server, you need to perform some preliminary actions such as adding the Kaltura RPM repos, setting SELinux to permissive mode and deploying MySQL. Please see pre-install steps
Note: prior to installing Kaltura, while not a must, we recommend you update the installed packages to latest by running:
# yum updateInstall the basic Kaltura Packages:
# yum clean all
# yum update "*kaltura*"
# yum install kaltura-serverConfigure MySQL with the required Kaltura Settings
# /opt/kaltura/bin/kaltura-mysql-settings.shStart required service and configure them to run at boot:
# service memcached restart
# service ntpd restart
# chkconfig memcached on
# chkconfig ntpd on# /opt/kaltura/bin/kaltura-config-all.shThe below is a sample question answer format, replace the input marked by <> with your own details:
[Email\NO]: "<your email address>"
CDN hostname [kalrpm.lcl]: "<your hostname>"
Apache virtual hostname [kalrpm.lcl]: "<your hostname>"
Which port will this Vhost listen on [80]?: "<443>"
DB hostname [127.0.0.1]: "<127.0.0.1>"
DB port [3306]: "<3306>"
MySQL super user [this is only for setting the kaltura user passwd and WILL NOT be used with the application]: "<root>"
MySQL super user passwd [this is only for setting the kaltura user passwd and WILL NOT be used with the application]: "<your root password>"
Analytics DB hostname [127.0.0.1]: "<127.0.0.1>"
Analytics DB port [3306]: "<3306>"
Sphinx hostname [127.0.0.1]: "<127.0.0.1>"
Secondary Sphinx hostname: [leave empty if none] "<empty>"
VOD packager hostname [kalrpm.lcl]: "<kaltura-nginx-hostname>"
VOD packager port to listen on [88]:
Service URL [http://kalrpm.lcl:443]: "<http://your-hostname:443>"
Kaltura Admin user (email address): "<your email address>"
Admin user login password (must be minimum 8 chars and include at least one of each: upper-case, lower-case, number and a special character): "<your kaltura admin password>"
Confirm passwd: "<your kaltura admin password>"
Your time zone [see http://php.net/date.timezone], or press enter for [Europe/Amsterdam]: "<your timezone>"
How would you like to name your system (this name will show as the From field in emails sent by the system) [Kaltura Video Platform]? "<your preferred system name>"
Your website Contact Us URL [http://corp.kaltura.com/company/contact-us]: "<your contact URL>"
'Contact us' phone number [+1 800 871 5224]? "<your phone number>"
Is your Apache working with SSL?[Y/n]: "<Y>"
Please input path to your SSL certificate: "</path/to/my/ssl/certificate>"
Please input path to your SSL key: "</path/to/my/ssl/key>"
Please input path to your SSL chain file or leave empty in case you have none: "</path/to/my/ssl/chainfile>"
Which port will this Vhost listen on? [443] "<443>"
Please select one of the following options [0]: "<0>"
Please see nginx-ssl-config.md
Kaltura CE includes the kaltura-nginx package, which is compiled with the Nginx RTMP module.
Please see documentation here nginx-rtmp-live-streaming.md
A longer post about it can be found at https://blog.kaltura.com/free-and-open-live-video-streaming
To use the monit Monitoring tab in admin console, you will need to also configure the SSL certificate for monit, see Generate PEM Instructions
Edit: /opt/kaltura/app/configurations/monit/monit.conf and add:
SSL ENABLE
PEMFILE /path/to/your/certificate.pem
The Monit HTTP daemon binds to loopback only by default [127.0.0.1]. If you wish to access the I/F from the Monitoring tab in admin console, edit /opt/kaltura/app/configurations/monit/monit.conf and change the following block to suit your needs:
set httpd port 2812
ADDRESS 127.0.0.1
allow root:@MONIT_PASSWD@
For Monit's conf documentation, please refer to https://mmonit.com/monit/documentation/monit.html, specifically, look under the "MONIT HTTPD" section.
Once done, run: /etc/init.d/kaltura-monit restart
Your Kaltura installation is now complete.
All the post install scripts optionally accept an answer file as the first argument In order to preform an unattended [silent] install, simply edit the template and pass it along to kaltura-config-all.sh.
This will only work if the initial install was using this packages based install, it will not work for old Kaltura deployments using the PHP installers
# rpm -Uhv http://installrepo.kaltura.org/releases/kaltura-release.noarch.rpm
# yum clean all
# yum update "*kaltura*"Once the upgrade completes, run:
# /opt/kaltura/bin/kaltura-config-all.shIn the event you would like to see what changes the package includes before deciding whether or not you wish to upgrade, run:
# yum install yum-plugin-changelog
# yum changelog all kaltura-package-name-hereUse this in cases where you want to clear the database and start from fresh.
# /opt/kaltura/bin/kaltura-drop-db.sh
# yum remove "*kaltura*"
# rm -rf /opt/kalturaOnce the configuration phase is done, you may wish to run the sanity tests, for that, run:
# /opt/kaltura/bin/kaltura-sanity.sh
If you experience unknown, unwanted or erroneous behaviour, the logs are a good place to start, to get a quick view into errors and warning run:
kaltlogIf this does not give enough information, increase logging verbosity:
# sed -i 's@^writers.\(.*\).filters.priority.priority\s*=\s*7@writers.\1.filters.priority.priority=4@g' /opt/kaltura/app/configurations/logger.iniTo revert this logging verbosity run:
# sed -i 's@^writers.\(.*\).filters.priority.priority\s*=\s*4@writers.\1.filters.priority.priority=7@g' /opt/kaltura/app/configurations/logger.iniOr output all logged information to a file for analysis:
allkaltlog > /path/to/mylogfile.logFor posting questions, please go to: (http://forum.kaltura.org)
- Please review the frequently answered questions document for general help before posting to the forums or issue queue.
- This guide describes the installation and upgrade of an all-in-one machine where all the Kaltura components are installed on the same server. For cluster deployments, please refer to cluster deployment document, or Deploying Kaltura using Opscode Chef.
- To learn about monitoring, please refer to configuring platform monitors.
- You can find VMWare images at - https://www.osboxes.org/vmware-images
- Two working solutions to the AWS EC2 email limitations are:
- Using SendGrid as your mail service (setting up ec2 with Sendgrid and postfix).
- Using Amazon's Simple Email Service.
- Kaltura Inc. also provides commercial solutions and services including pro-active platform monitoring, applications, SLA, 24/7 support and professional services. If you're looking for a commercially supported video platform with integrations to commercial encoders, streaming servers, eCDN, DRM and more - Start a Free Trial of the Kaltura.com Hosted Platform or learn more about Kaltura' Commercial OnPrem Edition™. For existing RPM based users, Kaltura offers commercial upgrade options.