I manage a kaltura server (from this week) with a special condition, someone disable /etc/cron.d/kaltura-dwh so, now when the cron try to run normally the load average is too high.
In fact we don’t need stats for old videos, but we need for new plays from right now.
How I can reset stats (from database and log files) for avoiding reprocess all…?
root@Kaltura:~# query “SELECT * FROM kalturadw_ds.locks”
I set update to “0” with
root@Kaltura:~# query "UPDATE kalturadw_ds.locks SET lock_state=0"
I deleted all content of /opt/kaltura/web/logs/ and run scripts on /etc/cron.d/kaltura-dwh (in this version i don’t have /opt/kaltura/bin/kaltura-run-dwh.sh) but, the first script:
And of course in admin/content/manage the stats for video aren’t updated (yes, I put iframe code into a html file for view it outside content/manage, like a normal user)
Does:
mysql> select * from kalturadw_ds.files where insert_time >=%Y%m%d;
show the files processed?
And, in these files, do you see calls for action=collect?
So we should still be seeing errors in /opt/kaltura/dwh/logs/
I would suggest you run /opt/kaltura/bin/kaltura-run-dwh.sh and then revisit the logs. the script removes old logs before starting so we should be able to see new ones from the recent run quite easily.