Upgrade Kaltura CE to 13.0

roger78 · August 9, 2017, 1:54pm

Hi

I just try to upgrade my single server test instance from 12.10 to 13.0, but the installation of kaltura-base fails with the output:

INFO: Copy tests from [/opt/kaltura/clients-generator/sources/php5]
INFO: Saving client library to [/opt/kaltura/web/content/clientlibs/testsClient]
INFO: testsClient generated successfully
ERROR 1046 (3D000) at line 1: No database selected
mysql: option ‘-P’ requires an argument
mysql: option ‘-P’ requires an argument

There is no posibility to set the db password during install.

The “old” instance have got proper configured config files.

Kind Regrads
Roger

jess · August 9, 2017, 2:08pm

HI @roger78,

During the postinst phase of the kaltura-base deb and RPM, the ‘kaltura’ MySQL user’s passwd is taken from the DB1_PASS ENV var, which is set in /etc/kaltura.d/system.ini. Your output also suggests you’re missing the other DB1_.* vars.
Please check /etc/kaltura.d/system.ini.

roger78 · August 9, 2017, 2:26pm

Hi Jess

Yes It looks like everything is correct in this file

DB1_HOST=localhost
DB1_NAME=kaltura
DB1_USER=kaltura
DB1_PASS=mycorrectpassword

I doublechecked the credentials and they are correct.

I am using debian.

jess · August 10, 2017, 10:20am

Hi @roger78,

I recommend that you edit:
/var/lib/dpkg/info/kaltura-base.postinst
so that:

#!/bin/bash

becomes:

#!/bin/bash -x

And then, either run:
# aptitude install -f
or
# dpkg-reconfigure kaltura-base

BASH will then output a lot of debug info to STDERR which will allow you to see exactly which line of code in the postinst script is failing and what ENV vars were set and what args were passed to the mysql client.
If you need help with the analysing the root cause, please paste that output here [minus the actual passwds of course].

roger78 · August 11, 2017, 1:37pm

Thank you @jess the DB1_PORT was missing for the kaltura-base setup and the SUPER_USER and SUPER_USER_PASSWD was missing for the kaltura-html5lib setup.
I entered the values to the system.ini and the installation went successfull throught.

After the setup were completed the values, which i entered weren’t in the system.ini anymore.
It seems that a script will overwrite this file after the setup and remove these vaules.

strange.
I entered the value once more for the next update.
Probably this happens only on a all-in-one installation. (Debian)

Best wishes
Roger Barras

jess · August 11, 2017, 2:05pm

Hi @roger78,

All these values are written to $BASE_DIR/app/configurations/system.ini which is symlinked to /etc/kaltura.d/system.ini, during the execution of /var/lib/dpkg/info/kaltura-base.postinst.

If the values do not already exist in the debconf DB, you will be prompted for them during the configure phase.
See:
https://github.com/kaltura/platform-install-packages/blob/Mercury-13.1.0/deb/kaltura-base/debian/postinst#L141-#L163

The writing of these values into system.ini happens here:

github.com

kaltura/platform-install-packages/blob/Mercury-13.1.0/deb/kaltura-base/debian/postinst#L542


KMC_PATH=`ls -ld $BASE_DIR/web/flash/kmc/v* 2>/dev/null|awk -F " " '{print $NF}' |tail -1`
KMC_LOGIN_PATH=`ls -ld $BASE_DIR/web/flash/kmc/login/v* 2>/dev/null|awk -F " " '{print $NF}' |tail -1`
if [ -d "$KMC_PATH" -a -d "$KMC_LOGIN_PATH" ];then
        KMC_VERSION=`basename $KMC_PATH`
        KMC_LOGIN_VERSION=`basename $KMC_LOGIN_PATH`
        sed -i "s#\(@KMC_VERSION@\)#$KMC_VERSION#g" $BASE_DIR/bin/sanity_config.ini
        sed -i "s#\(@KMC_LOGIN_VERSION@\)#$KMC_LOGIN_VERSION#g" $BASE_DIR/bin/sanity_config.ini
fi




#echo -e "${BRIGHT_BLUE}Configuration of $KALTURA_VERSION finished successfully!${NORMAL}"
send_install_becon `basename $0` $TIME_ZONE install_success 0
echo "
SERVICE_URL=$SERVICE_URL
SPHINX_HOST=$SPHINX_SERVER1
DB1_PORT=$DB1_PORT
SUPER_USER=$SUPER_USER
SUPER_USER_PASSWD=\"$SUPER_USER_PASSWD\"
KALTURA_VIRTUAL_HOST_NAME=$KALTURA_FULL_VIRTUAL_HOST_NAME
RED5_HOST=$RED5_HOST
">> $BASE_DIR/app/configurations/system.ini

So it is a bit odd that this didn’t happen to you.
Are you able to reproduce it when running:
# dpkg-reconfigure kaltura-base
?

Note that if you run the above, you’ll also need to run:
# dpkg-reconfigure kaltura-front
# dpkg-reconfigure kaltura-batch

Afterwards.

ArneWeise · November 22, 2017, 12:21pm

Sorry for thread jacking… but how did you manage to upgrade to 13 in the first place?

I’ve followed the steps for my Debian installation detailed here

github.com

kaltura/platform-install-packages/blob/master/doc/install-kaltura-deb-based.md

# Installing Kaltura on a Single Server (deb)
This guide describes deb installation of an all-in-one Kaltura server and applies to deb based Linux distros.

The processes was tested on Debian 8 and Ubuntu 14.04 but is expected to work on other versions. 

*When installing on Ubuntu Xenial [16.04], please refer to [this howto](install-kaltura-xenial.md) instead.*

If you tried a different deb based distro and failed, please report it.


[Kaltura Inc.](http://corp.kaltura.com) also provides commercial solutions and services including pro-active platform monitoring, applications, SLA, 24/7 support and professional services. If you're looking for a commercially supported video platform  with integrations to commercial encoders, streaming servers, eCDN, DRM and more - Start a [Free Trial of the Kaltura.com Hosted Platform](http://corp.kaltura.com/free-trial) or learn more about [Kaltura' Commercial OnPrem Edition™](http://corp.kaltura.com/Deployment-Options/Kaltura-On-Prem-Edition). Please note that this service in only offered for RHEL based distros. 

#### Table of Contents
[Prerequites](pre-requisites.md)

[Step-by-step Installation](install-kaltura-deb-based.md#step-by-step-installation)

[Unattended Installation](install-kaltura-deb-based.md#unattended-installation)

[Nginx SSL Configuration](nginx-ssl-config.md)

This file has been truncated. show original

aptitude install ~Nkaltura
only yields
0 packages upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

and I’m stuck on 12.20.0-2.

jess · November 22, 2017, 1:06pm

Hi @ArneWeise,

I have updated the upgrade instructions in the hope that they will now be clearer and easier to follow.
Please see:

github.com

kaltura/platform-install-packages/blob/Mercury-13.7.0/doc/install-kaltura-deb-based.md#upgrade-kaltura

# Installing Kaltura on a Single Server (deb)
This guide describes deb installation of an all-in-one Kaltura server and applies to deb based Linux distros.

The processes was tested on Debian 8 and Ubuntu 14.04 but is expected to work on other versions. 

*When installing on Ubuntu Xenial [16.04], please refer to [this howto](install-kaltura-xenial.md) instead.*

If you tried a different deb based distro and failed, please report it.


[Kaltura Inc.](http://corp.kaltura.com) also provides commercial solutions and services including pro-active platform monitoring, applications, SLA, 24/7 support and professional services. If you're looking for a commercially supported video platform  with integrations to commercial encoders, streaming servers, eCDN, DRM and more - Start a [Free Trial of the Kaltura.com Hosted Platform](http://corp.kaltura.com/free-trial) or learn more about [Kaltura' Commercial OnPrem Edition™](http://corp.kaltura.com/Deployment-Options/Kaltura-On-Prem-Edition). Please note that this service in only offered for RHEL based distros. 

#### Table of Contents
[Prerequites](https://github.com/kaltura/platform-install-packages/blob/master/doc/pre-requisites.md)

[Step-by-step Installation](https://github.com/kaltura/platform-install-packages/blob/master/doc/install-kaltura-deb-based.md#step-by-step-installation)

[Unattended Installation](https://github.com/kaltura/platform-install-packages/blob/master/doc/install-kaltura-deb-based.md#unattended-installation)

[Live Streaming with Nginx and the RTMP module](install-kaltura-redhat-based.md#live-streaming-with-nginx-and-the-rtmp-module)

This file has been truncated. show original

or, in the event you’re running a cluster:

github.com

kaltura/platform-install-packages/blob/Mercury-13.7.0/doc/deb-cluster-deployment-instructions.md#upgrade-kaltura

# Deploying Kaltura Clusters

Below are **deb** based instructions for deploying Kaltura Clusters.    
Refer to the [All-In-One Kaltura Server Installation Guide](https://github.com/kaltura/platform-install-packages/blob/master/doc/install-kaltura-deb-based.md) for more notes about deploying Kaltura in deb supported environments.    

### Instructions here are for a cluster with the following members:

* [Load Balancer](#apache-load-balancer)
* [NFS server](#the-nfs-server)
* [MySQL Database](#the-mysql-database)
* [Sphinx Indexing](#the-sphinx-indexing-server)
* [Front servers](#the-front)
* [Batch servers](#the-batch)
* [DWH server](#the-datawarehouse)
* [Nginx VOD server](#nginx-vod-server)
* [Live Streaming with Nginx and the RTMP module](#live-streaming-with-nginx-and-the-rtmp-module)
* [Upgrade Kaltura](#upgrade-kaltura)
* [Platform Monitoring](#platform-monitoring)
* [Backup and Restore](#backup-and-restore-practices)

This file has been truncated. show original

If you’re still not getting updates when running these commands, please paste the contents of /etc/apt/sources.list.d/kaltura.list here, as well as the output for each of the commands specified in the howto.

Thanks,

ArneWeise · November 22, 2017, 1:17pm

Thanks Jess!

mercury instead of lynx should do the trick I think. Will take a snapshot and give it a try.

Will post pack in case of errors.

jess · November 22, 2017, 1:22pm

Welcome @ArneWeise.
Indeed, always best to take a snapshot first:)
Also, I’ve revised the doc again because:

# dpkg-query -f '${Package} ' -W "kaltura-*"

will also output packages that were previously installed and are now removed which is not desired. You could do:

# dpkg-query -f '${Package} ${Status}\n' -W "kaltura-*"|grep "install ok installed"|awk -F " " '{print $1}'|xargs

To only get INSTALLED kaltura packages but to be honest, it’s best to just use:

# aptitude dist-upgrade

since really, you also want to upgrade all the packages the Kaltura packages rely on, such as Apache, OpenSSL, PHP, etc. This is especially important from a security standpoint.

ArneWeise · November 23, 2017, 9:45am

Got this error after updating /etc/apt/sources.list.d/kaltura.list
and adding the new key I still get this error.

W: GPG error: http://installrepo.kaltura.org/repo/apt/debian mercury InRelease: The following signatures were invalid: AD4200615722734CBBE6C52FE7EEDECAA1174D5E
W: The repository ‘http://installrepo.kaltura.org/repo/apt/debian mercury InRelease’ is not signed.
N: Data from such a repository can’t be authenticated and is therefore potentially dangerous to use.

jess · November 23, 2017, 10:40am

Hi @ArneWeise,

Did you import the right key?

wget -O - http://installrepo.kaltura.org/repo/apt/debian/kaltura-deb.gpg.key|apt-key add -

ArneWeise · November 23, 2017, 10:49am

Yes.

I even tried to first wget the key separately and then running apt-key add kaltura-deb.gpg.key.

What have I missed?
Is InRelease repo it’s own repo? Could it bee that it’s not signed?

jess · November 23, 2017, 11:37am

Hi @ArneWeise,

All our repos are signed:)
What’s the output for:

# apt-key list|grep Kaltura -A1
# cat /etc/apt/sources.list.d/kaltura.list

Thanks,

ArneWeise · November 23, 2017, 11:42am

apt-key list complaints that one should not parse it’s output…

However these the following keys seems to belong to kaltura
uid [ unknown] Kaltura deb repo community@kaltura.com
sub rsa2048 2015-04-18 [E]
–
uid [ unknown] Kaltura deb repo community@kaltura.com
sub rsa2048 2015-01-01 [E]

cat /etc/apt/sources.list.d/kaltura.list gives me
deb [arch=amd64] http://installrepo.kaltura.org/repo/apt/debian mercury main

jess · November 23, 2017, 11:46am

Hi @ArneWeise,

I suggest you try to remove all the Kaltura keys you have and reimport.
I just tested on 2 of my ENVs [it’s not the same Debian version as yours but that shouldn’t make a difference in this respect] and had no issues.

ArneWeise · November 23, 2017, 11:56am

Same thing.

For the purpose of debuging I tried apt-get update before importing the key.
That produced an error indicating a missing key ( NO_PUBKEY E7EEDECAA1174D5E )

After importing the keys again the message is different
The following signatures were invalid: AD4200615722734CBBE6C52FE7EEDECAA1174D5E

jess · November 23, 2017, 2:51pm

Hi @ArneWeise,

Only thing I can try to do is deploy on the exact same Debian version as you’re using, though again, the key handling should be the same regardless of the Debian/Ubuntu version, unless Ubuntu Xenial [16.04] is used, which has its own dedicated repo and thus a different GPG key. What version are you using?

ArneWeise · November 23, 2017, 2:54pm

#cat /etc/debian_version = 9.2

As for Kaltura I’m still on 12.20.0-2 - on my way to 13.

I’v read posts about Debian has abandoned SHA1 in apt as of version 9. Could that affect it?

jess · November 23, 2017, 3:13pm

Hi @ArneWeise,

Yes. Also, there are other issues with using Debian 9 [Stretch]. Please see a detailed explanation as to why, here:

For Debian, we only support 7 [Wheezy] and 8 [Jessie], for Ubuntu, both 14.04 and 16.04 are are supported.
If you want, you can deploy a Docker container of one of these versions on your actual machine, of course, a VM is fine too.

Note that the supported distros are always specified here:

github.com

kaltura/platform-install-packages/blob/Mercury-13.8.0/doc/pre-requisites.md

# Kaltura CE Pre-requisites
* 64 bit RHEL/CentOS 6.n, 7.n, Wheezy [7], Debian Jessie [8], Ubuntu 14.{04,10}, Ubuntu 16.{04,10}
* PHP 5.3.n, 5.4.n, 5.5.n, 5.6.n or 7.0.n [PHP >= 7.1 is not supported]
* MySQL/MariaDB [the official RPM/deb from the distro's repo or the Percona packages, MySQL 5.7 is not supported]. 
	*Note: Please make sure your MySQL is configured not to enforce strict mode.*
* JRE 1.7.n

Thanks,