Hi Jess,
The database ‘kaltura’; database doesn’t exist. And all other kaltura db’s:
kaltura kaltura_sphinx_log kalturadw kalturadw_ds kalturadw_bisources kalturalog
Please advise. I appreciate your help and your time.
Thanks,
Dmitri
mysql> show databases;
+--------------------+
| Database |
+--------------------+
| information_schema |
| mysql |
+--------------------
Hi @astrava,
This is because you ran the following as root from an interactive shell when testing:
# /opt/kaltura/sphinx/bin/searchd --config /usr/local/sphinx/etc/sphinx.conf
So the files under /opt/kaltura/sphinx were created with root.root 600 and now when the init script tries to run searchd as the kaltura user, it cannot write there.
I suggest you:
# rm $BASE_DIR/sphinx/kaltura_* $LOG_DIR/sphinx/data/binlog.*
and rerun the configure script.
Hi Jess,
Thanks for reply.
I dont have the kaltura db: kaltura kaltura_sphinx_log kalturadw kalturadw_ds kalturadw_bisources kalturalog
/opt/kaltura/bin/kaltura-db-config.sh localhost root root 13306
Checking MySQL version…
Ver 5.1.73 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…
ERROR: Couldn’t make an API request to http://sb-kaltura…com/api_v3/index.php?service=system&action=ping.
Please check your setup and then run /opt/kaltura/bin/kaltura-db-config.sh again.
kaltura:x:7373:7373:Kaltura:/opt/kaltura:/bin/bash
monit:x:493:486:monit daemon:/opt/kaltura//var/lib/monit:/bin/sh
mysql:x:27:27:MySQL Server:/var/lib/mysql:/bin/bash
Hi @astrava,
The main Sphinx conf file is here:
/opt/kaltura/app/configurations/sphinx/kaltura.conf
As you can see in /etc/init.d/kaltura-sphinx:
config="$APP_DIR/configurations/sphinx/kaltura.conf"
None of the Kaltura RPMs write files to /usr/local.
To see all the files shipped with kaltura-sphinx, run:
# rpm -ql kaltura-sphinx
Hi Jess,
Thank you for your help.
/opt/kaltura/bin/kaltura-sanity.sh
DEBUG: Restoring dir to [/opt/kaltura/clients-generator]
INFO: php5full generated successfully
[Check httpd daemon status] [FAILED, RC: 1] - [.112451766]
Napping 1 seconds to allow the daemon httpd to finish its init after monit restarted it…
root@sb-kaltura dsmirnof]# kaltlog
tail: cannot open `/opt/kaltura/log/batch/*.log’ for reading: No such file or directory
[2018-03-22 13:30:19]failed to connect [1] [0.003572940826416] 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[B…N] [wrapped: SQLSTATE[42000] [1049] Unknown database ‘kaltura_sphinx_log’]’ 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_read’)
ls -al /opt/kaltura/log/batch/
total 8
drwxrwxr-x. 2 kaltura apache 4096 Feb 26 07:59 .
drwxrwxr-x. 4 kaltura apache 4096 Mar 22 13:31 …
I’m running DB setup and getting error bellow:
I can see my port is blocked
/opt/kaltura/bin/kaltura-db-config.sh
Removing kaltura…Removing kaltura_sphinx_log…Removing kalturadw…Removing kalturadw_ds…Removing kalturadw_bisources…Removing kalturalog…
Successfully dropped kaltura databases and users
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://sb-kaltura…com/api_v3/index.php?service=system&action=ping.
Please check your setup and then run /opt/kaltura/bin/kaltura-db-config.sh again.
Hi @astrava,
The hostname you provide MUST be resolvable both from inside the Kaltura server and from any machine you’ll be using the kaltura API/web I/Fs and player embeds from.
According to your output, the curl command trying to verify the hostname is accessible over HTTP failed.
You need to understand why that is.
If the hostname IS resolvable then something must be wrong with your Apache configuration. If that’s the case, what’s the output for:
# apachectl -t -DDUMP_VHOSTS
?
Hi Jess,
I removed kaltura and started with new install.
kaltura-db-config.sh FAILED with: 255 on line 193
Archving logs to /opt/kaltura/log/log_27_03_18_08_38.tar.gz…
ERROR: we failed on something else…
193 php $APP_DIR/deployment/base/scripts/insertContent.php >> $LOG_DIR/insertContent.log 2>&1
194 if [ $? -ne 0 ];then
195 cat << EOF
/opt/kaltura/app/deployment/base/scripts/insertContent.php
There is no “insertContent.log” created.
I appreciate your time and effort.
Thank you for your support.
Dmitri
Hi @astrava,
Try running:
# php /opt/kaltura/app/deployment/base/scripts/insertContent.php
from the shell and let’s look at the output.
Hi Jess,
I have fixed my httpd with SSL. Thank you.
What should I do with enabled.apps.conf?
I re-run /opt/kaltura/bin/kaltura-config-all.sh
Stopping httpd: [ OK ]
Starting httpd: [Tue Mar 27 10:01:56 2018] [warn] The Alias directive in /opt/kaltura/app/configurations/apache/conf.d/enabled.apps.conf at line 38 will probably never match because it overlaps an earlier Alias.
(98)Address already in use: make_sock: could not bind to address [::]:80
(98)Address already in use: make_sock: could not bind to address 0.0.0.0:80
no listening sockets available, shutting down
Unable to open logs
kaltura-front-config.sh FAILED with: 1 on line 282 (282 service httpd restart)
Archving logs to /opt/kaltura/log/log_27_03_18_10_29.tar.gz…
ERROR: /opt/kaltura/bin/kaltura-front-config.sh failed:( You can re-run it when the issue is fixed.
38 Alias /apps/kea “/opt/kaltura/apps/kea”
39 <Directory “/opt/kaltura/apps/kea”>
Hi @astrava,
is just a warning. This is not what’s preventing Apache from successfully restarting.
Is there a different daemon currently listening on port 80 or is it just an errant/orphan Apache proc that cannot be stopped with SIGTERM? If the former, need to either stop it or set up Apache on a diff port, if the latter, try sending SIGKILL to all currently running Apache procs and then make sure restarting Apache with the init script works as expected. Once done, you can re-run the config script.
Hi Jess,
Thank you for reply. I run in another httpd error:
Starting httpd: [Tue Mar 27 13:07:50 2018] [warn] The Alias directive in /opt/kaltura/app/configurations/apache/conf.d/enabled.apps.conf at line 38 will probably never match because it overlaps an earlier Alias.
Syntax error on line 19 of /etc/httpd/conf.d/zzzkaltura.ssl.conf:
19 SSLCertificateFile @SSL_CERTIFICATE_FILE@
20 SSLCertificateKeyFile @SSL_CERTIFICATE_KEY_FILE@
21 SSLCACertificateFile @SSL_CERTIFICATE_CHAIN_FILE@
SSLCertificateFile: file ‘/etc/httpd/@SSL_CERTIFICATE_FILE@’ does not exist or is empty
[FAILED]
kaltura-batch-config.sh FAILED with: 1 on line 105
PHP Fatal error: Uncaught exception ‘KalturaClientException’ with message ‘couldn’t connect to host’ in /opt/kaltura/app/tests/lib/KalturaClientBase.php:362
Stack trace:
#0 /opt/kaltura/app/tests/lib/KalturaClientBase.php(953): KalturaClientBase->doQueue()
#1 /opt/kaltura/app/tests/standAloneClient/exec.php(345): KalturaClientBase->doMultiRequest()
#2 {main}
thrown in /opt/kaltura/app/tests/lib/KalturaClientBase.php on line 362
359 if ($error)
360 {
361 $this->resetRequest();
362 throw new KalturaClientException($error, KalturaClientException::ERROR_GENERIC);
363 }
364 else
365 {
service httpd reload
Reloading httpd: not reloading due to configuration syntax error
[FAILED]
kaltlog
in /opt/kaltura/app/tests/lib/KalturaClientBase.php:401
Stack trace:
0 /opt/kaltura/app/tests/lib/KalturaClientBase.php(953): KalturaClientBase->doQueue()
2018-03-27 08:34:03 [688530780] [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:65
-rw-r–r--. 1 root root 5413 Mar 7 10:23 /opt/kaltura/app/infra/log/KalturaLog.php
Stack trace:
0 /opt/kaltura/app/alpha/scripts/utils/permissions/addPermissionsAndItems.php(284): KalturaLog::alert(‘ERROR - Permiss…’)
tail: cannot open `/opt/kaltura/log/batch/*.log’ for reading: No such file or directory
ls -al /opt/kaltura/log/batch/
total 8
drwxrwxr-x. 2 kaltura apache 4096 Feb 26 07:59 .
drwxrwxr-x. 4 kaltura apache 4096 Mar 27 13:41 …
rm $BASE_DIR/app/base-config.lock
rm $BASE_DIR/app/base-config-generator.lock
/opt/kaltura/log/generate.php.log
INFO: Now generating: batchClient using Php5ClientGenerator
WARN: Service [multicenters_filesyncimportbatch] not found
WARN: Service [playready_playreadydrm] not found
WARN: Service [drm_drmprofile] not found
WARN: Missing type [KalturaHuluDistributionField]
id kaltura
uid=7373(kaltura) gid=7373(kaltura) groups=7373(kaltura),48(apache)
php /opt/kaltura/app/deployment/base/scripts/insertContent.php
Queuing action [userRole.add]
Queuing action [user.add]
Executing multirequest
PHP Fatal error: Uncaught exception ‘KalturaClientException’ with message ‘couldn’t connect to host’ in /opt/kaltura/app/tests/lib/KalturaClientBase.php:362
Stack trace:
#0 /opt/kaltura/app/tests/lib/KalturaClientBase.php(953):
KalturaClientBase->doQueue()
951 public function doMultiRequest()
952 {
953 return $this->doQueue();
954 }
#1 /opt/kaltura/app/tests/standAloneClient/exec.php(345):
KalturaClientBase->doMultiRequest()
344 echo “Executing multirequest\n”;
345 $multiResponse = $client->doMultiRequest();
346 foreach($multiResponse as $index => $response)
#2 {main}
thrown in /opt/kaltura/app/tests/lib/KalturaClientBase.php on line 362
362 throw new KalturaClientException($error, KalturaClientException::ERROR_GENERIC);
/opt/kaltura/bin/kaltura-sanity.sh
INFO: php5full generated successfully
[Check httpd daemon status] [FAILED, RC: 1] - [.100174303]
Napping 1 seconds to allow the daemon httpd to finish its init after monit restarted it…
Napping 2 seconds to allow the daemon httpd to finish its init after monit restarted it…
Napping 3 seconds to allow the daemon httpd to finish its init after monit restarted it…
I was able to install without httpd SSL . Troubleshooting.
OK. With SSL, please make sure to also set the CA. To verify the Apache SSL config, you can use:
# curl $SERVICE_URL
If that succeeds [without passing the -k arg] then you should be good to go.
Hi Jess,
Thank you for reply. I can’t login to admin console. And I can’t get reset password by email. I’m using right email and password. Please advise. Thanks, Dmitri
Are you sure the DB deployment phase completed successfully?
Please check for errors in /opt/kaltura/log/kaltura_api_v3.log, /opt/kaltura/log/kaltura_apache_errors*.log and /opt/kaltura/log/kaltura_prod.log
we dont have the /opt/kaltura/log/kaltura_prod.log
We have received a message.
-----Original Message-----
Sent: March-27-18 2:36 PM
Subject: Your new Kaltura server is up! and 6 Quick Tips For Smooth Kaltura Maintenance
Dear Kaltura administrator,
Thank you for installing Kaltura, the open source media management platform.
This email confirms that you’ve successfully installed a Kaltura server on: