Mwembed v2.23 update broken

When I updated to v2.23, the player and studio stopped working.
That is the error I’m getting:

==> /opt/kaltura/log/kaltura_apache_errors.log <==
[Mon Dec 15 07:45:54 2014] [error] [client 10.100.22.0] script ‘/opt/kaltura/web/html5/html5lib/v2.22/mwEmbedLoader.php’ not found or unable to stat, referer: http://backend1.flomina.com/apps/studio/v1.9.1/index.html

Jean.

Hi Jean,

How did you do the update? if you created a whole new player folder called v2.23 then you have to change the “html5_version” in base.ini (/opt/kaltura/app/configurations/base.ini)

Try change that, restart httpd and clear cache and test again.

I updated using the RPM update procedure for centos.

I changes base.ini html5_version to v2.23, removed the cache and restarted httpd.
Still have the same error:
==> /opt/kaltura/log/kaltura_apache_errors.log <==
[Mon Dec 15 12:42:49 2014] [error] [client 10.100.101.1] script ‘/opt/kaltura/web/html5/html5lib/v2.22/mwEmbedLoader.php’ not found or unable to stat, referer: http://backend1.flomina.com/apps/studio/v1.9.1/index.html

There’s something still linking to v2.22 instead of udpated v2.23

Did you run the post config scripts after updating the RPM?

I ran it now and it worked. Thanks a lot.

but analytics got broken after the configuration:

Here’s the kaltlog:
2014-12-15 14:50:18 [0.000256] [194.126.12.92] [765353749] [API] [myReportsMgr::executeQuery] NOTICE: Reports query using database host: [127.0.0.1] user [etl]
2014-12-15 14:50:18 [0.000285] [194.126.12.92] [765353749] [API] [myReportsMgr::executeQuery] ERR: exception ‘Exception’ with message ‘Invalid query: PROCEDURE kalturadw.calc_partner_usage_data does not exist’ in /opt/kaltura/app/infra/log/KalturaLog.php:82
Stack trace:
#0 /opt/kaltura/app/alpha/apps/kaltura/lib/reports/myReportsMgr.class.php(1298): KalturaLog::err(‘Invalid query: …’)

#11 {main}
2014-12-15 14:50:18 [0.000317] [194.126.12.92] [765353749] [API] [kCoreException->__construct] ERR: exception ‘kCoreException’ with message ‘Invalid query’ in /opt/kaltura/app/alpha/apps/kaltura/lib/reports/myReportsMgr.class.php:1300
Stack trace:
#0 /opt/kaltura/app/alpha/apps/kaltura/lib/reports/myReportsMgr.class.php(856): myReportsMgr::executeQuery(’?CALL kalturadw…’)

2014-12-15 14:50:18 [0.000109] [194.126.12.92] [765353749] [API] [myReportsMgr::executeQueryByType] NOTICE: Invalid query
2014-12-15 14:50:18 [0.000233] [194.126.12.92] [765353749] [API] [KalturaFrontController->getExceptionObject] CRIT: exception ‘kCoreException’ with message ‘Invalid query’ in /opt/kaltura/app/alpha/apps/kaltura/lib/reports/myReportsMgr.class.php:1300
Stack trace:
#0 /opt/kaltura/app/alpha/apps/kaltura/lib/reports/myReportsMgr.class.php(856): myReportsMgr::executeQuery(’?CALL kalturadw…’)
^C

DWH setup output:
[root@backend1 setup]# ./dwh_setup.sh
1
Error - bailing out!
[root@backend1 setup]# tail installation_log.log
1
Error - bailing out!
now executing /opt/kaltura/dwh/ddl//db_create.sql
ERROR 1045 (28000): Access denied for user ‘etl’@‘localhost’ (using password: NO)
1

dwh daily log:
ERROR 15-12 04:59:05,912 - Execute SQL script - Unexpected error
ERROR 15-12 04:59:05,912 - Execute SQL script - org.pentaho.di.core.exception.KettleStepException:
ERROR 15-12 04:59:05,913 - calc_storage_usage - Errors detected!
ERROR 15-12 04:59:05,914 - calc_storage_usage - Errors detected!
ERROR 15-12 04:59:06,006 - Abort job 1 - Aborting job.

I checked mysql kalturadw* databases, they check fine. I also checked etl user permissions for those tables and they are fine.

Hello,

Your problem is a missing stored procedure - kalturadw.calc_partner_usage_data.
I am not sure how this happened to you since when a DB exists, it does not get deleted or updated when running kaltura-config-all.sh since it check whether or not the DB exists and skips if so.

You can, AFTER creating backups of the entire DB just in case, drop all the DWH DBs using:
PASSWD=YOURPASSWD
for i in mysql -N -p$PASSWD kalturadw_bisources -e "show tables";do mysql -p$PASSWD kalturadw_bisources -e “drop table $i”;done
for i in mysql -N -p$PASSWD kalturadw -e "show tables";do mysql -p$PASSWD kalturadw -e “drop table $i”;done
for i in mysql -N -p$PASSWD kalturadw_ds -e "show tables";do mysql -p$PASSWD kalturadw_ds -e “drop table $i”;done
for i in mysql -N -p$PASSWD kalturalog -e "show tables";do mysql -p$PASSWD kalturalog -e “drop table $i”;done
for i in mysql -p$PASSWD -e "Show procedure status" |grep kalturadw|awk -F " " '{print $2}';do mysql kalturadw -p$PASSWD -e “drop procedure $i;”;done
for i in mysql -p$PASSWD -e "Show procedure status" |grep kalturadw_ds|awk -F " " '{print $2}';do mysql kalturadw_ds -p$PASSWD -e “drop procedure $i;”;done

And then re-running kaltura-dwh-config.sh

You will lose your current stats though, of course.

Worked great. Thanks a lot for the great support Jess.

Surething. Happy to help, Jean.