Upgrade to most current version

Community Forums Backend Server Support
1

So we are upgrading from kaltura-html5-studio-v1.9.6-1, to the most current version. When I run the upgrade process with YUM all looks okay, and then I run /opt/kaltura/bin/kaltura-config-all.sh and its working its way through rebooting everything and I then get:

Kaltura-batch-config.sh FAILED with: 6 on line 98 I’m guessing that is right around when its trying to restart apache.

So then I check our instance, and the client side is fine, but when I try and login with the administration console I get the white screen of death with “An error occurred” (error code: API:-1).

Bill K.

2

Hi @bkelm,

Are you upgrading to 12.16.0 [latest]?
Line 98 in /opt/kaltura/bin/kaltura-batch-config.sh is:

service httpd reload

Need to understand why the reload is failing.
As for the failure to login, in the shell on the server, run:
# . /etc/profile.d/kaltura*base.sh
# kaltlog

Then make the request and look at the output for errors.
In parallel, also open the dev tools in your browser and look at the errors under the console and network tabs. Once you have the error[s], please paste here.

3

Correct on the version. I can recreate the apache error pretty easily with just a restart, it looks like I have both of these files:

zzzkaltura.conf
zzzkaltura.ssl.conf

and the error on a graceful restart is:

httpd: Syntax error on line 221 of /etc/httpd/conf/httpd.conf: Syntax error on line 7 of /etc/httpd/conf.d/zzzkaltura.conf: Include directory ‘/etc/httpd/@APP_DIR@/configurations/apache/conf.d’ not found. Here is that file:

<VirtualHost *:@KALTURA_VIRTUAL_HOST_PORT@>
# for SSL offloading support, if LB has X_FORWARDED_PROTO set to ‘https’, set HTTPS to 'on’
SetEnvIf X-Forwarded-Proto https HTTPS=on
ErrorLog "@LOG_DIR@/kaltura_apache_errors.log"
CustomLog @LOG_DIR@/kaltura_apache_access.log vhost_kalt

    Include "@APP_DIR@/configurations/apache/conf.d/enabled.*.conf"

Here is the login error:

–
2017-06-02 09:39:24 [0.000100] [1749045569] [7] [%context%] [Kaltura_Client_Clie ntBase->doCurl] DEBUG: post: {“format”:“2”,“ignoreNull”:true,“clientTag”:“Kaltur a-admin",“apiVersion”:“3.2.0”,“loginId”:"bkelm@willamette.edu”,“password”:“XXXXXX”,“partnerId”:"-2",“privileges”:“disableentitlement”,“kalsig”:“0522cccdfc4 da3e073968f6f1fa2c217”}
2017-06-02 09:39:24 [0.005531] [1749045569] [8] [%context%] [ErrorController->er rorAction] ERR: exception ‘Kaltura_Client_ClientException’ with message ‘. RC : 0’ in /opt/kaltura/app/admin_console/lib/Kaltura/Client/ClientBase.php:919
Stack trace:
#0 /opt/kaltura/app/admin_console/lib/Kaltura/Client/ClientBase.php(249): Kaltur a_Client_ClientBase->getKalturaClientException(’. RC : 0’, -1)

4

Hi Bill,

Just to confirm, we are talking about an all in one instance [as opposed to a cluster], correct?

The tokens should be replaced when running /opt/kaltura/bin/kaltura-base-config.sh which is called from /opt/kaltura/bin/kaltura-config-all.sh.

Obviously, if this did not happen, the rest of the config operation would not work correctly and the ENV will be dysfunctional.
We need to understand why the tokens were not replaced.
Let’s start with deleting these lock files:
# rm $BASE_DIR/app/base-config.lock
# rm $BASE_DIR/app/base-config-generator.lock

and manually running:
# $BASE_DIR/bin/kaltura-base-config.sh

Then check the Apache config to ensure all tokens were correctly replaced.
Assuming that they were, you can move forward and run /opt/kaltura/bin/kaltura-config-all.sh.
Please look at the output closely to make sure all scripts executed by /opt/kaltura/bin/kaltura-config-all.sh exit without error.

Just a reminder: all config scripts accept an answer file as the first argument, passing along an answer file will save you from having to interactively input the values at each run.

5

Jess,

Well not perfect, but both interfaces are now running. Below is my screen output:

Stopping httpd: [ OK ]
Starting httpd: [ OK ]
Stopping memcached: [ OK ]
Starting memcached: [ OK ]
Shutting down monit: [ OK ]
Starting monit: Starting Monit 5.21.0 daemon with http interface at [*]:2812
[ OK ]
sed: -e expression #1, char 39: unterminated s' command sed: -e expression #1, char 19: unterminateds’ command
Running Sphinx config…

kaltura-sphinx-2.2.1-20.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 monit: Starting Monit 5.21.0 daemon with http interface at [*]:2812
[ OK ]
Running Batch config…

kaltura-batch-12.16.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

Reloading httpd: not reloading due to configuration syntax error
[FAILED]

kaltura-batch-config.sh FAILED with: 6 on line 98

Archving logs to /opt/kaltura/log/log_16_06_17_14_10.tar.gz…
ERROR: /opt/kaltura/bin/kaltura-batch-config.sh failed:( You can re-run it when the issue is fixed.

Looks like it was trying to do some batch config stuff, but both interfaces are now up.

Thanks,
Bill K.

6

Hi @bkelm,

According to your output, /opt/kaltura/bin/kaltura-batch-config.sh fails on line 98, which is:

service httpd reload

Please run this manually from the shell and let’s see why it’s not exiting with RC 0.