Kaltura Post installation script failed with ans file

[rohithmeethal]

Hi I am following installation using vagrant file based installation to install on Cent OS 6.7

I am getting following error at post installation stage

[root@ip-172-31-53-149 ~]# /opt/kaltura/bin/kaltura-config-all.sh kaltura.ans
Running base config...

kaltura-base-11.9.0-12.noarch

Welcome to Kaltura Server 11.9.0 post install setup.
Checking MySQL version..
Ver 5.1.73 found compatible

========================================================================================================================
Kaltura install answer file written to /tmp/kaltura_10_03_19_14.ans  -  Please save it!
This answers file can be used to silently-install re-install this machine or deploy other hosts in your cluster.
========================================================================================================================

sed: -e expression #7, char 31: unknown option to `s'

kaltura-base-config.sh FAILED with: 3642 on line 367

Archving logs to /opt/kaltura/log/log_10_03_16_19_14.tar.gz...
cp: cannot stat `/opt/kaltura/log/*log': No such file or directory
tar: *log: Cannot stat: No such file or directory
tar: Exiting with failure status due to previous errors

kaltura-config-all.sh FAILED with: 3557 on line 42

Archving logs to /opt/kaltura/log/log_10_03_16_19_14.tar.gz...
cp: cannot stat `/opt/kaltura/log/*log': No such file or directory
tar: *log: Cannot stat: No such file or directory
tar: Exiting with failure status due to previous errors

[KalturaCommunity-zz]

Hello,

Please email me the kaltura.ans file to jess.portnoy@kaltura.com. There must be some character in one of the ENV vars that's causing the sed on line 367 of /opt/kaltura/bin/kaltura-config-all.sh to fail.

May the source be with you,

Jess Portnoy

Kaltura Connect Virtual Summits 2015 - now on VOD! [connect.mediaspace.kaltura.com]

On Thu, 10 Mar 2016, Rohith Meethal wrote:

Hi I am following installation using vagrant file based installation to install on Cent OS 6.7

I am getting following error at post installation stage

[root@ip-172-31-53-149 ~]# /opt/kaltura/bin/kaltura-config-all.sh kaltura.ans Running base config...

kaltura-base-11.9.0-12.noarch

Welcome to Kaltura Server 11.9.0 post install setup. Checking MySQL version.. Ver 5.1.73 found compatible

Kaltura install answer file written to /tmp/kaltura_10_03_19_14.ans - Please save it!

This answers file can be used to silently-install re-install this machine or deploy other hosts in your cluster.

sed: -e expression #7, char 31: unknown option to `s'

kaltura-base-config.sh FAILED with: 3642 on line 367

Archving logs to /opt/kaltura/log/log_10_03_16_19_14.tar.gz... cp: cannot stat `/opt/kaltura/log/log': No such file or directory tar: log: Cannot stat: No such file or directory tar: Exiting with failure status due to previous errors

kaltura-config-all.sh FAILED with: 3557 on line 42

Archving logs to /opt/kaltura/log/log_10_03_16_19_14.tar.gz... cp: cannot stat `/opt/kaltura/log/log': No such file or directory tar: log: Cannot stat: No such file or directory tar: Exiting with failure status due to previous errors

— Reply to this email directly or view it on GitHub.[ACH7Xjea3mlGRioyGgycC43sHI43EF7_ks5psHF-gaJpZM4HuD6H.gif]

[rohithmeethal]

My answer file

TIME_ZONE="UTC"
KALTURA_FULL_VIRTUAL_HOST_NAME="My.Ip.He.re:80"
KALTURA_VIRTUAL_HOST_NAME="My.Ip.He.re"
DB1_HOST="127.0.0.1"
DB1_PORT="3306"
DB1_PASS="someSecretPass"
DB1_NAME="kaltura"
DB1_USER="kaltura"
SERVICE_URL="http://My.Ip.He.re:80"
SPHINX_SERVER1="127.0.0.1"
SPHINX_SERVER2=" "
DWH_HOST="127.0.0.1"
DWH_PORT="3306"
SPHINX_DB_HOST="127.0.0.1"
SPHINX_DB_PORT="3306"
ADMIN_CONSOLE_ADMIN_MAIL="myemail@company.org"
ADMIN_CONSOLE_PASSWORD="somesecret"
CDN_HOST="My.Ip.He.re"
KALTURA_VIRTUAL_HOST_PORT="80"
SUPER_USER="root"
SUPER_USER_PASSWD="someSecretPass"
ENVIRONMENT_NAME="Kaltura Local"
DWH_PASS="someSecretPass"
PROTOCOL="http"
RED5_HOST="My.Ip.He.re"
USER_CONSENT="0"
CONFIG_CHOICE="0"
CONTACT_MAIL="myemail@company.org"

#for SSL - change:
#IS_SSL=Y
#and uncomment and set correct paths for the following directives
#SSL cert path
#CRT_FILE=/etc/ssl/certs/localhost.crt
#SSL key path
#KEY_FILE=/etc/pki/tls/private/localhost.key
#if such exists enter path here, otherwise leave as is.
#CHAIN_FILE=NONE

IS_SSL="N"
IS_NGINX_SSL="N"
VOD_PACKAGER_HOST="My.Ip.He.re"
VOD_PACKAGER_PORT="88"
WWW_HOST="My.Ip.He.re"
IP_RANGE="0.0.0.0-255.255.255.255"

[rohithmeethal]

Thanks Jess for the replay I have cleared all the secrets and pasted the ans file here, I have used IP address instead of domain name. Since I don't have any domain name pointed.

[jessp01]

right, but there's a reason why I wanted you to send to me in private:) It is possible that the value in one of your passwds is what is failing to be replaced cause it has a character that gets in the way..

May the source be with you,

Jess Portnoy

Kaltura Connect Virtual Summits 2015 - now on VOD! [connect.mediaspace.kaltura.com]

On Thu, 10 Mar 2016, Rohith Meethal wrote:

Thanks Jess for the replay I have cleared all the secrets and pasted the ans file here, I have used IP address instead of domain name. Since I don't have any domain name pointed.

— Reply to this email directly or view it on GitHub.[AFBqvUd5NozQ8kAodQaYHcq9z3QF4e9Zks5psHM7gaJpZM4HuD6H.gif]

[rohithmeethal]

No problem, I have sent the mail to you :)

[rohithmeethal]

My issue was related to using mysql root password containing character #, after I changed the password issue is fixed. Thanks @jessp01 for the quick response.

[jessp01]

@rohithmeethal - welcome. I've also added a function which escapes hashes from inputs prior to running the sed so in the next release, one could input a passwd with a '#' and it would still work.

Thanks,