Frequently Asked Questions
Before You Get Started Notes
- If you see a
#at the beginning of a line, this line should be run as
Commercial Editions and Paid Support
The Open Source Kaltura Platform is provided under the AGPLv3 license and with no commercial support or liability.
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.
How to contribute
We value contributions from our CE user base very much. To make a contribution, follow the See our CONTRIBUTERS doc.
Changing Apache configurations post install.
Sometimes, you may want to change deployment settings post installation, for example: replacing the domain, port or protocol, or changing the system to use SSL or stop using SSL.
You can run
/opt/kaltura/bin/kaltura-front-config.sh as many times as you'd like with different values. The script will re-configure the system accordingly.
For instance, you may want to change the service URL, port or protocol.
Edit the answers file you've used to install Kaltura, then run:
# /opt/kaltura/bin/kaltura-front-config.sh /path/to/updated/ans/file
If you've lost your installation answers file, you can recreate one using the Kaltura Install Answers File Example.
Deploy Local Repository for Offline Install
On rare ocaasions, you may encounter the need to deploy Kaltura on an offline environment where internet connection is not available, and thus you can't reach the Kaltura packages install repository (http://installrepo.kaltura.org/releases/).
On such cases, the solution is to download the packages, deploy a local repository and install from it instead of the online repository.
Note that when following this path, you will need to re-deploy your local repository for every new version upgrade.
To perform an offline install, follow the Deploy Local Repository for Offline Install guide.
Fresh Database Installation
On occasions where you'd like to drop the database and content and re-install Kaltura. Follor the below commands:
# /opt/kaltura/bin/kaltura-drop-db.sh # /opt/kaltura/bin/kaltura-config-all.sh [answers-file-path]
General troubleshoot procedure
Increase log verbosity to 7 using the following method.
Run the following command:
# sed -i 's@^writers.\(.*\).filters.priority.priority\s*=\s*7@writers.\1.filters.priority.priority=4@g' /opt/kaltura/app/configurations/logger.ini
Then restart your Apache.
# kaltlog, which will continuously track (using
tail) an error grep from all Kaltura log files.
You can also use:
# allkaltlog (using root), which will dump all the error lines from the Kaltura logs once. Note that this can result in a lot of output, so the best way to use it will be to redirect to a file:
# allkaltlog > errors.txt.
This output can be used to analyze past failures but for active debugging use the kaltlog alias.
Cannot login to Admin Console
To manually reset the passwd, following this procedure: mysql> select * from user_login_data where email@example.com'\G
Then, update sha1_password and salt to read: sha1_password: 44e8c1db328d6d2f64de30a8285fb2a1c9337edb salt: a6a3209b8827759fa4286d87a33f99df
This should reset your passwd to 'admin123!'