Converstion profile id "7" not found

Hi,

The Kaltura server (5.0 CE) was already running but suddenly when a publisher try to upload a video, this message (Conversion profile id “7” not found) appears.

It happened once on another server for conversion id “2” not found and fixed it by creating the first published. But for this one, I tried to create another publisher but the id “number” keep its increment on the error message, that’s all.

Any thoughts ?

Hello,

Kaltura CE5 is very old and is no longer supported.
Please visit:


Thank you,

Hi Jess,

Thanks for your fast reply.

Is it possible to upgrade to the latest version ?

On the documentation you sent, it says: “This will only work if the initial install was using this packages based install, it will not work for old Kaltura deployments using the PHP installers” and CE 5.0 is a php installer :frowning:

Thanks again.

Hello,

The upgrade path from CE5 to 9 is somewhat difficult but certainly not impossible.
Please start by creating a clean install of 9 and then follow this thread:

Of course, I’ll be happy to help you during your work and if you can document your steps so it can be shared with others that would be great.
The issue I reference to was opened by another community member who is now going through the same process, feel free to add questions to the same issue

Thanks,

Hi Jess,

Thank you for the response!

I have been trying to do version 9.

I got this error message:
Error: Package: kaltura-front-9.19.0-1.noarch (Kaltura-noarch)
Requires: php
Error: Package: kaltura-kmc-v5.37.27-1.noarch (Kaltura-noarch)
Requires: php-cli
Error: Package: kaltura-kdp-v2.7.0-1.noarch (Kaltura-noarch)
Requires: httpd
Error: Package: kaltura-base-9.19.4-1.noarch (Kaltura-noarch)
Requires: php-xml
Error: Package: kaltura-base-9.19.4-1.noarch (Kaltura-noarch)
Requires: php-imap
Error: Package: kaltura-kmc-v5.37.27-1.noarch (Kaltura-noarch)
Requires: httpd
Error: Package: kaltura-batch-9.19.0-2.noarch (Kaltura-noarch)
Requires: php
Error: Package: kaltura-front-9.19.0-1.noarch (Kaltura-noarch)
Requires: mod_ssl
Error: Package: kaltura-base-9.19.4-1.noarch (Kaltura-noarch)
Requires: php-cli
Error: Package: kaltura-sphinx-2.2.1-16.x86_64 (Kaltura)
Requires: mysql-libs
Error: Package: kaltura-base-9.19.4-1.noarch (Kaltura-noarch)
Requires: php-ldap
Error: Package: kaltura-kdpwrapper-v11.0-1.noarch (Kaltura-noarch)
Requires: httpd
Error: Package: kaltura-front-9.19.0-1.noarch (Kaltura-noarch)
Requires: php-mysql
Error: Package: kaltura-kclip-v1.1.2.1-2.noarch (Kaltura-noarch)
Requires: httpd
Error: Package: 1:kaltura-clipapp-v1.0.7-1.noarch (Kaltura-noarch)
Requires: httpd
Error: Package: kaltura-base-9.19.4-1.noarch (Kaltura-noarch)
Requires: php-curl
Error: Package: kaltura-front-9.19.0-1.noarch (Kaltura-noarch)
Requires: php-mcrypt
Error: Package: kaltura-batch-9.19.0-2.noarch (Kaltura-noarch)
Requires: php-pecl-ssh2
Error: Package: kaltura-front-9.19.0-1.noarch (Kaltura-noarch)
Requires: httpd
Error: Package: kaltura-batch-9.19.0-2.noarch (Kaltura-noarch)
Requires: php-mcrypt
Error: Package: kaltura-kdp3wrapper-v37.0-1.noarch (Kaltura-noarch)
Requires: httpd
Error: Package: 1:kaltura-kdp3-v3.9.9-2.noarch (Kaltura-noarch)
Requires: httpd
Error: Package: kaltura-batch-9.19.0-2.noarch (Kaltura-noarch)
Requires: php-pecl-memcached
Error: Package: kaltura-kupload-1.0.0-1.noarch (Kaltura-noarch)
Requires: httpd
Error: Package: kaltura-front-9.19.0-1.noarch (Kaltura-noarch)
Requires: php-pecl-apc
Error: Package: kaltura-base-9.19.4-1.noarch (Kaltura-noarch)
Requires: php-mysql
Error: Package: kaltura-front-9.19.0-1.noarch (Kaltura-noarch)
Requires: php-pecl-memcached
Error: Package: kaltura-kvpm-v1.0.6-1.noarch (Kaltura-noarch)
Requires: httpd
Error: Package: kaltura-krecord-1.0.0-1.noarch (Kaltura-noarch)
Requires: httpd
Error: Package: kaltura-batch-9.19.0-2.noarch (Kaltura-noarch)
Requires: httpd
Error: Package: kaltura-kcw-1.0.0-6.noarch (Kaltura-noarch)
Requires: httpd
Error: Package: kaltura-batch-9.19.0-2.noarch (Kaltura-noarch)
Requires: mod_ssl
Error: Package: kaltura-base-9.19.4-1.noarch (Kaltura-noarch)
Requires: php-gd
Error: Package: kaltura-base-9.19.4-1.noarch (Kaltura-noarch)
Requires: php-gmp
You could try using --skip-broken to work around the problem
** Found 5 pre-existing rpmdb problem(s), ‘yum check’ output follows:
ConsoleKit-libs-0.4.1-3.el6.x86_64 has missing requires of dbus >= (‘0’, ‘0.90’, None)
libgsf-1.14.15-5.el6.x86_64 has missing requires of GConf2
libgsf-1.14.15-5.el6.x86_64 has missing requires of GConf2
libgsf-1.14.15-5.el6.x86_64 has missing requires of GConf2
sendmail-cf-8.14.4-8.el6.noarch has missing requires of sendmail = (‘0’, ‘8.14.4’, ‘8.el6’)

I am using CentOS 6 on a VPS with GoDaddy. It has PHP 5.5.

Is there something really obvious I’m missing? I have tried installing mysqld but it won’t work (I have the server set to mysqli in the easyapache settings).

In the meantime I will have a look at the thread you posted.

Thank you!!!
Fiona

Hello,

It seems your distro repos are not properly configured since you are missing core packages such as httpd.
What distribution is this?

Hi Jess,

I reset my server as there was nothing on it and I wanted to start over. It is Linux with CentOS 6.5.

I have someone helping me with the prerequisites as it currently has MySQL 5.5 instead of the 5.1 supported. I also get ‘no package available’ messages when yum installing httpd, mysqld, mysql-libs etc. So my colleague is helping. In the meantime I will update you on the progress. Thank you.

Best,
Fiona

Welcome, Fiona.

Let me know how it goes,

Hello,

So you have two issues to check:
Failed:
httpd.x86_64 0:2.2.15-31.el6.centos

Need to understand why the package failed to install. This is a standard distribution package so really has nothing to do with Kaltura. In any event, httpd must be started and listening.
To check:
# netstat -plntu | grep http
Should output somethign like:
tcp 0 0 :::80 :::* LISTEN 12612/httpd

Then make sure you can request:
http://yourhost and get Apache’s default index page.

Next is this one:
mysql: unknown variable ‘open_files_limit=20000’

What MySQL version are you using? this var should be recognized if set in /etc/my.cnf like so:
[mysqld]
open_files_limit = 20000

Hello there!

Everything has gone quite well and I am nearly there.

When running the /opt/kaltura/bin/kaltura-config-all.sh operation however, I get the following errors:

kaltura-batch-9.19.5-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

ERROR: could not retreive partner.admin_secret for id -1. It probably means you did not yet run /opt/kaltura/app/kaltura-base-config.sh yet. Please do.
ERROR: /opt/kaltura/bin/kaltura-batch-config.sh failed:( You can re-run it when the issue is fixed.
Running DWH config…

kaltura-dwh-9.4.0-2.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

ERROR: /opt/kaltura/bin/kaltura-dwh-config.sh failed:( You can re-run it when the issue is fixed.


Unfortunately I am limited to 3 replies!

I ran the drop db command and then did kaltura-config-all.

Here is the output:

Configuration of Kaltura Server 9.19.5 finished successfully!
Running FrontEnd config…

base-config completed successfully, if you ever want to re-configure you r system (e.g. change DB hostname) run the following script:

rm /opt/kaltura/app/base-config.lock

/opt/kaltura/bin/kaltura-base-config.sh

kaltura-front-9.19.5-1.noarch
Is your Apache working with SSL?[Y/n]
Please input path to your SSL certificate[/etc/ssl/certs/localhost.crt]:
/var/cpanel/ssl/system/certs/e_reelz_com_d38e0_34bd3_1447189946_25e3c4f7aaaeed65d7ccbdc
Please input path to your SSL key[/etc/pki/tls/private/localhost.key]:
/var/cpanel/ssl/system/keys/d38e0_34bd3_b28ec0992ff176c58cce57db6ec14c8e.key
Please input path to your SSL chain file or leave empty in case you have none:

WARNING: self signed cerificate detected. Will set settings.clientConfig.verifySSL=0 in

Which port will this Vhost listen on? [443]

Please select one of the following options [0]:
0. All web interfaces

  1. Kaltura Management Console [KMC], Hosted Apps, HTML5 lib and ClipApp
  2. KAC - Kaltura Admin Console
    0
    Enabling Apache config - apps.conf
    Enabling Apache config - var.conf
    Enabling Apache config - admin.conf

=======================================================================================
Kaltura install answer file written to /tmp/kaltura_11_11_17_02.ans - Please save it!
This answers file can be used to silently-install re-install this machine or deploy oth

Stopping httpd: [ OK ]
Starting httpd: [ OK ]
Shutting down monit: [ OK ]
Starting monit: Starting monit daemon with http interface at [*:2812]
[ OK ]
Running Sphinx config…

kaltura-sphinx-2.2.1-16.x86_64
base-config completed successfully, if you ever want to re-configure your system (e.g.

rm /opt/kaltura/app/base-config.lock

/opt/kaltura/bin/kaltura-base-config.sh

Starting monit: Starting monit daemon with http interface at [*:2812]
[ OK ]
Running Batch config…

kaltura-batch-9.19.5-1.noarch
base-config completed successfully, if you ever want to re-configure your system (e.g.

rm /opt/kaltura/app/base-config.lock

/opt/kaltura/bin/kaltura-base-config.sh

ERROR: could not retreive partner.admin_secret for id -1. It probably means you did notease do.
ERROR: /opt/kaltura/bin/kaltura-batch-config.sh failed:( You can re-run it when the iss
Running DWH config…

kaltura-dwh-9.4.0-2.noarch
base-config completed successfully, if you ever want to re-configure your system (e.g.

rm /opt/kaltura/app/base-config.lock

/opt/kaltura/bin/kaltura-base-config.sh

Deploying analytics warehouse DB, please be patient as this may take a while…
Output is logged to /opt/kaltura/dwh/logs/dwh_setup.log.

sending incremental file list
MySQLInserter/

sent 133 bytes received 25 bytes 316.00 bytes/sec
total size is 2646419 speedup is 16749.49
sending incremental file list
MappingFieldRunner/

sent 143 bytes received 25 bytes 336.00 bytes/sec
total size is 90670 speedup is 539.70
sending incremental file list
GetFTPFileNames/

sent 141 bytes received 25 bytes 332.00 bytes/sec
total size is 7308893 speedup is 44029.48
sending incremental file list
FetchFTPFile/

sent 131 bytes received 25 bytes 312.00 bytes/sec
total size is 5783119 speedup is 37071.28
sending incremental file list
DimLookup/

sent 126 bytes received 25 bytes 302.00 bytes/sec
total size is 3687964 speedup is 24423.60
sending incremental file list

sent 80 bytes received 12 bytes 184.00 bytes/sec
total size is 34770 speedup is 377.93
current version 5999
DWH configured.

=======================================================================================

Setup completed successfully!

Best,
Fiona

Hello,

It seems the install did not go through the DB config phase correctly.
Can you:
# /opt/kaltura/bin/kaltura-drop-db.sh
and the run the config again and paste the resulting output?

Thanks,

During the install, I didn’t get this question:

Is your Apache working with SSL?[Y/n]: “”

So once the install is done, HTTPS:// doesn’t work.

Any thoughts >

Hello,

Please paste the entire output for the config scripts, as well as the answer file created under /tmp/kaltura_*ans while masking
the passwds and also, the output for:
# apachectl -t -DDUMP_VHOSTS
# curl -I -v https://yourserviceurl

Thanks,

Hi Jess,

Here is the output:
#more /tmp/kaltura_10_12_19_17.ans
TIME_ZONE="UTC"
KALTURA_FULL_VIRTUAL_HOST_NAME="my_service_url:80"
KALTURA_VIRTUAL_HOST_NAME="my_service_url"
DB1_HOST="127.0.0.1"
DB1_PORT=“3306"
DB1_PASS=”*"
DB1_NAME="kaltura"
DB1_USER="kaltura"
SERVICE_URL="http://my_service_url: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="My_email_address"
ADMIN_CONSOLE_PASSWORD=""
CDN_HOST="my_service_url"
KALTURA_VIRTUAL_HOST_PORT="80"
SUPER_USER="root"
SUPER_USER_PASSWD="
"
ENVIRONMENT_NAME="Kaltura Video Platform"
DWH_PASS="
"
RED5_HOST="my_service_url"
USER_CONSENT="1"
CONTACT_MAIL="My_email_address"
CONFIG_CHOICE="0"
IS_SSL=“N”

apachectl -t -DDUMP_VHOSTS

VirtualHost configuration:
wildcard NameVirtualHosts and default servers:
default:443 ip-10-182-200-2.ec2.internal (/etc/httpd/conf.d/ssl.conf:74)
*:80 my_service_url (/etc/httpd/conf.d/zzzkaltura.conf:1)
Syntax OK

curl -I -v https://my_service_url

  • About to connect() to my_service_url port 443 (#0)
  • Trying 10.182.200.2… connected
  • Connected to my_service_url (10.182.200.2) port 443 (#0)
  • Initializing NSS with certpath: sql:/etc/pki/nssdb
  • CAfile: /etc/pki/tls/certs/ca-bundle.crt
    CApath: none
  • Certificate is signed by an untrusted issuer: ‘E=root@ip-10-182-200-2,CN=ip-10-182-200-2,OU=SomeOrganizationalUnit,O=SomeOrganization,L=SomeCity,ST=SomeState,C=–’
  • NSS error -8172
  • Closing connection #0
  • Peer certificate cannot be authenticated with known CA certificates
    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.