Unable to install Kaltura

1

Configuring your Kaltura DB…

Checking MySQL version…
Ver 5.1.52 found compatible

CREATE USER kaltura;
CREATE USER etl;
CREATE DATABASE kaltura;
CREATE DATABASE kaltura_sphinx_log;
CREATE DATABASE kalturadw;
CREATE DATABASE kalturadw_ds;
CREATE DATABASE kalturadw_bisources;
CREATE DATABASE kalturalog;
Checking connectivity to needed daemons…
Connectivity test passed:)
ERROR: Couldn’t make an API request to http://10.30.32.45/api_v3/index.php?service=system&action=ping.
Please check your setup and then run /opt/kaltura/bin/kaltura-db-config.sh again.

Do you wish to remove the Kaltura DBs? [n/Y]
Hit ‘n’ to keep it for debugging purposes.

2

Hello,

As the output indicates:
curl -I -v http://10.30.32.45/api_v3/index.php?service=system&action=ping
failed.
What is the output of:
# apachectl -t -DDUMP_VHOSTS

Also, is this an RPM or deb install?
If RPM, what is the output for:
# rpm -q kaltura-front
if deb:
# dpkg -l kaltura-front
?

3

Is 10.30.32.45 the correct IP?
Can you get this url from the browser?

4

hi,

apachectl -t -DDUMP_VHOSTS
httpd: Could not reliably determine the server’s fully qualified domain name, using 10.30.32.45 for ServerName
VirtualHost configuration:
wildcard NameVirtualHosts and default servers:
default:443 10.30.32.45 (/etc/httpd/conf.d/ssl.conf:75)
*:80 10.30.32.45 (/etc/httpd/conf.d/zzzkaltura.conf:1)
Syntax OK

#rpm -q kaltura-front
kaltura-front-11.8.0-1.noarch

5

Hi,

IP is correct, but I am unable to access (HTTPD service status showing as below)

service httpd status
httpd dead but subsys locked

6

Check /var/log/httpd/error_log and /opt/kaltura/log/kaltura_apache_errors.log to understand why Apache won’t start.

7

hi,

/var/log/httpd/error_log showin as below,

[root@media subsys]# tail /var/log/httpd/error_log
[Mon Mar 14 22:09:51 2016] [error] (28)No space left on device: Cannot create SSLMutex
Configuration Failed
[Mon Mar 14 22:11:02 2016] [notice] suEXEC mechanism enabled (wrapper: /usr/sbin/suexec)
[Mon Mar 14 22:11:02 2016] [notice] SSL FIPS mode disabled
[Mon Mar 14 22:11:02 2016] [error] (28)No space left on device: Cannot create SSLMutex
Configuration Failed
[Mon Mar 14 22:12:13 2016] [notice] suEXEC mechanism enabled (wrapper: /usr/sbin/suexec)
[Mon Mar 14 22:12:13 2016] [notice] SSL FIPS mode disabled
[Mon Mar 14 22:12:13 2016] [error] (28)No space left on device: Cannot create SSLMutex
Configuration Failed

opt/kaltura/log/kaltura_apache_errors.log is empty

tail /opt/kaltura/log/kaltura_apache_errors.log
[root@media subsys]# file /opt/kaltura/log/kaltura_apache_errors.log
/opt/kaltura/log/kaltura_apache_errors.log: empty

Use% Mounted on
55% /
0% /dev/shm
7% /boot
78% /opt
[root@media subsys]#

Disk space is there

8

The message by Apache is a bit misleading, it is not about disk space, it is about semaphores. Do:
# ipcs -s | grep apache | awk ’ { print $2 } ’ | xargs ipcrm sem
and try to restart Apache again:
# service httpd start

9

hi,

ipcs -s | grep apache | awk ’ { print $2 } ’ | xargs ipcrm sem

resource(s) deleted
[root@media subsys]# service httpd start
Starting httpd: httpd: Could not reliably determine the server’s fully qualified domain name, using 10.30.32.45 for ServerName
[ OK ]
[root@media subsys]# service httpd status
httpd dead but subsys locked
[root@media subsys]#

in /var/log/httpd/error_log
is showing as

[root@media bin]# tail -f /var/log/httpd/error_log
[Mon Mar 14 22:18:58 2016] [notice] suEXEC mechanism enabled (wrapper: /usr/sbinsuexec)
[Mon Mar 14 22:18:58 2016] [notice] SSL FIPS mode disabled
[Mon Mar 14 22:18:58 2016] [notice] Digest: generating secret for digest authentcation …
[Mon Mar 14 22:18:58 2016] [notice] Digest: done
[Mon Mar 14 22:18:59 2016] [apc-error] apc_mmap: ftruncate failed: File too larg
[Mon Mar 14 22:19:20 2016] [notice] suEXEC mechanism enabled (wrapper: /usr/sbinsuexec)
[Mon Mar 14 22:19:20 2016] [notice] SSL FIPS mode disabled
[Mon Mar 14 22:19:20 2016] [notice] Digest: generating secret for digest authentcation …
[Mon Mar 14 22:19:20 2016] [notice] Digest: done
[Mon Mar 14 22:19:20 2016] [apc-error] apc_mmap: ftruncate failed: File too larg
[Mon Mar 14 22:20:31 2016] [notice] suEXEC mechanism enabled (wrapper: /usr/sbin/suexec)
[Mon Mar 14 22:20:31 2016] [notice] SSL FIPS mode disabled
[Mon Mar 14 22:20:31 2016] [notice] Digest: generating secret for digest authentication …
[Mon Mar 14 22:20:31 2016] [notice] Digest: done
[Mon Mar 14 22:20:31 2016] [apc-error] apc_mmap: ftruncate failed: File too large

10

How much RAM do you have?
# free -m

11

Hi,

It it is running on my VM, Currently 1 GB i given to it. If I succeeded here i need to implement this in production.

free -m
total used free shared buffers cached
Mem: 990 919 70 0 91 641
-/+ buffers/cache: 187 803
Swap: 1023 0 1023
[root@media subsys]#

12

Try googling this. It might be something else and not memory limitation.
E.g.: https://elkano.org/blog/apc-error-apc_mmap-ftruncate-failed-file-too-large/

13

Hi

thank you for your support.
I resolved the issue by hashing (#) LoadModule php5_module modules/libphp5.so
in /etc/httpd/conf.d/php.conf