Kaltura CE 10.0.0 released

[jess]

Hello all,

The latest version is now available.

Core changelog:

• Webcasting BE enhancements
• Kaltura Media Server supporting Webcasting BE enhancements
• Kaltura-Live DVR Window change to 24 hours
• Allow searching cuepoints in categories
• SUP-2899 - User sessions cannot view their own user data
• SUP-2810 - ARF ingestion issue - audio garbled
• PLAT-2151 - report->getTable data amount restriction

HTML5 player changelog:

• FEC-2491 - VOD VS.Live: unstable off line DVR mode after disconnecting broadcasting.
• FEC-2455 - Live button & text are enabled when Live is on.
• FEC-2490 - “Jump to live” tooltip appear on Live entry without DVR
• FEC-2509 - Thumbnail is displayed on playing video.

KMC changelog:

• FEC-2282 - Lead with Universal studio ( instead of flash ) when pressing studio in KMC
• SUP-3269 - Edit Entry window of live entry with Manager KMC role
• PLAT-2081 - New live transcording profile is added to new streaming window just after refreshing KMC browser
• PLAT-1908 - Missing exception on approve content when user does not have permission
• PLAT-2223 - KMC - New Transcoding Profile - The creation of a new transcoding profile redirects the KMC to the Content tab (once per session)

To upgrade, please follow:

kaltura/platform-install-packages/blob/Jupiter-10.0.0/doc/install-kaltura-redhat-based.md#upgrade-kaltura

Or, if running a cluster:

kaltura/platform-install-packages/blob/Jupiter-10.0.0/doc/rpm-cluster-deployment-instructions.md#upgrade-kaltura

As always, your feedback is welcomed,

[jeansalim83]

Hi Jess,

Just FYI. I update my RPMs, but like each time I had to reindex sphynx in order for the content to appear in KMC.

Here’s the config-all output:
[root@backend1 /]# kaltura-config-all.sh /tmp/kaltura_03_12_00_13.ans
Running base config…

kaltura-base-10.0.0-9.noarch
Welcome to Kaltura Server 10.0.0 post install setup.

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

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

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

kaltura-front-10.0.0-1.noarch
Enabling Apache config - apps.conf
Enabling Apache config - var.conf
Enabling Apache config - admin.conf

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

Stopping httpd: [ OK ]
Starting httpd: [ OK ]
Shutting down monit: [ OK ]
Starting monit: /opt/kaltura/app/configurations/monit/monit.d/enabled.mysqld.rc:13: Warning: Program does not exist: 'service’
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. change DB hostname) run the following script:

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

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

searchd (pid 19895 19894) is running…
Stopping searchd: Sphinx 2.2.1-id64-dev (r4097)
Copyright © 2001-2013, Andrew Aksyonoff
Copyright © 2008-2013, Sphinx Technologies Inc (http://sphinxsearch.com)

using config file ‘/opt/kaltura/app/configurations/sphinx/kaltura.conf’…
stop: successfully sent SIGTERM to pid 19895

Backing up files to /opt/kaltura/sphinx.bck.1419242569. Once the upgrade is done and tested, please remove this directory to save space
PHP Notice: Undefined offset: 0 in /opt/kaltura/app/alpha/apps/kaltura/lib/db/DbManager.php on line 259
PHP Notice: Undefined offset: 0 in /opt/kaltura/app/alpha/apps/kaltura/lib/db/DbManager.php on line 259
2014-12-22 12:02:50 [global] ERR: exception ‘Exception’ with message ‘Failed to connect to any Sphinx config’ in /opt/kaltura/app/infra/log/KalturaLog.php:82
Stack trace:
#0 /opt/kaltura/app/deployment/base/scripts/populateSphinxEntries.php(36): KalturaLog::err(‘Failed to conne…’)
#1 {main}
Running Batch config…

kaltura-batch-10.0.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:
Starting monit: /opt/kaltura/app/configurations/monit/monit.d/enabled.mysqld.rc:13: Warning: Program does not exist: 'service’
Starting monit daemon with http interface at [*:2812]
[ OK ]
Running DWH config…

Jean.

[jess]

Hi Jean,

First, thanks for reporting.
Second, it is clear that the starting of Sphinx did not happen post clearing old data and thus the exception was raised.
What is not clear to me is why.
Can you look at /opt/kaltura/bin/kaltura-sphinx-schema-update.sh
Line 42 should read:
42 /etc/init.d/kaltura-sphinx start
Do you have this line?
Can you please re-run this script with
# bash -x /opt/kaltura/bin/kaltura-sphinx-schema-update.sh
So we can try to understand why this peace of code does not exec?

Thanks,

[jeansalim83]

Hi Jess,

The line /etc/init.d/kaltura-sphinx start is present.

[root@backend1 /]# bash -x /opt/kaltura/bin/kaltura-sphinx-schema-update.sh
++ dirname /opt/kaltura/bin/kaltura-sphinx-schema-update.sh

• KALTURA_FUNCTIONS_RC=/opt/kaltura/bin/kaltura-functions.rc
• ‘[’ ‘!’ -r /opt/kaltura/bin/kaltura-functions.rc ‘]’
• . /opt/kaltura/bin/kaltura-functions.rc
  ++ RC_FILE=/etc/kaltura.d/system.ini
  ++ ‘[’ -r /etc/kaltura.d/system.ini ‘]’
  ++ . /etc/kaltura.d/system.ini
  +++ WEB_DIR=/opt/kaltura/web
  +++ LOG_DIR=/opt/kaltura/log
  +++ APP_DIR=/opt/kaltura/app
  +++ BASE_DIR=/opt/kaltura
  +++ PHP_BIN=/usr/bin/php
  +++ OS_KALTURA_USER=kaltura
  +++ MAILTO=
  +++ ADMIN_CONSOLE_ADMIN_MAIL=
  +++ DB1_HOST=127.0.0.1
  +++ DB1_NAME=kaltura
  +++ DB1_USER=kaltura
  +++ DB1_PASS=gSwaHCyZoO9nwP5
  +++ DWH_HOST=127.0.0.1
  +++ DWH_PORT=3306
  +++ DWH_USER=etl
  +++ DWH_PASS=gSwaHCyZoO9nwP5
  +++ SERVICE_URL=http://backend1.flomina.com:80
  +++ SPHINX_HOST=127.0.0.1
  +++ DB1_PORT=3306
  +++ SUPER_USER=root
  +++ SUPER_USER_PASSWD=*******
  +++ KALTURA_VIRTUAL_HOST_NAME=backend1.flomina.com
  +++ RED5_HOST=backend1.flomina.com
  +++ dirname /opt/kaltura/bin/kaltura-sphinx-schema-update.sh
  ++ COLORS_RC=/opt/kaltura/bin/colors.sh
  ++ ‘[’ -r /opt/kaltura/bin/colors.sh ‘]’
  ++ . /opt/kaltura/bin/colors.sh
  +++ DULL=0
  +++ BRIGHT=1
  +++ FG_BLACK=30
  +++ FG_RED=31
  +++ FG_GREEN=32
  +++ FG_YELLOW=33
  +++ FG_BLUE=34
  +++ FG_VIOLET=35
  +++ FG_CYAN=36
  +++ FG_WHITE=37
  +++ FG_NULL=00
  +++ BG_BLACK=40
  +++ BG_RED=41
  +++ BG_GREEN=42
  +++ BG_YELLOW=43
  +++ BG_BLUE=44
  +++ BG_VIOLET=45
  +++ BG_CYAN=46
  +++ BG_WHITE=47
  +++ BG_NULL=00
  +++ ETCOLOR_ERROR=’\033[1;31m’
  +++ ESC=’\033’
  +++ NORMAL=’\033[m’
  +++ RESET=’\033[0;37;00m’
  +++ BLACK=’\033[0;30m’
  +++ RED=’\033[0;31m’
  +++ GREEN=’\033[0;32m’
  +++ YELLOW=’\033[0;33m’
  +++ BLUE=’\033[0;34m’
  +++ VIOLET=’\033[0;35m’
  +++ CYAN=’\033[0;36m’
  +++ WHITE=’\033[0;37m’
  +++ BRIGHT_BLACK=’\033[1;30m’
  +++ BRIGHT_RED=’\033[1;31m’
  +++ BRIGHT_GREEN=’\033[1;32m’
  +++ BRIGHT_YELLOW=’\033[1;33m’
  +++ BRIGHT_BLUE=’\033[1;34m’
  +++ BRIGHT_VIOLET=’\033[1;35m’
  +++ BRIGHT_CYAN=’\033[1;36m’
  +++ BRIGHT_WHITE=’\033[1;37m’
  +++ REV_CYAN=’\033[0;47;46m’
  +++ REV_RED=’\033[0;33; 41m’
  +++ JESS=‘Jess likes this one :)’
  ++ ‘[’ -r /etc/sysconfig/clock ‘]’
  ++ . /etc/sysconfig/clock
  +++ ZONE=Asia/Beirut
  ++ ‘[’ -r /opt/kaltura/app/configurations/consent_msgs ‘]’
  ++ . /opt/kaltura/app/configurations/consent_msgs
  +++ PRE_CONSENT=‘To improve your Kaltura experience and provide you with the best service, Kaltura would like your consent to collect necessary data and information regarding your installation and use of Kaltura and analyze it to provide an upgraded and more stable platform and services.
  This information helps us understand what problems users encounter when using Kaltura, so we can improve the quality, performance, and security of the platform accordingly. To review what information is being collected, please read: http://www.kaltura.org/kaltura-qa-tracking/ .
  By allowing Kaltura to collect data about your installation, we may be able provide more effective assistance in the event that you encounter an installation issue.
  To allow Kaltura to track and analyze QA and support information, please enter your email. Type NO to disallow:’
  +++ POST_CONSENT=‘Thank you for helping making Kaltura better! To review what information is being collected, please read: http://www.kaltura.org/kaltura-qa-tracking/ .’
  ++ CONSENT_FILE=/opt/kaltura/bin/contact.rc
  ++ APACHE_DAEMON=httpd
  ++ MYSQL_DAEMON=mysqld
  ++ SPHINX_DAEMON=kaltura-sphinx
  ++ BATCH_DAEMON=kaltura-batch
  ++ MEMCACHE_DAEMON=memcached
  ++ MONIT_DAEMON=kaltura-monit
  ++ ALL_DAEMONS=‘httpd kaltura-sphinx kaltura-batch kaltura-monit memcached’
  ++ POST_INST_MAIL_SUBJECT=‘Your new Kaltura server is up! and 6 Quick Tips For Smooth Kaltura Maintenance’
  ++ POST_INST_MAIL_TMPL=/opt/kaltura/app/configurations/post_inst_mail
  ++ ANALYTICS_SERVER_URI=http://installytics.kaltura.org/report
  ++ NEWSLETTER_URL=https://agentcontribs.kaltura.org/newsletter_subscribe.php
  ++ NEWSLETTER_MSG=‘
  To keep up with the bi-weekly Kaltura releases, and stay up to date with
  the latest news, security and bug updates, and connect with the global
  Kaltura community - sign up for our regular Kaltura Community updates.
  Please enter your email to sign up, or enter NO to pass.
  ’
• RC_FILE=/etc/kaltura.d/system.ini
• ‘[’ ‘!’ -r /etc/kaltura.d/system.ini ‘]’
• . /etc/kaltura.d/system.ini
  ++ WEB_DIR=/opt/kaltura/web
  ++ LOG_DIR=/opt/kaltura/log
  ++ APP_DIR=/opt/kaltura/app
  ++ BASE_DIR=/opt/kaltura
  ++ PHP_BIN=/usr/bin/php
  ++ OS_KALTURA_USER=kaltura
  ++ MAILTO=
  ++ ADMIN_CONSOLE_ADMIN_MAIL=
  ++ DB1_HOST=127.0.0.1
  ++ DB1_NAME=kaltura
  ++ DB1_USER=kaltura
  ++ DB1_PASS=gSwaHCyZoO9nwP5
  ++ DWH_HOST=127.0.0.1
  ++ DWH_PORT=3306
  ++ DWH_USER=etl
  ++ DWH_PASS=gSwaHCyZoO9nwP5
  ++ SERVICE_URL=http://backend1.flomina.com:80
  ++ SPHINX_HOST=127.0.0.1
  ++ DB1_PORT=3306
  ++ SUPER_USER=root
  ++ SUPER_USER_PASSWD=****
  ++ KALTURA_VIRTUAL_HOST_NAME=backend1.flomina.com
  ++ RED5_HOST=backend1.flomina.com
• ‘[’ -r /opt/kaltura/app/configurations/sphinx_schema_update ‘]’

[jess]

Hello Jean,

Please first run:
# touch $APP_DIR/configurations/sphinx_schema_update
The /opt/kaltura/bin/kaltura-sphinx-schema-update.sh checks for this file before starting because it should only happen post upgrade. Since you already run it once, the actions were skipped.

Thanks,

[jeansalim83]

[root@backend1 /]# touch $APP_DIR/configurations/sphinx_schema_update
[root@backend1 /]# bash -x /opt/kaltura/bin/kaltura-sphinx-schema-update.sh
++ dirname /opt/kaltura/bin/kaltura-sphinx-schema-update.sh

• KALTURA_FUNCTIONS_RC=/opt/kaltura/bin/kaltura-functions.rc
• ‘[’ ‘!’ -r /opt/kaltura/bin/kaltura-functions.rc ‘]’
• . /opt/kaltura/bin/kaltura-functions.rc
  ++ RC_FILE=/etc/kaltura.d/system.ini
  ++ ‘[’ -r /etc/kaltura.d/system.ini ‘]’
  ++ . /etc/kaltura.d/system.ini
  +++ WEB_DIR=/opt/kaltura/web
  +++ LOG_DIR=/opt/kaltura/log
  +++ APP_DIR=/opt/kaltura/app
  +++ BASE_DIR=/opt/kaltura
  +++ PHP_BIN=/usr/bin/php
  +++ OS_KALTURA_USER=kaltura
  +++ MAILTO=
  +++ ADMIN_CONSOLE_ADMIN_MAIL=
  +++ DB1_HOST=127.0.0.1
  +++ DB1_NAME=kaltura
  +++ DB1_USER=kaltura
  +++ DB1_PASS=gSwaHCyZoO9nwP5
  +++ DWH_HOST=127.0.0.1
  +++ DWH_PORT=3306
  +++ DWH_USER=etl
  +++ DWH_PASS=gSwaHCyZoO9nwP5
  +++ SERVICE_URL=http://backend1.flomina.com:80
  +++ SPHINX_HOST=127.0.0.1
  +++ DB1_PORT=3306
  +++ SUPER_USER=root
  +++ SUPER_USER_PASSWD=
  +++ KALTURA_VIRTUAL_HOST_NAME=backend1.flomina.com
  +++ RED5_HOST=backend1.flomina.com
  +++ dirname /opt/kaltura/bin/kaltura-sphinx-schema-update.sh
  ++ COLORS_RC=/opt/kaltura/bin/colors.sh
  ++ ‘[’ -r /opt/kaltura/bin/colors.sh ‘]’
  ++ . /opt/kaltura/bin/colors.sh
  +++ DULL=0
  +++ BRIGHT=1
  +++ FG_BLACK=30
  +++ FG_RED=31
  +++ FG_GREEN=32
  +++ FG_YELLOW=33
  +++ FG_BLUE=34
  +++ FG_VIOLET=35
  +++ FG_CYAN=36
  +++ FG_WHITE=37
  +++ FG_NULL=00
  +++ BG_BLACK=40
  +++ BG_RED=41
  +++ BG_GREEN=42
  +++ BG_YELLOW=43
  +++ BG_BLUE=44
  +++ BG_VIOLET=45
  +++ BG_CYAN=46
  +++ BG_WHITE=47
  +++ BG_NULL=00
  +++ ETCOLOR_ERROR=’\033[1;31m’
  +++ ESC=’\033’
  +++ NORMAL=’\033[m’
  +++ RESET=’\033[0;37;00m’
  +++ BLACK=’\033[0;30m’
  +++ RED=’\033[0;31m’
  +++ GREEN=’\033[0;32m’
  +++ YELLOW=’\033[0;33m’
  +++ BLUE=’\033[0;34m’
  +++ VIOLET=’\033[0;35m’
  +++ CYAN=’\033[0;36m’
  +++ WHITE=’\033[0;37m’
  +++ BRIGHT_BLACK=’\033[1;30m’
  +++ BRIGHT_RED=’\033[1;31m’
  +++ BRIGHT_GREEN=’\033[1;32m’
  +++ BRIGHT_YELLOW=’\033[1;33m’
  +++ BRIGHT_BLUE=’\033[1;34m’
  +++ BRIGHT_VIOLET=’\033[1;35m’
  +++ BRIGHT_CYAN=’\033[1;36m’
  +++ BRIGHT_WHITE=’\033[1;37m’
  +++ REV_CYAN=’\033[0;47;46m’
  +++ REV_RED=’\033[0;33; 41m’
  +++ JESS=‘Jess likes this one :)’
  ++ ‘[’ -r /etc/sysconfig/clock ‘]’
  ++ . /etc/sysconfig/clock
  +++ ZONE=Asia/Beirut
  ++ ‘[’ -r /opt/kaltura/app/configurations/consent_msgs ‘]’
  ++ . /opt/kaltura/app/configurations/consent_msgs
  +++ PRE_CONSENT=‘To improve your Kaltura experience and provide you with the best service, Kaltura would like your consent to collect necessary data and information regarding your installation and use of Kaltura and analyze it to provide an upgraded and more stable platform and services.
  This information helps us understand what problems users encounter when using Kaltura, so we can improve the quality, performance, and security of the platform accordingly. To review what information is being collected, please read: http://www.kaltura.org/kaltura-qa-tracking/ .
  By allowing Kaltura to collect data about your installation, we may be able provide more effective assistance in the event that you encounter an installation issue.
  To allow Kaltura to track and analyze QA and support information, please enter your email. Type NO to disallow:’
  +++ POST_CONSENT=‘Thank you for helping making Kaltura better! To review what information is being collected, please read: http://www.kaltura.org/kaltura-qa-tracking/ .’
  ++ CONSENT_FILE=/opt/kaltura/bin/contact.rc
  ++ APACHE_DAEMON=httpd
  ++ MYSQL_DAEMON=mysqld
  ++ SPHINX_DAEMON=kaltura-sphinx
  ++ BATCH_DAEMON=kaltura-batch
  ++ MEMCACHE_DAEMON=memcached
  ++ MONIT_DAEMON=kaltura-monit
  ++ ALL_DAEMONS=‘httpd kaltura-sphinx kaltura-batch kaltura-monit memcached’
  ++ POST_INST_MAIL_SUBJECT=‘Your new Kaltura server is up! and 6 Quick Tips For Smooth Kaltura Maintenance’
  ++ POST_INST_MAIL_TMPL=/opt/kaltura/app/configurations/post_inst_mail
  ++ ANALYTICS_SERVER_URI=http://installytics.kaltura.org/report
  ++ NEWSLETTER_URL=https://agentcontribs.kaltura.org/newsletter_subscribe.php
  ++ NEWSLETTER_MSG=‘
  To keep up with the bi-weekly Kaltura releases, and stay up to date with
  the latest news, security and bug updates, and connect with the global
  Kaltura community - sign up for our regular Kaltura Community updates.
  Please enter your email to sign up, or enter NO to pass.
  ’
• RC_FILE=/etc/kaltura.d/system.ini
• ‘[’ ‘!’ -r /etc/kaltura.d/system.ini ‘]’
• . /etc/kaltura.d/system.ini
  ++ WEB_DIR=/opt/kaltura/web
  ++ LOG_DIR=/opt/kaltura/log
  ++ APP_DIR=/opt/kaltura/app
  ++ BASE_DIR=/opt/kaltura
  ++ PHP_BIN=/usr/bin/php
  ++ OS_KALTURA_USER=kaltura
  ++ MAILTO=
  ++ ADMIN_CONSOLE_ADMIN_MAIL=
  ++ DB1_HOST=127.0.0.1
  ++ DB1_NAME=kaltura
  ++ DB1_USER=kaltura
  ++ DB1_PASS=gSwaHCyZoO9nwP5
  ++ DWH_HOST=127.0.0.1
  ++ DWH_PORT=3306
  ++ DWH_USER=etl
  ++ DWH_PASS=gSwaHCyZoO9nwP5
  ++ SERVICE_URL=http://backend1.flomina.com:80
  ++ SPHINX_HOST=127.0.0.1
  ++ DB1_PORT=3306
  ++ SUPER_USER=root
  ++ SUPER_USER_PASSWD=
  ++ KALTURA_VIRTUAL_HOST_NAME=backend1.flomina.com
  ++ RED5_HOST=backend1.flomina.com
• ‘[’ -r /opt/kaltura/app/configurations/sphinx_schema_update ‘]’
• /etc/init.d/kaltura-sphinx status
  searchd (pid 22213 22212) is running…
• rm /opt/kaltura/app/configurations/monit/monit.d/enabled.sphinx.rc
• /etc/init.d/kaltura-sphinx stop
  Stopping searchd: Sphinx 2.2.1-id64-dev (r4097)
  Copyright © 2001-2013, Andrew Aksyonoff
  Copyright © 2008-2013, Sphinx Technologies Inc (http://sphinxsearch.com)

using config file ‘/opt/kaltura/app/configurations/sphinx/kaltura.conf’…
stop: successfully sent SIGTERM to pid 22213

++ date +%s

• STMP=1419247999
• mkdir -p /opt/kaltura/sphinx.bck.1419247999
• echo 'Backing up files to /opt/kaltura/sphinx.bck.1419247999. Once the upgrade is done and tested, please remove this directory to save space’
  Backing up files to /opt/kaltura/sphinx.bck.1419247999. Once the upgrade is done and tested, please remove this directory to save space
• mv /opt/kaltura/sphinx/kaltura_caption_item_rt.kill /opt/kaltura/sphinx/kaltura_caption_item_rt.lock /opt/kaltura/sphinx/kaltura_caption_item_rt.meta /opt/kaltura/sphinx/kaltura_caption_item_rt.ram /opt/kaltura/sphinx/kaltura_category_kuser_rt.kill /opt/kaltura/sphinx/kaltura_category_kuser_rt.lock /opt/kaltura/sphinx/kaltura_category_kuser_rt.meta /opt/kaltura/sphinx/kaltura_category_kuser_rt.ram /opt/kaltura/sphinx/kaltura_category_rt.kill /opt/kaltura/sphinx/kaltura_category_rt.lock /opt/kaltura/sphinx/kaltura_category_rt.meta /opt/kaltura/sphinx/kaltura_category_rt.ram /opt/kaltura/sphinx/kaltura_cue_point_rt.kill /opt/kaltura/sphinx/kaltura_cue_point_rt.lock /opt/kaltura/sphinx/kaltura_cue_point_rt.meta /opt/kaltura/sphinx/kaltura_cue_point_rt.ram /opt/kaltura/sphinx/kaltura_distribution_rt.kill /opt/kaltura/sphinx/kaltura_distribution_rt.lock /opt/kaltura/sphinx/kaltura_distribution_rt.meta /opt/kaltura/sphinx/kaltura_distribution_rt.ram /opt/kaltura/sphinx/kaltura_kuser_rt.kill /opt/kaltura/sphinx/kaltura_kuser_rt.lock /opt/kaltura/sphinx/kaltura_kuser_rt.meta /opt/kaltura/sphinx/kaltura_kuser_rt.ram /opt/kaltura/sphinx/kaltura_rt.kill /opt/kaltura/sphinx/kaltura_rt.lock /opt/kaltura/sphinx/kaltura_rt.meta /opt/kaltura/sphinx/kaltura_rt.ram /opt/kaltura/sphinx/kaltura_tag_rt.kill /opt/kaltura/sphinx/kaltura_tag_rt.lock /opt/kaltura/sphinx/kaltura_tag_rt.meta /opt/kaltura/sphinx/kaltura_tag_rt.ram ‘/opt/kaltura/log/sphinx/data/binlog.’ /opt/kaltura/sphinx.bck.1419247999
  mv: cannot stat `/opt/kaltura/log/sphinx/data/binlog.’: No such file or directory
• /etc/init.d/kaltura-sphinx start
• ln -sf /opt/kaltura/app/configurations/monit/monit.avail/sphinx.rc /opt/kaltura/app/configurations/monit/monit.d/enabled.sphinx.rc
• php /opt/kaltura/app/deployment/base/scripts/populateSphinxEntries.php
  PHP Notice: Undefined offset: 0 in /opt/kaltura/app/alpha/apps/kaltura/lib/db/DbManager.php on line 259
  PHP Notice: Undefined offset: 0 in /opt/kaltura/app/alpha/apps/kaltura/lib/db/DbManager.php on line 259
  2014-12-22 13:33:23 [global] ERR: exception ‘Exception’ with message ‘Failed to connect to any Sphinx config’ in /opt/kaltura/app/infra/log/KalturaLog.php:82
  Stack trace:
  #0 /opt/kaltura/app/deployment/base/scripts/populateSphinxEntries.php(36): KalturaLog::err(‘Failed to conne…’)
  #1 {main}
• RC=0
• ‘[’ 0 -ne 0 ‘]’
• rm /opt/kaltura/app/configurations/sphinx_schema_update

[jess]

OK, so I see:

• /etc/init.d/kaltura-sphinx start

But it seems to be failing.
Can you please add:
bash -x /etc/init.d/kaltura-sphinx start
In the script so we can better understand why sphinx fails to start?
Also look at /opt/kaltura/log/sphinx/kaltura_sphinx_searchd.log for errors please?

Thanks,

[jeansalim83]

That’s the results:
[root@backend1 /]# bash -x /opt/kaltura/bin/kaltura-sphinx-schema-update.sh
++ dirname /opt/kaltura/bin/kaltura-sphinx-schema-update.sh

• KALTURA_FUNCTIONS_RC=/opt/kaltura/bin/kaltura-functions.rc
• ‘[’ ‘!’ -r /opt/kaltura/bin/kaltura-functions.rc ‘]’
• . /opt/kaltura/bin/kaltura-functions.rc
  ++ RC_FILE=/etc/kaltura.d/system.ini
  ++ ‘[’ -r /etc/kaltura.d/system.ini ‘]’
  ++ . /etc/kaltura.d/system.ini
  +++ WEB_DIR=/opt/kaltura/web
  +++ LOG_DIR=/opt/kaltura/log
  +++ APP_DIR=/opt/kaltura/app
  +++ BASE_DIR=/opt/kaltura
  +++ PHP_BIN=/usr/bin/php
  +++ OS_KALTURA_USER=kaltura
  +++ MAILTO=jeansalim@hotmail.com
  +++ ADMIN_CONSOLE_ADMIN_MAIL=jeansalim@hotmail.com
  +++ DB1_HOST=127.0.0.1
  +++ DB1_NAME=kaltura
  +++ DB1_USER=kaltura
  +++ DB1_PASS=gSwaHCyZoO9nwP5
  +++ DWH_HOST=127.0.0.1
  +++ DWH_PORT=3306
  +++ DWH_USER=etl
  +++ DWH_PASS=gSwaHCyZoO9nwP5
  +++ SERVICE_URL=http://backend1.flomina.com:80
  +++ SPHINX_HOST=127.0.0.1
  +++ DB1_PORT=3306
  +++ SUPER_USER=root
  +++ SUPER_USER_PASSWD=
  +++ KALTURA_VIRTUAL_HOST_NAME=backend1.flomina.com
  +++ RED5_HOST=backend1.flomina.com
  +++ dirname /opt/kaltura/bin/kaltura-sphinx-schema-update.sh
  ++ COLORS_RC=/opt/kaltura/bin/colors.sh
  ++ ‘[’ -r /opt/kaltura/bin/colors.sh ‘]’
  ++ . /opt/kaltura/bin/colors.sh
  +++ DULL=0
  +++ BRIGHT=1
  +++ FG_BLACK=30
  +++ FG_RED=31
  +++ FG_GREEN=32
  +++ FG_YELLOW=33
  +++ FG_BLUE=34
  +++ FG_VIOLET=35
  +++ FG_CYAN=36
  +++ FG_WHITE=37
  +++ FG_NULL=00
  +++ BG_BLACK=40
  +++ BG_RED=41
  +++ BG_GREEN=42
  +++ BG_YELLOW=43
  +++ BG_BLUE=44
  +++ BG_VIOLET=45
  +++ BG_CYAN=46
  +++ BG_WHITE=47
  +++ BG_NULL=00
  +++ ETCOLOR_ERROR=’\033[1;31m’
  +++ ESC=’\033’
  +++ NORMAL=’\033[m’
  +++ RESET=’\033[0;37;00m’
  +++ BLACK=’\033[0;30m’
  +++ RED=’\033[0;31m’
  +++ GREEN=’\033[0;32m’
  +++ YELLOW=’\033[0;33m’
  +++ BLUE=’\033[0;34m’
  +++ VIOLET=’\033[0;35m’
  +++ CYAN=’\033[0;36m’
  +++ WHITE=’\033[0;37m’
  +++ BRIGHT_BLACK=’\033[1;30m’
  +++ BRIGHT_RED=’\033[1;31m’
  +++ BRIGHT_GREEN=’\033[1;32m’
  +++ BRIGHT_YELLOW=’\033[1;33m’
  +++ BRIGHT_BLUE=’\033[1;34m’
  +++ BRIGHT_VIOLET=’\033[1;35m’
  +++ BRIGHT_CYAN=’\033[1;36m’
  +++ BRIGHT_WHITE=’\033[1;37m’
  +++ REV_CYAN=’\033[0;47;46m’
  +++ REV_RED=’\033[0;33; 41m’
  +++ JESS=‘Jess likes this one :)’
  ++ ‘[’ -r /etc/sysconfig/clock ‘]’
  ++ . /etc/sysconfig/clock
  +++ ZONE=Asia/Beirut
  ++ ‘[’ -r /opt/kaltura/app/configurations/consent_msgs ‘]’
  ++ . /opt/kaltura/app/configurations/consent_msgs
  +++ PRE_CONSENT=‘To improve your Kaltura experience and provide you with the best service, Kaltura would like your consent to collect necessary data and information regarding your installation and use of Kaltura and analyze it to provide an upgraded and more stable platform and services.
  This information helps us understand what problems users encounter when using Kaltura, so we can improve the quality, performance, and security of the platform accordingly. To review what information is being collected, please read: http://www.kaltura.org/kaltura-qa-tracking/ .
  By allowing Kaltura to collect data about your installation, we may be able provide more effective assistance in the event that you encounter an installation issue.
  To allow Kaltura to track and analyze QA and support information, please enter your email. Type NO to disallow:’
  +++ POST_CONSENT=‘Thank you for helping making Kaltura better! To review what information is being collected, please read: http://www.kaltura.org/kaltura-qa-tracking/ .’
  ++ CONSENT_FILE=/opt/kaltura/bin/contact.rc
  ++ APACHE_DAEMON=httpd
  ++ MYSQL_DAEMON=mysqld
  ++ SPHINX_DAEMON=kaltura-sphinx
  ++ BATCH_DAEMON=kaltura-batch
  ++ MEMCACHE_DAEMON=memcached
  ++ MONIT_DAEMON=kaltura-monit
  ++ ALL_DAEMONS=‘httpd kaltura-sphinx kaltura-batch kaltura-monit memcached’
  ++ POST_INST_MAIL_SUBJECT=‘Your new Kaltura server is up! and 6 Quick Tips For Smooth Kaltura Maintenance’
  ++ POST_INST_MAIL_TMPL=/opt/kaltura/app/configurations/post_inst_mail
  ++ ANALYTICS_SERVER_URI=http://installytics.kaltura.org/report
  ++ NEWSLETTER_URL=https://agentcontribs.kaltura.org/newsletter_subscribe.php
  ++ NEWSLETTER_MSG=‘
  To keep up with the bi-weekly Kaltura releases, and stay up to date with
  the latest news, security and bug updates, and connect with the global
  Kaltura community - sign up for our regular Kaltura Community updates.
  Please enter your email to sign up, or enter NO to pass.
  ’
• RC_FILE=/etc/kaltura.d/system.ini
• ‘[’ ‘!’ -r /etc/kaltura.d/system.ini ‘]’
• . /etc/kaltura.d/system.ini
  ++ WEB_DIR=/opt/kaltura/web
  ++ LOG_DIR=/opt/kaltura/log
  ++ APP_DIR=/opt/kaltura/app
  ++ BASE_DIR=/opt/kaltura
  ++ PHP_BIN=/usr/bin/php
  ++ OS_KALTURA_USER=kaltura
  ++ MAILTO=jeansalim@hotmail.com
  ++ ADMIN_CONSOLE_ADMIN_MAIL=jeansalim@hotmail.com
  ++ DB1_HOST=127.0.0.1
  ++ DB1_NAME=kaltura
  ++ DB1_USER=kaltura
  ++ DB1_PASS=gSwaHCyZoO9nwP5
  ++ DWH_HOST=127.0.0.1
  ++ DWH_PORT=3306
  ++ DWH_USER=etl
  ++ DWH_PASS=gSwaHCyZoO9nwP5
  ++ SERVICE_URL=http://backend1.flomina.com:80
  ++ SPHINX_HOST=127.0.0.1
  ++ DB1_PORT=3306
  ++ SUPER_USER=root
  ++ SUPER_USER_PASSWD=
  ++ KALTURA_VIRTUAL_HOST_NAME=backend1.flomina.com
  ++ RED5_HOST=backend1.flomina.com
• ‘[’ -r /opt/kaltura/app/configurations/sphinx_schema_update ‘]’
• /etc/init.d/kaltura-sphinx status
  searchd (pid 14891 14890) is running…
• rm /opt/kaltura/app/configurations/monit/monit.d/enabled.sphinx.rc
• /etc/init.d/kaltura-sphinx stop
  Stopping searchd: Sphinx 2.2.1-id64-dev (r4097)
  Copyright © 2001-2013, Andrew Aksyonoff
  Copyright © 2008-2013, Sphinx Technologies Inc (http://sphinxsearch.com)

using config file ‘/opt/kaltura/app/configurations/sphinx/kaltura.conf’…
stop: successfully sent SIGTERM to pid 14891

++ date +%s

• STMP=1419265192
• mkdir -p /opt/kaltura/sphinx.bck.1419265192
• echo 'Backing up files to /opt/kaltura/sphinx.bck.1419265192. Once the upgrade is done and tested, please remove this directory to save space’
  Backing up files to /opt/kaltura/sphinx.bck.1419265192. Once the upgrade is done and tested, please remove this directory to save space
• mv /opt/kaltura/sphinx/kaltura_caption_item_rt.kill /opt/kaltura/sphinx/kaltura_caption_item_rt.lock /opt/kaltura/sphinx/kaltura_caption_item_rt.meta /opt/kaltura/sphinx/kaltura_caption_item_rt.ram /opt/kaltura/sphinx/kaltura_category_kuser_rt.kill /opt/kaltura/sphinx/kaltura_category_kuser_rt.lock /opt/kaltura/sphinx/kaltura_category_kuser_rt.meta /opt/kaltura/sphinx/kaltura_category_kuser_rt.ram /opt/kaltura/sphinx/kaltura_category_rt.kill /opt/kaltura/sphinx/kaltura_category_rt.lock /opt/kaltura/sphinx/kaltura_category_rt.meta /opt/kaltura/sphinx/kaltura_category_rt.ram /opt/kaltura/sphinx/kaltura_cue_point_rt.kill /opt/kaltura/sphinx/kaltura_cue_point_rt.lock /opt/kaltura/sphinx/kaltura_cue_point_rt.meta /opt/kaltura/sphinx/kaltura_cue_point_rt.ram /opt/kaltura/sphinx/kaltura_distribution_rt.kill /opt/kaltura/sphinx/kaltura_distribution_rt.lock /opt/kaltura/sphinx/kaltura_distribution_rt.meta /opt/kaltura/sphinx/kaltura_distribution_rt.ram /opt/kaltura/sphinx/kaltura_kuser_rt.kill /opt/kaltura/sphinx/kaltura_kuser_rt.lock /opt/kaltura/sphinx/kaltura_kuser_rt.meta /opt/kaltura/sphinx/kaltura_kuser_rt.ram /opt/kaltura/sphinx/kaltura_rt.kill /opt/kaltura/sphinx/kaltura_rt.lock /opt/kaltura/sphinx/kaltura_rt.meta /opt/kaltura/sphinx/kaltura_rt.ram /opt/kaltura/sphinx/kaltura_tag_rt.kill /opt/kaltura/sphinx/kaltura_tag_rt.lock /opt/kaltura/sphinx/kaltura_tag_rt.meta /opt/kaltura/sphinx/kaltura_tag_rt.ram /opt/kaltura/log/sphinx/data/binlog.meta /opt/kaltura/sphinx.bck.1419265192
• bash -x /etc/init.d/kaltura-sphinx start
• . /etc/kaltura.d/system.ini
  ++ WEB_DIR=/opt/kaltura/web
  ++ LOG_DIR=/opt/kaltura/log
  ++ APP_DIR=/opt/kaltura/app
  ++ BASE_DIR=/opt/kaltura
  ++ PHP_BIN=/usr/bin/php
  ++ OS_KALTURA_USER=kaltura
  ++ MAILTO=jeansalim@hotmail.com
  ++ ADMIN_CONSOLE_ADMIN_MAIL=jeansalim@hotmail.com
  ++ DB1_HOST=127.0.0.1
  ++ DB1_NAME=kaltura
  ++ DB1_USER=kaltura
  ++ DB1_PASS=gSwaHCyZoO9nwP5
  ++ DWH_HOST=127.0.0.1
  ++ DWH_PORT=3306
  ++ DWH_USER=etl
  ++ DWH_PASS=gSwaHCyZoO9nwP5
  ++ SERVICE_URL=http://backend1.flomina.com:80
  ++ SPHINX_HOST=127.0.0.1
  ++ DB1_PORT=3306
  ++ SUPER_USER=root
  ++ SUPER_USER_PASSWD=
  ++ KALTURA_VIRTUAL_HOST_NAME=backend1.flomina.com
  ++ RED5_HOST=backend1.flomina.com
• . /opt/kaltura/app/infra/scripts/functions.rc
  ++ TEXTDOMAIN=initscripts
  ++ umask 022
  ++ PATH=/sbin:/usr/sbin:/bin:/usr/bin
  ++ export PATH
  ++ ‘[’ -z ‘’ ‘]’
  ++ COLUMNS=80
  ++ CONSOLETYPE=pty
  ++ ‘[’ -z pty ‘]’
  ++ ‘[’ -f /etc/sysconfig/i18n -a -z ‘’ -a -z ‘’ ‘]’
  ++ . /etc/profile.d/lang.sh
  ++ unset LANGSH_SOURCED
  ++ ‘[’ -z ‘’ ‘]’
  ++ ‘[’ -f /etc/sysconfig/init ‘]’
  ++ . /etc/sysconfig/init
  +++ BOOTUP=color
  +++ RES_COL=60
  +++ MOVE_TO_COL=‘echo -en \033[60G’
  +++ SETCOLOR_SUCCESS=‘echo -en \033[0;32m’
  +++ SETCOLOR_FAILURE=‘echo -en \033[0;31m’
  +++ SETCOLOR_WARNING=‘echo -en \033[0;33m’
  +++ SETCOLOR_NORMAL=‘echo -en \033[0;39m’
  +++ PROMPT=yes
  +++ AUTOSWAP=no
  +++ ACTIVE_CONSOLES=’/dev/tty[1-6]’
  +++ SINGLE=/sbin/sushell
  ++ ‘[’ pty = serial ‘]’
  ++ __sed_discard_ignored_files=’/(~|.bak|.orig|.rpmnew|.rpmorig|.rpmsave)$/d’
• prog=searchd
• config=/opt/kaltura/app/configurations/sphinx/kaltura.conf
• exec=/opt/kaltura/sphinx/bin/searchd
• pid_file=/opt/kaltura/sphinx/searchd.pid
• case “$1” in
• rh_status_q
• rh_status
• start
• ‘[’ -x /opt/kaltura/sphinx/bin/searchd ‘]’
• ‘[’ -f /opt/kaltura/app/configurations/sphinx/kaltura.conf ‘]’
• echo -n 'Starting searchd: '
  Starting searchd: + su kaltura -c '/opt/kaltura/sphinx/bin/searchd --config /opt/kaltura/app/configurations/sphinx/kaltura.conf’
  Sphinx 2.2.1-id64-dev (r4097)
  Copyright © 2001-2013, Andrew Aksyonoff
  Copyright © 2008-2013, Sphinx Technologies Inc (http://sphinxsearch.com)

using config file ‘/opt/kaltura/app/configurations/sphinx/kaltura.conf’…
listening on all interfaces, port=9312
WARNING: index ‘kaltura_base’: no fields configured (use rt_field directive) - NOT SERVING
WARNING: index ‘kaltura_kuser_base’: no fields configured (use rt_field directive) - NOT SERVING
precaching index 'kaltura_entry’
precaching index 'kaltura_category’
precaching index 'kaltura_kuser’
precaching index 'kaltura_category_kuser’
precaching index 'kaltura_cue_point’
precaching index 'kaltura_entry_distribution’
precaching index 'kaltura_caption_item’
precaching index 'kaltura_tag’
precached 8 indexes in 0.018 sec

• retval=0

• echo

• return 0

• exit 0

• ln -sf /opt/kaltura/app/configurations/monit/monit.avail/sphinx.rc /opt/kaltura/app/configurations/monit/monit.d/enabled.sphinx.rc

• php /opt/kaltura/app/deployment/base/scripts/populateSphinxEntries.php

• RC=0

• ‘[’ 0 -ne 0 ‘]’

• rm /opt/kaltura/app/configurations/sphinx_schema_update

[jeansalim83]

And that’s the sphinx log:

[Mon Dec 22 18:19:52.003 2014] [14891] caught SIGTERM, shutting down
[Mon Dec 22 18:19:52.062 2014] [14891] rt: index kaltura_entry: ramchunk saved in 0.007 sec
[Mon Dec 22 18:19:52.193 2014] [14891] rt: index kaltura_kuser: ramchunk saved in 0.124 sec
[Mon Dec 22 18:19:52.212 2014] [14891] shutdown complete
[Mon Dec 22 18:19:52.213 2014] [14890] Child process 14891 has been finished, exit code 0. Watchdog finishes also. Good bye!
[Mon Dec 22 18:19:52.613 2014] [14317] Child process 14318 has been forked
[Mon Dec 22 18:19:52.613 2014] [14318] listening on all interfaces, port=9312
[Mon Dec 22 18:19:52.620 2014] [14318] WARNING: index ‘kaltura_base’: no fields configured (use rt_field directive) - NOT SERVING
[Mon Dec 22 18:19:52.620 2014] [14318] WARNING: index ‘kaltura_kuser_base’: no fields configured (use rt_field directive) - NOT SERVING
[Mon Dec 22 18:19:52.652 2014] [14318] accepting connections

[jess]

So this output looks like everything succeeded… Does that mean the issue does not happen anymore? i.e the exception does not occur? Thanks,

[jeansalim83]

Well the issue was still there.
I had to reindex sphinx for it to work.