Centos 7 Installation Error

hi all, it is one week i’m trying to install Kaltura. I’m not confident with linux but i think there is some problem in the installation.

As in previous post i have the same issue

kaltura-sphinx-2.2.1-17.x86_64
base-config completed successfully, if you ever want to re-configure your system (e.g. change DB hostname) run the following script:

rm /opt/kaltura/app/base-config.lock

/opt/kaltura/bin/kaltura-base-config.sh

Starting kaltura-monit (via systemctl): [ OK ]

Configuring your Kaltura DB…

Checking MySQL version…
Ver 5.5.44-MariaDB 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 connect to Sphinx with mysql -h127.0.0.1 -P9312.
Please check your setup and then run /opt/kaltura/bin/kaltura-db-config.sh again.

My problem is there
ERROR: Couldn’t connect to Sphinx with mysql -h127.0.0.1 -P9312.

I tried to access writing as root
mysql -h127.0.0.1 -P9312.
It doesn’t work. I can access if i put
mysql -pXXXX -h127.0.0.1 -P9312.

the password i set is the same of the root for mariadb.

many thanks in advance.

Carlo

Carlo,

Please read what I wrote to you here and provide info accordingly:

Many thanks for the reply.

This is the content of /opt/kaltura/log/sphinx/kaltura_sphinx_searchd.log

[Mon Feb 15 00:34:13.425 2016] [20445] Child process 20446 has been forked
[Mon Feb 15 00:34:13.426 2016] [20446] listening on all interfaces, port=9312
[Mon Feb 15 00:34:13.426 2016] [20446] WARNING: index ‘kaltura_base’: no fields configured (use rt_field directive) - NOT SERVING
[Mon Feb 15 00:34:13.426 2016] [20446] WARNING: index ‘kaltura_kuser_base’: no fields configured (use rt_field directive) - NOT SERVING
[Mon Feb 15 00:34:13.453 2016] [20446] accepting connections
[Mon Feb 15 00:36:25.524 2016] [20446] caught SIGTERM, shutting down
[Mon Feb 15 00:36:25.571 2016] [20446] rt: index kaltura_entry: ramchunk saved in 0.002 sec
[Mon Feb 15 00:36:25.575 2016] [20446] shutdown complete
[Mon Feb 15 00:36:25.576 2016] [20445] Child process 20446 has been finished, exit code 0. Watchdog finishes also. Good bye!

Hello,

I suspect this has to do with monit’s configuration.
See CentOs 7 Installation Errors

I suggest you try the new version [11.8.0] and let me know if you’re still having issues.

Ok, many thanx it works.
Now I’m able to install Kaltura in Centos 7 but i have still problem with memecached.

this is the log activated in verbose mode from journalctl

Feb 16 12:41:59 localhost.localdomain systemd[1]: Started Session c85 of user kaltura.
Feb 16 12:41:59 localhost.localdomain systemd[1]: Starting Session c85 of user kaltura.
Feb 16 12:41:59 localhost.localdomain su[50176]: pam_unix(su:session): session opened for user kaltura by (uid=0)
Feb 16 12:41:59 localhost.localdomain su[50176]: pam_unix(su:session): session closed for user kaltura
Feb 16 12:43:01 localhost.localdomain monit[2694]: ‘batch’ failed to start
Feb 16 12:43:11 localhost.localdomain monit[2694]: ‘localhost.localdomain’ ‘localhost.localdomain’ cpu wait usage check succeeded [current c
Feb 16 12:43:11 localhost.localdomain monit[2694]: Sendmail: No mail servers are defined – see manual for ‘set mailserver’ statement
Feb 16 12:43:11 localhost.localdomain monit[2694]: Aborting event
Feb 16 12:43:11 localhost.localdomain monit[2694]: ‘localhost.localdomain’ loadavg(5min) of 2.8 matches resource limit [loadavg(5min)>2.0]
Feb 16 12:43:11 localhost.localdomain monit[2694]: ‘memcachedconf’ checksum was changed for /etc/sysconfig/memcached
Feb 16 12:43:11 localhost.localdomain monit[2694]: Sendmail: No mail servers are defined – see manual for ‘set mailserver’ statement
Feb 16 12:43:11 localhost.localdomain monit[2694]: Aborting event
Feb 16 12:43:11 localhost.localdomain monit[2694]: ‘memcachedconf’ exec: /sbin/service
Feb 16 12:43:11 localhost.localdomain monit[2694]: ‘memcache’ process is not running
Feb 16 12:43:11 localhost.localdomain monit[2694]: ‘memcache’ trying to restart
Feb 16 12:43:11 localhost.localdomain monit[2694]: ‘memcache’ start: /sbin/service
Feb 16 12:43:11 localhost.localdomain systemd[1]: Stopping Memcached…
Feb 16 12:43:11 localhost.localdomain systemd[1]: Started Memcached.
Feb 16 12:43:11 localhost.localdomain systemd[1]: Starting Memcached…
Feb 16 12:43:11 localhost.localdomain memcached[50525]: slab class 1: chunk size 96 perslab 10922
Feb 16 12:43:11 localhost.localdomain memcached[50525]: slab class 2: chunk size 120 perslab 8738
Feb 16 12:43:11 localhost.localdomain memcached[50525]: slab class 3: chunk size 152 perslab 6898
Feb 16 12:43:11 localhost.localdomain memcached[50525]: slab class 4: chunk size 192 perslab 5461
Feb 16 12:43:11 localhost.localdomain memcached[50525]: slab class 5: chunk size 240 perslab 4369
Feb 16 12:43:11 localhost.localdomain memcached[50525]: slab class 6: chunk size 304 perslab 3449
Feb 16 12:43:11 localhost.localdomain memcached[50525]: slab class 7: chunk size 384 perslab 2730
Feb 16 12:43:11 localhost.localdomain memcached[50525]: slab class 8: chunk size 480 perslab 2184
Feb 16 12:43:11 localhost.localdomain memcached[50525]: slab class 9: chunk size 600 perslab 1747
Feb 16 12:43:11 localhost.localdomain memcached[50525]: slab class 10: chunk size 752 perslab 1394
Feb 16 12:43:11 localhost.localdomain memcached[50525]: slab class 11: chunk size 944 perslab 1110
Feb 16 12:43:11 localhost.localdomain memcached[50525]: slab class 12: chunk size 1184 perslab 885
Feb 16 12:43:11 localhost.localdomain memcached[50525]: slab class 13: chunk size 1480 perslab 708
Feb 16 12:43:11 localhost.localdomain memcached[50525]: slab class 14: chunk size 1856 perslab 564
Feb 16 12:43:11 localhost.localdomain memcached[50525]: slab class 15: chunk size 2320 perslab 451
Feb 16 12:43:11 localhost.localdomain memcached[50525]: slab class 16: chunk size 2904 perslab 361
Feb 16 12:43:11 localhost.localdomain memcached[50525]: slab class 17: chunk size 3632 perslab 288
Feb 16 12:43:11 localhost.localdomain memcached[50525]: slab class 18: chunk size 4544 perslab 230
Feb 16 12:43:11 localhost.localdomain memcached[50525]: slab class 19: chunk size 5680 perslab 184
Feb 16 12:43:11 localhost.localdomain memcached[50525]: slab class 20: chunk size 7104 perslab 147
Feb 16 12:43:11 localhost.localdomain memcached[50525]: slab class 21: chunk size 8880 perslab 118
Feb 16 12:43:11 localhost.localdomain memcached[50525]: slab class 22: chunk size 11104 perslab 94
Feb 16 12:43:11 localhost.localdomain memcached[50525]: slab class 23: chunk size 13880 perslab 75
Feb 16 12:43:11 localhost.localdomain memcached[50525]: slab class 24: chunk size 17352 perslab 60
Feb 16 12:43:11 localhost.localdomain memcached[50525]: slab class 25: chunk size 21696 perslab 48
Feb 16 12:43:11 localhost.localdomain memcached[50525]: slab class 26: chunk size 27120 perslab 38
Feb 16 12:43:11 localhost.localdomain memcached[50525]: slab class 27: chunk size 33904 perslab 30
Feb 16 12:43:11 localhost.localdomain memcached[50525]: slab class 28: chunk size 42384 perslab 24
Feb 16 12:43:11 localhost.localdomain memcached[50525]: slab class 29: chunk size 52984 perslab 19
Feb 16 12:43:11 localhost.localdomain memcached[50525]: slab class 30: chunk size 66232 perslab 15
Feb 16 12:43:11 localhost.localdomain memcached[50525]: slab class 31: chunk size 82792 perslab 12
Feb 16 12:43:11 localhost.localdomain memcached[50525]: slab class 32: chunk size 103496 perslab 10
Feb 16 12:43:11 localhost.localdomain memcached[50525]: slab class 33: chunk size 129376 perslab 8
Feb 16 12:43:11 localhost.localdomain memcached[50525]: slab class 34: chunk size 161720 perslab 6
Feb 16 12:43:11 localhost.localdomain memcached[50525]: slab class 35: chunk size 202152 perslab 5
Feb 16 12:43:11 localhost.localdomain memcached[50525]: slab class 36: chunk size 252696 perslab 4
Feb 16 12:43:11 localhost.localdomain memcached[50525]: slab class 37: chunk size 315872 perslab 3
Feb 16 12:43:11 localhost.localdomain memcached[50525]: slab class 38: chunk size 394840 perslab 2
Feb 16 12:43:11 localhost.localdomain memcached[50525]: slab class 39: chunk size 493552 perslab 2
Feb 16 12:43:11 localhost.localdomain memcached[50525]: slab class 40: chunk size 616944 perslab 1
Feb 16 12:43:11 localhost.localdomain memcached[50525]: slab class 41: chunk size 771184 perslab 1
Feb 16 12:43:11 localhost.localdomain memcached[50525]: slab class 42: chunk size 1048576 perslab 1
Feb 16 12:43:11 localhost.localdomain memcached[50525]: <26 server listening (auto-negotiate)
Feb 16 12:43:11 localhost.localdomain memcached[50525]: <27 send buffer was 212992, now 268435456
Feb 16 12:43:11 localhost.localdomain memcached[50525]: <27 server listening (udp)
Feb 16 12:43:11 localhost.localdomain memcached[50525]: <27 server listening (udp)
Feb 16 12:43:11 localhost.localdomain memcached[50525]: <27 server listening (udp)
Feb 16 12:43:11 localhost.localdomain memcached[50525]: <27 server listening (udp)
Feb 16 12:44:12 localhost.localdomain monit[2694]: ‘memcache’ failed to start
Feb 16 12:44:12 localhost.localdomain monit[2694]: ‘batch’ process is not running
Feb 16 12:44:12 localhost.localdomain monit[2694]: ‘batch’ trying to restart
Feb 16 12:44:12 localhost.localdomain monit[2694]: ‘batch’ start: /etc/init.d/kaltura-batch

Why memecache cannot start? From this log i can’t understand.

Carlo

Hi Carlo,

Are you sure memcached is not running? or is it just monit that THINK it is not?
You can verify easily with:
# ps fax|grep memcached
which should show something like:
2025 ? Sl 2:14 /usr/bin/memcached -vv -m 128 -p 11211 -u memcache -l 127.0.0.1

Then you can also telnet to make sure it answers with:
# telnet 127.0.0.1 11211

if it is indeed running and the issue is only with monit not detecting it, then, does /var/run/memcached/memcached.pid exist and has the correct PID for memcached?

If not, try killing the current memcached process, removing /var/run/memcached/memcached.pid and use:
# /sbin/service memcached start
to start it again, then make sure /var/run/memcached/memcached.pid exists and has the correct PID.

ok, maybe is just monit that THINK it is not working:

if i execute: ps fax|grep memcached I obtain:
1083 ? Ssl 0:00 /usr/bin/memcached -u memcached -p 11211 -m 64 -c 1024 -l 127.0.0.1 -vv
8889 pts/0 S+ 0:00 _ grep --color=auto memcached

if i try to use telnet 127.0.0.1 11211: it works.
when i search for /var/run/memcached/memcached.pid: it doesn’t exist.

if i execute: /sbin/service memcached start : it works!
but if i search again for /var/run/memcached/memcached.pid: it doesn’t exist.

What do you think?

Carlo

Hi Carlo,

I looked into it and this stems from what I would call a rather faulty configuration of the memcache daemon in RHEL/CentOS 7.

The way to fix it is:
edit /etc/sysconfig/memcached and add:
OPTIONS=" -P/var/run/memcached/memcached.pid"

If you already have the OPTIONS var there, just add “-P/var/run/memcached/memcached.pid” in the end of it.

# mkdir /var/run/memcached
# chown memcached /var/run/memcached/
# service memcached restart

Then make sure you see /var/run/memcached/memcached.pid with the correct PID.
This way, monit should detect that it is correctly running.

Dear jess,
after the change of /etc/sysconfig/memcached file, setting up the OPTIONS as you writed, now I’m able to see the service memcached up and running.

The last service not working in my installation of Kaltura is batch. Could you help me in this last thing?

Carlo

Hello,

What’s is in the of at /opt/kaltura/log/kaltura_batch.log?
Does the hostname, in /opt/kaltura/app/configurations/batch/batch.ini look OK? i.e:
[YOURHOST : mainTemplate]
Do the serviceUrl and secret directives hold the correct value? for the secret, should be the value of:
mysql> select admin_secret from kaltura.partner where id=-1;

Dear Jess,

looking inside the batch.ini I can check:
serviceUrl=http://localhost.localdomain (from my point of view is correct, it is a server intended working only locally)
secret: is the same as doing the query of mysql from kaltura.partner table.

kaltura_batch.log is reporting this suspect row
2016-02-16 00:20:52 [0.000000] [627159371] [1] [BATCH] [KSchedulerConfig->load] NOTICE: loading configuration /opt/kaltura/app/configuratio$
PHP Warning: file_put_contents(/batch.pid): failed to open stream: Permission denied in /opt/kaltura/app/batch/scheduler/KGenericScheduler$
2016-02-16 00:20:52 [0.064829] [627159371] [2] [BATCH] [KGenericScheduler->loadConfig] INFO: 2.0.2
sh: line 0: kill: (19639) - No such process

Maybe is something related to permission for Kaltura Service?