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.
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!
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.
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?
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;
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?