@jess

this one

kaltura-sphinx-2.2.1-19.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

curl: (60) Peer certificate cannot be authenticated with known CA certificates
More details here: http://curl.haxx.se/docs/sslcerts.html

curl performs SSL certificate verification by default, using a "bundle"
of Certificate Authority (CA) public keys (CA certs). If the default
bundle file isn't adequate, you can specify an alternate file
using the --cacert option.
If this HTTPS server uses a certificate signed by a CA represented in
the bundle, the certificate verification probably failed due to a
problem with the certificate (it might be expired, or the name might
not match the domain name in the URL).
If you'd like to turn off curl's verification of the certificate, use
the -k (or --insecure) option.

Starting monit: Starting Monit 5.18 daemon with http interface at [*]:2812
[ OK ]

curl: (60) Peer certificate cannot be authenticated with known CA certificates
More details here: http://curl.haxx.se/docs/sslcerts.html

curl performs SSL certificate verification by default, using a "bundle"
of Certificate Authority (CA) public keys (CA certs). If the default
bundle file isn't adequate, you can specify an alternate file
using the --cacert option.
If this HTTPS server uses a certificate signed by a CA represented in
the bundle, the certificate verification probably failed due to a
problem with the certificate (it might be expired, or the name might
not match the domain name in the URL).
If you'd like to turn off curl's verification of the certificate, use
the -k (or --insecure) option.

Enter password:

it must be the mysql password i think because it failed when i used a new password

Configuring your Kaltura DB...

curl: (60) Peer certificate cannot be authenticated with known CA certificates
More details here: curl.haxx.se/docs/sslcerts.html

curl performs SSL certificate verification by default, using a "bundle"
of Certificate Authority (CA) public keys (CA certs). If the default
bundle file isn't adequate, you can specify an alternate file
using the --cacert option.
If this HTTPS server uses a certificate signed by a CA represented in
the bundle, the certificate verification probably failed due to a
problem with the certificate (it might be expired, or the name might
not match the domain name in the URL).
If you'd like to turn off curl's verification of the certificate, use
the -k (or --insecure) option.

Checking MySQL version..
mysql: [Warning] Using a password on the command line interface can be insecure.
mysql: [ERROR] Unknown suffix '.' used for variable 'port' (value '127.0.0.1')
mysql: [ERROR] mysql: Error while setting value '127.0.0.1' to 'port'

kaltura-db-config.sh FAILED with: 9 on line 65

Archving logs to /opt/kaltura/log/log_13_09_16_13_51.tar.gz...
curl: (60) Peer certificate cannot be authenticated with known CA certificates
More details here: curl.haxx.se/docs/sslcerts.html

curl performs SSL certificate verification by default, using a "bundle"
of Certificate Authority (CA) public keys (CA certs). If the default
bundle file isn't adequate, you can specify an alternate file
using the --cacert option.
If this HTTPS server uses a certificate signed by a CA represented in
the bundle, the certificate verification probably failed due to a
problem with the certificate (it might be expired, or the name might
not match the domain name in the URL).
If you'd like to turn off curl's verification of the certificate, use
the -k (or --insecure) option.
ERROR: we failed on something else..

ill run the -sf code again on the system.ini file and then rerun this again and use the mysql password this time

oh ok i guess i dont need to run the ln -sf again do i, your just creating a link so it should still be linked right?

Also i just received an kaltura update, should i wait until this is done before installing that update?