Nothing in Top Content Analytics

1

Hi Experts,

I’m running on Centos 7.1 with Kaltura 10.16.0

I try to run manually DWH and I’m expecting this error in etl_hourly-20150730-09.log

ERROR 30-07 09:40:56,539 - parse bandwidth lines - Unexpected error
ERROR 30-07 09:40:56,539 - parse bandwidth lines - org.pentaho.di.core.exception.KettleValueException:
Javascript error:
Could not apply the given format dd/MMM/yyyy:HH:mm:ss on the string for 30/Jul/2015:08:36:57 : Format.parseObject(String) failed (script#14)

        at org.pentaho.di.trans.steps.scriptvalues_mod.ScriptValuesMod.addValues(ScriptValuesMod.java:457)
        at org.pentaho.di.trans.steps.scriptvalues_mod.ScriptValuesMod.processRow(ScriptValuesMod.java:688)
        at org.pentaho.di.trans.step.RunThread.run(RunThread.java:40)
        at java.lang.Thread.run(Thread.java:745)
Caused by: org.mozilla.javascript.EvaluatorException: Could not apply the given format dd/MMM/yyyy:HH:mm:ss on the string for 30/Jul/2015:08:36:57 : Format.parseObject(String) failed (script#14)
        at org.mozilla.javascript.DefaultErrorReporter.runtimeError(DefaultErrorReporter.java:109)
        at org.mozilla.javascript.Context.reportRuntimeError(Context.java:938)
        at org.mozilla.javascript.Context.reportRuntimeError(Context.java:994)
        at org.pentaho.di.trans.steps.scriptvalues_mod.ScriptValuesAddedFunctions.str2date(ScriptValuesAddedFunctions.java:909)
        at sun.reflect.GeneratedMethodAccessor4.invoke(Unknown Source)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
        at java.lang.reflect.Method.invoke(Method.java:497)
        at org.mozilla.javascript.MemberBox.invoke(MemberBox.java:161)
        at org.mozilla.javascript.FunctionObject.call(FunctionObject.java:413)
        at org.mozilla.javascript.optimizer.OptRuntime.callName(OptRuntime.java:97)
        at org.mozilla.javascript.gen.c15._c0(script:14)
        at org.mozilla.javascript.gen.c15.call(script)
        at org.mozilla.javascript.ContextFactory.doTopCall(ContextFactory.java:398)
        at org.mozilla.javascript.ScriptRuntime.doTopCall(ScriptRuntime.java:3065)
        at org.mozilla.javascript.gen.c15.call(script)
        at org.mozilla.javascript.gen.c15.exec(script)
        at org.pentaho.di.trans.steps.scriptvalues_mod.ScriptValuesMod.addValues(ScriptValuesMod.java:376)
        ... 3 more

INFO  30-07 09:40:56,560 - Not a bandwidth match - Finished processing (I=0, O=0, R=3244, W=3244, U=0, E=0)
INFO  30-07 09:40:56,562 - Filter BW rows - Finished processing (I=0, O=0, R=3340, W=3340, U=0, E=0)
ERROR 30-07 09:40:56,562 - process file - Errors detected!
ERROR 30-07 09:40:56,569 - process file - Errors detected!
INFO  30-07 09:40:56,571 - parse playManifest line - Finished processing (I=0, O=0, R=2536, W=2536, U=0, E=0)
INFO  30-07 09:40:56,577 - parse bandwidth lines - Finished processing (I=0, O=0, R=1989, W=1988, U=0, E=1)
INFO  30-07 09:40:56,578 - process file - process file
INFO  30-07 09:40:56,578 - process file - process file
INFO  30-07 09:40:56,578 - Append cycle and file to bandwidth - Finished processing (I=0, O=0, R=1, W=0, U=0, E=0)
INFO  30-07 09:40:56,590 - parse bandwidth lines - Finished processing (I=0, O=0, R=1833, W=1832, U=0, E=0)
INFO  30-07 09:40:56,593 - parse playManifest line - Finished processing (I=0, O=0, R=1931, W=1930, U=0, E=0)
INFO  30-07 09:40:56,600 - not a play match - Finished processing (I=0, O=0, R=3641, W=3641, U=0, E=0)
INFO  30-07 09:40:56,601 - Filter rows - Finished processing (I=0, O=0, R=3836, W=3836, U=0, E=0)
INFO  30-07 09:40:56,629 - Append cycle_id, file_id - Finished processing (I=0, O=0, R=1, W=0, U=0, E=0)
INFO  30-07 09:40:56,630 - Append file_id - Finished processing (I=0, O=0, R=1, W=0, U=0, E=0)
INFO  30-07 09:40:58,558 - process_events - Finished job entry [Process events] (result=[false])
INFO  30-07 09:40:58,575 - Process single cycle - Starting entry [set cycle status failed]
INFO  30-07 09:40:58,575 - set cycle status running - Loading transformation from XML file [/opt/kaltura/dwh/etlsource/cycles/set_cycle_status.ktr]
INFO  30-07 09:40:58,585 - set_cycle_status - Dispatching started for transformation [set_cycle_status]
INFO  30-07 09:40:58,594 - Get rows from result - Finished processing (I=0, O=0, R=1, W=1, U=0, E=0)
INFO  30-07 09:40:58,596 - Setting cycle status -
------------> Linenr 1------------------------------
cycle_id = 9
new_status = 'FAILED'

I don’t have any values in Top Content Analytics and I plays videos out of kmc with embed integration.

Best regards,

Julien

2

Hello Julien,

Please provide info on your ENV. i.e:

  • what OS is being used? and accordingly, what versions of: kaltura-base, kaltura-dwh and kaltura-pentaho are installed

  • what MySQL version is being used?

Thanks,

3

Hi Jess,

my OS is:

[root@kaltest2 logs]# cat /etc/redhat-release
CentOS Linux release 7.1.1503 (Core)

Kaltura Installed:

[root@kaltest2 logs]# yum list installed |grep kaltura-*
kaltura-a52dec.x86_64             0.7.4-11                       @Kaltura
kaltura-base.noarch               10.16.0-7                      @Kaltura-noarch
kaltura-batch.noarch              10.16.0-1                      @Kaltura-noarch
kaltura-clipapp.noarch            1:1.3-2                        @Kaltura-noarch
kaltura-dwh.noarch                9.4.0-2                        @Kaltura-noarch
kaltura-fdk-aac.x86_64            0.1.3-1                        @Kaltura
kaltura-ffmpeg.x86_64             2.1.3-2                        @Kaltura
kaltura-ffmpeg-aux.x86_64         0.6-2                          @Kaltura
kaltura-flexwrapper.noarch        v1.2-1                         @Kaltura-noarch
kaltura-front.noarch              10.16.0-1                      @Kaltura-noarch
kaltura-html5-studio.noarch       v2.0.0-1                       @Kaltura-noarch
kaltura-html5lib.noarch           v2.33-1                        @Kaltura-noarch
kaltura-kclip.noarch              v1.1.2.1-2                     @Kaltura-noarch
kaltura-kcw.noarch                1.0.0-6                        @Kaltura-noarch
kaltura-kdp.noarch                v2.7.0-1                       @Kaltura-noarch
kaltura-kdp3.noarch               1:v3.9.9-2                     @Kaltura-noarch
kaltura-kdp3wrapper.noarch        v37.0-1                        @Kaltura-noarch
kaltura-kdpwrapper.noarch         v11.0-1                        @Kaltura-noarch
kaltura-kmc.noarch                v5.39.6-3                      @Kaltura-noarch
kaltura-krecord.noarch            1.0.0-1                        @Kaltura-noarch
kaltura-kupload.noarch            1.0.0-1                        @Kaltura-noarch
kaltura-kvpm.noarch               v1.0.6-1                       @Kaltura-noarch
kaltura-lame.x86_64               3.99.5-3                       @Kaltura
kaltura-libass.x86_64             0.9.11-2                       @Kaltura
kaltura-libfaac.x86_64            1.28-1                         @Kaltura
kaltura-libopencore-amr.x86_64    0.1.3-1                        @Kaltura
kaltura-mencoder.x86_64           3.4.6-9                        @Kaltura
kaltura-monit.x86_64              5.13-1                         @Kaltura
kaltura-nginx.x86_64              1:1.8.0-1                      @Kaltura
kaltura-pentaho.x86_64            4.2.1-2                        @Kaltura
kaltura-postinst.noarch           1.0.28-2                       @Kaltura-noarch
kaltura-red5.x86_64               1.0.4-1                        @Kaltura
kaltura-release.noarch            10.16.0-1                      @Kaltura-noarch
kaltura-segmenter.x86_64          1.0-1                          @Kaltura
kaltura-server.noarch             10.16.0-1                      @Kaltura-noarch
kaltura-sphinx.x86_64             2.2.1-16                       @Kaltura
kaltura-sshpass.x86_64            1.05-1                         @Kaltura
kaltura-widgets.noarch            1.0.0-8                        @Kaltura-noarch
kaltura-x264.x86_64               0.140-2.20140104               @Kaltura

Mysql used is:

[root@kaltest2 logs]# mysql --version
mysql  Ver 15.1 Distrib 10.0.20-MariaDB, for Linux (x86_64) using readline 5.1

And my ENV:

LANG=fr_FR.UTF-8

Regards,

Julien

4

Something else that I was run:

    [root@kaltest2 yum.repos.d]# /opt/kaltura/bin/kaltura-sanity.sh
[Space on /] [PASSED, RC: 0] - [.015708446]
[Space on /opt/kaltura/web] [PASSED, RC: 0] - [.004053308]
Redirecting to /bin/systemctl status  httpd.service
[Check httpd daemon status] [PASSED, RC: 0] - [.036305549]
Redirecting to /bin/systemctl stop  httpd.service
Redirecting to /bin/systemctl status  httpd.service
Napping 1 seconds to allow the daemon httpd to finish its init after monit restarted it..
Redirecting to /bin/systemctl status  httpd.service
Napping 2 seconds to allow the daemon httpd to finish its init after monit restarted it..
Redirecting to /bin/systemctl status  httpd.service
Napping 3 seconds to allow the daemon httpd to finish its init after monit restarted it..
Redirecting to /bin/systemctl status  httpd.service
Napping 4 seconds to allow the daemon httpd to finish its init after monit restarted it..
Redirecting to /bin/systemctl status  httpd.service
Napping 5 seconds to allow the daemon httpd to finish its init after monit restarted it..
Redirecting to /bin/systemctl status  httpd.service
Napping 6 seconds to allow the daemon httpd to finish its init after monit restarted it..
Redirecting to /bin/systemctl status  httpd.service
Napping 7 seconds to allow the daemon httpd to finish its init after monit restarted it..
Redirecting to /bin/systemctl status  httpd.service
Napping 8 seconds to allow the daemon httpd to finish its init after monit restarted it..
Redirecting to /bin/systemctl status  httpd.service
Napping 9 seconds to allow the daemon httpd to finish its init after monit restarted it..
Redirecting to /bin/systemctl status  httpd.service
Napping 10 seconds to allow the daemon httpd to finish its init after monit restarted it..
Redirecting to /bin/systemctl status  httpd.service
Napping 11 seconds to allow the daemon httpd to finish its init after monit restarted it..
Redirecting to /bin/systemctl status  httpd.service
Napping 12 seconds to allow the daemon httpd to finish its init after monit restarted it..
Redirecting to /bin/systemctl status  httpd.service
Napping 13 seconds to allow the daemon httpd to finish its init after monit restarted it..
Redirecting to /bin/systemctl status  httpd.service
Napping 14 seconds to allow the daemon httpd to finish its init after monit restarted it..
Redirecting to /bin/systemctl status  httpd.service
Napping 15 seconds to allow the daemon httpd to finish its init after monit restarted it..
Redirecting to /bin/systemctl status  httpd.service
Napping 16 seconds to allow the daemon httpd to finish its init after monit restarted it..
Redirecting to /bin/systemctl status  httpd.service
Napping 17 seconds to allow the daemon httpd to finish its init after monit restarted it..
Redirecting to /bin/systemctl status  httpd.service
Napping 18 seconds to allow the daemon httpd to finish its init after monit restarted it..
Redirecting to /bin/systemctl status  httpd.service
Napping 19 seconds to allow the daemon httpd to finish its init after monit restarted it..
Redirecting to /bin/systemctl status  httpd.service
Napping 20 seconds to allow the daemon httpd to finish its init after monit restarted it..
Redirecting to /bin/systemctl status  httpd.service
Napping 21 seconds to allow the daemon httpd to finish its init after monit restarted it..
Redirecting to /bin/systemctl status  httpd.service
Napping 22 seconds to allow the daemon httpd to finish its init after monit restarted it..
Redirecting to /bin/systemctl status  httpd.service
Napping 23 seconds to allow the daemon httpd to finish its init after monit restarted it..
Redirecting to /bin/systemctl status  httpd.service
Napping 24 seconds to allow the daemon httpd to finish its init after monit restarted it..
Redirecting to /bin/systemctl status  httpd.service
Napping 25 seconds to allow the daemon httpd to finish its init after monit restarted it..
Redirecting to /bin/systemctl status  httpd.service
Napping 26 seconds to allow the daemon httpd to finish its init after monit restarted it..
Redirecting to /bin/systemctl status  httpd.service
Napping 27 seconds to allow the daemon httpd to finish its init after monit restarted it..
Redirecting to /bin/systemctl status  httpd.service
Napping 28 seconds to allow the daemon httpd to finish its init after monit restarted it..
Redirecting to /bin/systemctl status  httpd.service
Napping 29 seconds to allow the daemon httpd to finish its init after monit restarted it..
Redirecting to /bin/systemctl status  httpd.service
Napping 30 seconds to allow the daemon httpd to finish its init after monit restarted it..
Redirecting to /bin/systemctl status  httpd.service
Napping 31 seconds to allow the daemon httpd to finish its init after monit restarted it..
Redirecting to /bin/systemctl status  httpd.service
Napping 32 seconds to allow the daemon httpd to finish its init after monit restarted it..
Redirecting to /bin/systemctl status  httpd.service
Napping 33 seconds to allow the daemon httpd to finish its init after monit restarted it..
Redirecting to /bin/systemctl status  httpd.service
Napping 34 seconds to allow the daemon httpd to finish its init after monit restarted it..
Redirecting to /bin/systemctl status  httpd.service
Napping 35 seconds to allow the daemon httpd to finish its init after monit restarted it..
Redirecting to /bin/systemctl status  httpd.service
Napping 36 seconds to allow the daemon httpd to finish its init after monit restarted it..
Redirecting to /bin/systemctl status  httpd.service
Napping 37 seconds to allow the daemon httpd to finish its init after monit restarted it..
Redirecting to /bin/systemctl status  httpd.service
Napping 38 seconds to allow the daemon httpd to finish its init after monit restarted it..
Redirecting to /bin/systemctl status  httpd.service
[Check httpd daemon is started by Monit] [PASSED, RC: 0] - [39.787221412]
Note : transfert de la requête par « systemctl is-enabled httpd.service ».
enabled
[check daemon httpd init status] [PASSED, RC: 0] - [.011559881]
[Check kaltura-sphinx daemon status] [PASSED, RC: 0] - [.042299845]
Napping 1 seconds to allow the daemon kaltura-sphinx to finish its init after monit restarted it..
Napping 2 seconds to allow the daemon kaltura-sphinx to finish its init after monit restarted it..
Napping 3 seconds to allow the daemon kaltura-sphinx to finish its init after monit restarted it..
Napping 4 seconds to allow the daemon kaltura-sphinx to finish its init after monit restarted it..
Napping 5 seconds to allow the daemon kaltura-sphinx to finish its init after monit restarted it..
Napping 6 seconds to allow the daemon kaltura-sphinx to finish its init after monit restarted it..
Napping 7 seconds to allow the daemon kaltura-sphinx to finish its init after monit restarted it..
Napping 8 seconds to allow the daemon kaltura-sphinx to finish its init after monit restarted it..
Napping 9 seconds to allow the daemon kaltura-sphinx to finish its init after monit restarted it..
[Check kaltura-sphinx daemon is started by Monit] [PASSED, RC: 0] - [9.831453197]
[check daemon kaltura-sphinx init status] [PASSED, RC: 0] - [.004764906]
[Check kaltura-batch daemon status] [PASSED, RC: 0] - [.032058154]
Napping 1 seconds to allow the daemon kaltura-batch to finish its init after monit restarted it..
Napping 2 seconds to allow the daemon kaltura-batch to finish its init after monit restarted it..
Napping 3 seconds to allow the daemon kaltura-batch to finish its init after monit restarted it..
Napping 4 seconds to allow the daemon kaltura-batch to finish its init after monit restarted it..
Napping 5 seconds to allow the daemon kaltura-batch to finish its init after monit restarted it..
Napping 6 seconds to allow the daemon kaltura-batch to finish its init after monit restarted it..
Napping 7 seconds to allow the daemon kaltura-batch to finish its init after monit restarted it..
Napping 8 seconds to allow the daemon kaltura-batch to finish its init after monit restarted it..
Napping 9 seconds to allow the daemon kaltura-batch to finish its init after monit restarted it..
Napping 10 seconds to allow the daemon kaltura-batch to finish its init after monit restarted it..
Napping 11 seconds to allow the daemon kaltura-batch to finish its init after monit restarted it..
Napping 12 seconds to allow the daemon kaltura-batch to finish its init after monit restarted it..
Napping 13 seconds to allow the daemon kaltura-batch to finish its init after monit restarted it..
Napping 14 seconds to allow the daemon kaltura-batch to finish its init after monit restarted it..
Napping 15 seconds to allow the daemon kaltura-batch to finish its init after monit restarted it..
Napping 16 seconds to allow the daemon kaltura-batch to finish its init after monit restarted it..
Napping 17 seconds to allow the daemon kaltura-batch to finish its init after monit restarted it..
Napping 18 seconds to allow the daemon kaltura-batch to finish its init after monit restarted it..
Napping 19 seconds to allow the daemon kaltura-batch to finish its init after monit restarted it..
Napping 20 seconds to allow the daemon kaltura-batch to finish its init after monit restarted it..
Napping 21 seconds to allow the daemon kaltura-batch to finish its init after monit restarted it..
Napping 22 seconds to allow the daemon kaltura-batch to finish its init after monit restarted it..
Napping 23 seconds to allow the daemon kaltura-batch to finish its init after monit restarted it..
Napping 24 seconds to allow the daemon kaltura-batch to finish its init after monit restarted it..
Napping 25 seconds to allow the daemon kaltura-batch to finish its init after monit restarted it..
Napping 26 seconds to allow the daemon kaltura-batch to finish its init after monit restarted it..
Napping 27 seconds to allow the daemon kaltura-batch to finish its init after monit restarted it..
Napping 28 seconds to allow the daemon kaltura-batch to finish its init after monit restarted it..
Napping 29 seconds to allow the daemon kaltura-batch to finish its init after monit restarted it..
Napping 30 seconds to allow the daemon kaltura-batch to finish its init after monit restarted it..
Napping 31 seconds to allow the daemon kaltura-batch to finish its init after monit restarted it..
Napping 32 seconds to allow the daemon kaltura-batch to finish its init after monit restarted it..
Napping 33 seconds to allow the daemon kaltura-batch to finish its init after monit restarted it..
Napping 34 seconds to allow the daemon kaltura-batch to finish its init after monit restarted it..
Napping 35 seconds to allow the daemon kaltura-batch to finish its init after monit restarted it..
Napping 36 seconds to allow the daemon kaltura-batch to finish its init after monit restarted it..
Napping 37 seconds to allow the daemon kaltura-batch to finish its init after monit restarted it..
Napping 38 seconds to allow the daemon kaltura-batch to finish its init after monit restarted it..
Napping 39 seconds to allow the daemon kaltura-batch to finish its init after monit restarted it..
Napping 40 seconds to allow the daemon kaltura-batch to finish its init after monit restarted it..
Napping 41 seconds to allow the daemon kaltura-batch to finish its init after monit restarted it..
Napping 42 seconds to allow the daemon kaltura-batch to finish its init after monit restarted it..
[Check kaltura-batch daemon is started by Monit] [PASSED, RC: 0] - [43.009864301]
[check daemon kaltura-batch init status] [PASSED, RC: 0] - [.004661467]
[Check kaltura-monit daemon status] [PASSED, RC: 0] - [.025843316]
[check daemon kaltura-monit init status] [PASSED, RC: 0] - [.004904404]
Redirecting to /bin/systemctl status  memcached.service
[Check memcached daemon status] [PASSED, RC: 0] - [.017907100]
Redirecting to /bin/systemctl stop  memcached.service
Redirecting to /bin/systemctl status  memcached.service
Napping 1 seconds to allow the daemon memcached to finish its init after monit restarted it..
Redirecting to /bin/systemctl status  memcached.service
Napping 2 seconds to allow the daemon memcached to finish its init after monit restarted it..
Redirecting to /bin/systemctl status  memcached.service
Napping 3 seconds to allow the daemon memcached to finish its init after monit restarted it..
Redirecting to /bin/systemctl status  memcached.service
Napping 4 seconds to allow the daemon memcached to finish its init after monit restarted it..
Redirecting to /bin/systemctl status  memcached.service
Napping 5 seconds to allow the daemon memcached to finish its init after monit restarted it..
Redirecting to /bin/systemctl status  memcached.service
Napping 6 seconds to allow the daemon memcached to finish its init after monit restarted it..
Redirecting to /bin/systemctl status  memcached.service
Napping 7 seconds to allow the daemon memcached to finish its init after monit restarted it..
Redirecting to /bin/systemctl status  memcached.service
Napping 8 seconds to allow the daemon memcached to finish its init after monit restarted it..
Redirecting to /bin/systemctl status  memcached.service
Napping 9 seconds to allow the daemon memcached to finish its init after monit restarted it..
Redirecting to /bin/systemctl status  memcached.service
Napping 10 seconds to allow the daemon memcached to finish its init after monit restarted it..
Redirecting to /bin/systemctl status  memcached.service
Napping 11 seconds to allow the daemon memcached to finish its init after monit restarted it..
Redirecting to /bin/systemctl status  memcached.service
Napping 12 seconds to allow the daemon memcached to finish its init after monit restarted it..
Redirecting to /bin/systemctl status  memcached.service
Napping 13 seconds to allow the daemon memcached to finish its init after monit restarted it..
Redirecting to /bin/systemctl status  memcached.service
[Check memcached daemon is started by Monit] [PASSED, RC: 0] - [13.272367062]
Note : transfert de la requête par « systemctl is-enabled memcached.service ».
enabled
[check daemon memcached init status] [PASSED, RC: 0] - [.004030540]
[kaltura-html5lib ver in KMC config.ini] [PASSED, RC: 0] - [.084491980]
[kaltura-kdp3 ver in KDP3 config.ini] [PASSED, RC: 0] - [.037194211]
[kaltura-kmc ver in KMC config.ini] [PASSED, RC: 0] - [.041201411]
[Get KMC SWFs] [PASSED, RC: 0] - [.492099587]
[check_testme_page] [PASSED, RC: 0] - [.420589891]
[check_kmc_index_page] [PASSED, RC: 0] - [.193785381]
[check_admin_console_index_page] [PASSED, RC: 0] - [1.124122099]
[check_studio_index_page] [PASSED, RC: 0] - [.166078147]
[check_clipapp_index_page] [PASSED, RC: 0] - [.770939229]
[Create Partner] [PASSED, RC: 0] - [2.350526980]
[Local dropfolder creation] [PASSED, RC: 0] - [1.530236023]
[Create flavor param] [PASSED, RC: 0] - [1.010033595]
[Delete flavor param] [PASSED, RC: 0] - [.761509340]
[HTTP notification: ID: 25, URL: http://localhost/1.php] [PASSED, RC: 0] - [1.010033595]
[Mail notification: ID: 26, Subject: Your video is ready to be played!, Mail body: Hello world:)] [PASSED, RC: 0] - [1.010033595]
[Upload content kaltura_logo_animated_blue.flv] [PASSED, RC: 0] - [1.633925244]
Napping 10 seconds to allow entry 0_4pty1m6e to digest..
Napping 10 seconds to allow entry 0_4pty1m6e to digest..
Napping 10 seconds to allow entry 0_4pty1m6e to digest..
Napping 10 seconds to allow entry 0_4pty1m6e to digest..
Napping 10 seconds to allow entry 0_4pty1m6e to digest..
Napping 10 seconds to allow entry 0_4pty1m6e to digest..
Napping 10 seconds to allow entry 0_4pty1m6e to digest..
Napping 10 seconds to allow entry 0_4pty1m6e to digest..
Napping 10 seconds to allow entry 0_4pty1m6e to digest..
[kaltura_logo_animated_blue.flv - 0_4pty1m6e status] [FAILED, RC: 1] - [-.562123049]
Napping 30 seconds to allow mail to be sent out..
[Found an email sending entry for mb-kaltest2.univ-amu.fr@kaltura.com[PID is 103] in /var/log/maillog] [PASSED, RC: 0] - [30.010686001]
Testing analytics, be patient..

Please note: if you are running this test on a clustered ENV, it will fail but this does not mean there is an actual problem.
The tech information as to why is available here:
https://github.com/kaltura/platform-install-packages/issues/106#issuecomment-42837404

[DWH cycle] [FAILED, RC: 255] - [7.104853116]
[Upload content kaltura_logo_animated_green.flv] [PASSED, RC: 0] - [1.689475250]
[Upload bulk using CSV] [PASSED, RC: 0] - [1.208983685]
[Upload bulk using XML] [PASSED, RC: 0] - [.981079771]
[Create player] [PASSED, RC: 0] - [.626543272]
[Generate thumb] [FAILED, RC: 255] - [.623210309]
[Delete partner] [PASSED, RC: 0] - [.651181141]
[Red5 file upload] [PASSED, RC: 0] - [4.218432238]

if it’s help too.

Regards,

Julien

5

Hello Julien,

Sanity seems to run correctly, apart from the DWH portion.
For MySQL, what I am more interested in is the server version, not the client.
Please provide output for:
# rpm -q mariadb-server
or:
# rpm -q mysql-server

Seeing how you use CentOS 7, my guess would be 5.5.41 but want to make sure…

Thanks,

6

Hi Jess,

My version of mysql is:

MariaDB-Galera-server.x86_64 10.0.20-1.el7.centos @mariadb

Does I have to come back to mariadb 5.5.X ? And follow that and come back to you ?

https://github.com/kaltura/platform-install-packages/blob/Jupiter-10.17.0/doc/kaltura-packages-faq.md#analytics-issues

Regards,

Julien

7

Hello Julien,

I am unfamiliar with this version… where did you obtain it from and also, which Major MySQL version is it compatible with?
We support 5.1,5.5 and 5.6.
It would be best for you to use the version supplied by the official CentOS repo, which is also the one we use when testing.

8

Hello Jess,

I obtained from official maridb repository.
I change the MySQL and come back to you

Regards,

Julien

9

Hi Jess,

I installed MariaDB 5.5.44:

MariaDB-client.x86_64             5.5.44-1.el7.centos            @mariadb
MariaDB-common.x86_64             5.5.44-1.el7.centos            @mariadb
MariaDB-server.x86_64             5.5.44-1.el7.centos            @mariadb
MariaDB-shared.x86_64             5.5.44-1.el7.centos            @mariadb

I was reconfigure all kaltura from start…

Actually I have no error in my dwh logs.

I try to make some video playing to see if datas are come in analytics.

I was face of one problem when I reinstall all I can’t access anymore to olfaDemo from RED5 server.
And I don’t have anymore the flash button in my kmc -> studio.

Regards,

Julien

10

Hi Julien,

Please be more specific:) did you uninstall and reinstall everything or just rebuilt the DB? what exactly is the error you’re seeing when trying to access oflaDemo and the KMC->studio?
Check the logs by running:
# kaltlog
in the shell while making the requests, also, open the dev tools in the browser and check the nework and console tabs for errors

11

Hi Jess,

I was uninstall and reinstall everything to be sure.
When I was want to configure Red5, on the admin interface: http://kalturaserver.com:5080
For installing olfaDemo, the message was already installed package. Now to read again the installation process I found my error:

Edit /usr/lib/red5/webapps/oflaDemo/index.html and replace ‘localhost’ with your actual Red5 hostname or IP

Sorry end of day :blush:

I check with Sanity and DWH failed again :frowning:

 [root@kaltest2 conf.d]# /opt/kaltura/bin/kaltura-sanity.sh
[Space on /] [PASSED, RC: 0] - [.039487003]
[Space on /opt/kaltura/web] [PASSED, RC: 0] - [.004071981]
Redirecting to /bin/systemctl status  httpd.service
[Check httpd daemon status] [PASSED, RC: 0] - [.129325052]
Redirecting to /bin/systemctl stop  httpd.service
Redirecting to /bin/systemctl status  httpd.service
Napping 1 seconds to allow the daemon httpd to finish its init after monit restarted it..
Redirecting to /bin/systemctl status  httpd.service
Napping 2 seconds to allow the daemon httpd to finish its init after monit restarted it..
Redirecting to /bin/systemctl status  httpd.service
Napping 3 seconds to allow the daemon httpd to finish its init after monit restarted it..
Redirecting to /bin/systemctl status  httpd.service
Napping 4 seconds to allow the daemon httpd to finish its init after monit restarted it..
Redirecting to /bin/systemctl status  httpd.service
Napping 5 seconds to allow the daemon httpd to finish its init after monit restarted it..
Redirecting to /bin/systemctl status  httpd.service
Napping 6 seconds to allow the daemon httpd to finish its init after monit restarted it..
Redirecting to /bin/systemctl status  httpd.service
Napping 7 seconds to allow the daemon httpd to finish its init after monit restarted it..
Redirecting to /bin/systemctl status  httpd.service
Napping 8 seconds to allow the daemon httpd to finish its init after monit restarted it..
Redirecting to /bin/systemctl status  httpd.service
Napping 9 seconds to allow the daemon httpd to finish its init after monit restarted it..
Redirecting to /bin/systemctl status  httpd.service
Napping 10 seconds to allow the daemon httpd to finish its init after monit restarted it..
Redirecting to /bin/systemctl status  httpd.service
Napping 11 seconds to allow the daemon httpd to finish its init after monit restarted it..
Redirecting to /bin/systemctl status  httpd.service
Napping 12 seconds to allow the daemon httpd to finish its init after monit restarted it..
Redirecting to /bin/systemctl status  httpd.service
Napping 13 seconds to allow the daemon httpd to finish its init after monit restarted it..
Redirecting to /bin/systemctl status  httpd.service
Napping 14 seconds to allow the daemon httpd to finish its init after monit restarted it..
Redirecting to /bin/systemctl status  httpd.service
Napping 15 seconds to allow the daemon httpd to finish its init after monit restarted it..
Redirecting to /bin/systemctl status  httpd.service
Napping 16 seconds to allow the daemon httpd to finish its init after monit restarted it..
Redirecting to /bin/systemctl status  httpd.service
Napping 17 seconds to allow the daemon httpd to finish its init after monit restarted it..
Redirecting to /bin/systemctl status  httpd.service
Napping 18 seconds to allow the daemon httpd to finish its init after monit restarted it..
Redirecting to /bin/systemctl status  httpd.service
Napping 19 seconds to allow the daemon httpd to finish its init after monit restarted it..
Redirecting to /bin/systemctl status  httpd.service
Napping 20 seconds to allow the daemon httpd to finish its init after monit restarted it..
Redirecting to /bin/systemctl status  httpd.service
Napping 21 seconds to allow the daemon httpd to finish its init after monit restarted it..
Redirecting to /bin/systemctl status  httpd.service
Napping 22 seconds to allow the daemon httpd to finish its init after monit restarted it..
Redirecting to /bin/systemctl status  httpd.service
Napping 23 seconds to allow the daemon httpd to finish its init after monit restarted it..
Redirecting to /bin/systemctl status  httpd.service
Napping 24 seconds to allow the daemon httpd to finish its init after monit restarted it..
Redirecting to /bin/systemctl status  httpd.service
Napping 25 seconds to allow the daemon httpd to finish its init after monit restarted it..
Redirecting to /bin/systemctl status  httpd.service
Napping 26 seconds to allow the daemon httpd to finish its init after monit restarted it..
Redirecting to /bin/systemctl status  httpd.service
Napping 27 seconds to allow the daemon httpd to finish its init after monit restarted it..
Redirecting to /bin/systemctl status  httpd.service
Napping 28 seconds to allow the daemon httpd to finish its init after monit restarted it..
Redirecting to /bin/systemctl status  httpd.service
Napping 29 seconds to allow the daemon httpd to finish its init after monit restarted it..
Redirecting to /bin/systemctl status  httpd.service
Napping 30 seconds to allow the daemon httpd to finish its init after monit restarted it..
Redirecting to /bin/systemctl status  httpd.service
Napping 31 seconds to allow the daemon httpd to finish its init after monit restarted it..
Redirecting to /bin/systemctl status  httpd.service
Napping 32 seconds to allow the daemon httpd to finish its init after monit restarted it..
Redirecting to /bin/systemctl status  httpd.service
Napping 33 seconds to allow the daemon httpd to finish its init after monit restarted it..
Redirecting to /bin/systemctl status  httpd.service
[Check httpd daemon is started by Monit] [PASSED, RC: 0] - [34.765357424]
Note : transfert de la requête par « systemctl is-enabled httpd.service ».
enabled
[check daemon httpd init status] [PASSED, RC: 0] - [.021478397]
[Check kaltura-sphinx daemon status] [PASSED, RC: 0] - [.056657178]
Napping 1 seconds to allow the daemon kaltura-sphinx to finish its init after monit restarted it..
Napping 2 seconds to allow the daemon kaltura-sphinx to finish its init after monit restarted it..
Napping 3 seconds to allow the daemon kaltura-sphinx to finish its init after monit restarted it..
Napping 4 seconds to allow the daemon kaltura-sphinx to finish its init after monit restarted it..
Napping 5 seconds to allow the daemon kaltura-sphinx to finish its init after monit restarted it..
Napping 6 seconds to allow the daemon kaltura-sphinx to finish its init after monit restarted it..
Napping 7 seconds to allow the daemon kaltura-sphinx to finish its init after monit restarted it..
Napping 8 seconds to allow the daemon kaltura-sphinx to finish its init after monit restarted it..
Napping 9 seconds to allow the daemon kaltura-sphinx to finish its init after monit restarted it..
Napping 10 seconds to allow the daemon kaltura-sphinx to finish its init after monit restarted it..
Napping 11 seconds to allow the daemon kaltura-sphinx to finish its init after monit restarted it..
Napping 12 seconds to allow the daemon kaltura-sphinx to finish its init after monit restarted it..
Napping 13 seconds to allow the daemon kaltura-sphinx to finish its init after monit restarted it..
Napping 14 seconds to allow the daemon kaltura-sphinx to finish its init after monit restarted it..
Napping 15 seconds to allow the daemon kaltura-sphinx to finish its init after monit restarted it..
Napping 16 seconds to allow the daemon kaltura-sphinx to finish its init after monit restarted it..
Napping 17 seconds to allow the daemon kaltura-sphinx to finish its init after monit restarted it..
Napping 18 seconds to allow the daemon kaltura-sphinx to finish its init after monit restarted it..
Napping 19 seconds to allow the daemon kaltura-sphinx to finish its init after monit restarted it..
Napping 20 seconds to allow the daemon kaltura-sphinx to finish its init after monit restarted it..
Napping 21 seconds to allow the daemon kaltura-sphinx to finish its init after monit restarted it..
Napping 22 seconds to allow the daemon kaltura-sphinx to finish its init after monit restarted it..
Napping 23 seconds to allow the daemon kaltura-sphinx to finish its init after monit restarted it..
Napping 24 seconds to allow the daemon kaltura-sphinx to finish its init after monit restarted it..
Napping 25 seconds to allow the daemon kaltura-sphinx to finish its init after monit restarted it..
Napping 26 seconds to allow the daemon kaltura-sphinx to finish its init after monit restarted it..
Napping 27 seconds to allow the daemon kaltura-sphinx to finish its init after monit restarted it..
Napping 28 seconds to allow the daemon kaltura-sphinx to finish its init after monit restarted it..
Napping 29 seconds to allow the daemon kaltura-sphinx to finish its init after monit restarted it..
Napping 30 seconds to allow the daemon kaltura-sphinx to finish its init after monit restarted it..
Napping 31 seconds to allow the daemon kaltura-sphinx to finish its init after monit restarted it..
Napping 32 seconds to allow the daemon kaltura-sphinx to finish its init after monit restarted it..
Napping 33 seconds to allow the daemon kaltura-sphinx to finish its init after monit restarted it..
Napping 34 seconds to allow the daemon kaltura-sphinx to finish its init after monit restarted it..
Napping 35 seconds to allow the daemon kaltura-sphinx to finish its init after monit restarted it..
Napping 36 seconds to allow the daemon kaltura-sphinx to finish its init after monit restarted it..
Napping 37 seconds to allow the daemon kaltura-sphinx to finish its init after monit restarted it..
Napping 38 seconds to allow the daemon kaltura-sphinx to finish its init after monit restarted it..
Napping 39 seconds to allow the daemon kaltura-sphinx to finish its init after monit restarted it..
Napping 40 seconds to allow the daemon kaltura-sphinx to finish its init after monit restarted it..
Napping 41 seconds to allow the daemon kaltura-sphinx to finish its init after monit restarted it..
Napping 42 seconds to allow the daemon kaltura-sphinx to finish its init after monit restarted it..
Napping 43 seconds to allow the daemon kaltura-sphinx to finish its init after monit restarted it..
Napping 44 seconds to allow the daemon kaltura-sphinx to finish its init after monit restarted it..
Napping 45 seconds to allow the daemon kaltura-sphinx to finish its init after monit restarted it..
Napping 46 seconds to allow the daemon kaltura-sphinx to finish its init after monit restarted it..
Napping 47 seconds to allow the daemon kaltura-sphinx to finish its init after monit restarted it..
Napping 48 seconds to allow the daemon kaltura-sphinx to finish its init after monit restarted it..
Napping 49 seconds to allow the daemon kaltura-sphinx to finish its init after monit restarted it..
[Check kaltura-sphinx daemon is started by Monit] [PASSED, RC: 0] - [51.045116425]
[check daemon kaltura-sphinx init status] [PASSED, RC: 0] - [.039866395]
[Check kaltura-batch daemon status] [PASSED, RC: 0] - [.090331280]
Napping 1 seconds to allow the daemon kaltura-batch to finish its init after monit restarted it..
Napping 2 seconds to allow the daemon kaltura-batch to finish its init after monit restarted it..
Napping 3 seconds to allow the daemon kaltura-batch to finish its init after monit restarted it..
Napping 4 seconds to allow the daemon kaltura-batch to finish its init after monit restarted it..
Napping 5 seconds to allow the daemon kaltura-batch to finish its init after monit restarted it..
Napping 6 seconds to allow the daemon kaltura-batch to finish its init after monit restarted it..
Napping 7 seconds to allow the daemon kaltura-batch to finish its init after monit restarted it..
Napping 8 seconds to allow the daemon kaltura-batch to finish its init after monit restarted it..
Napping 9 seconds to allow the daemon kaltura-batch to finish its init after monit restarted it..
Napping 10 seconds to allow the daemon kaltura-batch to finish its init after monit restarted it..
Napping 11 seconds to allow the daemon kaltura-batch to finish its init after monit restarted it..
Napping 12 seconds to allow the daemon kaltura-batch to finish its init after monit restarted it..
Napping 13 seconds to allow the daemon kaltura-batch to finish its init after monit restarted it..
Napping 14 seconds to allow the daemon kaltura-batch to finish its init after monit restarted it..
Napping 15 seconds to allow the daemon kaltura-batch to finish its init after monit restarted it..
Napping 16 seconds to allow the daemon kaltura-batch to finish its init after monit restarted it..
Napping 17 seconds to allow the daemon kaltura-batch to finish its init after monit restarted it..
Napping 18 seconds to allow the daemon kaltura-batch to finish its init after monit restarted it..
Napping 19 seconds to allow the daemon kaltura-batch to finish its init after monit restarted it..
Napping 20 seconds to allow the daemon kaltura-batch to finish its init after monit restarted it..
Napping 21 seconds to allow the daemon kaltura-batch to finish its init after monit restarted it..
Napping 22 seconds to allow the daemon kaltura-batch to finish its init after monit restarted it..
Napping 23 seconds to allow the daemon kaltura-batch to finish its init after monit restarted it..
Napping 24 seconds to allow the daemon kaltura-batch to finish its init after monit restarted it..
Napping 25 seconds to allow the daemon kaltura-batch to finish its init after monit restarted it..
Napping 26 seconds to allow the daemon kaltura-batch to finish its init after monit restarted it..
Napping 27 seconds to allow the daemon kaltura-batch to finish its init after monit restarted it..
Napping 28 seconds to allow the daemon kaltura-batch to finish its init after monit restarted it..
Napping 29 seconds to allow the daemon kaltura-batch to finish its init after monit restarted it..
Napping 30 seconds to allow the daemon kaltura-batch to finish its init after monit restarted it..
Napping 31 seconds to allow the daemon kaltura-batch to finish its init after monit restarted it..
Napping 32 seconds to allow the daemon kaltura-batch to finish its init after monit restarted it..
Napping 33 seconds to allow the daemon kaltura-batch to finish its init after monit restarted it..
Napping 34 seconds to allow the daemon kaltura-batch to finish its init after monit restarted it..
[Check kaltura-batch daemon is started by Monit] [PASSED, RC: 0] - [34.838018646]
[check daemon kaltura-batch init status] [PASSED, RC: 0] - [.032018173]
[Check kaltura-monit daemon status] [PASSED, RC: 0] - [.035800658]
[check daemon kaltura-monit init status] [PASSED, RC: 0] - [.021434673]
Redirecting to /bin/systemctl status  memcached.service
[Check memcached daemon status] [PASSED, RC: 0] - [.018215125]
Redirecting to /bin/systemctl stop  memcached.service
Redirecting to /bin/systemctl status  memcached.service
Napping 1 seconds to allow the daemon memcached to finish its init after monit restarted it..
Redirecting to /bin/systemctl status  memcached.service
Napping 2 seconds to allow the daemon memcached to finish its init after monit restarted it..
Redirecting to /bin/systemctl status  memcached.service
Napping 3 seconds to allow the daemon memcached to finish its init after monit restarted it..
Redirecting to /bin/systemctl status  memcached.service
Napping 4 seconds to allow the daemon memcached to finish its init after monit restarted it..
Redirecting to /bin/systemctl status  memcached.service
Napping 5 seconds to allow the daemon memcached to finish its init after monit restarted it..
Redirecting to /bin/systemctl status  memcached.service
Napping 6 seconds to allow the daemon memcached to finish its init after monit restarted it..
Redirecting to /bin/systemctl status  memcached.service
Napping 7 seconds to allow the daemon memcached to finish its init after monit restarted it..
Redirecting to /bin/systemctl status  memcached.service
Napping 8 seconds to allow the daemon memcached to finish its init after monit restarted it..
Redirecting to /bin/systemctl status  memcached.service
Napping 9 seconds to allow the daemon memcached to finish its init after monit restarted it..
Redirecting to /bin/systemctl status  memcached.service
Napping 10 seconds to allow the daemon memcached to finish its init after monit restarted it..
Redirecting to /bin/systemctl status  memcached.service
Napping 11 seconds to allow the daemon memcached to finish its init after monit restarted it..
Redirecting to /bin/systemctl status  memcached.service
Napping 12 seconds to allow the daemon memcached to finish its init after monit restarted it..
Redirecting to /bin/systemctl status  memcached.service
Napping 13 seconds to allow the daemon memcached to finish its init after monit restarted it..
Redirecting to /bin/systemctl status  memcached.service
[Check memcached daemon is started by Monit] [PASSED, RC: 0] - [13.285029618]
Note : transfert de la requête par « systemctl is-enabled memcached.service ».
enabled
[check daemon memcached init status] [PASSED, RC: 0] - [.004176354]
[kaltura-html5lib ver in KMC config.ini] [PASSED, RC: 0] - [.089794666]
[kaltura-kdp3 ver in KDP3 config.ini] [PASSED, RC: 0] - [.037417615]
[kaltura-kmc ver in KMC config.ini] [PASSED, RC: 0] - [.041316187]
[Get KMC SWFs] [PASSED, RC: 0] - [.595310831]
[check_testme_page] [PASSED, RC: 0] - [14.096939461]
[check_kmc_index_page] [PASSED, RC: 0] - [.191930893]
[check_admin_console_index_page] [PASSED, RC: 0] - [1.147815293]
[check_studio_index_page] [PASSED, RC: 0] - [.173698841]
[check_clipapp_index_page] [PASSED, RC: 0] - [.759381638]
[Create Partner] [PASSED, RC: 0] - [2.436197093]
[Local dropfolder creation] [PASSED, RC: 0] - [1.486498470]
[Create flavor param] [PASSED, RC: 0] - [1.045685988]
[Delete flavor param] [PASSED, RC: 0] - [.784391961]
[HTTP notification: ID: 24, URL: http://localhost/1.php] [PASSED, RC: 0] - [1.045685988]
[Mail notification: ID: 25, Subject: Your video is ready to be played!, Mail body: Hello world:)] [PASSED, RC: 0] - [1.045685988]
[Upload content kaltura_logo_animated_blue.flv] [PASSED, RC: 0] - [1.823594168]
Napping 10 seconds to allow entry 0_w1y890ms to digest..
Napping 10 seconds to allow entry 0_w1y890ms to digest..
Napping 10 seconds to allow entry 0_w1y890ms to digest..
Napping 10 seconds to allow entry 0_w1y890ms to digest..
[kaltura_logo_animated_blue.flv - 0_w1y890ms status] [PASSED, RC: 0] - [42.586487473]
[Create thumb for 0_w1y890ms] [PASSED, RC: 0] - [1.062530072]
[Clipping 0_w1y890ms] [PASSED, RC: 0] - [1.318840442]
[Trimming 0_w1y890ms] [PASSED, RC: 0] - [1.240176926]
[Mock playback 0_w1y890ms] [PASSED, RC: 0] - [1.355953394]
[Adding captions to 0_w1y890ms] [PASSED, RC: 0] - [1.102374982]
[Searching for Example||Deja||Bold in 0_w1y890ms metadata] [PASSED, RC: 0] - [.890096203]
[Entry reconversion of 0_w1y890ms succeeded] [PASSED, RC: 0] - [1.183734375]
Napping 30 seconds to allow mail to be sent out..
[Found an email sending entry for mb-kaltest2.univ-amu.fr@kaltura.com[PID is 102] in /var/log/maillog] [PASSED, RC: 0] - [30.088678087]
Testing analytics, be patient..

Please note: if you are running this test on a clustered ENV, it will fail but this does not mean there is an actual problem.
The tech information as to why is available here:
https://github.com/kaltura/platform-install-packages/issues/106#issuecomment-42837404

[DWH cycle] [FAILED, RC: 255] - [7.219708594]
[Upload content kaltura_logo_animated_green.flv] [PASSED, RC: 0] - [1.756928873]
[Upload bulk using CSV] [PASSED, RC: 0] - [1.249246009]
[Upload bulk using XML] [PASSED, RC: 0] - [1.018385553]
[Create player] [PASSED, RC: 0] - [.708243125]
[Generate thumb] [PASSED, RC: 0] - [.870587591]
[Delete partner] [PASSED, RC: 0] - [.583702294]
[Red5 file upload] [PASSED, RC: 0] - [3.157354825]

All is clear and ok expect DWH.

Regards,

Julien

12

Sometimes DWH test fails cause it takes too long to process. Take a look at the logs under /opt/kaltura/dwh/logs and grep for ‘ERROR’ and lets see…

13

I get just that:

[root@kaltest2 logs]# grep ERROR *
etl_perform_retention_policy-20150730.log:ERROR 30-07 17:51:50,192 - Lock is already seized - Row nr 1 causing abort : [retention_lock], [1], [0], [null]
etl_perform_retention_policy-20150730.log:ERROR 30-07 17:51:50,192 - Lock is already seized - Aborting after having seen 1 rows.
etl_perform_retention_policy-20150730.log:ERROR 30-07 17:51:50,204 - seize_lock_by_name - Errors detected!
etl_perform_retention_policy-20150730.log:ERROR 30-07 17:51:50,205 - seize_lock_by_name - Errors detected!
14

If it’s help too:

MariaDB [(none)]> select * from kalturadw_ds.locks ;
+---------+-----------------------------+---------------------+------------+
| lock_id | lock_name                   | lock_time           | lock_state |
+---------+-----------------------------+---------------------+------------+
|       1 | daily_lock                  | 2015-07-30 19:19:24 |          0 |
|       2 | retention_lock              | 2015-07-30 19:19:30 |          0 |
|       3 | hourly_kaltest2.univ-amu.fr | 2015-07-30 19:19:06 |          0 |
|       4 | update_dims_lock            | 2015-07-30 19:19:17 |          0 |
+---------+-----------------------------+---------------------+------------+
4 rows in set (0.00 sec)

MariaDB [(none)]> select * from kalturadw_ds.files where insert_time >=20150730;
+---------+------------------------------------------------------------+-------------+-------------+---------------------+----------+---------------+-------+-----------+--------------+------------+----------+--------------------+--------+
| file_id | file_name                                                  | file_status | prev_status | insert_time         | run_time | transfer_time | lines | err_lines | file_size_kb | process_id | cycle_id | compression_suffix | subdir |
+---------+------------------------------------------------------------+-------------+-------------+---------------------+----------+---------------+-------+-----------+--------------+------------+----------+--------------------+--------+
|       1 | kaltest2.univ-amu.fr-kaltura_apache_access.log-20150730-17 | IN_CYCLE    | NULL        | 2015-07-30 17:50:57 | NULL     | NULL          |  NULL |      NULL |            3 |          1 |        1 | gz                 |        |
|       2 | kaltest2.univ-amu.fr-kaltura_apache_access.log-20150730-19 | IN_CYCLE    | NULL        | 2015-07-30 19:19:01 | NULL     | NULL          |  NULL |      NULL |           14 |          1 |        2 | gz                 |        |
+---------+------------------------------------------------------------+-------------+-------------+---------------------+----------+---------------+-------+-----------+--------------+------------+----------+--------------------+--------+
2 rows in set (0.00 sec)

MariaDB [(none)]> select * from kalturadw.dwh_fact_events where event_date_id >=20150730;
Empty set (0.00 sec)
15

so it does not seem like the lock is currently stuck… play an entry via embed, run /opt/kaltura/bin/kaltura-run-dwh.sh and take another look at the logs please.

16

I was play a video and still same:

MariaDB [(none)]> select * from kalturadw_ds.locks;
+---------+-----------------------------+---------------------+------------+
| lock_id | lock_name                   | lock_time           | lock_state |
+---------+-----------------------------+---------------------+------------+
|       1 | daily_lock                  | 2015-07-30 19:38:10 |          0 |
|       2 | retention_lock              | 2015-07-30 19:38:17 |          0 |
|       3 | hourly_kaltest2.univ-amu.fr | 2015-07-30 19:37:55 |          0 |
|       4 | update_dims_lock            | 2015-07-30 19:38:04 |          0 |
+---------+-----------------------------+---------------------+------------+
4 rows in set (0.00 sec)

MariaDB [(none)]> select * from kalturadw_ds.files where insert_time >=20150730;
+---------+------------------------------------------------------------+-------------+-------------+---------------------+----------+---------------+-------+-----------+--------------+------------+----------+--------------------+--------+
| file_id | file_name                                                  | file_status | prev_status | insert_time         | run_time | transfer_time | lines | err_lines | file_size_kb | process_id | cycle_id | compression_suffix | subdir |
+---------+------------------------------------------------------------+-------------+-------------+---------------------+----------+---------------+-------+-----------+--------------+------------+----------+--------------------+--------+
|       1 | kaltest2.univ-amu.fr-kaltura_apache_access.log-20150730-17 | IN_CYCLE    | NULL        | 2015-07-30 17:50:57 | NULL     | NULL          |  NULL |      NULL |            3 |          1 |        1 | gz                 |        |
|       2 | kaltest2.univ-amu.fr-kaltura_apache_access.log-20150730-19 | IN_CYCLE    | NULL        | 2015-07-30 19:19:01 | NULL     | NULL          |  NULL |      NULL |           14 |          1 |        2 | gz                 |        |
+---------+------------------------------------------------------------+-------------+-------------+---------------------+----------+---------------+-------+-----------+--------------+------------+----------+--------------------+--------+
2 rows in set (0.00 sec)

MariaDB [(none)]> select * from kalturadw.dwh_fact_events where event_date_id >=20150730;
Empty set (0.00 sec)
17

you played one and then ran kaltura-run-dwh.sh? what’s in the logs?

18

I play and run kaltura-run-dwh.sh and in logs no errors

[root@kaltest2 logs]# grep ERROR *
[root@kaltest2 logs]#

19

OK, this is good. Have you played it from an embed code or from KMC? KMC plays are not registered…
What does:
mysql> select * from kalturadw.dwh_fact_events;
return?

20

What’s mean IN CYCLE in the database