I have tried many times to install kaltura-server in my CentOS 7 system, but it doesn’t work:
I have install Community Edition 10.13.0 on CentOS 7 successfully without errors, but if I watch the monitoring page (on admin-console) the stutus of mysql and memcache processes is “Execution failed”
If I try to access in KMC page, it doesn’t load (white screen) or browser refuse the connection.
This is the stat service result on my system:
systemctl status mariadb
mariadb.service - MariaDB database server
Loaded: loaded (/usr/lib/systemd/system/mariadb.service; disabled)
Active: active (running) since Mon 2015-06-22 07:41:19 UTC; 4h 35min ago
Main PID: 1247 (mysqld_safe)
systemctl status memcached
memcached.service - Memcached
Loaded: loaded (/usr/lib/systemd/system/memcached.service; enabled)
Active: active (running) since Mon 2015-06-22 07:41:25 UTC; 4h 37min ago
Main PID: 1512 (memcached)
Lets start with the KMC, cause obviously the Memcached and MariaDB are up and it must be some config issue with the monit configs which we can solve later.
As for KMC, run kaltlog in the shell while making the request and use an HTTP sniffer in parallel, lets see what errors come up.
Seems that doesn’t connect to the database, but during installation there wasn’t any problem.
This is log result:
# kaltlog
[2015-06-22 07:45:20]failed to connect [1] [0.013349056243896] mysql:host=127.0.0.1;port=3306;dbname=kaltura_sphinx_log;
PHP Fatal error: Uncaught exception 'PropelException' with message 'Unable to open PDO connection dsn[mysql:host=127.0.0.1;port=3306;dbname=kaltura_sphinx_log;] user[kaltura] password[xxxxx] [wrapped: SQLSTATE[28000] [1045] Access denied for user 'kaltura'@'localhost' (using password: YES)]' in /opt/kaltura/app/vendor/propel/Propel.php:649
Stack trace:
#0 /opt/kaltura/app/vendor/propel/Propel.php(532): Propel::initConnection(Array, 'sphinx_log')
--
2015-06-22 07:47:14 [1404212679] [addPermissionsAndItems.php] [addItemToPermissions] ALERT: exception 'Exception' with message 'ERROR - Permission name [BATCH_BASE] for partner [0] not found in database - skipping!' in /opt/kaltura/app/infra/log/KalturaLog.php:64
Stack trace:
#0 /opt/kaltura/app/alpha/scripts/utils/permissions/addPermissionsAndItems.php(280): KalturaLog::alert('ERROR - Permiss...')
--
==> /opt/kaltura/log/batch/mailer-0-2015-06-22.err.log <==
PHP Notice: Array to string conversion in /opt/kaltura/app/batch/batches/Mailer/KAsyncMailer.class.php on line 204
PHP Notice: Array to string conversion in /opt/kaltura/app/batch/batches/Mailer/KAsyncMailer.class.php on line 223
PHP Notice: Array to string conversion in /opt/kaltura/app/batch/batches/Mailer/KAsyncMailer.class.php on line 146
PHP Notice: Array to string conversion in /opt/kaltura/app/batch/batches/Mailer/KAsyncMailer.class.php on line 146
PHP Notice: Array to string conversion in /opt/kaltura/app/batch/batches/Mailer/KAsyncMailer.class.php on line 204
PHP Notice: Array to string conversion in /opt/kaltura/app/batch/batches/Mailer/KAsyncMailer.class.php on line 223
PHP Notice: Array to string conversion in /opt/kaltura/app/batch/batches/Mailer/KAsyncMailer.class.php on line 146
PHP Notice: Array to string conversion in /opt/kaltura/app/batch/batches/Mailer/KAsyncMailer.class.php on line 146
PHP Notice: Array to string conversion in /opt/kaltura/app/batch/batches/Mailer/KAsyncMailer.class.php on line 204
PHP Notice: Array to string conversion in /opt/kaltura/app/batch/batches/Mailer/KAsyncMailer.class.php on line 223
talking about monit config file, I already edit this file “/opt/kaltura/app/configurations/monit/monit.d/enabled.mysqld.rc” and changed pidfile path from “/var/run/mysqld/mysqld.pid” to “/var/run/mariadb/mariadb.pid”
For MariaDB, there is /opt/kaltura/app/configurations/monit/monit.avail/mariadb.rc which you should use.
About the DB deployment, can you:
# kaltura-drop-db.sh
and then rerun:
# kaltura-config-all.sh
And make sure the deployment passes w.o any errors?
Nginx port to listen on [88]:
Note: Forwarding request to 'systemctl enable kaltura-nginx.service'.
Redirecting to /bin/systemctl reload kaltura-nginx.service
Running DWH config...
kaltura-dwh-9.4.0-2.noarch
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
Deploying analytics warehouse DB, please be patient as this may take a while...
Output is logged to /opt/kaltura/dwh/logs/c.
if I try to open dwh_setup.log this is the result:
sent 143 bytes received 25 bytes 336.00 bytes/sec
total size is 90670 speedup is 539.70
sending incremental file list
GetFTPFileNames/
sent 141 bytes received 25 bytes 332.00 bytes/sec
total size is 7308893 speedup is 44029.48
sending incremental file list
FetchFTPFile/
sent 131 bytes received 25 bytes 312.00 bytes/sec
total size is 5783119 speedup is 37071.28
sending incremental file list
DimLookup/
sent 122 bytes received 25 bytes 294.00 bytes/sec
total size is 3687964 speedup is 25088.19
sending incremental file list
sent 80 bytes received 12 bytes 184.00 bytes/sec
total size is 34770 speedup is 377.93
current version 5999
Now, opening admin console in the browser I read this message:
“An error occurred
(error code: Server:INVALID_KS)”
First of all, I proceeded to create manually in my DB “kaltura” and “etl” users with their passwords specified in /etc/kaltura.d/system.ini
Cleaning cache I can log-in into admin-console.
The impediment now, after I create in my DB “kaltura” and “etl” users, run “kaltura-drop-db.sh” and “kaltura-config-all.sh” , the installation seems to crash in this point
Running DWH config...
kaltura-dwh-9.4.0-2.noarch
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
Deploying analytics warehouse DB, please be patient as this may take a while...
Output is logged to /opt/kaltura/dwh/logs/dwh_setup.log.
While these messages look alarming, they are actually not that important:)
Are you able to request KMC’s index using curl?
# curl $SERVICE_URL/kmc
If so, does the issue happen to you in all browsers? if curl fails, what do you see?
Yes, indeed much more important…
Still seems like the DB is corrupted. Can you please drop the DB again and attach the entire output for kaltura-config-all.sh?
/opt/kaltura/bin/kaltura-config-all.sh
Running base config...
kaltura-base-10.13.0-7.noarch
Welcome to Kaltura Server 10.13.0 post install setup.
To keep up with the bi-weekly Kaltura releases, and stay up to date with
the latest news, security and bug updates, and connect with the global
Kaltura community - sign up for our regular Kaltura Community updates.
Please enter your email to sign up, or enter NO to pass.
[Email\NO]:NO
In order to finalize the system configuration, please input the following:
CDN hostname [euve77323.serverprofi24.net]:
Apache virtual hostname [euve77323.serverprofi24.net]
(Must be accessible from both inside the machine and from any clients / browsers that will use Kaltura):
Vhost port to listen on [80]:
range of ip addresses belonging to internal kaltura servers [0.0.0.0-255.255.255.255]:
The range is used when checking service actions permissions and allowing to access certain services without KS from the internal servers.
The default is only good for testing, on a production ENV you should adjust according to your network.
DB port [3306]:
MySQL super user [only for install, default root]: root
Analytics DB hostname [127.0.0.1]:
Analytics DB port [3306]:
Sphinx hostname [127.0.0.1]:
Secondary Sphinx hostname [leave empty if none]:
VOD packager hostname [euve77323.serverprofi24.net]:
VOD packager port to listen on [88]:
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):
Confirm passwd:
Your time zone [see http://php.net/date.timezone]: UTC
Your Kaltura install name (this name will show as the From field in emails sent by the system) [Kaltura Video Platform]:
Your website Contact Us URL [http://corp.kaltura.com/company/contact-us]:
Your 'Contact us' phone number [+1 800 871 5224]:
========================================================================================================================
Kaltura install answer file written to /tmp/kaltura_24_06_06_56.ans - Please save it!
This answers file can be used to silently-install re-install this machine or deploy other hosts in your cluster.
========================================================================================================================
Configuration of 10.13.0 finished successfully!
Running FrontEnd config...
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
kaltura-front-10.13.0-1.noarch
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]
Please select one of the following options [0]:
0. All web interfaces
1. Kaltura Management Console [KMC], Hosted Apps, HTML5 lib and ClipApp
2. KAC - Kaltura Admin Console
0
Enabling Apache config - apps.conf
Enabling Apache config - var.conf
Enabling Apache config - admin.conf
========================================================================================================================
Kaltura install answer file written to /tmp/kaltura_24_06_06_56.ans - Please save it!
This answers file can be used to silently-install re-install this machine or deploy other hosts in your cluster.
========================================================================================================================
Redirecting to /bin/systemctl restart httpd.service
Nota: Inoltro richiesta a 'systemctl enable httpd.service'.
Restarting kaltura-monit (via systemctl): [ OK ]
Running Sphinx config...
kaltura-sphinx-2.2.1-16.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.41-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:)
Cleaning cache..
Populating DB with data.. please wait..
Output for /opt/kaltura/app/deployment/base/scripts/installPlugins.php being logged into /opt/kaltura/log/installPlugins.log
Output for /opt/kaltura/app/deployment/base/scripts/insertDefaults.php being logged into /opt/kaltura/log/insertDefaults.log
Output for /opt/kaltura/app/deployment/base/scripts/insertPermissions.php being logged into /opt/kaltura/log/insertPermissions.log
Output for /opt/kaltura/app/deployment/base/scripts/insertContent.php being logged into /opt/kaltura/log/insertContent.log
Generating UI confs..
Restarting kaltura-monit (via systemctl): [ OK ]
Running Batch config...
kaltura-batch-10.13.0-1.noarch
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
Nota: Inoltro richiesta a 'systemctl enable httpd.service'.
Redirecting to /bin/systemctl reload httpd.service
Starting kaltura-monit (via systemctl): [ OK ]
kaltura-nginx-1.8.0-1.x86_64
Kaltura API host [euve77323.serverprofi24.net]:
Nginx server name [euve77323.serverprofi24.net]:
Nginx port to listen on [88]:
Nota: Inoltro richiesta a 'systemctl enable kaltura-nginx.service'.
Redirecting to /bin/systemctl reload kaltura-nginx.service
Running DWH config...
kaltura-dwh-9.4.0-2.noarch
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
Deploying analytics warehouse DB, please be patient as this may take a while...
Output is logged to /opt/kaltura/dwh/logs/dwh_setup.log.
sending incremental file list
MySQLInserter/
sent 137 bytes received 25 bytes 324.00 bytes/sec
total size is 2646419 speedup is 16335.92
sending incremental file list
MappingFieldRunner/
sent 143 bytes received 25 bytes 336.00 bytes/sec
total size is 90670 speedup is 539.70
sending incremental file list
GetFTPFileNames/
sent 141 bytes received 25 bytes 332.00 bytes/sec
total size is 7308893 speedup is 44029.48
sending incremental file list
FetchFTPFile/
sent 131 bytes received 25 bytes 312.00 bytes/sec
total size is 5783119 speedup is 37071.28
sending incremental file list
DimLookup/
sent 122 bytes received 25 bytes 294.00 bytes/sec
total size is 3687964 speedup is 25088.19
sending incremental file list
sent 80 bytes received 12 bytes 184.00 bytes/sec
total size is 34770 speedup is 377.93
current version 5999
DWH configured.
====================================================================================================================
Setup completed successfully!
To access your Kaltura tools visit:
http://euve77323.serverprofi24.net:80
To verify the integrity of your deployment and that all components are fully configured and installed,
you can run the sanity tests using the following command:
/opt/kaltura/bin/kaltura-sanity.sh
To begin, access the Admin Console using the Admin email and password you've entered while installing.
When logged in to the KAC, create a new publisher account to being using Kaltura.
Visit http://www.kaltura.org to join the community and get help!
Visit http://forum.kaltura.org to post issues and help others with theirs.
Visit http://knowledge.kaltura.com to read documentation and learn more.
=====================================================================================================================
Thank you for running Kaltura! To keep Kaltura viable, stable and tested, please join the community and help by contributing sanity tests that verify overall platform stability: http://bit.ly/kaltura-ci , and by contributing to the project roadmap by solving simple tasks and challenges: http://bit.ly/kaltura-tasks.
Indeed looks perfectly fine.
Can I access your machine over SSH? If so, please create an account for me with sudo privileges [do not provide root so you can easily revoke me once done] and send to jess.portnoy@kaltura.com.
